Back

Veeam Software Group GmbH
Patches for Veeam Agent x64
Windows
7 patches available
A comprehensive backup and recovery solution for Windows-based servers, workstations and cloud instancesnVeeam Software is a privately held US-based information technology company owned by Insight Partners that develops backup, disaster recovery and modern data protection software for virtual, physical and multi-cloud infrastructures.
Veeam Agent x64 Version 6.3.0.177
Release Date
12/3/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes

Refer-$$$https://helpcenter.veeam.com/rn/veeam_agent_windows_6_3_release_notes.html
Veeam Agent x64 Version 6.2.0.121
Release Date
8/28/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes

Refer-$$$https://helpcenter.veeam.com/rn/veeam_agent_windows_6_2_release_notes.html
Veeam Agent x64 Version 6.1.2.134
Release Date
5/21/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes

Refer-$$$https://www.veeam.com/veeam_agent_windows_6_1_release_notes_rn.pdf
Veeam Agent x64 Version 6.1.0.349
Release Date
12/5/2023
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes

Refer-$$$https://www.veeam.com/veeam_agent_windows_6_1_release_notes_rn.pdf
Veeam Agent x64 Version 6.0.2.1090
Release Date
4/13/2023
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes

Known Issues$$$General$$$• Certain antivirus applications may crash the operating system when file level recovery is initiated. To $$$prevent this from happening; exclude Veeam Agent for Microsoft Windows service and application $$$folders from real-time antivirus monitoring.$$$Backup$$$• Standalone full backup functionality is temporarily blocked for backup jobs targeted at a Veeam backup$$$repository.$$$• exFAT file system is no longer supported as a backup target; please change your backup job settings $$$accordingly.$$$• Backup job may fail with the “Cannot create a shadow copy of the volumes containing writers data. VSS $$$asynchronous operation is not completed“ error if file-level recovery is being performed at the same $$$time.$$$• Backup job cannot wake a computer up from sleep or detect missed backup on mobile devices in $$$Connected Standby power saving mode.$$$• Backup job cannot wake a computer up from sleep to perform a retry cycle if “Sleep after” power saving$$$scheme timeout is set to less than 10 minutes. $$$• Encrypted files and folders are skipped during file level backup with the “Access denied” error. To work $$$around the issue; use volume-level backup.$$$• Prior to storing incremental restore points to the backup cache at least one successful job run to the $$$primary repository is required.$$$• Backup job targeted at the SMB share with the path that contains non-Latin characters cannot create a $$$backup correctly on machines running Microsoft Windows 7 SP1; Microsoft Windows Server 2008 R2 SP1 $$$and Microsoft Windows Server 2012 OSes.$$$• Import and export of backup job configuration is not supported for backup jobs targeted directly at $$$object storage.$$$• Backup job targeted at the Wasabi object storage in the eu-central-1 region and throttled to 15 MB/s$$$may have occasional connection drops or reconnections.$$$• If a backup job is targeted at the Amazon S3 object storage and the selected bucket resides in US or $$$Canada; make sure that the bucket name does not contain the dot character (.). Otherwise; the backup $$$job will fail.$$$Restore$$$• “File is ready for archiving” and “Allow this file to have content indexed in addition to file properties” $$$advanced file and folder attributes are enabled on files recovered with the file level recovery.$$$• Launching file level recovery by double clicking a backup file residing in a shared folder location may fail $$$to validate user credentials if this shared folder is also mapped as a network drive.$$$5 | Veeam Agent for Microsoft Windows 6.0.2.1090 | Release Notes 13042023$$$• Resizing volume during the recovery of Microsoft Windows Server 2012 may fail with access denied $$$error.$$$Changed Block Tracking Driver$$$• Changed Block Tracking driver for backup requires 64-bit Microsoft Windows 1803 or later operating $$$system.$$$• Changed Block Tracking driver for file-level backup tracks files of 50 MB and larger. Smaller files are not $$$tracked by the driver and are processed regularly without Changed Block Tracking driver.$$$• Changed Block Tracking driver is unable to track the volume changes made by non-Windows operating $$$systems while the original Windows operating system with CBT driver was offline. Consider using MFT $$$changed-block tracking with such setup or perform an active full after the changes were made for $$$volumes.$$$Veeam Backup & Replication Integration$$$• Size estimation may not work correctly when performing backup to a scale-out repository; deduplication $$$repository or repository with ReFS configuration.$$$• Restore to the original location via Veeam Enterprise Manager may not work if the original computer $$$and Enterprise Manager server are in different domains.$$$Setup$$$• Certain antivirus applications may cause various issues during the product setup. To work around the $$$issue; disable the antivirus for the duration of the product installation.$$$• Microsoft Smart App Control feature must be disabled on the machine as otherwise the installation $$$process will be bl
Veeam Agent x64 Version 5.0.3.4708
Release Date
3/12/2022
Bug Fix?
Yes
Minor Release?
No
Patch Notes

Known Issues$$$General$$$• Certain antivirus applications may crash the operating system when file level recovery is initiated. To $$$prevent this from happening; exclude Veeam Agent for Microsoft Windows service and application $$$folders from real-time antivirus monitoring.$$$Backup$$$• Backup job may fail with the “Cannot create a shadow copy of the volumes containing writers data. VSS $$$asynchronous operation is not completed“ error if file-level recovery is being performed at the same $$$time.$$$• Backup job cannot wake a computer up from sleep or detect missed backup on mobile devices in $$$Connected Standby power saving mode.$$$• Backup job cannot wake a computer up from sleep to perform a retry cycle if “Sleep after” power saving $$$scheme timeout is set to less than 10 minutes. $$$• Encrypted files and folders are skipped during file level backup with the “Access denied” error. To work $$$around the issue; use volume-level backup.$$$• Prior to storing incremental restore points to the backup cache at least one successful job run to the $$$primary repository is required.$$$• Backup job targeted at the SMB share with the path that contains non-Latin characters cannot create a $$$backup correctly on machines running Microsoft Windows Server 2012.$$$• Backup job does not support application-aware processing scrips with the & symbol.$$$• If a backup job is targeted at the storage device with the exFAT file system and the protected computer $$$runs Microsoft Windows 10 or Microsoft Windows Server 2019 and later; the backup data corruption$$$may be caused by the exFAT file system issue.$$$Restore$$$• “File is ready for archiving” and “Allow this file to have content indexed in addition to file properties” $$$advanced file and folder attributes are enabled on files recovered with the file level recovery.$$$• Launching file level recovery by double clicking a backup file residing in a shared folder location may fail $$$to validate user credentials if this shared folder is also mapped as a network drive.$$$• Resizing volume during the recovery of Microsoft Windows Server 2012 may fail with access denied $$$error.$$$Changed Block Tracking Driver$$$• Changed Block Tracking driver is unable track the volume changes made by non-Windows operating $$$systems while the original Windows operating system with CBT driver was offline. Consider using MFT $$$changed-block tracking with such setup or perform an active full after the changes were made for $$$volumes
Interested in automating patching for Adobe Acrobat?