That Microsoft Store message is a queue lock, not an error. Windows Update is already running another install, so Store won't start a second job until the first one finishes or gets cleared. In most cases the fix is to let the current update finish, restart the device, and run the Store troubleshooterβthen use the Windows Update troubleshooter only if the block persists. If the block survives all of that, check that neither service host is stuck in a pending-restart state, which is the most common reason the message repeats for days.
The wording changes slightly by version, which is why people describe it differently. Windows 10 and Windows 11 both use the Microsoft Store's own download queue, and both hand off larger installs to the Windows Update backend. That shared backend is why a Patch Tuesday update can block a Store game update, and why a Store app update can block a Windows cumulative update.
Why Microsoft Store Says Updates Are Already in Progress
Windows runs one update job at a time per install channel, and the Store is a front end onto the same servicing stack that Windows Update uses. The store's message appears when the Store's download queue holds a job β an app, a game, a codec, a dependency like the Visual C++ redistributable β and a second request arrives before the first completes. Nothing is broken; the queue is simply occupied.
Microsoft groups updates into "update sessions," and each session performs a single scan-and-download cycle followed by one install phase. A session cannot overlap with another on the same device. That design reduces disk thrashing on the system drive and prevents two installers from writing to the same component store.
The practical consequence is that a large game download can hold the queue for hours. A 40 GB game update on a 25 Mbps connection takes roughly 3.6 hours of pure download time (40,000 MB Γ· 3.125 MB per second β 12,800 seconds). Every Store app update queued behind it will report that other updates are in progress for that entire window.
This is also why the message can appear when you didn't knowingly start anything. Store apps update automatically, and Windows Update can trigger driver and .NET Framework installs through the same session. Check Settings β Windows Update β Update history before assuming something is frozen.
Check Windows Update History Before You Touch Anything
Look at what's actually running before you touch a troubleshooting tool. Open Settings β Windows Update and read the status line at the top. If it says "Updates in progress" or shows a percentage, the machine is busy and the Store message is accurate. If it says "You're up to date," the Store is blocking on a queue entry that never closed.
Next, open Update history on the same page. It lists installed updates with dates, and it separately lists failed ones with error codes such as 0x80070005 (access denied) or 0x800f0922 (insufficient system partition space). A failed update in history is a strong signal that a previous session never cleaned up, leaving a pending operation that the store now collides with.
Check the Microsoft Store's own queue in parallel. Open Microsoft Store, select Library, and choose Get updates. The button reports either a spinner with active downloads or the message you're chasing. This tells you which of the two queues is holding the lock.
Run these checks in order and write down what each one says. The status lines are your evidence for which fix applies, and calling support with three recorded status lines is faster than describing the symptom in prose.
Let the Current Session Finish, Then Restart
Restarting mid-download can corrupt a partial package and lengthen your wait. Allow the running session to complete first. Watch the Windows Update percentage or the Store download progress until it reports done, then restart the PC through Start β Power β Restart rather than a shutdown, because Restart completes the pending file-replacement phase that Fast Startup skips.
The restart matters because installers frequently stage files and commit them on the next boot. Windows uses a pending-file-rename operation on system files that cannot be replaced while they're in use. If you power off instead of restarting, those staged operations can persist across sessions, which is exactly the state that generates the "other updates are in progress" message even when nothing visible is downloading.
A normal restart on a solid-state drive takes 20 to 60 seconds plus boot time, and Windows will show "Getting Windows ready" or "Working on updates" if the servicing stack has pending work. That screen is progress, not a hang β leave it alone for up to 30 minutes before assuming trouble.
After the restart, reopen Microsoft Store β Library β Get updates. If your queued app installs normally, the session closed cleanly and you're done. If the message returns within a few minutes with no visible download, move to the store's own troubleshooter.
Run the Microsoft Store Apps Troubleshooter
Windows ships a dedicated repair tool for this store, and it clears stuck queue state without touching your installed programs. Go to Settings β System β Troubleshooters (Windows 11) or Settings β Update & Security β Troubleshoot (Windows 10), select Other troubleshooters, find Windows Store Apps, and click Run. The tool checks permissions on the store's cache folders, verifies service state, and resets the download queue's registration.
The troubleshooter's checks are narrow, which is why it's safe. It does not reinstall apps or delete your library. It may reset the Windows Update service, the Background Intelligent Transfer Service, and the Cryptographic Services to their defaults if any of them is disabled or set to manual start.
Expect the scan to take one to three minutes and to list what it changed. If it reports "Windows Update components must be repaired," it has detected a service-level fault and the next section applies. If it reports no problems found, the lock lives elsewhere and you should continue down the list.
Re-run the store's Get updates action immediately after the troubleshooter finishes, before opening any other app. The tool releases the queue, and a fast retry catches the window before another automatic update reoccupies it.
Clear Stuck Services and the SoftwareDistribution Folder
If the store troubleshooter finds nothing, the servicing stack itself is likely holding a lock. The safest sequence is a scripted series of stops, a folder rename, and a restart of those services. Open Command Prompt as administrator and run each line below, waiting for each to finish.
1: Type net stop wuauserv and press Enter β stops Windows Update. 2: Type net stop bits and press Enter β stops the transfer service that downloads packages. 3: Type net stop cryptsvc and press Enter β stops Cryptographic Services. 4: In File Explorer, navigate to C:\Windows\SoftwareDistribution and rename it to SoftwareDistribution.old. 5: Return to Command Prompt and type net start wuauserv, then net start bits, then net start cryptsvc. 6: Restart the PC, then open Settings β Windows Update and click Check for updates.
Renaming rather than deleting the folder preserves the old cache in case you need to restore it. Windows rebuilds a fresh SoftwareDistribution folder on the next update check, and the size of a healthy rebuild is typically a few hundred megabytes. The old folder can be deleted once a successful update cycle completes.
Fix a Genuine Pending-Restart State
A pending restart is the stubborn version of this problem, and it produces the message even when no download is visible. Windows records pending operations in the registry under Component Based Servicing, and if a restart was interrupted, that record survives and blocks new sessions indefinitely. The store can't start a job because the system believes one is already committed.
This is where the messaging misleads people. Nothing shows in the store's queue, Windows Update shows no percentage, and yet the message persists. Erasing the store's cache does nothing because the lock lives in the servicing stack, not the app.
FAQ
Does the message mean my Windows installation is corrupted?
No β the block is queue contention in most cases, and Windows Update history typically shows a clean record. Corruption shows up as repeated failed installs with error codes like 0x80070005 or 0x800f0922 in Update history. Check history before assuming corruption, because repair operations are far more disruptive than letting a session finish.
Can I install my app by pausing Windows Update?
Pausing updates doesn't release the store's queue, because the store's own downloads run independently of the pause setting. In Windows 11, pausing stops the automatic check but doesn't cancel an in-flight session. You'd need to finish or clear the active session through the services route instead of the pause control.
Does this happen on Windows 10 as well as Windows 11?
Yes β both versions share the same servicing stack and store backend, and both produce near-identical wording. The path to the troubleshooter differs: Settings β Update & Security β Troubleshoot on Windows 10, Settings β System β Troubleshooters on Windows 11. Everything else in the repair sequence is identical.
How long should I wait before treating it as stuck?
Give a running session 24 hours for a large game download on a slow connection, and about 2 hours for typical app updates. If Windows Update shows no percentage and the store shows no active download for 2 hours, treat the state as stuck rather than busy. That threshold reflects typical package sizes rather than any Microsoft-documented timeout.
Will resetting the Store delete my installed apps or purchases?
No β a Store reset clears the app's local cache and settings, and your library and purchases stay tied to your Microsoft account. Your installed apps remain installed. What you lose is the store's cached sign-in state, which means signing in again. Purchased content remains re-downloadable from Library.
What if the block returns every time I update?
A repeating block usually points to a scheduled task or a third-party updater competing for the same session. Check Task Scheduler for update-related triggers and review installed security suites, since some run their own update agents that invoke the Windows installer. Confirm the suspected agent on the vendor's own documentation before disabling anything.
Is there a command that bypasses the queue entirely?
No supported command skips the session lock; the servicing stack enforces it by design. Commands like wuauclt /detectnow or usoclient startscan trigger a scan, not a parallel install, so they'll fail the same way. The supported path is clearing the lock, not routing around it.