[German]A short note or addendum for users of Windows 11 24H2 who rely on Veeam Backup & Recovery. Rudi has already pointed out to me on March 22, 2025 that the restore functionality of Veeam backups via Veeam Recovery in Windows 11 no longer works. Windows updates from February 2025 seem to be to blame. Veeam has confirmed this and is working with Microsoft to resolve the issue.
Advertising
A short note from a reader
It was a short email from blog reader Rudi (thanks for that), who wrote me that he had some information that is relevant for the readership of Borncity and could save admins a lot of search work. It seems that the restore functionality of Veeam Backups / Restore via Veeam Recovery after installing Windows Updates no longer works in Windows 11.
Discussion in communities
Rudi had sent me a link to the Veeam forum post Recovery Media does not work (v6.3), where an affected person writes that since the upgrade (and reinstallation) of Veeam Agent for Microsoft Windows 6.3.0.177, he can no longer use the media to restore an image if the backup files are located on a Veeam backup server. The user receives an error message.
The Veeam Community article Veeam bootable media cannot connect to backup server also discusses a recovery problem with media created under Windows 11 24H2 IoT Enterprise LTSC.
Bestätigung durch Veeam, untersucht mit Microsoft
The reader told me that the problem has been confirmed by Veeam since Friday, March 21, 2025, and that they have opened a support case with Microsoft. I came across the following comment in the support articles linked above.
Advertising
Veeam has published the support article KB4726: Windows 11 24H2 Recovery Media Issue (via). It states that when restoring from a Veeam recovery media created from a computer running Windows 11 24H2 (Build 26100.3194) or later, the connection to the Veeam Backup Server or a network share fails with errors. The errors in question are documented by Veeam in the article.
The underlying cause of this problem is currently unknown and is being investigated by Veeam and Microsoft. However, it appears that this error is related to a change within the Windows 11 24H2 February update (KB5051987). However, I have not yet found anything in the Known Issues of the support article
Customers affected by this issue are advised to work around this issue by using Veeam recovery media created from a computer running an older build of Windows 11, build 26100.3037 or lower.
Advertising
