Fix it now
A Store install runs through four separate stages and the client rarely tells you which one failed. 0x80070141 decodes to Win32 error 321, ERROR_DEVICE_UNREACHABLE, so this is as likely to be the path out as the cache on the device. Clear client state, check the services, then look at the network.
wsreset.exe
Get-Service wuauserv,bits,DoSvc,InstallService,AppXSvc,ClipSVC
Get-AppxPackage -AllUsers *WindowsStore* | ForEach-Object {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
Get-AppxLog
- Close the Store first, then run
wsreset.exe. Microsoft’s description: a blank Command Prompt window opens, and after about ten seconds it closes and the Store opens by itself. It has not hung. - Start any of those six services that came back stopped. Cleanup and debloat scripts routinely disable the Microsoft Store Install Service and Delivery Optimization, and Store installs then fail permanently.
- Repair the Store client: Settings, Apps, Installed apps, Microsoft Store, Advanced options, Repair – then Reset if Repair does not help.
- Test the same account on a different network, such as a phone hotspot. Given what the code decodes to, that one test separates device state from network path faster than anything else.
The Windows Store Apps troubleshooter runs on the Microsoft Support Diagnostic Tool, which Microsoft has deprecated and says will be removed in a future release of Windows. On a current build it may simply not be there.
If installs complete after that, stop here. If they still stall at Pending, the next section explains what the four stages are and which one you are stuck in.
Why it happens
A Store install is not one operation. The client asks the service what the account is entitled to, a licence is issued and cached locally, the package content is fetched through the download stack, and only then does the deployment engine stage and register it exactly as it would any other package. Four components, four sets of services, four ways to fail – and one generic message in the client.
That is why the entry sits at Pending. When a stage fails, the client does not always have a useful error to show, so it leaves the queue entry in place and retries, and the retry fails identically. Clearing client state works so often not because the cache is magic but because it discards a broken queue entry and starts the sequence again from the beginning.
0x80070141 is worth decoding rather than treating as a Store code. The 0x8007 prefix is the Win32 facility, and 0x141 is 321 – ERROR_DEVICE_UNREACHABLE, “the device is unreachable.” No Microsoft page ties it specifically to the Store, so treat that decode as the direction of travel rather than a diagnosis: it points at something not being reachable, which puts the network path and the endpoint list alongside the cache and service checks rather than after them.
The Store client state is damaged
You have this one if Installs fail immediately, the Store may render blank or partially, and several unrelated applications behave the same way.
- Close the Store completely, including from the taskbar, then run
wsreset.exeand wait for the Store to reopen on its own. - If that changes nothing, repair the Store from Settings, Apps, Installed apps, Microsoft Store, Advanced options.
- Re-register the Store per user with the Add-AppxPackage one-liner in the fix layer, from an elevated session.
A service the pipeline needs has been turned off
You have this one if Every Store install has failed for weeks, and someone ran a cleanup or debloat script at some point.
Get-Service wuauserv,bits,DoSvc,InstallService,AppXSvc,ClipSVCand start what is stopped.- Set the startup types back to their defaults, or the next reboot returns you here.
- Check whether a policy or a management platform is disabling them, in which case fixing it on the device is temporary.
The download never completes
You have this one if The entry sits at Pending or shows a percentage that does not move, and other network activity on the machine is fine.
- Test on a different network. If the same account installs cleanly on a hotspot, the fault is the path, not the device.
- Read
Get-AppxLogafter the failure. It carries the deployment side of the story even when the client shows nothing. - If the machine is behind an inspecting proxy or a filtering appliance, that is a different article’s problem and it produces its own codes.
The deployment half fails after the download succeeds
You have this one if The download completes and the install then fails, or the app appears and will not launch.
- Run
Get-AppxLogimmediately. The deployment codes are precise where the Store client’s are not. - Repair the component store:
DISM /Online /Cleanup-Image /RestoreHealth, thensfc /scannow, then reboot. - Check free space on the system drive. Staging needs room for the payload plus working space.
Full reference
The services behind a Store install
| Service name | Its part in the chain |
|---|---|
InstallService |
Drives Store installs and updates |
AppXSvc |
Stages and registers the package |
ClipSVC |
Holds the local licence state for Store applications |
DoSvc |
Fetches the content |
bits |
Background transfers used elsewhere in the pipeline |
wuauserv |
Servicing, which parts of the pipeline lean on |
Those are the short names the Services console lists them under; open services.msc if you would rather match them by display name. Disabling any of them is a popular line in cleanup scripts, and because the effect is delayed – installs keep working from cache until they do not – nobody connects the failure to the change. The service check is often the fastest win in this whole article.
Reading the deployment side
Get-AppxLog returns the log for the most recent deployment operation. Run it immediately after a failure and you get that attempt rather than a guess; Get-AppxLog -All returns every log on the machine, with more information available when run elevated. The same records are in Event Viewer under Applications and Services Logs, Microsoft, Windows, AppXDeployment-Server, in the Operational channel.
This matters because the Store client and the deployment engine have different vocabularies. The client shows a code with no published meaning; the deployment log shows one of the documented ERROR_INSTALL_* codes with a specific cause. Where the two disagree, the deployment log is the one to work from.
On the codes in this article
Only one of the three is traceable to Microsoft documentation, and only by decoding rather than by a published gloss. 0x803FB005 and 0x80D02017 return no documentation results at all, so they get functional descriptions here and nothing more. That is not a gap in the troubleshooting: the fix path for a stalled Store install does not depend on knowing what those numbers stand for, and inventing meanings for them would make the article less useful, not more.
The troubleshooter question
Older guidance sends readers to Settings, System, Troubleshoot, Other troubleshooters and the Windows Store Apps entry. The legacy inbox troubleshooters run on the Microsoft Support Diagnostic Tool, and Microsoft’s deprecated features list says MSDT is deprecated and will be removed in a future release of Windows. No removal date is published. Treat the troubleshooter as something that may or may not exist on the build in front of you, and do not build a procedure around it.
When installs still will not complete
- Confirm the date, time zone and region are right. Certificate validation and licensing both care, and both fail unhelpfully when the clock is wrong.
- Check free space on the system drive, and on the package volume if packages are configured to install elsewhere.
- Create a new local profile and try there. A per-user state problem and a machine-wide one look identical from inside one account.
- Try a different account on the same machine. If one account installs and another does not, the fault is licensing or profile state rather than the pipeline.
- If several machines on one network fail together while a hotspot works, stop troubleshooting the devices.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80070141 |
Decodes to Win32 error 321, ERROR_DEVICE_UNREACHABLE, ‘the device is unreachable’. No Microsoft page publishes a Store-specific meaning, so treat the decode as direction rather than diagnosis | Microsoft Learn |
0x803FB005 |
Seen from the Store client when an install or update fails. No Microsoft page publishes a meaning; diagnose it by the stage it fails at rather than by the number | not published by the vendor |
0x80D02017 |
Seen on the content delivery side of a Store install. No Microsoft page publishes a meaning; treat it as a download-stage failure and check the services and the network path | not published by the vendor |
Confirm the fix worked
- All six services in the table are running and set to their default startup types.
- A test install of a small free application completes rather than sitting at Pending.
Get-AppxLogfor that install shows staging and registration completing.- The application launches and updates without returning to Pending on the next check.
Questions people ask about this
What does wsreset.exe actually do, and how long should it take?
It resets the Store cache. Microsoft’s description is that a blank Command Prompt window opens and after about ten seconds it closes and the Store opens automatically. If it sits there longer, give it a minute before assuming it has hung.
Does 0x80070141 mean my network is broken?
It decodes to ERROR_DEVICE_UNREACHABLE, but no Microsoft page ties that code to the Store, so it is a hint rather than a verdict. Use it as a reason to test the same account on another network early, rather than spending an hour on the cache first.
The Windows Store Apps troubleshooter is missing from Settings.
That is expected on newer builds. The legacy inbox troubleshooters run on the Microsoft Support Diagnostic Tool, which Microsoft has deprecated and says will be removed in a future release of Windows. Use the service checks and wsreset instead.
Why do the same apps install fine for another user on this machine?
Because licensing and registration are per user. A profile whose licence cache or registration state is damaged fails while the machine-wide pipeline is healthy. Test with a new profile before spending time on the services.
