December patches for Azure DevOps Server

Gloridel Morales

December 15th, 202141 1

This month, we are releasing fixes that impact our self-hosted product, Azure DevOps Server.

The following will be fixed with this patch:

  • Fix work item macro for queries with “Contains Words”. Previously, queries were returning incorrect results for values that contained a line break.
  • Increase limits for Maven package version character length.
  • Localization issue for custom work items layout states.
  • Localization issue in email notification template.
  • Issue with console logs getting truncated when there are multiple identical links in a row.
  • Issue with NOTSAMEAS rules evaluation when multiple NOTSAMEAS rules were defined for a field.

Azure DevOps Server 2020.1.1 Patch 3

If you have Azure DevOps Server 2020.1.1, you should install Azure DevOps Server 2020.1.1 Patch 3. Check out the release notes for more details.

Verifying Installation

  • Option 1: Run devops2020.1.1patch3.exe CheckInstall, devops2020.1.1patch3.exe is the file that is downloaded from the link above. The output of the command will either say that the patch has been installed, or that is not installed.

  • Option 2: Check the version of the following file: [INSTALL_DIR]\Azure DevOps Server 2020\Application Tier\bin\Microsoft.Teamfoundation.Framework.Server.dll. Azure DevOps Server 2020.1.1 is installed to c:\Program Files\Azure DevOps Server 2020 by default. After installing Azure DevOps Server 2020.1.1 Patch 3, the version will be 18.181.32011.3.

Azure DevOps Server 2020.0.1 Patch 8

If you have Azure DevOps Server 2020.0.1, you should install Azure DevOps Server 2020.0.1 Patch 8. Check out the release notes for more details.

Verifying Installation

  • Option 1: Run devops2020.0.1patch8.exe CheckInstall, devops2020.0.1patch8.exe is the file that is downloaded from the link above. The output of the command will either say that the patch has been installed, or that is not installed.

  • Option 2: Check the version of the following file: [INSTALL_DIR]\Azure DevOps Server 2020\Application Tier\bin\Microsoft.Teamfoundation.Framework.Server.dll. Azure DevOps Server 2020.0.1 is installed to c:\Program Files\Azure DevOps Server 2020 by default. After installing Azure DevOps Server 2020.0.1 Patch 8, the version will be 18.170.32011.2.

Azure DevOps Server 2019.1.1 Patch 12

If you have Azure DevOps Server 2019 Update 1.1, you should install Azure DevOps Server 2019 Update 1.1 Patch 12. Check out the release notes for more details

Verifying Installation

  • Option 1: Run devops2019.1.1patch12.exe CheckInstall. devops2019.1.1patch12.exe is the file that is downloaded from the link above. The output of the command will either say that the patch has been installed, or that is not installed.

  • Option 2: Check the version of the following file: [INSTALL_DIR]\Azure DevOps Server 2019\Application Tier\Web Services\bin\Microsoft.VisualStudio.Services.Feed.Server.dll. Azure DevOps Server 2019 is installed to c:\Program Files\Azure DevOps Server 2019 by default. After installing Azure DevOps Server 2019.1.1 Patch 12, the version will be 17.153.32011.1.

Gloridel Morales Senior Technical Program Manager, Azure DevOps

Read next

41 comments

Discussion is closed. Login to edit/delete existing comments.

  • nikita egorov 0

    Does your team have any news about Azure DevOps Server 2022?

    • Gloridel MoralesMicrosoft employee 0

      Hi Nikita, we plan to release on Q1 of 2022.

  • Daniel Steiner 0

    is a fix for Log4j (ElasticSearch for Code Search functionality) included or will there be a another patch in the next 2-3 days ?

  • Trent Bielejeski 0

    Am trying to install the December patch, we have 18.181.31527.1 but the patch keeps saying “This patch does not apply to Azure DevOps Server version 18.181.31527.1.”

    • Kevin Trace 0

      I am getting the same issue. Patch output is the following:

      Checking SOFTWARE\Microsoft\TeamFoundationServer\18.0 to see if Azure DevOps Server is installed
Found InstallPath: D:\Azure DevOps Server 2020\
Found InstallVersion: 18.181.31527.1
Could not find Patch version in registry, no patches installed.
The Application Tier is configured.
The Search Tier is configured.
The Proxy Tier is not configured.
This patch does not apply to Azure DevOps Server version 18.181.31527.1.
        • Gloridel MoralesMicrosoft employee 0

          Thank you Daniel for providing guidance 🙂

          • dewo web 0

            We, dewoweb.com are one of the leading third-party technical assistance providers for web design. dewoweb All the images, trademarks, and logos are used for education purposes only. We provide assistance only at customers’ requests.

            For Further Information connect with Us:
            Call Us:+98-21-7105-7477
            write Us:info@dewoweb.com
            Visit Us: https://www.dewoweb.com/

      • Gloridel MoralesMicrosoft employee 0

        Hi Kevin, like Daniel mention it seems like your install is being impacted by an issue after upgrading from 2020.1 patch 2 to 2020.1.1. The Azure DevOps Server 2020.1.1 blog post has more details.

        • Kevin Trace 0

          Thank you. Re-applying 2020.1.1 seems to have worked.

    • Gloridel MoralesMicrosoft employee 0

      Hi Trent, it seems like your install is being impacted by an issue after upgrading from 2020.1 patch 2 to 2020.1.1. The Azure DevOps Server 2020.1.1 blog post has more details.

      • Trent Bielejeski 0

        Thanks – I updated devops server again and that seems to have resolved it.

        Thank you

  • Kevin Trace 0

    Does this patch add support for pipeline builds using Visual Studio 2022? We keep getting the following error after we upgraded our build to .NET6

    ##[warning]Visual Studio version '17.0' not found. Falling back to version '16.0'.

    I upgraded the build agent to v2.195.2 but it did not help. We are using the VSBuild@1 task and have tried passing ‘17.0’ and ‘latest’ but both still run with VS2019.

    Both VisualStudio_17.0 and MSBuild_17.0 show up under the agent capabilities tab and are pointing to VS2022. The yaml task for VSBuild@1 is showing as 1.166.2 in the logs. Does this need to be updated?

      • Gloridel MoralesMicrosoft employee 0

        Thank you, Kevin, for sharing your findings and providing guidance.

        • Tore Østergaard Jensen (TORE) 0

          Hi Gloridel

          We are facing the same problem and wondering why the MSBuild, VSBuild and VSTest build tasks is created so that they look for a hardcoded set of Visual studio version that were know at compile time, instead of relying on vswhere to find either a specifically specified version or latest. That would work in cases where no breaking changes have been made.

  • 辛直陽 Cyang San 0

    Hi everyone, i was facing a problem that may be hard for me.

    I can’t solve the “Security Updates for Microsoft Team Foundation Server and zure DevOps Server (April 2021)”
    I had installed the patch 11 and double checked the “…..Feed.Server.dll” was version 17.153.31707.1
    Azure Resource Group Deployment V2 also been uplaoded (I guess so)
    Any else i need to install or how can i check?

      • 辛直陽 Cyang San 0

        Hi Daniel, is the issue following the blog post that you share also impacted version 2019.1.1?? Because i’m using version 2019.1.1 in a intranet environment. Thanks.

    • Alireza Abdollahi 0

      After updating to Patch 8 for AzureDevOps 2020.0.1 we are no longer able to receive email notifications when using @funigma in our user stories and bugs.
      anyone else having this issue or found a way to resolve

  • Chris Waldschmidt 0

    Log4j/ElasticSearch Vulnerability in Microsoft Visual Studio Team Foundation Server

    Gloridel,

    Sorry if this is a repetitive inquiry. We use Microsoft Visual Studio Team Foundation Server Version 16.131.28601.4 which had the vulnerable Log4j library located in the directory C:\Program Files\Microsoft Team Foundation Server 2018\Search\ES\elasticsearchv5\lib. We have manually patched the vulnerability. As a point of clarification, does Microsoft intend to publish an update to patch on-premises versions of TFS?

  • Joe Brun 0

    After updating to Patch 8 for AzureDevOps 2020.0.1 we are no longer able to receive email notifications when using @mentions in our user stories and bugs.
    anyone else having this issue or found a way to resolve?

  • Linh Le Ngoc 0

    Hi, i cannot update my Azure DevOps server, the log said: This patch does not apply to Azure DevOps Server version 18.181.31230.2

    Microsoft (R) AzureDevOpsPatch - Azure DevOps Server update tool - version 18.170.32011.2
Copyright (c) Microsoft Corporation.  All rights reserved.

Checking SOFTWARE\Microsoft\TeamFoundationServer\18.0 to see if Azure DevOps Server is installed
Found InstallPath: C:\Program Files\Azure DevOps Server 2020\
Found InstallVersion: 18.181.31230.2
Could not find Patch version in registry, no patches installed.
The Application Tier is configured.
The Search Tier is configured.
The Proxy Tier is not configured.
This patch does not apply to Azure DevOps Server version 18.181.31230.2.

    I tried with all patches from this site https://docs.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2020?view=azure-devops#azure-devops-server-2020-patch-1-date-december-8-2020, and i got the same issue. Can you tell me what should I do?

    • Gloridel MoralesMicrosoft employee 0

      Hi Linh. Based on the version number, you have Azure DevOps Server 2020.1. You should install Azure DevOps Server 2020.1.1 from our download page and then apply the patch.

    • Gloridel MoralesMicrosoft employee 0

      Hi Kevin, we plan to fix @mentions email notifications with our next patch.

      • Krisztián Melczer 0

        Hi Gloridel,

        Is there any public target date for this fix? We’re also struggling due to this problem…

  • Web Mehr 0

    Dear Gloridel, I am very happy with your posts on this blog. All of your posts are informative and come from experience. Good lock.

    طراحی سایت

Feedback usabilla icon