Microsoft pushed out a cumulative update for Windows 11 on March 10, 2026, and while the patch notes might look mundane at first glance, KB5079466 packs a few twists that Windows users and admins need to understand. The update, which lifts the OS to build 28000.1719, ships as a multi-MSU package – a departure from the typical single-file servicing stack. More quietly, it also bundles updates to on-device AI components, but only for systems meeting the Copilot+ hardware bar.

The KI5079466 update, unpacked

The delivery mechanism is the first thing you’ll notice. Instead of a single .msu file, Microsoft published multiple MSUs that must be installed either together using DISM’s folder-targeting trick or one by one in a prescribed sequence. This multi-MSU approach isn’t brand new, but it’s uncommon enough to warrant attention. It typically signals tight interdependencies between the servicing stack, core OS, and optional components.

What’s inside for the OS itself? The cumulative rollup addresses standard quality and reliability fixes, though Microsoft’s support page offers only a terse description. The build number moves from the 28000 baseline to 28000.1719, suggesting a modest set of non-security changes. There are no urgent zero-day patches highlighted, but the usual under-the-hood polish is included.

The more interesting payload sits alongside the OS bits: AI component updates. Microsoft specifically flags these as applicable only to Windows Copilot+ PCs. On a regular laptop or server, those AI packages won’t install – they’re gated by hardware checks. That means if you’re running a standard Intel or AMD machine without a qualifying NPU/accelerator, you’ll still get the OS fixes but none of the AI tweaks.

What this means for your PC

The answer hinges on what kind of device you have.

Home users

If you own a garden-variety Windows 11 laptop or desktop, KB5079466 will arrive through Windows Update as a normal cumulative update. You don’t need to do anything special, and the multi-MSU packaging is handled behind the scenes. Expect a standard reboot, and the build number will bump to 28000.1719. Don’t go hunting for new AI tricks – they aren’t there on non-Copilot+ machines.

For those with a Copilot+ PC (think recent Snapdragon X Elite or Intel Core Ultra with integrated NPU, certified by Microsoft), the update may include changes to on-device models such as Phi Silica or image processing engines. These are the components that power quick local AI tasks in apps like Photos, Paint, and the Copilot sidebar. After installation, you might notice subtle improvements in response times or accuracy for those features. Microsoft doesn’t detail exactly what changes, but the fact that they’re versioning and shipping these models separately indicates ongoing tuning.

System administrators and IT pros

For fleets, the multi-MSU format adds a wrinkle. If you’re pushing updates via WSUS or Configuration Manager, you’ll need to ensure the packages are applied in the correct order. Microsoft’s guidance is clear: let DISM discover and sequence the MSUs in a folder, or follow the explicit sequence listed in the KB article. Failing to do so can lead to servicing stack inconsistencies, incomplete installs, or errors that require an offline repair.

Testing becomes critical. Spin up a pilot ring that includes at least one Copilot+ device if your organization has any in circulation. Verify AI features still work as expected after the update. Check driver versions for vendor-specific AI execution providers (Qualcomm QNN, Intel OpenVINO, NVIDIA TensorRT) because the new model artifacts might expect particular driver baselines.

Image maintenance also gets affected. When you inject this update into offline Windows images for deployment, you must align the SafeOS and Setup Dynamic Update packages to March 2026 versions. If an exact March version isn’t available, use the most recent one, as the KB recommends. This prevents OOBE failures and WinRE boot issues.

Developers and ISVs

If you build applications that tap into Windows’ AI runtime or directly invoke models like Phi Silica, monitor the component versions after this update. A subtle model change could affect output quality or inference behavior. The update history page in Settings on a Copilot+ device will list the individual AI components and their versions, so compare before and after.

How we arrived at multi-MSU and gated AI

The 28000 build stream is something of a platform release – a foundation for next-gen silicon, especially Arm-based and AI-centric chips. Microsoft has been componentizing Windows’ AI stack for over a year, decoupling pieces like the local language model (Phi Silica), Image Processing AI, and Image Transform AI from the core OS. These components get their own update cadence and can be delivered alongside cumulative updates or independently.

The multi-MSU approach likely stems from the need to keep the servicing stack and AI runtimes in sync. Because a new AI model might depend on a specific core OS library version, shipping both in a coordinated bundle prevents version skew. It also lets Microsoft gate the AI payloads so they only land on hardware that actually benefits from them, avoiding wasted disk space and potential support headaches on older machines.

This isn’t the first time Microsoft has used such a strategy. Back in Windows 10’s later years, we saw similar patterns with feature-specific packages for Windows Mixed Reality or Windows Ink. The difference now is the scale and sensitivity of on-device AI, where a poorly matched model can produce inaccurate or biased results.

How to install KB5079466 without tripping up

For most consumers, Windows Update handles everything. But if you’re working with standalone installers for offline PCs or custom images, follow these steps carefully.

Method 1: Install all MSU files together (recommended)

  1. Download every MSU file linked to KB5079466 from the Microsoft Update Catalog.
  2. Place all files into a single folder, say C:\KB5079466.
  3. Open an elevated Command Prompt and run:
    DISM /Online /Add-Package /PackagePath:C:\KB5079466\windows11.0-kb5079466-arm64_ce4511a3d3417df08755d55ec6b0a19e2685424b.msu
    (Replace the filename with the actual primary MSU name for your architecture.)

DISM will scan the folder, discover any prerequisite packages, and install them in the correct order automatically. This path avoids most sequencing errors.

Method 2: Install each MSU individually, in order

If DISM’s folder discovery isn’t viable, you’ll need to reference Microsoft’s prescribed order. At the time of writing, the KB lists only one MSU file for ARM64; however, the support page mentions “one or more MSU files.” For x64, you might see additional files. Always check the KB article for the current list.

Apply each MSU with DISM /Online /Add-Package or wusa.exe, in the sequence specified.

Applying to a mounted image

For offline servicing of deployment assets:

DISM /Image:C:\mount\offline /Add-Package /PackagePath:Windows11.0-kb5079466-arm64_ce4511a3d3417df08755d55ec6b0a19e2685424b.msu

Or in PowerShell:

Add-WindowsPackage -Path "C:\offline" -PackagePath "Windows11.0-kb5079466-arm64_ce4511a3d3417df08755d55ec6b0a19e2685424b.msu" -PreventPending

After applying, ensure all Dynamic Update packages match the month. If you can’t find March 2026 SafeOS or Setup DU, grab the latest and test thoroughly.

Verifying installation

  • OS version: Check winver or Settings > System > About; you should see 28000.1719.
  • AI components (Copilot+ only): Navigate to Settings > Windows Update > Update history, then look under “Other updates” for entries like “Windows AI Components – Image Processing” or “Phi Silica.”

If things go wrong

Multi-MSU installs can fail silently if prerequisites aren’t met. Common pitfalls:

  • A missing Servicing Stack Update (SSU). Ensure you have the latest SSU from February or March 2026 before attempting the cumulative update.
  • Out-of-sequence installation. If you installed an MSU individually in the wrong order, you may need to uninstall the affected packages and re-deploy using Method 1.
  • Incompatible drivers. On Copilot+ PCs, an AI component update might require a specific NPU driver version. If AI features break, check with your OEM for driver updates aligned to Windows 11 24H2/28000.

Gather DISM logs, CBS logs, and Windows Update logs if you need to open a support case.

The bigger picture

KB5079466 isn’t a headline-grabbing feature drop, but it’s a signal of how Windows servicing is morphing to accommodate a world where the OS hosts machine-learning models alongside traditional code. The split delivery – common fixes for everyone, plus gated AI components for certified hardware – lets Microsoft iterate on AI experiences without forcing unnecessary bits onto billions of devices that can’t use them.

For IT admins, the operational lesson is clear: patching is no longer a simple “push one MSU and forget.” You must track component prerequisites, validate hardware-specific payloads, and align imaging processes. Microsoft provides the tools (DISM folder installs, update history entries), but the burden of coordination falls on you.

Looking ahead, expect this pattern to repeat. As the Copilot+ ecosystem grows and more devices gain local AI capabilities, we’ll see more KBs carrying silent AI companions. The next step is crossing fingers and proper testing.