Known and Resolved issues for Windows 11 version 25H2

Known issues in this update​

For the most up-to-date information about known issues for Windows 11, version 25H2, go to the Windows release health dashboard.


Symptoms
Some Digital TV and Blu-ray/DVD apps might not play protected content as expected.

Apps that use Enhanced Video Renderer with HDCP enforcement or Digital Rights Management (DRM) for digital audio might show copyright protection errors, frequent playback interruptions, unexpected stops, or black screens.
Streaming services are not affected.

Workaround
This issue is partially resolved. Problems affecting certain applications that use Enhanced Video Renderer with HDCP enforcement have been addressed in the September 2025 Windows preview update (KB5065789) and later updates.

We recommend installing the latest update for your device. It includes important improvements and fixes, including a resolution for this issue.

However, some apps that use DRM for digital audio might still experience problems.

We’re investigating a long-term solution for affected apps and will share more information when it's available.


Symptoms
Windows updates installed using the Windows Update Standalone Installer (WUSA) might fail with error ERROR_BAD_PATHNAME when installed by double-clicking a .msu file or using WUSA from a network share that contains multiple .msu files. These issues might occur on devices that installed updates released on May 28, 2025 (KB5058499) or later.

WUSA installs updates using the Windows Update Agent API, a method typically used in enterprise environments. It’s not commonly used in personal or home settings.

This issue does not occur when:

• Only one .msu file is present in the network share.
• The .msu file is stored locally on the device.

After installing an update using WUSA or by double-clicking the .msu file, and restarting Windows, you might still see a message on the Update History page in Settings indicating that a restart is required to complete the update. This is a temporary display issue and should resolve automatically.

Workaround
To work around this issue, save the .msu files locally on the device and install the update from that location.

If you’ve restarted Windows after installing an .msu file using WUSA, wait at least 15 minutes before checking the Update History page in Settings. After this short delay, the Settings app should correctly indicate if the update installed successfully.

Mitigation
This issue is addressed using Known Issue Rollback (KIR) and is resolved automatically for most home users and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster.

IT administrators can resolve this issue on managed devices that have installed the affected update by deploying a special Group Policy. For information on deploying and configuring the special Group Policy, see How to use Group Policy to deploy a Known Issue Rollback.

The special Group Policy can be found in: Computer Configuration > Administrative Templates > Group Policy name.

Group Policy downloads with Group Policy name: Download for Windows 11, version 24H2 and Windows Server, version 2025 - Windows 11 24H2 and Windows Server 2025 KB5062660 250806_17201 Known Issue Rollback.msi

Next steps: The issue is under investigation, and additional information will be shared as soon as it becomes available.


Symptoms
The Windows 11 media creation tool (version 26100.6584), released on September 29, 2025, might not work as expected on devices with Arm64. Users may encounter an error message such as:

"We're not sure what happened, but we're unable to run this tool on your PC."

Note: The media creation tool doesn't support creating media for use on Arm64 devices. However, Arm64 devices are normally able to create media for x64 devices—this functionality is not working as expected.

This issue is unlikely to affect most users, as this feature is rarely used on Arm64 devices.

Workaround
To prevent this issue, the media creation tool can be used on devices that have AMD64 processors. Use of the tool on these devices is not affected.

The issue is under investigation, and additional information will be shared as soon as it becomes available.

Windows message center

Does your organization use hotpatch quality update policies and want to upgrade to Windows 11, version 25H2? Plan when to upgrade because it can affect whether devices continue to receive hotpatch updates during the current hotpatch cycle. Devices that upgrade during a designated baseline release period (such as October) will remain eligible for hotpatching. Devices that upgrade during a non-baseline month (such as November) will temporarily stop receiving hotpatch updates. Instead, these devices will receive standard security updates that require a restart until the next baseline release (that is January 2026). For complete information, review the hotpatching release cycles.

Report of something that happened here on W11 25h2 have an Asus Rampage Extreme IV, and twice the USB ports would disconnect and everything connected to them would no longer work. They only came back on when I restarted the PC. So I decided to mess with the BIOS. I have an old USB 2.0 mouse and joystick, and they're connected to the Asmedia 3.0 port. So far, since I've enabled EHCi Hand-off in the BIOS, there's no longer a "disconnect" issue.

UPDATE 10/16:
New known issue below. See first post for more details.

IIS websites might fail to load
Server-side applications that rely on HTTP.sys may experience issues with incoming connections.

UPDATE 10/17:
New resolved issue below. See first post for more details.

Smartcard authentication issues might occur with the October 2025 Windows update
This issue is related to a security change introduced for strengthening Windows Cryptographic Services.

A new issue:
USB mouse and keyboard not working in the Windows Recovery Environment (WinRE)
This issue affects USB devices only within WinRE after installing Windows updates released on October 14, 2025.
OS Build 26100.6899
KB5066835
2025-10-14
Confirmed

Ive just tested Windows Recovery Environment (WinRE) with this latest build OS Build 26100.6899 and my Bluetooth Keyboard & Mouse works fine just not with any USB Dongle's.
Fine in Windows itself though with either USB or Bluetooth.

Wow ..... how would this pass testing. Oh that is right, the public does the testing.

UPDATE 10/19:
New resolved issue below. See first post for more details.

USB mouse and keyboard not working in the Windows Recovery Environment (WinRE)
This issue affects USB devices only within WinRE after installing Windows updates released on October 14, 2025.

Brink said:

UPDATE 10/19:
New resolved issue below. See first post for more details.

USB mouse and keyboard not working in the Windows Recovery Environment (WinRE)
This issue affects USB devices only within WinRE after installing Windows updates released on October 14, 2025.

Click to expand...

Yep, just tested it, working fine now with .6901

Brink said:

Kerberos and NTLM authentication failures due to duplicate SIDs - Microsoft Support

support.microsoft.com

Click to expand...

Wouldn't things like NEWSID or similar address this issue? I know it's no longer available for download, but there are other similar utilities available.

gunrunnerjohn said:

Wouldn't things like NEWSID or similar address this issue? I know it's no longer available for download, but there are other similar utilities available.

Click to expand...

You'd think so.

Brink said:

You'd think so.

Click to expand...

I guess since that's not an "official" MSC solution, they're solution is to reinstall Windows.

Someone get Mark Russinovich to update his blog. He still works for MS.

garlin said:

Someone get Mark Russinovich to update his blog. He still works for MS.

Click to expand...

I see that it doesn't say much anymore except that NEWSID is gone.

For nearly two decades, Mark asserted duplicate SID's don't cause any problems in a shared environment. Until MS finally tightened the security rules to prove him wrong. Some older folks may vehemently disagree, but if you were cloning images without generalizing, you deserve this mess.

Where this impacts normal users is if you took a system image from one PC and restored it to another, and left both PC's running side by side. The new restrictions on unique SID's also affects SMB file sharing and RDP for non-Active Directory users.

Fortunately, my installs were all from scratch, probably a good thing.

Guess we'll have to wait until it leaks.

IT administrators can temporarily address this issue by installing and configuring a special Group Policy. To obtain this special Group Policy, please contact Microsoft’s Support for business.

Click to expand...