A recent Windows 11 update has caused significant issues for users of Veeam Recovery Media, a critical tool used by over 550,000 customers worldwide for data protection and recovery.
The problem affects systems running Windows 11 24H2 (build 26100.3194 or higher) and is believed to stem from changes introduced in the KB5051987 February update.
Connection Errors Plague Recovery Attempts
Users attempting to restore data using Veeam Backup & Replication via Veeam Recovery Media are encountering critical network connection failures.
These errors include:
- Lack of valid IP addresses
- Inability to establish authenticated client-server connections
- Failed SSPI (Security Support Provider Interface) calls
Additionally, efforts to recover data from SMB network shares result in the error, “The remote procedure call failed and did not execute”.
The issue appears to be related to subtle but impactful modifications to the Windows Recovery Environment (Windows RE), which Veeam Recovery Media relies on.
Temporary Workaround and Ongoing Investigation
While Microsoft and Veeam are jointly investigating this known issue, a temporary workaround has been provided.
Users experiencing these disruptions are advised to use Veeam Recovery Media generated on systems running older Windows 11 builds (build 26100.3037 or earlier).
Veeam has emphasized that its Recovery Media is based on Microsoft’s Windows RE and contains proprietary components of the Windows operating system.
As such, Veeam cannot provide pre-generated Recovery Media images.
It’s important to note that while Recovery Media from one machine can generally be used to perform bare metal restores on another, proprietary drivers needed to initialize hardware (such as network, wireless, and RAID controllers) may be missing if the original machine used to generate the recovery media has different drivers.
The disruption is particularly concerning for organizations relying on Veeam, which is used by 82% of Fortune 500 and 74% of Global 2,000 companies.
Veeam has officially acknowledged the issue in their knowledge base article KB4726, stating that the underlying cause is currently unknown and under investigation by both Veeam and Microsoft.
As the tech community awaits a permanent fix, IT administrators and Windows enthusiasts are advised to stay informed about any updates from Microsoft or Veeam regarding this issue.
The situation underscores the delicate balance between system updates and the functionality of critical recovery tools, highlighting the need for thorough testing and compatibility checks in the ever-evolving landscape of operating system updates.
Also Read:
%20(1).webp?resize=1600,900&ssl=1&description=The problem affects systems running Windows 11 24H2 and is believed to stem from changes introduced in the KB5051987 February update.){kind=link}