Microsoft Store Downloads Finally Break Free of Years of Throttling

Microsoft’s June 2026 Patch Tuesday update fixed a Microsoft Store download problem that Windows 11 users have complained about for years. The cumulative update, KB5094126, released June 9, ends throttling that kept Store speeds crawling at a fraction of a PC’s real connection. Windows Latest, which first tested the fix, documented downloads jumping from barely usable to fully saturating a home connection.

The fix reaches only the download pipe. It leaves the Store’s decade-old interface exactly as sluggish as before, and the framework that could modernize that interface still carries its own unresolved bugs.

Gigabit Connections, Kilobyte Speeds

For years, the Microsoft Store has behaved like it was running on a different internet connection than the rest of the PC. A user on a 1 Gbps line could pull down a full Steam game in about ten minutes, then watch the same hardware struggle to move a Store download at speeds between 200 kilobytes per second and 4 megabytes per second.

It wasn’t a hardware problem. A system built around a Ryzen 7 9800X3D processor, an RTX 5070 Ti graphics card, and 32GB of RAM would sit almost idle while the Store inched through a file. One recurring example: CapCut updates, which land roughly every two months and run around 700MB, a file that could take twenty minutes in the Store versus under two minutes through a browser.

The symptoms were consistent enough that users learned to expect them:

• Throttled to a fraction of the available connection speed, no matter how fast the line actually was.
• Paused mid-download for no apparent reason, sometimes for minutes at a stretch.
• Got stuck in a pending state that required restarting the app to finish at all.

Some of that frustration had already spilled into Microsoft’s own support channels, where users pinned the slowdown on Delivery Optimization quietly capping Store traffic well below what the connection could actually handle.

Microsoft’s Fix Arrives Without Much of an Explanation

KB5094126 is a mandatory update, and its headline features are things like a Low Latency Profile that briefly spikes CPU clock speed, Shared Audio for two people listening on one PC, and multi-app camera access. The Store fixes sit further down the changelog, without much fanfare.

Microsoft’s own description of the download fix is short on detail.

This update includes underlying changes that improve download performance and bandwidth usage.

That is the entire explanation Microsoft has offered. The update itself is available now through the Update Catalog listing for KB5094126, moving Windows 11 25H2 to build 26200.8655 and 24H2 to build 26100.8655.

• What we know: KB5094126 shipped June 9, 2026, and Microsoft credits the speed improvement to unspecified changes in download performance and bandwidth usage.
• What we know: The fix rolls out gradually through Microsoft’s Controlled Feature Rollout system, so not every PC gets it the same week.
• What’s unconfirmed: Whether the change touches BITS, the Background Intelligent Transfer Service that manages background downloads, download-priority handling, or how bandwidth is split between the Store and other processes. Microsoft hasn’t said which.
• What’s unconfirmed: Whether the same change reaches the Xbox app, which has logged similar throttling complaints on Game Pass installs.

This is being rolled out gradually, and Microsoft says it will reach everyone in the coming weeks.

IT Admins Finally Get a Straight Answer

The second Store fix in KB5094126 targets a narrower but genuinely painful problem for managed devices. The Microsoft Store shares download infrastructure with Windows Update, and IT departments that restrict direct Windows Update access, commonly through internal servers like WSUS (Windows Server Update Services) or SCCM (System Center Configuration Manager), can accidentally block Store downloads as a side effect.

Before this update, the failure was nearly useless for troubleshooting. Users on domain-joined machines would see a generic message saying the install was blocked by policy, with no indication of which setting caused it. Microsoft’s changelog says the fix now improves error reporting specifically for downloads blocked by Windows Update group policy settings.

For IT staff who spend hours chasing vague error codes across a fleet of machines, a named policy in the error message is a real time saver.

Scrolling Still Lags Behind the Google Play Store

Faster downloads don’t fix what the Store looks like once it’s open. The app is built on Universal Windows Platform (UWP), the aging framework Microsoft has spent years trying to move developers away from. Pages load slowly, transitions lag, and scrolling through the app library still feels choppy on high-end hardware.

The comparison is not flattering. On a budget Android phone in 2026, the Google Play Store scrolls at a smooth 60 frames per second. On a premium Windows 11 laptop, the Microsoft Store still runs behind by multiple frames. The macOS App Store fares little better by comparison to Windows, coming across as noticeably faster and more visually consistent than what Windows 11 offers today.

The technical reason is rendering, not raw hardware. WinUI, Microsoft’s newer interface layer, draws through the system compositor and gets frame-rate-independent animation as a result. UWP does not get that benefit, which is part of why parts of File Explorer that were rebuilt in WinUI scroll smoothly while older UWP sections still stutter. Developers have raised the same complaint in public forums, including a benchmark discussion on Microsoft’s own WinUI repository where one contributor argued WinUI 3 still trails both UWP and WPF in raw performance.

Why Hasn’t Microsoft Rebuilt the Store in WinUI?

Microsoft hasn’t ruled it out, but it hasn’t set a date either. Rebuilding the Store in WinUI would likely fix its choppy scrolling, since WinUI renders through the compositor and UWP does not. The catch is that WinUI itself still has an unresolved visual bug: apps torn and blacked out at the edges mid-resize.

Microsoft has already admitted the problem publicly. March Rogers, Microsoft’s Partner Director of Design, said the platform-level fix for the tearing will start rolling out over the summer, after testing on Microsoft’s own inbox apps first. Until that lands in the Windows App SDK, a WinUI-based Store would risk trading choppy scrolling for ugly resizing.

There are signs Microsoft is serious about the shift regardless. Windows Latest has reported that Rudy Huyn, a Partner Architect at Microsoft, is building a team focused on fully native WinUI apps. At Build 2026, Chris Anderson, Microsoft’s vice president of software engineering, said the top priority is fixing fundamentals before adding features, and Microsoft dropped the number from the WinUI 3 branding to signal it’s the permanent platform, with no WinUI 4 planned.

Microsoft Is Working Through a Backlog of Complaints

The Store fix fits a wider pattern this year. Windows 11 has spent much of 2026 clearing out complaints that had piled up for a long time. KB5094126 follows KB5089573, which fixed an earlier Patch Tuesday reboot failure during installation. Windows 11 Search also picked up a native toggle to remove Bing from search results, closing out one of the most requested Start menu changes. And Microsoft has said it is working to end the Windows 11 Microsoft account requirement during setup.

Not every reversal has been welcome, and not every addition has stuck. Microsoft had been testing a floating Copilot button inside the Store meant to push app downloads; it appears to have quietly disappeared. That mirrors what happened in Word, Excel, and PowerPoint, where Microsoft admitted the floating Copilot button was a mistake and now lets people hide it. The one AI feature that has stuck around in the Store is its review summaries, which condense user ratings into a short overview before install, a small, useful application rather than a visible gimmick.

Frequently Asked Questions

Which Windows 11 Versions Get KB5094126?

KB5094126 applies to Windows 11 versions 24H2 and 25H2, moving them to builds 26100.8655 and 26200.8655. Version 23H2, which has already reached the end of support, instead gets KB5093998, a security-only release with no new features.

How Do I Check If My PC Has the Fix Yet?

Because the download fix rolls out gradually, open Settings, then Windows Update, then Update history, and confirm the listed build reads 26200.8655 or 26100.8655. Typing winver into the Run box shows the same build number faster.

Why Did Microsoft Store Downloads Throttle in the First Place?

Community troubleshooting on Microsoft’s own support forums pointed to Delivery Optimization, the background-transfer feature that by default capped Store-related traffic well below a connection’s real speed, along with metered-connection detection that throttled downloads even on unmetered Wi-Fi. Microsoft’s changelog never confirmed which mechanism, if any, its June fix actually addresses.

What Does Error Code 0x8024500C Mean?

That code has shown up on enterprise and school PCs when a Group Policy setting, such as one blocking direct Windows Update internet access for devices running internal WSUS or SCCM servers, silently prevents a Store download. Before KB5094126, the Store simply said the install was blocked by policy; now it names the specific setting responsible.

Will Microsoft Ever Rebuild the Store in WinUI?

Microsoft hasn’t committed to a date, but the direction points that way. Rudy Huyn’s push for fully native WinUI apps and Microsoft’s decision to drop the “3” from WinUI 3 branding both signal a long-term commitment, though a Store rebuild would likely wait for the resize-tearing fix due later this summer.