The "Couldn't download this app" error in the Microsoft Store is one of the most frustrating roadblocks Windows users encounter. Think about it: it appears without warning, often providing a generic error code like 0x80070005, 0x80073CF9, or simply a "Try again" button that never works. Whether you are trying to install a productivity suite, a game from Xbox Game Pass, or a simple utility, this failure halts productivity and creates unnecessary confusion. Understanding why this happens and applying the correct fixes in the right order can restore the Store’s functionality without requiring a full system reset.
Understanding Why the Microsoft Store Fails to Download Apps
Before jumping into solutions, it helps to understand the underlying architecture. But the Microsoft Store is not just a simple website wrapper; it is a Universal Windows Platform (UWP) application deeply integrated with the Windows Update service, the Background Intelligent Transfer Service (BITS), and the Windows License Manager Service. A failure in any of these dependencies triggers the download error Small thing, real impact..
Common root causes include corrupted local cache files, outdated Windows components, incorrect system time or region settings, conflicting antivirus software, and corrupted system files. Sometimes, the issue stems from a stuck update for the Store app itself, creating a paradox where you need the Store to update the Store. Identifying the specific trigger allows for a targeted fix rather than a shotgun approach.
This changes depending on context. Keep that in mind.
Quick Preliminary Checks
Start with the basics before moving to advanced troubleshooting. These steps resolve a surprising number of cases instantly.
- Check Internet Connectivity and Speed: Ensure you have a stable connection. Try loading a webpage in Edge or Chrome. If using a VPN or proxy, disable it temporarily; the Store often blocks downloads over non-standard network routes.
- Verify Date, Time, and Region: Go to Settings > Time & Language > Date & Time. Turn on "Set time automatically" and "Set time zone automatically." Crucially, check Region settings. The Store relies on your region to determine app availability. Set "Country or region" to your actual location (e.g., United States, United Kingdom).
- Check for Windows Updates: The Store requires specific underlying OS updates to function. handle to Settings > Windows Update and click "Check for updates." Install any pending updates and reboot.
- Sign Out and Back In: Open the Microsoft Store, click your profile icon in the top right, select your account, and choose "Sign out." Close the app, reopen it, and sign back in. This refreshes the licensing token.
Method 1: Run the Windows Store Apps Troubleshooter
Windows includes a built-in diagnostic tool designed specifically for UWP app issues. It automatically resets cache folders and re-registers the Store manifest.
- Press Win + I to open Settings.
- Go to System > Troubleshoot > Other troubleshooters.
- Locate Windows Store Apps and click Run.
- Follow the on-screen prompts. The tool will detect issues like "Cache may be corrupted" or "Security settings are incorrect" and attempt to fix them automatically.
- Restart your computer once the process finishes and try the download again.
Method 2: Reset the Microsoft Store Cache (WSReset.exe)
This is the single most effective fix for the "Couldn't download this app" error. It clears the local cache without deleting your installed apps or account settings.
- Press Win + R to open the Run dialog.
- Type
wsreset.exeand press Enter. - A blank Command Prompt window will appear. Do not close it. Wait approximately 30–60 seconds.
- The window will close automatically, and the Microsoft Store will launch with a clean cache.
- Attempt your download immediately.
If wsreset.Because of that, exe fails to launch or hangs indefinitely, you can manually clear the cache folder:
- WindowsStore_8wekyb3d8bbwe\LocalCache
, and hit Enter. Delete all files inside this folder (press Ctrl+A, then Delete). Press **Win + R**, type%localappdata%\Packages\Microsoft.Day to day, 2. Worth adding: 3. Restart the Store.
Method 3: Re-register the Microsoft Store via PowerShell
If the cache reset fails, the Store app package itself might be unregistered or corrupted. PowerShell can force a re-registration of the app manifest Small thing, real impact. Worth knowing..
-
Right-click the Start button and select Terminal (Admin) or PowerShell (Admin).
-
Copy and paste the following command exactly, then press Enter:
Get-AppXPackage *WindowsStore* -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} -
Wait for the process to complete. Ignore any red text errors regarding "AppXManifest.xml not found" for other packages; focus on the WindowsStore line.
-
Reboot the system.
Method 4: Repair or Reset the Store App via Settings
Windows 10 and 11 allow you to repair or reset UWP apps directly from the Settings menu, which fixes corrupted internal files Still holds up..
- Open Settings > Apps > Installed apps (or Apps & features in Windows 10).
- Scroll down to Microsoft Store, click the three-dot menu (...), and select Advanced options.
- Scroll down to the Reset section.
- Click Repair first. This attempts to fix files while keeping your data. Test the Store.
- If Repair fails, click Reset. Warning: This deletes the Store's local data (cache, preferences, sign-in status), effectively giving you a fresh install of the app.
- Reopen the Store, sign in, and retry the download.
Method 5: Verify Critical System Services
The Microsoft Store relies heavily on specific background services. If these are disabled or stopped, downloads will fail instantly with error codes like 0x80070422.
- Press Win + R, type
services.msc, and press Enter. - Locate the following services and ensure Startup type is set to Automatic (or Automatic (Delayed Start)) and Status is Running:
- Windows Update (wuauserv)
- Background Intelligent Transfer Service (BITS)
- Delivery Optimization (DoSvc)
- Windows License Manager Service (LicenseManager)
- If any are stopped, right-click > Start. If they are disabled, right-click > Properties > change Startup type to Automatic > Apply > Start.
- Restart your PC.
Method 6: Run System File Checker (SFC) and DISM
Corrupted Windows system files can break the Store’s ability to write to the protected WindowsApps folder. Running these command-line tools restores system integrity.
- Open Terminal (Admin) or PowerShell (Admin).
- Run the DISM tool first to repair the component store:
Wait for this to reach 100% (can take 5–15 minutes).DISM /Online /Cleanup-Image /RestoreHealth - Immediately run the System File Checker:
sfc /scannow - If SFC reports "Windows Resource Protection found corrupt files and successfully repaired them," reboot and test the Store.
Method 7: Check Storage Permissions and Drive Health
The Store downloads apps to the system drive (usually C:) by default, specifically to the hidden WindowsApps folder. Permission issues here are a major cause of error 0x80073CF9.
-
Open File Explorer, handle to This PC > Local Disk (C:).
-
Click the View tab (Windows 11: View > Show) and check Hidden items Took long enough..
-
Locate the WindowsApps folder. Right-click it > Properties > Security tab.
-
Click Advanced. Ensure the following principals have Full Control (or at least Read & Execute + List folder contents for SYSTEM/Administrators, and Read for ALL APPLICATION PACKAGES):
- SYSTEM
- Administrators (your admin group)
- ALL APPLICATION PACKAGES (Critical for UWP apps)
- ALL RESTRICTED APPLICATION PACKAGES
-
If any are missing, click Add > Select a principal, type the name (e.g.,
ALL APPLICATION PACKAGES), click Check Names, then OK. Grant Full Control (applies to "This folder, subfolders and files") Small thing, real impact.. -
Click Apply > OK. Windows will propagate permissions; this may take several minutes.
-
Check Drive Health: Open Terminal (Admin) and run
chkdsk /f /r C:. TypeYto schedule on next reboot. Restart and let the scan complete (this fixes file system corruption causing write errors) It's one of those things that adds up..
Method 8: Re-register the Microsoft Store via PowerShell
If the AppX manifest is corrupted, the Store essentially "uninstalls" itself from the user profile. Re-registering forces Windows to re-read the manifest and reinstall the app container.
- Right-click Start > Terminal (Admin) or PowerShell (Admin).
- Run the following command exactly (copy/paste to avoid typos):
Get-AppXPackage -AllUsers -Name Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -Verbose} - Ignore any red text regarding "AppXManifest.xml not found" for other packages if they appear; focus on the Microsoft.WindowsStore line.
- Once the prompt returns, restart the computer and launch the Store.
Method 9: Verify Region, Date/Time, and Proxy Settings
The Store enforces strict geo-licensing and SSL certificate validation. Mismatched system clocks or active proxies break the handshake with Microsoft's CDN.
- Date/Time: Settings > Time & Language > Date & Time. Enable Set time automatically and Set time zone automatically. Click Sync now.
- Region: Settings > Time & Language > Language & Region. Set Country or region to your actual physical location (matches your Microsoft account billing address).
- Proxy/VPN: Settings > Network & Internet > Proxy. Turn Off "Use a proxy server" (unless mandated by corporate IT). Disable VPNs temporarily—many commercial VPN IPs are blocklisted by the Microsoft Store CDN.
Method 10: Create a New User Profile
Corrupted user-profile registry hives (NTUSER.DAT) or AppData folders can isolate the Store failure to a single account. This is the definitive test for profile corruption.
- Settings > Accounts > Other users (Windows 11) / Family & other users (Windows 10).
- Click Add account > I don't have this person's sign-in information > Add a user without a Microsoft account.
- Name it
TestUser, set a password, and answer security questions. - Sign out of your current account and sign in as
TestUser. - Open the Store immediately. If it works, your primary profile is corrupted. Migrate data (Documents, Pictures, Desktop) to the new profile via
C:\Users\OldUser>C:\Users\TestUserand switch permanently.
Method 11: Perform an In-Place Upgrade Repair (Nuclear Option)
If all above methods fail, the Windows component store (WinSxS) or servicing stack is damaged beyond DISM/SFC repair. An in-place upgrade reinstalls the OS kernel and system apps while keeping all files, apps, and settings Surprisingly effective..
-
Go to the official Microsoft Software Download page (search "Download Windows 11" or "Download Windows 10").
-
Download the Media Creation Tool (or ISO for Windows 11).
-
Run
MediaCreationTool.exe(or mount ISO >Setup.exe) Easy to understand, harder to ignore.. -
Accept license terms > Choose "Upgrade this PC now".
-
Critical: On the "Ready to install" screen, click Change what to keep > Select Keep personal files and apps The details matter here..
-
Let the
-
Let the upgrade complete (typically 30–90 minutes). The PC will restart several times. Do not interrupt the process That's the whole idea..
-
After the final reboot, sign in and launch the Microsoft Store. The in-place upgrade re-registers all system apps and resets the Windows component store to a known-good state, which resolves even deeply corrupted Store dependencies That's the whole idea..
Final Thoughts
The "AppXManifest.And xml not found" error—and its many Store-launch cousins—almost always traces back to one of three root causes: a corrupted package registration, a damaged system component store, or a profile-specific fault. Work through the methods in order, starting with the least invasive (WSReset, PowerShell re-registration) and escalating only when necessary. Most users will find relief by Method 4 or 5; the later methods exist for the stubborn minority whose corruption has burrowed into WinSxS or the user hive.
Before resorting to Method 11, always create a full system image backup (Control Panel > Backup and Restore > Create a system image) or at least verify that File History is current. An in-place upgrade is safe by design, but no repair is risk-free Easy to understand, harder to ignore..
If the Store still refuses to launch after a clean in-place upgrade, the problem is likely external: a group policy blocking Store access (common on domain-joined machines), a third-party antivirus filter driver, or a hardware-level issue such as failing storage. In those cases, check Event Viewer > Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server for specific error codes, and consider posting the relevant entries to Microsoft's Q&A forums or the Windows subreddit with your Windows build number (winver) for targeted help.
Above all, resist the temptation to download "Store fixer" tools from third-party sites—they frequently bundle adware or worse. That said, the built-in PowerShell cmdlets and DISM/SFC utilities are the only repair mechanisms Microsoft supports, and they are more than sufficient when applied methodically. With patience and the steps above, your Store should be back online without a full reinstall.