So, your problem is solved, right?
Microsoft store fails to install anything: Code: 0x80070005
I am utterly at my wits end at this point. I've tried the following:
- Check if doesn't have any corrupt files on the windows.
- Right-Click on Start then click on Windows Powershell (admin)
- Type these commands.
- sfc /scannow (and press Enter)
- Dism /Online /Cleanup-Image /ScanHealth (and press Enter)
- Dism /Online /Cleanup-Image /CheckHealth (and press Enter)
- It might be that something went wrong with the update files itself. Clearing the folder where all of the update files are stored will force Windows Update to download fresh files. Here how to clear update database cache, reset windows update components to the default setup.
- Press Windows + R, type services.msc and ok to open windows services.
- Scroll down and look for windows update service.
- Right-click on it and select stop.
- Also, do the same with BITs (Background Intelligent Transfer Service) and Superfetch (superfetch now called sysmain) right-click and select stop.
- Now Go to the following location C:\Windows\SoftwareDistribution\Download.
- Delete everything inside the download folder, but do not delete the folder itself. To do so, press CTRL + A to select everything and then press Delete to remove the files. Again open windows services and restart the services (windows update, BITS) which you previously stopped.
- Reboot and try again
- Reinstall the Microsoft Store.
- Right click on Start.
- Click on Windows PowerShell(admin)
- Type: Get-AppXPackage -allusers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} and press ENTER.
- Reboot your pc and try open the Microsoft Store.
- I've also tried the Window App Store trouble shooter in settings.
The store can see the various bits I have on it, but it just fails to install anything, even the Xbox App.
I am actually really irritated by this; the act of buying something means it should download and work and not flake out so badly.
Any ideas of what to do would be great.
Windows for home | Windows 10 | Microsoft Store
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
6 answers
Sort by: Most helpful
-
Anonymous
2023-08-10T02:06:09+00:00 None of these suggestions made any difference because they do not attack the cause: the error code indicates some kind of file permissions are out of wack often.
I gave up fighting the thing and simply reset the system (but keep files); after doing so, it worked. The main stink is the act of reset, a handful or programs need to be reinstalled (and/or reconfigured). The biggest stink is the awfulness of Epic (and EA) where all the games needs to be either downloaded again or a tedious ritual to get the launcher clients to recognize the previous downloads. Sighs. Atleast Steam did not have that issue.
-
Igor Leyko 111K Reputation points Independent Advisor
2023-08-09T23:33:57+00:00 Hi Kevin,
My name is Igor, it's a pleasure for me to help others and I'll do all my best to help you.
Do you install apps to a disk C: or to some other?
Please run command prompt as administrator, run
chkdsk C: /r /scan
command and show the result. Change drive letter if needed.
Try to restart wuauserv service.
-
Igor Leyko 111K Reputation points Independent Advisor
2023-08-10T00:16:18+00:00 Please check if the problem persists during clean boot and safe mode with networking.
-
Anonymous
2023-08-09T23:57:00+00:00 Try to restart wuauserv service.
I tried it, still got the exact same error message. Also, running the Xbox Installer directly also gives the exact same error code.
Do you install apps to a disk C: or to some other?
For MS Store, it is left as defaults; the machine has other drives where Steam, Epic and GOG stash their stuff.
chkdsk C: /r /scan
Output:
C:\WINDOWS\system32>chkdsk C: /r /scan
The type of the file system is NTFS.
Volume label is OS.
Stage 1: Examining basic file system structure ...
1130752 file records processed.
File verification completed.
Phase duration (File record verification): 12.14 seconds.
19429 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.18 milliseconds.
Stage 2: Examining file name linkage ...
622 reparse records processed.
1664560 index entries processed.
Index verification completed.
Phase duration (Index verification): 30.72 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 10.65 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.43 milliseconds.
622 reparse records processed.
Phase duration (Reparse point and Object ID verification): 5.85 milliseconds.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 85.31 milliseconds.
266905 data files processed.
Phase duration (Data attribute verification): 0.86 milliseconds.
CHKDSK is verifying Usn Journal...
33612832 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 127.91 milliseconds.
Stage 4: Looking for bad clusters in user file data ...
1130736 files processed.
File data verification completed.
Phase duration (User file recovery): 9.63 minutes.
Stage 5: Looking for bad, free clusters ...
56909117 free clusters processed.
Free space verification is complete.
Phase duration (Free space recovery): 0.00 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
376515583 KB total disk space.
147063512 KB in 844334 files.
564992 KB in 266906 indexes. 0 KB in bad sectors.1250611 KB in use by the system.
65536 KB occupied by the log file.227636468 KB available on disk.
4096 bytes in each allocation unit.94128895 total allocation units on disk.
56909117 allocation units available on disk.
Total duration: 10.52 minutes (631708 ms).
I ran it, the issue is not a drive issue, it is some awful software (likely config issue).