Microsoft’s latest Windows 11 installation images have quietly crossed the 8 GB mark — more than double the size of the original Windows 10 media from 2015. The culprit? A growing arsenal of on-device AI components intended for Copilot+ PCs, which now account for roughly 3 GB of the download even on computers that will never use them. The trend, documented by deployment expert Michael Niehaus and analyzed by ZDNET’s Ed Bott, forces every Windows user and IT administrator to carry the weight of features their hardware may not support.

What’s Inflated the Windows 11 ISO

The shift becomes stark when you compare version histories. Multi-edition ISOs from the initial Windows 10 release weighed around 4 GB. By Windows 11 24H2’s debut in November 2024, that number had swollen to approximately 6.5 GB. But the real jump occurred between 24H2 and the July 2026 release of Windows 11 25H2: Niehaus counted nearly 6,000 additional folders and over 20,000 more files packed into the image, pushing the total well past 8 GB. Even the lighter Media Creation Tool version now tips the scales at 6.8 GB.

The bulk of that growth comes from shared AI models that power features like semantic search, image analysis, live captions, and Windows Studio Effects on Copilot+ PCs with dedicated neural processing units (NPUs). Microsoft confirms these components are included in both the 24H2 and 25H2 servicing branches but will only install on hardware that meets the Copilot+ spec. For the vast majority of PCs — those lacking an NPU — the bits are downloaded, cached, and then ignored.

What This Means for You

Home Users

If you’re downloading a fresh ISO to create a USB installer or run a clean install, expect a file north of 8 GB. That means longer download times, especially on slower connections, and a USB drive that must be at least 16 GB (the old 8 GB sticks won’t cut it anymore). Once installed, a bare Windows 11 system with all updates applied consumes around 28.2 GB of drive space — nearly half the official 64 GB minimum storage requirement. That leaves precious little room for apps, personal files, and the inevitable cruft of temporary files, restore points, and update caches. Entry-level laptops with 64 GB eMMC storage are particularly pinched; they may struggle to install future feature updates without first freeing space or connecting external storage.

IT Administrators and Deployment Teams

Larger ISOs ripple through every aspect of enterprise deployment. Distribution points, branch office cache servers, and VPN connections now face fatter payloads. Creating or updating gold images for System Center Configuration Manager (SCCM) or Microsoft Deployment Toolkit (MDT) takes longer. Network bandwidth costs can spike when hundreds of clients pull monthly cumulative updates that contain the same unused AI components. USB deployment kits need to be re-provisioned with higher-capacity drives. Even virtual machine labs, which might spin up dozens of test environments daily, see increased storage consumption and slower provisioning.

The problem extends beyond initial rollout. Monthly cumulative updates through Windows Update are also packing these AI models, meaning every Windows 11 24H2 or 25H2 machine — regardless of hardware — must download the extra 3 GB repeatedly. For organizations with metered links or offline servicing strategies, this is a planning headache.

How We Got Here

Microsoft’s push into on-device AI isn’t new. Copilot+ PCs, launched in mid-2024, introduced dedicated NPUs and a suite of AI experiences. The company opted to bake the supporting models directly into the core OS servicing pipeline rather than deliver them as optional add-ons. In the past, Microsoft has moved system components to the Microsoft Store — think Notepad, Paint, or even the Windows Terminal — allowing them to update independently and only download when needed. But for Copilot+, the AI models are treated as part of the Windows servicing stack, akin to the Component Store. This design choice ensures that any PC that gets an NPU in the future will have the models ready, but it also locks every other device into carrying the payload.

Windows 11 25H2 itself is a small enablement package, meaning it’s just a switch that activates features already lying dormant in the 24H2 codebase. The fact that the ISO still ballooned underscores that the weight was already loaded into 24H2’s monthly updates. Essentially, the AI foundation was laid months before 25H2, and the enablement package simply turned on the lights.

What to Do Now

For Home Users

  • If you’re on a limited data plan, schedule large ISO downloads for off-peak hours or use a download manager. Consider using the Media Creation Tool, which produces a slightly smaller (~6.8 GB) image, though the difference is shrinking.
  • Clean up after installation: Run Disk Cleanup as administrator, select “Windows Update Cleanup” and “Delivery Optimization Files” to reclaim space taken by superseded updates and AI model caches.
  • When buying a new PC, seriously consider stepping up to at least 128 GB of storage — anything less will become a squeeze within a year. If you have a 64 GB device, disable hibernation (powercfg /h off) and move file storage to an SD card or cloud to free the system drive.

For IT Pros

  • Audit your deployment infrastructure: Ensure WDS servers, PXE boot images, and offline media are prepared for 8 GB+ payloads. Update your USB creation scripts to check for adequate capacity.
  • Leverage Delivery Optimization in Microsoft Endpoint Manager to peer-cache updates and reduce WAN impact. Consider grouping non-Copilot+ PCs into separate rings if your device inventory allows, though currently there’s no official way to exclude AI components from updates.
  • Adjust storage expectations in your hardware purchasing requirements. For standard office machines, set 128 GB as the floor; for developers or designers, push for 256 GB or more.
  • Stay informed about cleanup tools: Windows 11 24H2 introduced a “Windows Update Cleanup” option in Settings (System > Storage > Temporary files) that can automatically remove old update files. You can also script the removal of Component Store bloat with DISM.

For Everyone

Monitor Microsoft’s direction. The AI model payload is likely to grow as more on-device features ship. If the company heeds the feedback documented by Niehaus and Bott, it may refactor the models into optional Store-delivered packages. Until then, the download bill is collective.

Outlook: Will Microsoft Lighten the Load?

There’s precedent for decoupling. Microsoft has already moved the Quick Assist app, Windows Terminal, and other components to the Store, trimming the core OS image. Doing the same for the Copilot+ AI models would mean that only PCs with qualifying NPUs would fetch the 3 GB package — and only when needed. This would also allow Microsoft to update those models more frequently without issuing a full cumulative update.

However, such a change won’t come overnight. Engineering the separation, testing servicing scenarios, and ensuring that Copilot+ features work seamlessly on a just-in-time delivery model is complex. The company may also be wary of fragmentation if some users never download the models and then encounter broken AI features after adding an NPU later.

For now, Windows 11’s expanding footprint is a clear signal that AI is no longer an optional add-on — it’s woven into the fabric of the operating system. The practical consequence is that every download, every installation, and every storage budget must accommodate a future that hasn’t fully arrived.