Fix Windows Store Error 0x80d02017 Easily

This guide walks you through fixing Windows Store error code 0x80d02017, which typically appears when downloading or updating apps and prevents the Store from completing the operation. The fix usually involves clearing a corrupted cache, resetting the Store app, or adjusting date/time and network settings.

What You’ll Need

• Administrator access to your Windows PC (to run commands in PowerShell or Command Prompt)
• A stable internet connection
• Your Microsoft account credentials (in case a re-sign-in is needed)

Step-by-Step

1. Close the Windows Store completely. Right-click the Store icon on the taskbar and choose “Close window,” or press Ctrl+Shift+Esc to open Task Manager, find “Microsoft Store” under Apps, right-click it, and select “End task.”
2. Run the Windows Store Apps troubleshooter. Go to Settings (Windows key + I) > System > Troubleshoot > Other troubleshooters. Scroll to “Windows Store Apps,” click “Run,” and follow the prompts. Let it apply any fixes it finds, then restart your PC and try the Store again.
3. Clear the Store cache using WSReset. Press Windows key + R, type wsreset.exe, and press Enter. A blank Command Prompt window will open; wait for it to finish (it may take a minute or two) and the Store should open automatically. If it doesn’t, open the Store manually and try your download again.
4. Reset the Microsoft Store app via Settings. Go to Settings > Apps > Installed apps, find “Microsoft Store,” click the three-dot menu next to it, choose “Advanced options,” then click “Reset.” Confirm when prompted. This clears the app’s data without removing it. Restart your PC afterward.
5. Check your system date and time. Right-click the clock in the taskbar, select “Adjust date and time,” and ensure “Set time automatically” and “Set time zone automatically” are both toggled on. If they are already on, toggle them off, wait a few seconds, and toggle them back on. Then sync the clock by clicking “Sync now” under “Additional settings.”
6. Re-register the Store app with PowerShell. Right-click the Start button and select “Terminal (Admin)” or “Windows PowerShell (Admin).” Copy and paste this command, then press Enter:
   Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
   Wait for it to complete, then close the window and restart your PC.
7. Check your network proxy and VPN settings. If you use a VPN or proxy, temporarily disconnect from it and try the Store again. Also go to Settings > Network & Internet > Proxy and make sure “Use a proxy server” is off unless you specifically need it.
8. Run the DISM and SFC system file checks. Open an admin Terminal or PowerShell window and run these commands one at a time, pressing Enter after each:
   DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
   Let each finish completely (this can take 10–20 minutes). Restart your PC after both complete.
9. Sign out and back into the Store. Open the Store, click your profile icon at the top right, choose “Sign out,” close the Store, reopen it, and sign back in with your Microsoft account.
10. Create a new local administrator account (last resort). Go to Settings > Accounts > Other users > Add account. Choose “I don’t have this person’s sign-in information,” then “Add a user without a Microsoft account.” Create the account, make it an administrator (under the same menu, click the account, then “Change account type”), sign into it, and test the Store there. If it works, you can migrate your files and switch to that account.

Common Mistakes

• Skipping the restart between steps. Several fixes (especially resets and re-registration) only take effect after a full restart. Rebooting after each major step saves time in the long run.
• Running PowerShell without admin rights. The re-registration command requires an elevated (administrator) window. If you get an access denied error, close and reopen the terminal as admin.
• Leaving a VPN or proxy on. Many Store errors, including 0x80d02017, are caused by network interference. Always test with VPN/proxy off before assuming a deeper issue.
• Not waiting for wsreset.exe to finish. The window may look stuck, but it is working. Closing it early leaves the cache half-cleared, which can make the problem worse.
• Ignoring date/time drift. Even a few minutes of clock skew can break the Store’s license verification. Always check this before more invasive fixes.

Tips

• Keep Windows Update current; many Store errors are fixed silently by cumulative updates. Check Settings > Windows Update > Check for updates after resolving the error.
• Use the Store’s built-in “Get updates” button (bottom left) after a successful fix to verify downloads work for all pending apps.
• If you have multiple user accounts on the PC, test the Store in another account early in the process. This quickly tells you whether the issue is system-wide or tied to your profile.
• Disable any third-party antivirus temporarily (not Windows Defender) to rule out file-access blocking. Re-enable it immediately after testing.
• Make sure your Windows installation is activated. An unactivated copy can cause Store errors because licensing services fail silently.

Troubleshooting

If the error persists after all steps, work through these checks in order:

• Check the Store’s service dependencies. Press Windows key + R, type services.msc, and press Enter. Find “Windows Update,” “Microsoft Store Install Service,” and “Background Intelligent Transfer Service.” Ensure each is set to “Automatic” (or “Manual” for the Store Install Service) and is currently “Running.” Right-click any stopped service and select “Start.”
• Look at the event logs. Open Event Viewer (Windows key + R, type eventvwr.msc), go to Windows Logs > Application, and look for errors with source “AppXDeployment-Server” or “Microsoft-Windows-Store.” The details may point to a specific corrupted package that you can remove with PowerShell using Get-AppxPackage | Remove-AppxPackage for that app, then reinstall it from the Store.
• Try a different network. Connect your PC to a mobile hotspot or a different Wi-Fi network. If the Store works there, the problem is your router or ISP. Power-cycle your router and check if any parental controls or firewall rules block Microsoft’s servers.
• Perform a clean boot. Type msconfig in the Run dialog, go to the Services tab, check “Hide all Microsoft services,” click “Disable all,” then go to the Startup tab and open Task Manager to disable all startup items. Restart and test the Store. If it works, re-enable services in batches to find the culprit.
• Check for disk corruption. Open an admin Command Prompt and run chkdsk C: /f. You’ll need to restart to let it run. This is slower but catches file-system issues that DISM and SFC miss.
• As a final step, consider an in-place upgrade repair. Download the Windows 11 Installation Assistant (or the Windows 10 Media Creation Tool) from Microsoft’s official site and run it while keeping your files and apps. This reinstalls the OS core without wiping your data and resolves most persistent Store corruption.

Frequently Asked Questions

Q: Will resetting the Store delete my installed apps?
A: No. Resetting the Store only clears its cache and settings. Your installed apps and their data remain untouched.

Q: Why does error 0x80d02017 happen in the first place?
A: It’s most often caused by a corrupted Store cache, a misconfigured system clock, or network interference from a VPN/proxy. Less commonly, it stems from a damaged Windows component store.

Q: Can I fix this without admin rights?
A: The wsreset.exe step and the Settings reset work without admin rights. The PowerShell re-registration and DISM/SFC commands require admin. If you don’t have admin access, contact your IT department or the account owner.

Q: How long does the wsreset.exe command take?
A: Usually 30 seconds to 2 minutes. If it takes longer than 5 minutes, close the window, restart your PC, and try the Settings-based reset instead.

Q: Will this error go away after a Windows update?
A: Sometimes yes, if the cause is a known bug. But if the cache or clock is the issue, an update won’t help. Run the steps above first, then check for updates.

Q: Is there a way to prevent this error from returning?
A: Keep your clock set to automatic, avoid third-party proxy tools unless necessary, and periodically run wsreset.exe if you notice the Store acting slow. Regular Windows updates also help.

Related

• iPad Handwriting Text Feature: Tips & Tricks
• Why Are My USB Ports Not Working on Laptop?
• Fix Dragon’s Dogma 2 Crashes, Stuttering & Low FPS