wsappx at the top of Task Manager’s disk column, 100% disk usage, laptop crawling — and you didn’t install anything. WsAppx is Windows’ Store app installer working in the background: updating your Store apps, licensing them, finishing interrupted installs. It’s doing real work, but on slow disks that work can monopolize the drive for an uncomfortably long time. And when an update gets stuck, wsappx doesn’t give up — it retries, forever, at full disk throttle.

The fix isn’t disabling it (that breaks the Store) — it’s managing what it’s doing: clearing the update backlog, stopping the automatic churn, and unpoking stuck updates. For the broader disk picture, see our 100% disk guide ; for Store-specific issues, our Runtime Broker guide .

Why this happens

  • Backlog of Store app updates: Dozens of pending updates all processing at once saturate the disk.
  • Large app updates: Games and creative apps from the Store are gigabytes — heavy disk writes.
  • Stuck update in a retry loop: A failed update that wsappx retries endlessly.
  • First-boot provisioning: New user accounts trigger Store app provisioning — heavy one-time disk work.
  • Corrupt Store cache: Damaged metadata makes the deployment service thrash.
  • Slow disk amplifying normal work: On HDDs, legitimate update I/O saturates the drive completely.
  • License sync churn: ClipSVC re-validating licenses repeatedly when the Store state is confused.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Check what’s actually updating

See the work before managing it.

  1. Open the Microsoft Store > Library — look at pending updates and active downloads.
  2. If there’s a long list of pending updates, that’s your answer — wsappx is legitimately busy.
  3. Note any update stuck at the same percentage or showing an error — that’s a stuck one needing Fix 4.
  4. In Task Manager > Details, you’ll see the wsappx-related services: AppXSvc and ClipSVC — note which is busier.
  5. Decision: big backlog = let it finish (Fix 2); stuck/error items = intervene (Fix 4); nothing pending but still busy = cache issue (Fix 5).

Fix 2: Let the backlog finish on your terms

Sometimes the fix is scheduling, not fighting.

  1. Plug into AC power and connect to unmetered internet — updates pause on metered connections and slow on battery.
  2. Open Microsoft Store > Library > Get updates and let everything download and install in one session — preferably overnight.
  3. Don’t use the laptop heavily during the big update run — you’re competing with wsappx for the same disk.
  4. After the library shows everything updated, restart — the boot-time wsappx spike should be dramatically shorter.
  5. A cleared backlog often ends the problem permanently — the daily churn was just Windows catching up.

Fix 3: Disable automatic Store app updates

Take control of when the disk gets hit.

  1. Open Microsoft Store > click your profile icon > Settings.
  2. Turn off App updates (automatic updates) — updates now only happen when you manually trigger them.
  3. Make it a monthly habit: open Library > Get updates when convenient (e.g., overnight).
  4. This doesn’t affect Windows Update — only Store apps. Security-wise, monthly manual updates are fine for Store apps.
  5. With auto-updates off, wsappx goes quiet except when you explicitly update — the disk is yours again.

Fix 4: Fix stuck Store app updates

Break the retry loop.

  1. In Microsoft Store > Library, find the stuck update — click the X or pause it, then retry it individually.
  2. If it won’t clear, run wsreset.exe (Win+R) to reset the Store cache — this resolves most stuck-update states.
  3. For a stubborn app: Settings > Apps > Installed apps > find the app > Advanced options > Repair, then Reset if needed.
  4. As a last resort for one broken app, uninstall and reinstall it from the Store — fresh install, no stuck state.
  5. After clearing stuck items, re-run Get updates — the queue should now process cleanly.

Fix 5: Reset the Store and deployment services

Clear systemic corruption.

  1. Run wsreset.exe from Win+R — the standard Store cache reset.
  2. Open an elevated PowerShell and re-register the Store: Get-AppxPackage -AllUsers *WindowsStore* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}.
  3. Check Settings > Windows Update and install pending updates — servicing stack fixes repair AppX deployment issues.
  4. Restart and monitor — wsappx should now only activate during genuine update activity.
  5. Microsoft documents Store troubleshooting on Windows support if you need the guided troubleshooter path.

Fix 6: Reduce the Store app footprint

Fewer apps, less update churn.

  1. Settings > Apps > Installed apps — uninstall preinstalled Store apps you never use (Tips, Solitaire, Spotify trials, manufacturer bloat).
  2. Each removed app is one fewer update wsappx must process forever.
  3. For apps you keep, disable background permissions (Advanced options > Never) — less background activity overall.
  4. Our startup trim guide covers the broader background-app cleanup.
  5. A lean app list means lean update cycles — the gift that keeps giving.

Fix 7: Address the underlying disk speed

When wsappx is innocent but the disk can’t cope.

  1. If wsappx behaves the same after all fixes but the disk still pins at 100%, the disk is the bottleneck — check health with wmic diskdrive get status.
  2. Ensure 15–20% free space on the system drive — full drives make every I/O operation slower.
  3. On a spinning HDD, this entire problem class is worse — an SSD upgrade is the definitive fix for Store-update disk storms.
  4. Schedule Store updates overnight (Fix 2’s approach) as the practical compromise on slow disks.
  5. For the full disk-performance picture, our 100% disk guide covers the other contributors.

Closing

WsAppx high disk usage is Windows maintaining your Store apps — legitimate work that becomes a problem when it’s backlogged, stuck, or fighting a slow disk. Clear the backlog, take control of update timing, unstick the failures, and trim the app list. The deployment service goes back to brief, unnoticed maintenance instead of all-day disk occupation.

Frequently asked questions

What is wsappx and why is it using my disk?
WsAppx is actually two Windows services — AppX Deployment Service (AppXSVC) and Client License Service (ClipSVC) — that install, update, and license Microsoft Store apps. High disk usage from wsappx means it’s actively installing or updating Store apps in the background. It’s legitimate work, but it can saturate slow disks for extended periods, especially during large app updates.
Can I disable wsappx?
You shouldn’t disable wsappx permanently — Store apps depend on it for installation and updates, and disabling it breaks the Microsoft Store. But you can calm it down: disable automatic Store app updates, pause updates during work hours, and let pending updates complete overnight. Ending the task in Task Manager is safe temporarily; the service restarts when needed.
Why does wsappx run at every startup?
At startup, wsappx checks for Store app updates and resumes any interrupted installations — that’s the boot-time disk spike many users see. If it runs long at every boot, you likely have a large backlog of pending app updates or a stuck update retrying. Clearing the backlog (letting updates finish) usually ends the recurring startup spike.
How long should wsappx disk activity last?
During active app installations or updates, expect heavy disk usage for minutes to an hour depending on app sizes and disk speed. It should settle when updates complete. If wsappx pins the disk for hours daily with no apps visibly updating, something is stuck — usually a failed update in a retry loop that needs the Store cache reset.