Veeam Support Knowledge Base
Windows 11 24H2 | Server 2025 - Recovery Media Issue

Windows 11 24H2 | Server 2025 - Recovery Media Issue

KB ID:	4726
Product:	Veeam Agent for Microsoft Windows \| 6.0 \| 6.1 \| 6.2 \| 6.3 \| 6.3.1
Published:	2025-03-25
Last Modified:	2025-03-28

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

Oops! Something went wrong.

Please, try again later.

Challenge

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 remote procedure call failed and did not execute.

Cause

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.

Solution

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).

More Information

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.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

Product

Topic

Description

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Verify your email to continue your product download

We've sent a verification code to:

An email with a verification code was just sent to

Didn't receive the code? Click to resend in sec

Didn't receive the code? Click to resend

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.