Loading...
Loading...
When Restoring from Veeam Recovery Media created from a machine running either Windows 11 24H2 (build 26100.3194) or higher or Server 2025 (build 26100.3194) or higher, the connection to the Veeam Backup Server or a network share fails with the following errors: Connection problems. Exception has been thrown by the target of an invocation. Failed to establish connection: no valid IP addresses were found. Unable to establish authenticated client-server connection. A call to SSPI failed, see inner exception. The Local Security Authority cannot be contacted.
The underlying cause of this issue is unknown at this time and is under investigation by Veeam and Microsoft. The issue appears to be related to a change within the February update (KB5051987) for Windows 11 24H2 and Server 2025.
Customers impacted by this issue are advised to consider the following workarounds: If the restore is from backups stored in a Veeam Backup & Replication repository, use the recovery token option to access the backups. Use Veeam Recovery Media generated from a machine running an older Windows 11 or Server 2025 build (26100.3037 or lower).
The Veeam Recovery Media is based on the Microsoft Windows RE and contains proprietary components of the Windows operating system. As such, Veeam cannot provide a pre-generated Veeam Recovery Media image. Generally speaking, the Veeam Recovery Media from one machine can be used to perform bare metal restores of another. However, the proprietary drivers that may be needed to initialize hardware (network, wireless, RAID controller, etc.) may be missing if the original machine used to generate the recovery media has different drivers.
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.