Microsoft released the January 13, 2026 cumulative for Windows 11 as KB5074109, advancing 25H2 installs to
OS Build 26200.7623 and 24H2 installs to
OS Build 26100.7623, and distributing the package as one or more MSU files that must be applied in the correct sequence for offline servicing or installed together with DISM to allow automatic prerequisite sequencing.
Background
Microsoft’s monthly cumulative model now routinely bundles the latest LCU (Latest Cumulative Update) content with servicing stack elements and — in some months — component payloads used by on-device AI features. That packaging approach reduces fragmentation for the majority of online devices, but it also introduces important operational nuances for offline installers, image servicing teams, and environments that require tight rollback control.
This particular January 2026 update (KB5074109) follows that pattern: it is a standard monthly cumulative that primarily delivers security and reliability fixes while continuing Microsoft’s practice of
Controlled Feature Rollouts (CFR) for certain Copilot-era UI and AI experiences. The update is provided through Windows Update (recommended for most users), and as downloadable MSU(s) from the Microsoft Update Catalog for offline deployment.
Overview of KB5074109: what’s in the package
Headline items
- Advances Windows 11 to Build 26200.7623 (25H2) and Build 26100.7623 (24H2) after a successful install.
- Delivered as one or more MSU files on the Microsoft Update Catalog; if multiple MSUs are present they represent a checkpoint-style sequence (prerequisite checkpoint + LCU) and must be applied in order when installing individually.
- Contains the usual mix of security fixes and quality improvements, and continues staged enablement of Copilot-era features (feature visibility remains gated by server-side entitlements, device hardware, and account/region policies).
Notable user-visible items
- Incremental UI polish and staged Copilot/Copilot+ features (taskbar Copilot shortcuts and new File Explorer surfaces may appear on qualifying devices after install, subject to server-side enablement).
- Expanded File Explorer dark-mode coverage and other small UI fixes that have been rolling out since late 2025.
- Packaging footprint has grown relative to older cumulatives; offline MSU bundles for this family are commonly multi‑gigabyte (community reports and catalog entries show offline bundle sizes in the ~3.9–4.3 GB range depending on architecture).
Why the installation order matters (technical context)
Microsoft’s cumulative and servicing-stack model now frequently uses
checkpoint-style MSUs and often bundles the Servicing Stack Update (SSU) with the LCU. That means:
- If the Update Catalog lists multiple MSU files for the same KB, those files form a sequenced chain where a small checkpoint or SSU MSU must be applied before the main cumulative in certain offline scenarios. Installing the files out of order may cause errors, partial servicing, or a failed state that requires manual troubleshooting.
- DISM’s package discovery behavior (when all MSU files are placed in a single folder) simplifies offline servicing by automatically discovering and applying prerequisites in the correct order. Microsoft explicitly recommends placing all MSU files for a given KB into the same folder and using DISM to install the target MSU so prerequisites are resolved automatically.
- When SSUs are bundled into a combined package, the SSU component is effectively permanent on that host; the SSU portion cannot be removed with wusa /uninstall and complicates rollbacks if you planned to revert an LCU. Plan rollback strategies and golden-image retention accordingly.
These behaviors are not theoretical: multiple community-run reports and Microsoft’s own KB guidance emphasize DISM + PackagePath sequencing as the reliable method for offline installs and image servicing.
Practical deployment guidance
Recommended path for most users
- Use Windows Update (the trusted, staged delivery channel) and allow the update to install automatically. Windows Update will handle SSU/LCU sequencing, express/differential payloads, and server-side rollouts. This is the least risky choice for home users and small businesses.
For administrators, image builders, and air-gapped environments
- Download all MSU files for KB5074109 from the Microsoft Update Catalog and place them in a single folder (for example,
C:\Packages). Use DISM to install so the servicing engine can discover any prerequisite MSUs automatically. Example commands (run from an elevated prompt):
- To install on a running PC with DISM:
DISM /Online /Add-Package /PackagePath:C:\Packages\Windows11.0-KB5074109-x64.msu- Or, from an elevated PowerShell prompt:
Add-WindowsPackage -Online -PackagePath "C:\Packages\Windows11.0-KB5074109-x64.msu"- To service a mounted offline image:
DISM /Image:mountdir /Add-Package /PackagePath:Windows11.0-KB5074109-x64.msu- Or PowerShell:
Add-WindowsPackage -Path "C:\offline" -PackagePath "Windows11.0-KB5074109-x64.msu" -PreventPending
- If the Update Catalog shows multiple MSU components and you prefer to install each file individually, follow Microsoft’s exact sequence in the KB. For KB5074109 the KB lists the files (example order shown in the KB):
windows11.0-kb5043080-x64_...msuwindows11.0-kb5074109-x64_...msu
Always use the exact filenames and hashes you downloaded from the Update Catalog to avoid mismatches.- After installing to a running machine, verify the install and OS build:
- Run
winver or check Settings → System → About to confirm Build 26200.7623 or Build 26100.7623 as appropriate.
- Use DISM to locate installed packages:
DISM /Online /Get-Packages | findstr /i 5074109. Check Windows Update history in Settings for the KB entry and confirm any reboot completed. Inspect CBS logs and Event Viewer for component-based servicing events if troubleshooting is required.
Image hygiene and WinRE/SafeOS notes
- SafeOS and WinRE dynamic updates are effectively one-way changes on images. If you inject SafeOS or WinRE updates into offline images, the changes are not trivially reversible; keep a golden image backup before servicing. Run
reagentc /info to validate WinRE state after servicing.
- Finish with component cleanup to reduce WIM size after injecting packages:
DISM /Cleanup-Image /StartComponentCleanup and, where appropriate, DISM /Export-Image to produce optimized images for distribution.
Verification checklist (concise, copy-ready)
- Download MSU(s) from Microsoft Update Catalog and save to
C:\Packages.
- Run (elevated):
DISM /Online /Add-Package /PackagePath:C:\Packages\Windows11.0-KB5074109-x64.msu.
- Reboot if prompted.
- Confirm OS build via
winver or Settings → System → About: Build 26200.7623 (25H2) or 26100.7623 (24H2).
- Validate package presence:
DISM /Online /Get-Packages | findstr /i 5074109.
Size, performance expectations, and packaging remarks
Community testing and catalog entries indicate offline MSU bundles for the 26100/26200 families commonly fall
in the 3.9–4.3 GB range for x64 bundles; download and install times will vary with network speed and hardware. On a typical modern connection (200 Mbps) and recent hardware, reported download times are on the order of minutes with installation times commonly in the single-digit minutes range for the LCU install itself. These community measurements align with the larger offline package footprint driven in part by on-device AI components that Microsoft delivers to qualifying devices. Caveat: bundle size and composition may differ by architecture and month (some months include larger model payloads or distinct component KBs). Always confirm the Microsoft Update Catalog file sizes before scheduling bandwidth-constrained rollouts.
Critical analysis — strengths, operational trade-offs, and risks
Strengths
- Improved update reliability for online devices: bundling SSU with the LCU and using Windows Update’s express/diff delivery reduces widespread failed-install noise for most end users. This approach improves the day-to-day reliability of patching on connected machines.
- DISM discovery simplifies offline sequencing: placing all MSU files in one folder and letting DISM handle prerequisite sequencing reduces human error in image servicing workflows. It’s a practical improvement for IT teams that maintain offline images.
- Targeted CFR keeps risky features gated: Controlled Feature Rollouts allow Microsoft to enable new Copilot-era experiences only on qualifying hardware/accounts and to slowly expand the user-visible surface without broad immediate exposure. For organizations concerned about behavioral or compliance impacts, CFR prevents surprise mass changes.
Operational trade-offs and risks
- SSU permanence and rollback complexity: when SSUs are bundled into combined MSUs, the SSU portion is not removable. That complicates rollback strategies when a critical LCU needs to be reverted and the environment expects to be able to "uninstall" an update. Organizations must plan for redeploying golden images rather than relying on simple package uninstall.
- Third-party compatibility is still the largest real-world risk: historically, problematic updates often correlate with third-party agent stacks, specialized virtualization drivers, or legacy kernel-mode components. A pilot ring that includes critical third‑party agents, VDI images, and representative hardware (including Copilot+ test devices) remains essential.
- WinRE / SafeOS changes are effectively irreversible on serviced images: injecting SafeOS updates into WinRE/WinPE images can alter recovery images in a way that isn’t easily undone; maintain unmodified golden recovery images.
- Controlled Feature Rollouts (CFR) mean inconsistent post-update behavior: installing KB5074109 does not guarantee every device will show the Copilot or UI features described in secondary coverage; those are subject to server-side gating, device entitlement, and region/account controls. Treat feature presence as variable and validate expectations against qualifying hardware only.
Specific caution: on-device model claims
Multiple community reports and secondary outlets note that Microsoft’s on-device small language models (often referenced by community shorthand such as
Phi Silica) are distributed through component KBs and may sometimes be packaged into monthly catalogs, which contributes to larger offline bundle sizes. However, claims that every monthly cumulative universally includes the full set of on-device model binaries for all hardware types are
not consistently documented by Microsoft and should be treated with caution; verify component KB listings in the Update Catalog for your platform before making procurement or policy decisions.
Recommended deployment plan (practical, risk-aware)
- Small businesses / home users
- Allow Windows Update to handle the rollout. Accept the recommended reboot window and let differential/express deltas minimize download impact.
- Enterprises with large estates
- Inventory and prioritize: identify devices with legacy kernel drivers, virtualization hosts, line-of-business appliances, and Copilot+ hardware that may have unique entitlements.
- Pilot ring: stage KB5074109 to a pilot group for 48–72 hours that includes representative endpoints (VDI hosts, laptops, Copilot+ devices, and servers where applicable).
- Image servicing validation: perform offline image servicing in a lab, using DISM with all MSUs in a single folder to validate sequencing and verify WinRE/WinPE recovery images after injection. Keep golden images backed up before making WinRE changes.
- Rollback plan: prepare redeployment procedures (redeploy golden images) rather than relying on MSU uninstall for LCU rollback if the SSU is bundled. Ensure SCCM/WSUS catalogs reflect the correct SSU/LCU dependencies.
- Monitoring and telemetry: collect CBS and DISM logs from test hosts, monitor Windows Update status, and track Help Desk tickets closely during the first week after deployment.
Troubleshooting highlights (quick reference)
- If an offline install fails with package sequencing errors:
- Confirm all MSU files for the KB are present in one folder and use DISM to allow automatic sequencing.
- Use
DISM /Online /Get-Packages and inspect Component-Based Servicing (CBS) logs (C:\Windows\Logs\CBS\CBS.log) for failures.
- If a device unexpectedly reboots or goes into uninstall/recovery loops:
- Collect
C:\Windows\Panther and C:\Windows\Logs\CBS logs, check Event Viewer for servicing events, and verify third-party drivers and security agents that could intercept kernel updates. Historical community incidents show third-party agents are a frequent source of regressions.
Final assessment
KB5074109 is a routine but important January monthly cumulative that delivers security and quality fixes while continuing Microsoft’s cautious feature rollouts for Copilot-era experiences. For most consumers and smaller organizations, the recommended path is to let Windows Update handle the install. For image builders, offline installers, and enterprises, treat the update as you would any combined SSU+LCU package: download the MSUs from the Update Catalog, place them in a single folder, and use DISM to allow automatic sequencing; maintain golden images and plan rollbacks as redeployments rather than relying on uninstall.
The key operational takeaways are straightforward:
- Use Windows Update when possible for lowest risk and simplest experience.
- For offline or mass deployment, use DISM against a folder containing all MSU files so prerequisites are discovered and applied automatically.
- Keep golden images and recovery media untouched until after you’ve validated any SafeOS/WinRE changes in a lab.
Administrators should pilot, validate third‑party stacks, and treat SSU permanence and WinRE hygiene as first-class concerns during this rollout cycle; doing so will minimize surprises and help ensure a smooth and secure KB5074109 deployment across diverse Windows 11 estates.
(Verification note: this article is based on Microsoft’s KB guidance and community testing guidance reproduced in the KB text and associated community summaries; practical commands and sequencing recommendations come from the KB’s installation instructions and community servicing runbooks. Where specific product-model bundle claims (for example, monthly inclusion of particular on-device model binaries) are not explicitly documented by Microsoft, that point is flagged as provisional and should be verified against the Update Catalog entries for your hardware and the official Microsoft support page for KB5074109.
Source: Microsoft Support
January 13, 2026—KB5074109 (OS Builds 26200.7623 and 26100.7623) - Microsoft Support