Win Update KB5127648 Windows 11 Cumulative Update build 26100.9711 (24H2), 26200.9711 (25H2), 26300.9711 (26H2) - Oct. 13



 Microsoft Support:

Announcements and messages​

This section provides key notifications related to this release, including announcements, change logs, and end-of-support notices.

Important: Windows 11, version 24H2 Home and Pro has reached end of updates. The October 2026 monthly security update is the last update available for these editions. Devices running these editions will no longer receive monthly security and non-security preview updates containing protections from the latest security threats. To stay protected and up to date, we recommend you upgrade to the latest version of Windows 11.

Windows Secure Boot certificate expiration
Secure Boot certificate updates remain in progress as Microsoft transitions devices from certificates that began expiring in 2026 to newer certificates. Devices that have not yet received the newer certificates can continue to start and receive standard Windows updates. Microsoft will continue delivering the newer Secure Boot certificates to eligible devices through Windows Update.


Improvements​

This update includes improvements from the following previously released updates:
The following summary outlines key quality improvements addressed by this update. The bold text within the brackets indicates the item or area of the change.
  • [Security updates] This update provides security improvements. For more information about the security vulnerabilities resolved by this update, see the Security Update Guide.
  • [Secure Boot] This update continues the deployment of updated Secure Boot certificates using the latest high-confidence targeting data to identify eligible devices that are ready to automatically receive the new certificates. Deployment through Windows Update remains ongoing across supported devices.
  • [Windows Explorer (Known issue)] Fixed This update fixes an issue that affects Windows Explorer in multi-user environments, such as Azure Virtual Desktop and FSLogix. After sign-in, Explorer.exe might fail to start or repeatedly crash, causing a black screen.
  • [Audio (known issue)] Fixed This update fixes an issue that affects AC-3 audio playback in some applications.
  • [Always On VPN] This update fixes an issue that affects Always On VPN connections after installing KB5124008. When automatic protocol selection or protocol fallback was configured, affected VPN connections could remain stuck in a Connecting state or fail to connect after an initial connection attempt failed. In some cases, subsequent connection attempts could display the error, "The specified port is already in use."
  • [Storage Spaces] This update fixes an issue that affects tiered Storage Spaces Direct virtual disks. Some virtual disks might fail to come online after installing certain security updates, making dependent clustered workloads unavailable.
  • [Date and Time] This update introduces the new (UTC-05:00) Manitoba time zone to support Manitoba’s November 1, 2026, time zone change.
  • [ReFS security] This update adds auditing and optional policy controls for ReFS volumes on externally attached storage devices. Auditing is enabled by default, while enforcement controls remain disabled by default to give administrators time to evaluate and prepare for future security hardening changes. To learn more, see KB5130741.

  • [Printing] This update resolves an issue where printing could fail in some applications and on devices using RAW or Generic Text Only printer drivers after installing the August 2026 security update.
  • [Gaming] This update fixes an issue that could cause mouse input to stutter in some games.
  • [Windows Hello] This update fixes an issue where fingerprint sign-in might not work after a cold boot on some devices.
  • [Authentication] This update strengthens NTLMv1 security by changing the internal default behavior when the BlockNtlmv1SSO registry value is not set. Windows now uses Enforce mode (1) instead of Audit mode (0), blocking the generation of NTLMv1-derived credentials for Single Sign-On (SSO). This change applies only to devices where Credential Guard is disabled and the BlockNtlmv1SSO registry value is not set, and might affect Wi-Fi, Ethernet, and VPN connections that use MS-CHAPv2-based authentication. For more information, see KB5066470.

If you've already installed previous updates, your device will download and install only the new updates included in this package.

Components updates​

AI components
This release updates the following AI components to version 1.2608.951.0: Image Search, Content Extraction, Semantic Analysis, and Settings Model. To learn more, see Release information for AI components.

Servicing stack update
Includes KB5127647 (Build 26100.9703), which improves the reliability of the Windows update installation process. To learn more about SSUs, see Servicing stack updates.

Known issues in this update​

Symptoms

After installing this update, some devices might be unable to turn on Smart App Control in the Windows Security app if it has been turned off. On affected devices, the option to turn on Smart App Control might be grayed out.

Devices where Smart App Control is already turned on are not affected and remain protected.

Resolution

Important: This section contains information about modifying the registry. Before you modify the registry, back it up and make sure that you know how to restore it if a problem occurs. For more information, see How to back up and restore the registry in Windows.


Option #1: Modify the registry

You can modify the registry to restore the ability to turn on Smart App Control by following these steps:
  1. Open a Command Prompt window by typing cmd in the Search box.
  2. Select Run as administrator.
  3. At the command prompt, enter the following commands. Then restart the device.

    reg add "HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" /v 2883193997 /t REG_DWORD /d 1 /f

    reg add "HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" /v 2850574478 /t REG_DWORD /d 1 /f
Option #2: Install a Group Policy

IT administrators can instead choose to mitigate this issue for enterprise-managed devices managed by IT departments by installing and configuring the special Group Policies listed below.

Group Policy downloads with Group Policy name:
Important: You should install and configure both Group Policies to resolve this issue. The first Group Policy is needed to turn on Smart App Control. The second Group Policy ensures that logging is available to assist with troubleshooting in case any problems arise.

The special Group Policies can be found in Computer Configuration > Administrative Templates > {Group Policy name} > Windows 11, version 24H2, 25H2. After installing the Group Policies, configure the value for both settings to Enabled and restart your device(s) to apply the Group Policy settings.

Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

Symptoms

After installing the September 2026 non-security preview update KB5124010, or later updates, non-admin users might be unable to establish Remote Desktop connections to remote devices that have Administrator protection enabled. Attempts to connect might fail with error 0xC000000D and display the message, “The token that was passed to the function is invalid.” This issue primarily affects enterprise-managed remote devices used as Remote Desktop hosts with Administrator protection enabled, regardless of how the feature was enabled.

Note: If your organization uses Windows security baselines, published through the Microsoft Security Compliance Toolkit, Administrator protection is enabled by default in Windows 11, version 24H2, 25H2, and 26H2 security baselines, unless your organization has configured the policy differently.

Resolution

IT administrators can mitigate this issue on devices affected by the Remote Desktop connection failure by using their existing policy management method to temporarily turn off Administrator protection. Reset the User Account Control Type Of Admin Approval Mode policy in Microsoft Intune or Group Policy. For more information, see Administrator protection on Windows 11.

Next steps: Microsoft is working to address this issue in a future Windows update and will provide more information when it is available.

Symptoms

After installing the September 8, 2026, Windows security update (KB5124012), some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms:
  • The device displays an error in Device Manager: "This device cannot start (Code 10).”
  • No audio output.
  • Volume controls are unresponsive or remain at zero.
  • Sound settings are unresponsive or unavailable.
Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode.

This issue is limited to USB Audio Class 1.0 devices.

Resolution

This issue is partially resolved in the out-of-band (OOB) update released on September 14, 2026, (KB5129195). This OOB update resolves the symptoms experienced on devices using 8-channel or 3D audio modes. Microsoft is working to address the other symptoms and will provide more information when it is available.

IT administrators who need an immediate workaround for the symptoms not addressed yet by the OOB update should contact Microsoft Support for Business for assistance.

How to get this update​

Deployment​

If you deploy dynamic updates such as this update to an existing Windows image, ensure the boot.stl file is included as part of the installation media. Failure to include the file might prevent devices from successfully starting from the installation media and can result in error code 0xc0430001.

Note: The boot.stl file is used during Secure Boot validation and must match the Windows version and architecture of the image you are updating.

To ensure the boot.stl file is included as part of the installation media, do one of the following:
  • Use the Update WinPE script to update an existing Windows image. (Recommended)
  • Manually copy the boot.stl file from the device Windows\Boot\EFI folder to the corresponding folder on your installation media before deploying the update.
For information about how to apply Dynamic Update packages to existing Windows images, see Update Windows installation media with Dynamic Update.

Install this update​

To install this update, use one of the following Windows and Microsoft release channels.

Available​
Next Step​
Available
This update downloads and installs automatically from Windows Update and Microsoft Update.
Available
To install this update, download the standalone package(s) for this update from the Microsoft Update Catalog. This update contains MSU files that require installation in a specific order. Follow the Arm64 installation instructions or x64 installation instructions, as appropriate.

File information​

For a list of the files provided in this update, download the file information for cumulative update KB5127648.

For a list of the files provided in the servicing stack update, download the file information for the SSU KB5127647 - (Build 26100.9703).


 Source:



Check Windows Updates


26H2 ISO from Microsoft MCT:



UUP Dump:

64-bit ISO download:

ARM64 ISO download:

 
Last edited:

My Computer My Computer

At a glance

Windows 11 25H2Intel Core i516GB DDR4 RAMNvidia RTX 2050, Intel Internal Graphics
OS
Windows 11 25H2
Computer type
Laptop
Manufacturer/Model
Lenovo LOQ 15IRH8
CPU
Intel Core i5
Memory
16GB DDR4 RAM
Graphics Card(s)
Nvidia RTX 2050, Intel Internal Graphics
Screen Resolution
1920x1080
Hard Drives
512 GB SSD (Primary)
2TB Seagate External HDD (Secondary)
Mouse
Logitech wired mouse
Browser
Google Chrome
Antivirus
Windows Defender, Malwarebytes
you must restore health from iso use this comand
DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:f:\sources\install.wim:2 /LimitAccess
replace f with your drive letter and then scan health works perfect
I specifically tried the repair install with WU and a local ISO file as the source, neither of those fixed this issue. That doesn't work for a majority of these cases.
 

My Computers My Computers

  • At a glance

    Win 11 Pro 26H2, Build 26300.9711Intel Core i5 14500, 14th Generation64GB DDR4GeForce RTX 4060
    OS
    Win 11 Pro 26H2, Build 26300.9711
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Brew
    CPU
    Intel Core i5 14500, 14th Generation
    Motherboard
    Gigabyte B760M G P WIFI
    Memory
    64GB DDR4
    Graphics Card(s)
    GeForce RTX 4060
    Sound Card
    Chipset Realtek
    Monitor(s) Displays
    LG 45" Ultragear & Acer 24" 1080p
    Screen Resolution
    5120x1440 & 1920x1080
    Hard Drives
    Crucial P310 2TB 2280 PCIe Gen4 3D NAND NVMe M.2 SSD (O/S)
    Silicon Power 2TB US75 NVMe PCIe Gen4 M.2 2280 SSD (backup)
    Crucial BX500 2TB 3D NAND (2nd backup)
    Seagate 4TB Ironwolf, rotating HDD secondary backup
    External off-line backup Drives: 2 NVMe 4TB drives in external enclosures
    PSU
    Thermaltake Toughpower GF3 750W
    Case
    LIAN LI LANCOOL 216 E-ATX PC Case
    Cooling
    Lots of fans!
    Keyboard
    Microsoft Comfort Curve 2000
    Mouse
    Logitech G305
    Internet Speed
    Verizon FiOS 1GB
    Browser
    Firefox
    Antivirus
    MalwareBytes & Windows Defender Security
  • At a glance

    Win 11 Pro 25H2, Build 26300.9550Intel Core i5 1440032GB DDR5Intel 700 Embedded GPU
    Operating System
    Win 11 Pro 25H2, Build 26300.9550
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Brew
    CPU
    Intel Core i5 14400
    Motherboard
    Gigabyte B760M DS3H AX
    Memory
    32GB DDR5
    Graphics card(s)
    Intel 700 Embedded GPU
    Sound Card
    Realtek Embedded
    Monitor(s) Displays
    27" HP 1080p
    Screen Resolution
    1920x1080
    Hard Drives
    Crucial P310 2TB NVMe Gen4 SSD
    Samsung EVO 990 2TB NVMe Gen4 SSD
    Samsung 2TB SATA SSD
    Seagate 4TB Ironwolf, rotating HDD secondary backup
    PSU
    Thermaltake Smart BM3 650W
    Case
    Okinos Micro ATX Case
    Cooling
    Fans
    Keyboard
    Microsoft Comfort Curve 2000
    Mouse
    Logitech G305
    Internet Speed
    Verizon FiOS 1GB
    Browser
    Firefox
    Antivirus
    Malware Bytes & Windows Defender Security
  • Nimo N171 17" Laptop, (Intel i3-1215U, 16GB RAM, 2TB NVMe, Win11 Pro)
    Acemagic Vista Mini PC V1 (Intel N150, 16GB RAM, 1TB NVMe, Win11 Pro)
    HP ENVY h8-1540t, (24GB RAM, 2TB SSD, 2TB HDD, Win11 Pro)
Installed with no issues...
 

My Computer My Computer

At a glance

win 11 pro 25 h2
OS
win 11 pro 25 h2
Computer type
PC/Desktop
I specifically tried the repair install with WU and a local ISO file as the source, neither of those fixed this issue. That doesn't work for a majority of these cases.
No need for /RESTOREHEALTH here. 🤞🤷‍♂️
1792267438306.webp
 

My Computer My Computer

At a glance

Windows 11 Pro 25H2Intel I9-9900K64GBNVIDIA RTX 2060
OS
Windows 11 Pro 25H2
Computer type
PC/Desktop
Manufacturer/Model
Dell XPS 8930
CPU
Intel I9-9900K
Memory
64GB
Graphics Card(s)
NVIDIA RTX 2060
Sound Card
NVIDIA High Definition Audio
Monitor(s) Displays
4k Samsung
Screen Resolution
3840 x 2160
Hard Drives
512GB NVMe, ADATA SU 800, 2TB HDD

Latest Support Threads

Latest Tutorials

Back
Top Bottom