Since upgrading (and fresh installs) of Veeam Agent for Microsoft Windows 6.3.0.177, I can no longer use the media to restore an image if the backup files are on a Veeam backup server. I get the following errors:
It doesn't matter if I use the IP address or the backup server's name. I get this same error, regardless.
This error is thrown if you try to edit any settings and try to connect, a second time. The only way to avoid this error is to hard reset the PC. Just exiting to main menu and re-entering the Bare Metal Restore option does not get rid of this error.
If you select Restart or Shutdown, you will get the error message depicted in the image below...
NOTES:
These issues do NOT occur if I use media (ISO's) created with older versions of Veeam Agent for Microsoft Windows.
Backups are stored in a Veeam repository.
The PC's and Veeam servers are all on the same, local network.
I get the same results when I try to access the backups directly via network share.
The login credentials are correct.
I get the same results with credentials and recovery tokens.
These issues occur with every ISO that is created with Veeam Agent for Microsoft Windows 6.3.0.177.
I get the same results with Secure Boot enabled and disabled on the PC I'm restoring to.
I get the same results with fresh installs of Veeam Agent for Microsoft Windows 6.3.0.177 and with PC's that have been upgraded from a previous version of Veeam Agent for Microsoft Windows.
I get the same results if I try to PXE boot and when using a USB thumb drive on the PC.
I get the same results regardless of whether the boot USB thumb drive was created by the Veeam media creation tool or if I use a third-party tool to create a bootable USB drive using an ISO file that was created by the Veeam media creation tool.
I get the same results if I connect the Ethernet cable to the on-board Ethernet port or if I try to use a different NIC including USB-to-Ethernet adapters.
Even though these issues occur, I can always go back to the Tools -> Command Prompt, run the ipconfig command and see that the PC does have an IP address.
I can ping both the name and IP address of the Veeam backup server.
I get the same results if I set a static IP address on the PC.
If I copy the backup files (from the repository) onto an external USB drive, connect it to the PC that I want to restore to, boot the PC using the ISO created by Veeam Agent for Microsoft Windows 6.3.0.177, select local storage, I can perform the bare metal restore.
I have tested using two different PC's and a laptop. I get the same results on all of them.
Case #07639014 - NFR license so case will probably be closed without any support.
I forgot to include that B&R is v12.3.0.310 and it's a Windows Server 2022 VM running on a Dell R720XD server with ESXi v8x being the physical server's OS.
All PC's are various models made by Dell.
All ISO's were created on Windows 11 Enterprise 24H2 PC's/laptops.
Hi, this is not a support forum for environment-specific issues. Kindly don't just ignore the forum rules displayed when you click New Topic with your future posts in this community. Please review the forum rules for further information on the purpose of this community. Thank you for understanding!
Gostev wrote: ↑Mar 21, 2025 7:02 pm
Our Customer Support has confirmed an issue, which I understood is likely caused by a recent Windows update.
They plan to open a case with Microsoft and create a support KB article about it.
This thread is therefore reopened to enable further exchange as the issue is being resolved.
As a complete and slightly irrelevant side-note. In Windows 11 24H2 the old RDP client (mstsc.exe) doesn't work with Windows Server 2012 R2 or older. It will connect, but after a minute it will disconnect to automatically re-connect again and this goes on and on and on and... Software using RDP are most likely affected as well (Royal TS for instance has this problem in version 7). Solution is to use the RDP client from Microsoft Store.
Same issue here with the Veeam Agent for Windows - Free edition on a Windows 11 24H2 laptop that includes the March 2025 Microsoft security updates.
Creating the Veeam Recovery media (without integration of the network config and drivers) for this laptop on a Windows 10 22H2 desktop where the March 2025 Microsoft security updates were applied does work.
You can create it on any machine running an earlier Windows 11 version, or remove the offending Microsoft update temporarily from your existing machine and create a Recovery Media on it.
The bug is on Microsoft to fix, we've opened a case with Microsoft and demonstrated the issue without Veeam in the picture.
It isn't mentioned in this discussion or in the workarounds on the KB but does recovery still work if the required backup files are copied to a local USB memory stick/hard drive?
May not be practical for everyone but useful for some.
Good news, it looks like a recent Windows update has addressed the issue in both Windows 11 24H2 and Server 2025 24H2.
Most likely this update, even if it's not documented in the release notes > May 13, 2025—KB5058411 (OS Build 26100.4061)
