Microsoft Acknowledges Four Issues in Windows 11 25H2 Release, Yet No Major Concerns

Windows 11 version 25H2 has just begun its public rollout, but it is already experiencing several notable issues. As of September 30, Microsoft has acknowledged at least four problems associated with this release. Fortunately, there are indications that the Windows 11 2025 Update will not face the same challenges that plagued version 24H2, as Microsoft is actively working on a patch to address these concerns.

As reported by Windows Latest, Microsoft has released a new support document that elaborates on the issues found in Windows 11 25H2.

Identified Issues in Windows 11 25H2

It’s important to note that many of the problems with Windows 11 25H2 originate from version 24H2. Given that 25H2 serves as an enablement update built on the same code base as 24H2, it has inherited these existing bugs. Thus, while users of Windows 11 24H2 need to have the September update to encounter these issues, anyone upgrading to 25H2 will experience them immediately, without requiring any additional updates.

1. Playback Issues with DRM-Protected Content

A significant issue affecting users is that DRM (Digital Rights Management) protected content may fail to play under certain circumstances after upgrading to Windows 11 25H2. Microsoft has identified a bug that disrupts the Enhanced Video Renderer, which is essential for playing DRM-secured media.

This technical hiccup primarily impacts older applications—while modern streaming services like Netflix do not rely on this feature, users of DVD, Blu-ray, or legacy TV applications may find they encounter copyright errors, abrupt playback stops, or even a black screen. Microsoft is currently investigating this problem and anticipates a fix is forthcoming in October 2025, potentially delivered through an optional update.

2. WUSA Fails to Install.msu Packages

Another issue arises with the Windows Update Standalone Installer (WUSA), particularly when users try to install updates using.msu files after having previously applied updates from Windows 11 24H2. This situation may trigger an error coded as ERROR_BAD_PATHNAME.

While this problem primarily affects specific enterprise scenarios, it does not pose issues for mainstream consumer devices. Microsoft has indicated that they are aware of it and are planning to address this in an upcoming release, although a specific timeline remains unclear.

3. SMB v1 File Sharing Breaks

The recent update also disrupts Windows SMB v1 file sharing capability. Despite Microsoft’s efforts to phase out SMB v1 in favor of more secure protocols like v2 and v3, many businesses still depend on this legacy feature. Following the installation of the latest updates, users will find they cannot share files or directories using SMB v1.

Microsoft has confirmed that this issue is attributed to a failure in the SMB v1 protocol connection when using NetBIOS over TCP/IP (NetBT).If either the SMB client is running Windows 11 version 25H2 or the SMB server has the September 2025 security update installed, problems will arise. For those who need to use SMB v1, it is recommended to allow traffic on TCP port 445 to enable SMB connectivity while increasing compatibility.

Microsoft reiterates that it does not support SMB v1 and this protocol is disabled by default in newer system versions. Transitioning to SMB v2 or v3 is encouraged for seamless file sharing.

4. Media Creation Tool Issues on ARM64 Devices

Another glitch affects the Media Creation Tool, specifically for ARM64 PCs, where the tool inadvertently fails to initiate when attempting to create installation media. Users may encounter the message: “We’re not sure what happened, but we’re unable to run this tool on your PC.”

While Microsoft asserts that the Media Creation Tool is not yet functional for creating installation media on ARM64 systems, it can still be utilized to generate ISO images for x64 architecture. This unusual limitation primarily impacts a limited number of users, as most do not typically use the feature on ARM64 devices. Microsoft suggests using either AMD or Intel systems when creating bootable Windows 11 25H2 installation media.

Source&Images