6 comments

Join the discussion.

• 

  Aeon Zeon December 12, 2025 · Edited 0

  Collapse this comment Copy link

  Greetings.

  Previously, we’ve had:

  • Azure DevOps Server 2019.
  • Azure DevOps Server 2020.
  • Azure DevOps Server 2022.

  Is this latest new release supposed to be:

  • Azure DevOps Server 2025?

  If “yes”, then I’d like to report a bug, that this release is missing “2025” from the product title.

  If “no”, then could you inform us when can we expect the “Azure DevOps Server 2025” release, please?

  Thank you.

  Best regards.

• 

  Gloridel Morales Author 1 day ago 0

  Collapse this comment Copy link

  Hi Stephen, you can find the Build number in the Azure DevOps Server build documentation

• 

  Stephen Barnes 1 day ago 0

  Collapse this comment Copy link

  What is the actual version number for this release, and why doesn’t it get a versioning label in the release documentation?

• 

  Luke Mosley 1 day ago · Edited 0

  Collapse this comment Copy link

  Hi there appears to be a bug in this version with the newer version of CodeSearch provided.
  When running Configure-TFSSearch.ps1 and installing code search on a separate Server/Tier it gives a error as below at the high level and the service never starts.

  <code>

  If you dig into the elastic logs a bit further this is the actual error. It appears somewhere is setting instead of when running?

  <code>

  Can this be looked at and fixed/patched please.
  Thanks

  Read more

  Hi there appears to be a bug in this version with the newer version of CodeSearch provided.
  When running Configure-TFSSearch.ps1 and installing code search on a separate Server/Tier it gives a error as below at the high level and the service never starts.

  [2025-12-11 16:54:28] [error] ( prunsrv.c:1003) [ 7112] Failed to start service 'elasticsearch-service-x64'.
  [2025-12-11 16:54:28] [info]  ( prunsrv.c:1011) [ 7112] Finished starting service 'elasticsearch-service-x64', returning 0.
  [2025-12-11 16:54:28] [error] ( prunsrv.c:2077) [ 7112] Apache Commons Daemon procrun failed with exit value: 5 (failed to start service).
  
  Failed to start service.
  ERROR: Failed starting 'elasticsearch-service-x64' service, with exit code 5

  If you dig into the elastic logs a bit further this is the actual error. It appears somewhere is setting --quiet instead of --silent when running?

  Apache Commons Daemon procrun stderr initialized.
  Starts and stops the Elasticsearch server process for a Windows Service
  
  Option             Description        
  ------             -----------        
  -E   Configure a setting
  -h, --help         Show help          
  -s, --silent       Show minimal output
  -v, --verbose      Show verbose output
  ERROR: quiet is not a recognized option

  Can this be looked at and fixed/patched please.
  Thanks

  Read less
• 

  Liran Dobrish 2 days ago 0

  Collapse this comment Copy link

  Hello Gloridel

  Does this version include support for VS2026 (vsbuild, vstest, mstest) in the pipelines?
  and what about “Automate work item state transitions” which you stated that it will be added to the release notes (still not there….)

  • 

    Gloridel Morales Author 1 day ago · Edited 0

    Collapse this comment Copy link

    Hi Liran, this version does not support VS2026 (vsbuild, vstest, mstest) in pipelines. We plan to add support for on-prem once it is fully deployed in the hosted version of the product.
    The release notes for Boards were updated to remove Automate Work Item State Transitions since this feature is not included in the current release.