For organizations planning recovery operations with Veeam in a Windows 11 environment, creating recovery media on computers running Windows 11 builds earlier than 26100.3194 is advisable until a permanent solution is available. Veeam advises customers to use Recovery Media generated on systems running older Windows 11 builds (26100.3037 or earlier) as a temporary solution. While Microsoft and Veeam are still investigating the exact technical mechanism, the issue seems to affect the Windows Recovery Environment (Windows RE) on which Veeam Recovery Media is built. The problem, linked to Microsoft’s February update (KB5051987), is preventing organizations from performing data recovery operations, potentially compromising business continuity plans for affected enterprises. Users report they can ping both the name and IP address of their Veeam backup servers from the recovery environment’s command prompt, yet the Veeam recovery application itself cannot establish a proper connection. For enterprises depending on timely data restoration capabilities, this issue represents a serious risk to disaster recovery plans and compliance requirements. This workaround acknowledges that recovery media created on machines with earlier Windows 11 versions does not exhibit connection problems. IT administrators attempting to resolve the issue have found that traditional troubleshooting approaches such as using different network adapters, configuring static IP addresses, or adjusting secure boot settings do not resolve the connection problems. Recovery media made on one system can be used on another, however proprietary drivers such as network, WLAN, and RAID controllers may not be present if the hardware configurations differ.
This Cyber News was published on cybersecuritynews.com. Publication date: Wed, 26 Mar 2025 13:55:15 +0000