#1 Global Leader in Data Resilience

Release Information for Veeam ONE 13 Patch 1

KB ID: 4776
Product: Veeam ONE | 13
Published: 2025-09-24
Last Modified: 2025-10-03
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Prerequisites and Recommendations

  • Ensure you are running Veeam ONE 13.0.0.5630.
  • Perform a full backup of the Veeam ONE database.
  • If the Veeam ONE server is virtual, create a VM snapshot or another rollback point.
  • Close all Veeam ONE Client sessions. Use Task Manager to verify that no Veeam ONE Client processes (Monitor.exe) are running.
  • Run the update with local administrator privileges.
  • Each of the .msp installers will restart the Veeam ONE services during patching; no manual service restarts or system reboot are needed.

Resolved Issues

  • High CPU usage in Veeam Analytics Service: Fixed an issue in Veeam.One.Agent.DataCollectionService that continued collecting after the historical collection completed. This behavior also caused higher CPU usage in dependent satellite services, including *.AgentUpdaterService, *.LogAnalyzer, and *.RemedyService.
  • Unable to enable Veeam Backup & Replication Servers Analytics in Web Client: Fixed an issue where data sources added using the Veeam Analytics Service offline package could not be enabled via Veeam ONE Web Client..
  • Internal Server Error on Alarms Overview after upgrade: Addressed an error condition when locations were configured for Platform Health Anomalies after upgrading from v12.x.

Download Information

Download Veeam ONE 13 P1

Filename: VeeamONE_13.0.0.5761_20251003.zip

MD5: 7B50480DEC67282CBBD50DC510E20FFC
SHA1: 148C20776E10C71863E4FDA984E98D8EF5EB99D2

Contents:

  • VeeamONE.Agent.x64.msp
  • VeeamONE.Reporter.Server.x64_13.0.0.5761.msp
  • VeeamOneMonitorCln_x64_13.0.0.5761.msp
  • VeeamOneMonitorSrv_x64_13.0.0.5761.msp

Deployment Information

  1. Copy the .zip to the Veeam ONE server and extract it to a local folder, for example, C:\Temp\
  2. Verify that the four .msp files listed above are present.
  3. Close any running Veeam ONE Monitor Client instances.
  4. Apply all four .msp files.
    They can be applied in any order. Veeam ONE services will be restarted automatically.

Note: The Veeam Analytics Service automatically pushes the new package to the Veeam Backup Server. The default check for updates can take up to 60 minutes.

Version Listing in Application
After installing this patch, only the version listed in the Veeam ONE Web Client will be updated. The version listed within the Veeam ONE Client will still list 13.0.0.5630.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.