Overview of KB5051987 Update

​

Overview of KB5051987 Update

​

On February 11, 2025, Microsoft released cumulative update KB5051987 for Windows 11 version 24H2, which advanced the operating system to build 26100.3194. This update, like most Patch Tuesday releases, included a range of security patches and internal system improvements designed to enhance performance, user experience, and stability.

​

Among the key features of this update were refinements to the Windows taskbar. Users saw improved responsiveness and animations when hovering over icons, aiming to deliver a more fluid interface experience. Additionally, the update introduced a new system tray icon for Windows Studio Effects—an enhancement targeting devices with integrated Neural Processing Units (NPUs). These effects allow users to apply features like automatic framing, background blur, and eye contact adjustments during video calls.

Another notable addition was the introduction of Simsun-ExtG, a simplified Chinese font that supports an additional 9,753 ideographs from Unicode Extensions G, H, and I. This change is part of Microsoft’s continued effort to improve localization and global language support.

​

While the update delivered visible improvements to the user interface and system functionality, it also introduced a critical compatibility issue with a widely-used enterprise backup and recovery solution—Veeam.

​

Veeam Recovery Breaks After Update: Investigation Underway

Following the release of KB5051987, users began reporting serious issues when attempting to use Veeam Recovery Media to restore data on systems running the updated version of Windows 11 24H2. Specifically, systems updated to build 26100.3194 or later have experienced failure when trying to connect to backup servers or access data hosted on network shares.

​

Administrators attempting to restore backups using Veeam Recovery Media may encounter error messages such as:

• "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."

​

These errors effectively prevent users from accessing backup environments during system recovery scenarios—a situation that can have severe consequences in enterprise and business-critical environments. The issue appears to be connected to changes in the way Windows 11 handles network authentication and communication in the updated build.

​

Veeam, a leading provider of backup, disaster recovery, and data protection solutions, has acknowledged the problem and is working in collaboration with Microsoft to investigate the root cause. However, Microsoft has yet to officially list the issue in its known problems documentation for the 24H2 release.

​

Temporary Workaround and Cautionary Measures

Until a permanent fix is developed, Veeam has recommended a workaround: users should create and use recovery media on machines running older builds of Windows 11, specifically build 26100.3037 or earlier. Doing so appears to bypass the connection issue introduced in the newer build.

However, this workaround comes with its own risks. Recovery media built on a different machine may lack the necessary drivers for critical hardware components such as network interfaces, wireless adapters, or RAID controllers. This could complicate or entirely prevent recovery operations in certain environments.

Organizations are therefore urged to test recovery media thoroughly before relying on it for production or critical recovery scenarios.

Broader Impact and Recommendations

The implications of this issue are significant. Veeam's solutions are widely adopted across the globe, used by more than 550,000 customers, including 82% of Fortune 500 companies and 74% of the Global 2000. Disruptions to restore operations can delay business continuity, violate compliance mandates, and result in costly downtime.

​

IT administrators and enterprise support teams are advised to:

• Postpone deployment of the KB5051987 update on systems where recovery may be required.

• Rebuild Veeam Recovery Media using a known-good version of Windows 11 (build 26100.3037 or earlier).

• Test recovery scenarios proactively to ensure compatibility.

• Monitor official channels from both Microsoft and Veeam for patches, advisories, and updated guidance.

​

At this time, there is no confirmed timeline for a fix, but both companies have indicated they are actively investigating the issue.

Let me know if you want this version adapted for an email alert, internal tech bulletin, or anything else!