KB5072359 (OS Build 26100.7178) Out-of-Band Update for Windows Server 2025 - November 18, 2025
Out-of-band cumulative update for Windows Server 2025, OS build 26100.7178, released November 18, 2025. Fixes a boot failure on Intel C2030 systems upgrading to Server 2025.
Summary
This is a cumulative, out-of-band update for Windows Server 2025, released on November 18, 2025, producing OS build 26100.7178. It carries all fixes from the November 11, 2025 security update (KB5068861) and adds one targeted quality fix for a boot failure that can occur when upgrading specific Intel systems to Windows Server 2025. See Microsoft Support for the official page.
Improvements and fixes
- Intel C2030 / Samsung NVMe upgrade fix: On some Intel C2030 systems equipped with Samsung NVMe storage and running Windows Server 2022, the in-place upgrade to Windows Server 2025 could fail. Affected machines would not boot, displaying stop error code 0x7B (INACCESSIBLE_BOOT_DEVICE). The root cause is an Asynchronous Event Notification (AEN) error sent by the NVMe device during startup. This update defers AEN enablement until system initialization is complete, preventing the boot failure. IT admins must inject this OOB update into the Windows Server 2025 upgrade image before upgrading Windows Server 2022 devices.
Known issues
WSUS does not display synchronization error details
Symptom: After installing KB5070881 or any later update, Windows Server Update Services (WSUS) no longer shows synchronization error details inside its error reporting interface.
Workaround: This functionality has been temporarily removed by Microsoft to address the Remote Code Execution vulnerability CVE-2025-59287. No customer-side workaround is documented; the removal is intentional pending a longer-term resolution.
How to get this update
The latest servicing stack update (SSU) for Windows Server 2025 - KB5067035, version 26100.7010 - is now combined with this cumulative update, so no separate SSU installation step is required before applying KB5072359.
Windows Update / Windows Update for Business: KB5072359 is listed as available; follow the catalog instructions below to obtain the standalone package.
Microsoft Update Catalog: Download the MSU files directly from the Microsoft Update Catalog website. Two installation methods are supported.
- Method 1 - Install all MSU files together: Download all MSU files for KB5072359 and place them in a single folder (for example,
C:\Packages). Use DISM or the Add-WindowsPackage PowerShell cmdlet, pointing at the target MSU. DISM will automatically locate and install any prerequisite MSU files found in the same folder. - Method 2 - Install each MSU file individually in order: First install
windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu, then installwindows11.0-kb5072359-x64_9de812f726178f4c43c10ad84a8d6168daf7260d.msu.
WSUS: Available via the catalog option; see the catalog tab for details.
Uninstalling the LCU: Use DISM /online /remove-package with the LCU package name. Running wusa.exe /uninstall against the combined package will not work because it includes the SSU, and the SSU cannot be removed after installation.
Note on AI components: This update includes AI component updates, but those components apply only to Windows Copilot+ PCs and will not install on standard Windows PCs or Windows Server.
Frequently asked questions
Do I need to install a separate servicing stack update before applying KB5072359?
No. Microsoft now ships the latest servicing stack update (SSU) combined with the cumulative update. KB5067035 (version 26100.7010) is included in KB5072359, so you do not need to install it separately before applying this OOB update to your Windows Server 2025 systems.
Which systems are affected by the boot failure this update fixes?
The fix targets systems running Intel C2030 hardware paired with Samsung NVMe storage devices that were running Windows Server 2022 and attempting an in-place upgrade to Windows Server 2025. The failure manifests as a 0x7B INACCESSIBLE_BOOT_DEVICE stop error caused by NVMe Asynchronous Event Notification errors during startup.
How do I apply this update to an upgrade image before deploying it to affected servers?
Download the MSU from the Microsoft Update Catalog, mount your Windows Server 2025 installation image, and use DISM with /Add-Package pointing at the MSU file. The update must be injected into the upgrade image before the Windows Server 2022 to Windows Server 2025 upgrade takes place on affected Intel C2030 systems.
Why is WSUS not showing synchronization error details after this update?
Microsoft temporarily removed that WSUS error-reporting capability to mitigate a Remote Code Execution vulnerability tracked as CVE-2025-59287. The absence of synchronization error details in the WSUS console is intentional and is not a product defect introduced by KB5072359 itself.
