wsappx High CPU on Windows: What It Runs and When It Stops

wsappx is not a virus and not a program you installed. It is the name Windows gives to the service host that runs the Microsoft Store's deployment and licensing services. When it uses a lot of CPU or disk, the usual reason is that the Store is installing, updating or removing an app in the background, and the load drops once that work finishes. The useful questions are which service is busy, what it is installing, and whether the work ever completes.

What wsappx hosts

Two services matter here. Microsoft's service reference describes both:

Manual means they start on demand. Neither should be busy all day on an idle PC. They wake up when there is Store work to do: an app being installed or updated, a Store app being removed, or license checks for apps bought from the Store. Deploying a package means writing its files to disk, so the same work can show up as disk activity as well as CPU.

Confirm which service is busy

Open Task Manager with Ctrl + Shift + Esc, sort the Processes tab by CPU and note the time. If the busy entry is the service host for wsappx, find its process ID in the Details tab (the svchost.exe row with that PID), then look at the Services tab, which lists each service with the PID that runs it.

The tasklist command can answer the same question in one step. From Command Prompt:

tasklist /svc /fi "SERVICES eq AppXSvc"
tasklist /svc /fi "SERVICES eq ClipSVC"

Each line gives the image name, the PID and the services in that process. Compare the PID with the one using CPU in Task Manager. If it matches AppXSvc, an app package is being deployed or removed. If it matches ClipSVC, the work is licensing for Store apps.

Mole's Status page shows the same thing from a different angle. Windows service hosts in the system session fold into one process row, and opening the row's details lists the services it hosts, busiest process first, so AppXSvc or ClipSVC appears by name instead of a column of identical svchost.exe entries. Mole does not offer End for that row, because it belongs to Windows services.

Check what the Store is doing

Most wsappx spikes line up with Store updates. Microsoft says it is making app updates automatic to keep security patches current, so updates can start without you opening the Store. Apps that came with Windows, such as Solitaire, To Do or the Xbox apps, are Store packages too, which is why the spike can appear on a PC where you never installed anything from the Store.

1. Open Microsoft Store.
2. Select Check for Updates and look at what is downloading or installing.
3. Let the queue finish, then watch wsappx again for a few minutes.

If the CPU drops when the queue empties, nothing was wrong: the service did its job. A one-off spike after a large app update is expected.

Removing Store apps uses the same service. When Mole for Windows removes a Store app, the request goes through the deployment service like any other removal, and Windows queues it behind any Store install or update already in progress. So an app removal can briefly add to the same wsappx load.

Turn off automatic Store updates, if you really want to

If background updates keep landing at bad moments, for example on a metered connection or during a presentation, Microsoft's automatic app updates page shows the switch: open Microsoft Store, select your profile picture, choose Store Settings and change App updates. Microsoft also notes that app updates are becoming automatic and that you can pause them when needed, so your Store version may show a pause choice instead of an off switch.

This trades CPU spikes now for older apps later. Store apps receive security fixes through these updates. A middle path is to leave updates on and select Check for Updates yourself at a time that suits you, so the work happens while you are not using the PC.

When it never settles

A wsappx process that stays busy for hours with nothing visible in the Store is a different pattern. Look for:

• The same app retrying an update over and over in the Store's downloads list.
• Store errors or a stuck download, which the app update failures guide walks through stage by stage.
• Low disk space on drive C:, which makes package deployment slow or failing. Sorting out a full C: drive covers that.

Change one thing at a time and repeat the same check. If wsappx calms down after one stuck app finishes or is removed, you have found the cause. For the general method of tracing CPU to an owner, see high CPU usage on Windows; if the disk is pinned at 100% instead, disk usage at 100% separates active time from real throughput.

What not to do

• Do not disable AppXSvc or ClipSVC in Services or by changing their Start value in the registry. Microsoft's description is direct: with the deployment service disabled, Store applications are not deployed and may not work properly; with the license service disabled, apps bought from the Store do not behave correctly.
• Do not end the wsappx service host in Task Manager to make the number go down. It stops the install or update in the middle, and the Store will start it again later.
• Do not strip the built-in Store apps with a removal script to stop the updates. Windows refuses to remove some packages that are part of it, and Mole for Windows leaves the Microsoft Store, App Installer and Windows Security out of its Apps list, so they cannot be removed there by accident. A short spike is not a reason to take the system apart.
• Do not treat a short spike as a fault. Measure over several minutes, with the Store queue in view.

FAQ

What is wsappx and why is it using so much CPU?

It is the service host for the AppX Deployment Service and the Client License Service, which install, update, remove and license Microsoft Store apps. High CPU usually means a Store app update or install is running, and it settles when that finishes.

Can I disable wsappx?

Not safely. Microsoft says that with these services disabled, Store apps are not deployed and may not work properly, and purchased Store apps do not behave correctly. Pausing or turning off automatic Store updates is the supported way to control when the work happens.

Is wsappx high CPU a virus?

The genuine wsappx services run inside svchost.exe from the Windows folder and are listed by name with tasklist /svc. If the busy process lives somewhere else or the services list does not show AppXSvc or ClipSVC, investigate it as an unknown program instead.

Why does wsappx run when I never use the Microsoft Store?

Apps that came with Windows, such as Solitaire, To Do and the Xbox apps, are Store packages and are updated through the same services, even if you never open the Store yourself.