Release Information for Veeam ONE 13.0.1 RTM Patch 0
| KB ID: | 4791 |
| Product: | Veeam ONE | 13 |
| Published: | 2025-11-19 |
| Last Modified: | 2025-11-19 |
This "Patch 0" update for Veeam ONE 13.0.1 is strictly intended for deployments using the RTM release (build 13.0.1.5860).
If Veeam ONE 13.0.1 GA (build 13.0.1.5924) is installed, this update can be ignored as it is not needed. All resolved issues listed in this article were found between RTM and GA releases and were included in the GA release version.
Requirements
This update is intended for existing installations of Veeam ONE v13.0.1 RTM (build 13.0.1.5860) and will update those installations to Veeam ONE v13.0.1 GA (build 13.0.1.5924).
All new Veeam ONE v13.0.1 installations must be performed using the Veeam ONE v13.0.1 GA ISO that is available for download from Veeam My Account portal starting from November 19, 2025.
Please delete the Veeam ONE v13.0.1 RTM ISO to ensure you don't accidentally use it in the future.
Resolved Issues
Resolved Issues
Reporting
- Export Naming Convention Reverted
Based on customer feedback, the export file name format change introduced in version 13 has been reverted to the previous format used in version 12.3.- RTM: YYYY_MM_DD_Report_Name
- GA: Report_Name_YYYY_MM_DD
Installer
- Invalid Product Name in User Account Control Dialog
The Windows User Account Control dialog incorrectly displayed "Veeam Backup & Replication" instead of "Veeam ONE."
This has been corrected.
Alarms
- Unusual Job Duration Alarm Includes Full Job Sessions
The "Unusual Job Duration" alarm was incorrectly analyzing the duration of both Incremental and Full job sessions, resulting in false alarms.
Now, only Incremental job sessions are considered, as intended. The next incremental session after the upgrade will resolve any lingering false alarms.
Data Collection
- Collection Stopped After Upgrade During Agentless Monitoring
In specific upgrade scenarios, collection would stop if Veeam Backup & Replication 12.3 was monitored agentless and credentials for agent setup were not set after upgrading Veeam ONE to 13.0.1. Even after updating Veeam Backup & Replication to version 13.0.1 and accepting the new certificates, the collection would not resume until the Veeam Analytics Service was installed.
This process has been streamlined, and collection now resumes as expected after the upgrade steps are completed.
Deployment Information
Prerequisites and Recommendations
- Ensure you are running Veeam ONE 13.0.1 RTM (build 13.0.1.5860).
- 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 Monitor Client sessions. Use Task Manager to verify no Veeam ONE or Veeam ONE Monitor client processes are running.
- Run the update with local administrator privileges.
- Allow the .msp installers to stop and start Veeam ONE services during patching.
Updating
To update an existing Veeam ONE v13.0.1 RTM deployment to the GA build using Patch 0, follow these steps:
- Copy the .zip to the Veeam ONE server and extract it to a local folder, for example C:\Temp\VONE1301_GA\
- Verify that the .msp files listed in the Download Information section are present.
- Close any running Veeam ONE Monitor Client instances.
- Execute all four .msp files. You can apply them in any order.
- Right-click each .msp and select Install.
- Follow on-screen prompts.
Services will be stopped and started automatically
Download Information
This "Patch 0" update is strictly intended only for deployments using the RTM release (build 13.0.1.5860).
If Veeam ONE 13.0.1 GA (build 13.0.1.5924) is installed, this update can be ignored as it is not needed. All resolved issues listed in this article were found between RTM and GA releases and were included in the GA release version.
Contents:
- VeeamONE.Agent.x64.msp
- VeeamONE.Monitor.Client.x64_13.0.1.5924.msp
- VeeamONE.Monitor.Server.x64_13.0.1.5924.msp
- VeeamONE.Reporter.Server.x64_13.0.1.5924.msp
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.