December 15th, 2021

December patches for Azure DevOps Server

Gloridel Morales

Senior Technical Program Manager

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.

Author

Gloridel Morales

Senior Technical Program Manager

Gloridel is a Senior Technical Program Manager on the Azure DevOps team.

41 comments

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

Sort by :

Newest

Newest Popular Oldest

Amresh Mishra February 5, 2022 0

I am facing 0x0 0x0 Error on my windows Laptop since Windows 11 Launch. I want to Upgrade my PC.
Juan Garcia January 21, 2022 0

HI Gloridel,

I am encountering an issue with attempting to apply the Azure DevOps Server 2020 Update 1, Patch 3. While my issue is similar to previously reported; we are current running Azure DevOps Server 2020 Update 1 Patch 1, where others may not have been. Patch 3 is reporting that it does not apply to our environment.
The other posts indicate to re-apply Azure DevOps server 2020.1.1; but are concerned it will remove...
Read more
HI Gloridel,

I am encountering an issue with attempting to apply the Azure DevOps Server 2020 Update 1, Patch 3. While my issue is similar to previously reported; we are current running Azure DevOps Server 2020 Update 1 Patch 1, where others may not have been. Patch 3 is reporting that it does not apply to our environment.
The other posts indicate to re-apply Azure DevOps server 2020.1.1; but are concerned it will remove Patch 1.

Microsoft.TeamFoundation.Framework.Server.dll under the install path does show as version: 18.181.31402.2

Patch version information below.
= = = = =
Microsoft (R) AzureDevOpsPatch – Azure DevOps Server update tool – version 18.181.32011.3
Copyright (c) Microsoft Corporation. All rights reserved.
Logging going to ‘C:\ProgramData\Microsoft\Azure DevOps\Server Configuration\Logs\Patch_2022-01-21_13-19-10.log’
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
Latest patch installed on machine is version 18.181.31402.2
Patch 18.181.32011.3 is the same or later version as the patch installed on machine, patch can be 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.
= = = = =
Thanks for any assistance.

Read less
Henrik E January 13, 2022 · Edited 0

Are there any details on what features will be included in Azure DevOps Server 2022? I feel like that the Azure DevOps Feature timeline is pretty much useless for us who use the server version since all the features availability information concerning the server version is only mentioned as "Future", "TBD" or "N/A".

This means that I can not communicate with our users in our organization when for example the new and improved Delivery Plans will...
Read more
Are there any details on what features will be included in Azure DevOps Server 2022? I feel like that the Azure DevOps Feature timeline is pretty much useless for us who use the server version since all the features availability information concerning the server version is only mentioned as “Future”, “TBD” or “N/A”.

This means that I can not communicate with our users in our organization when for example the new and improved Delivery Plans will be available for them. I just have no idea, and also me and my team can not plan for when we are going to upgrade.

Please, do improve your communications regarding the new feature availability for the Azure DevOps Server version. The lack of information makes me feel like that the server version might have been forgotten about and perhaps might be abandoned soon. It also seems to me that Microsoft’s focus on Azure DevOps Server is only including bug fixes and security fixes – which of course is great – but it is not the only thing that we want. We also need new features, and our users are really requesting these – for example Delivery Plans.

Read less
- Tore Østergaard Jensen (TORE) January 21, 2022 · Edited 0
  
  Hi Henrik
  
  I agree with you!
  
  Another example is Auditing which will be GA soon on the service, but is currently not planned for the Server edition:
  https://devblogs.microsoft.com/devops/auditing-coming-to-general-availability-ga-early-2022/#comment-2869
  
  Yet another example is when you want to build using Visual Studio 2022, released 2½ month ago, then you have to update inbox build tasks:
  https://devblogs.microsoft.com/devops/december-patches-for-azure-devops-server/#comment-2973
Web Mehr January 10, 2022 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.

طراحی سایت
Kevin Trace January 3, 2022 0

Hi Gloridel,

Any update on this bug? https://developercommunity.visualstudio.com/t/Use-mention-in-work-items-no-working-af/1615815

I was about to apply the update but just saw people having this issue which is a show stopper.
- Gloridel Morales Author January 6, 2022 0
  
  Hi Kevin, we plan to fix @mentions email notifications with our next patch.
  - Krisztián Melczer January 13, 2022 · Edited 0
    
    Hi Gloridel,
    
    Is there any public target date for this fix? We’re also struggling due to this problem…
Linh Le Ngoc January 2, 2022 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

<code>

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?

Read more
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?
Read less
- Gloridel Morales Author January 6, 2022 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.
Joe Brun December 21, 2021 · Edited 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?
- Gloridel Morales Author January 6, 2022 0
  
  Hi Joe, we apologize for the impact this may have caused. We have a fix for the issue and plan to release with the next patch.
  Developer Community Ticket
- Michael Hirsch December 21, 2021 0
  
  Yes, we have the same problem since installation of 2020.1.1 Patch 3. This is also discussed here:
  https://developercommunity.visualstudio.com/t/Use-mention-in-work-items-no-working-af/1615815
  - Gloridel Morales Author January 6, 2022 0
    
    Hi Michael, we apologize for the impact this may have caused. We have a fix for the issue and plan to release with the next patch.
    Developer Community Ticket
Chris Waldschmidt December 17, 2021 · Edited 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?

Read more
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?

Read less
- Gloridel Morales Author January 6, 2022 · Edited 0
  
  Hi Chris, please see the guidance provided in the Azure DevOps (and Azure DevOps Server) and the log4j vulnerability.
  
  We will continue to post updates in the blog as we learn more.
辛直陽 Cyang San December 15, 2021 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?
- Alireza Abdollahi December 27, 2021 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
  - Raphael Schweizer January 19, 2022 · Edited 0
    
    https://developercommunity.visualstudio.com/t/Use-mention-in-work-items-no-working-af/1615815#T-N1637342
- Daniel Steiner December 16, 2021 0
  
  Hi San, it looks like you are being impacted by the issue reported in this blog post https://devblogs.microsoft.com/devops/azure-devops-server-2020-1-1-rtw-now-available/
  The initial release of 2020.1.1 was buggy and had been replaced after a few days and you should reinstall the new version again before applying any patches.
  - 辛直陽 Cyang San December 19, 2021 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.
Kevin Trace December 15, 2021 · Edited 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

<code>

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...
Read more
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?
Read less
- Kevin Trace December 15, 2021 0
  
  If anyone else has this issue I followed the instructions mentioned in the link below and it seems to be working.
  https://github.com/microsoft/azure-pipelines-agent/issues/3567#issuecomment-947764654
  
  After manually updating the VSBuild@1 task it shows as 1.192.3 in the logs and uses VS2022.
  - Gloridel Morales Author December 16, 2021 0
    
    Thank you, Kevin, for sharing your findings and providing guidance.
  - Tore Østergaard Jensen (TORE) December 20, 2021 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.