March 12th, 2024

March 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 versions of the products have been patched. Check out the links for each version for more details.

Azure DevOps Server 2022.1 Patch 3

If you have Azure DevOps Server 2022.1, you should install Azure DevOps Server 2022.1 Patch 3.

Release notes

  • Resolved an issue where the Proxy Server stopped working after installing Patch 2.
  • Fixed a rendering issue on the extension details page affecting languages that were not English.

Verifying Installation

  • Run devops2022.1patch3.exe CheckInstall, devops2022.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 it is not installed.

Azure DevOps Server 2020.1.2 Patch 13

If you have Azure DevOps Server 2020.1.2, you should install Azure DevOps Server 2020.1.2 Patch 13.

Release notes

  • Resolved an issue where the Proxy Server stopped working after installing Patch 12.

Verifying Installation

  • Run devops2020.1.2patch13.exe CheckInstall, devops2020.1.2patch13.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 it is not installed.

Azure DevOps Server 2019.1.2 Patch 8

If you have Azure DevOps Server 2019.1.2, you should install Azure DevOps Server 2019.1.2 Patch 8.

Release notes

  • Resolved an issue where the Proxy Server stopped working after installing Patch 7.

Verifying Installation

  • Run devops2019.1.2patch8.exe CheckInstall, devops2019.1.2patch8.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 it is not installed.

Author

Gloridel Morales
Senior Technical Program Manager

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

9 comments

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

  • João Vitor Cosmo

    Just installed a fresh azuredevops2022.1 from ISO and now im trying to apply the patches, after i've done initial configuration. Can you guys help me?

    devops2022.1patch1:

    Checking SOFTWARE\Microsoft\TeamFoundationServer\19.0 to see if Azure DevOps Server is installed
    Found InstallPath: D:\Azure DevOps Server 2022\
    Found InstallVersion: 19.225.34309.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.
    ...

    Writing "D:\Azure DevOps Server 2022\Version Control Proxy\Web Services\bin\BuildInfo\VssfSdk.xml"
    Starting process D:\Azure DevOps Server 2022\Tools\tfsconfig featureFlags /updateFeatureFlags
    Error running a command: System.ComponentModel.Win32Exception (0x80004005): The specified executable is not a valid application for...

    Read more
  • Tanner Montgomery

    Are patches cumulative? For example, We have Azure DevOps Server 2020 Update 1.2 Patch #5 installed, can we skip to Patch #13?

    • Gloridel MoralesMicrosoft employee Author

      Hi Tanner, patches are cummulative. You can skip previous patches and install Azure DevOps Server 2020 Update 1.2 Patch 13.

  • DarrellW · Edited

    Windows 2019 Datacenter 1809

    Azure DevOps Server Version: Azure DevOps Server 2022.0.1 (AzureDevOpsServer_20230721.2)
    Trying to Apply March Patch: Azure DevOps 2022.1 Patch 3
    When I run the patch I get this error message and the patch is not applied.

    Starting process C:\Program Files\Azure DevOps Server 2022\Tools\tfsconfig featureFlags /updateFeatureFlags
    Error running a command: System.ComponentModel.Win32Exception (0x80004005): The specified executable is not a valid application for this OS platform.
    at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
    at Microsoft.TeamFoundation.AzureDevOpsPatch.ProcessHandler.RunExe(Logger log, String fileName, String arguments)
    at Microsoft.TeamFoundation.AzureDevOpsPatch.Command.Run(Logger log)
    at Microsoft.TeamFoundation.AzureDevOpsPatch.AzureDevOpsPatch.RunCommands(Logger log)

    I have not been able to find anything concerning...

    Read more
      • DarrellW · Edited

        Thanks for this reply. I had been banging my head against the wall trying to figure out why it didn't work.

        https://devblogs.microsoft.com/devops/author/glmorale/
        It appears that upgrading to Azure DevOps Server 2022.1 didn't help. I still get the same error on every patch 1-4 and when I run the devops2022.1patch4.exe CHECKINSTALL it says that Patch 19.225.35005.1 is not installed on this machine.

        But if I go to the Admin Console and look at Version under the Application Tier Summary, it says 19.225.35005.1 (AzureDevOps2022.1)
        and under Data Tier Summary Azure DevOps Database Version is 19.225.35309.2 (AzureDevOps2022.1)

        I don't know what to do to...

        Read more
  • ZeBobo5 Bobo

    What about all ‘Under review’ or ‘On Roadmap’ tickets whithout any updates since so many years on https://developercommunity.visualstudio.com/AzureDevOps ?! Azure DevOps is dead ? Or Microsoft stopped listening to its users ?
    A lot of features are missing or not even completed…

    • Gloridel MoralesMicrosoft employee Author

      Hi, Azure DevOps is not dead and we continue to invest in the product. Usage continues to grow at a healthy rate and we use it internally as the foundation for our DevSecOps toolchain. In fact, Microsoft is our single biggest customer with teams like Azure, Office, and Windows.

    • Tobias Larsson

      I agree – its time to say if 2022 is the end of azure devops server and if so – are there any plans for users that use Azure DevOps Server on-premise?

      Currently going to github enterprise for agile, test and requirements handling with workitems is not good enought. How about all companies that have been adapted safe portfolio planning and such.

      To quiet about new versions – we need to know.