What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
“0x800700” is not a complete Microsoft Store error code. Copy the entire hexadecimal message before choosing a repair. The two common endings, 0x80070005 and 0x80070057, point to different problems: the first is an access-denied condition, while the second indicates invalid arguments or incorrect configuration and can also appear with corrupted files. Start with the low-risk Store checks below, then follow the branch that matches your complete code.
Why 0x800700 is not enough to diagnose the failure
Windows error codes contain a final two-digit portion that changes the meaning. A message truncated to 0x800700 does not tell you whether the Store lacks permission, received an invalid argument, or encountered another condition altogether. Open the full message, copy the code exactly, and note what was happening when it appeared:
As an Amazon Associate I earn from qualifying purchases.
- Opening the Microsoft Store
- Downloading an app
- Installing an app
- Updating an installed app
If the Store displays a longer message, copy that text too. The operation and the Windows build are useful when you need to escalate the problem. A code shown in a notification, Event Viewer entry, or PowerShell output can include extra digits or a different suffix, so do not infer the missing characters from a partial screenshot.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11The same prefix can also occur in Windows Update and AppX deployment messages. Those components share Windows servicing files, but they do not always need the same repair. Identify the component and operation first; otherwise, it is easy to reset the Store when the actual failure is Windows Update, or to change permissions when one app package is the only thing affected.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
The two likely completions at a glance
| Complete code | Meaning | Best first branch | Risk of initial checks |
|---|---|---|---|
0x80070005 |
Access denied (E_ACCESSDENIED). Permissions, security software, or policy can prevent access to protected Windows resources. |
Check account, policy, security software, and protected-folder permissions. | Low for cache reset and updates; advanced when permissions or ownership are changed. |
0x80070057 |
Invalid argument (E_INVALIDARG), or an associated configuration or file-corruption problem. |
Run the built-in troubleshooter and System File Checker, then inspect AppX deployment details if installation or registration is involved. | Low for the troubleshooter and SFC; increase caution before changing system configuration. |
Both branches use the same safe Store checks first. Do not apply permission changes intended for 0x80070005 simply because a message begins with 0x800700. If your final digits are different, use the complete code when searching Microsoft’s documentation or contacting support rather than forcing it into one of these two branches.
Run the low-risk Microsoft Store checks first
1. Record the failure precisely
Write down the complete code, the app involved, the operation that failed, and whether other Store apps behave the same way. Note your Windows edition and build from Settings > System > About. Record whether the problem affects one user or every account on the computer. This information prevents you from troubleshooting the wrong component and gives support a reproducible starting point.
If the error disappears after a restart and returns only for one particular app, note that pattern. If every download fails immediately, note that too. Timing is useful: an error before any download begins points to account, registration, policy, or network access, while a failure during package registration can point to AppX deployment or local file integrity.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →2. Reset the Store cache with wsreset.exe
- Press Win + R to open the Run dialog.
- Enter
wsreset.exeand press Enter. - Wait while a blank Command Prompt window appears. Microsoft says it closes after about ten seconds, and Microsoft Store then opens automatically.
- Try the original download, installation, or update again.
This clears the Store cache without deleting your installed applications. You may see no explanatory text while it runs; the blank window is expected. Do not type commands into that window or terminate it immediately. If the window remains open indefinitely, close it, restart Windows, and run the command once more. A persistent failure after the reset is evidence that the problem is not just stale cache data.
3. Install pending Windows and Store updates
Open Settings > Windows Update, select Check for updates, install everything offered, and restart when requested. Then open Microsoft Store, select your account or profile menu, open Library, and choose Get updates (the label can vary slightly by Windows release). Retry the same app after both update checks complete.
Do not interrupt a servicing update or force a shutdown while Windows is restarting. Store components and the Windows servicing stack can depend on the same system files. If Windows reports that a restart is pending, complete it before running another repair so that you are not diagnosing files that are still being replaced.
4. Check registration, firewall, proxy, and network access
Microsoft’s Store download-failure checklist calls for verifying that Store is registered for the affected user, can launch, and can download updates. It also calls for checking that required firewall or proxy endpoints are not blocked. Review these points in order:
- Sign in to Windows with the account that is failing and confirm that Store opens normally.
- Temporarily test a different network, such as a phone hotspot, if your organization’s network uses filtering or an authenticated proxy.
- Review Windows proxy settings at Settings > Network & internet > Proxy. Remove a proxy you do not recognize; if the device is managed, ask the administrator before changing it.
- Check firewall or endpoint-security logs for blocked Microsoft Store or update traffic. Do not permanently disable protection as a diagnostic shortcut.
- Where appropriate, use
wingetto test whether package installation works outside the Store interface. A successfulwingetoperation does not prove the Store registration is healthy, but a matching failure can show that the issue is broader than the Store app.
Store access can be affected by a corporate proxy, content filter, or security product even when ordinary websites load. Compare the timestamp of a blocked request with the Store failure and preserve the log entry. On a managed computer, policy may intentionally prevent Store downloads; changing the setting yourself can violate the organization’s configuration.
If Store is not registered for the user, use Microsoft’s current Store registration procedure for your Windows build rather than copying an old PowerShell command from an unverified source. Registration commands differ between releases and should be run exactly as documented. A registration repair should be performed for the affected user and followed by a restart or sign-out if Microsoft’s procedure requests it.
Branch A: Fix error 0x80070005 (access denied)
What this code means
Microsoft defines 0x80070005 as E_ACCESSDENIED. Microsoft describes it as a permissions problem affecting the Windows component store, the %windir%SoftwareDistribution folder, or related system resources. Other documented causes include registry permission problems, third-party security software locking files, missing rights for the SYSTEM account, and policy restrictions.
Because these locations are protected, changing permissions casually can make Windows Update, servicing, or Store failures worse. Work from the least invasive checks toward the advanced sequence only when the complete code is confirmed. An administrator account is not a reason to grant broad permissions to every user or to take ownership of system folders permanently.
Check account and policy conditions
- Confirm that the affected user can install other software and that the computer is not restricted by a work or school policy.
- If security software recently quarantined, locked, or monitored an installer, review its event log. Use the vendor’s documented exclusion or troubleshooting process instead of deleting protected files.
- Test with another local administrator account only to distinguish a user-profile problem from a system-wide problem. Do not assume that a second account fixes the original profile.
- Check whether the failure occurs only when a nonadministrator account uses Store. That distinction can indicate a per-user permission or registration issue, but it does not justify permanently running Store as administrator.
If a clean administrator account works while the original account fails, retain both results. Microsoft Support can use them to separate a profile-specific problem from a damaged component store. If every account fails in the same way, focus on system permissions, policy, servicing, and security software instead.
Back up before changing protected permissions
Microsoft’s escalation procedure says to back up the operating-system disk before changing permissions. Use a backup that you can restore, and make sure you know the recovery password or key if device encryption is enabled. A restore point alone is not a substitute for a restorable backup of important files.
Rank #2
- Emergency Boot USB compatible with Windows 98, 2000, XP, Vista, 7, and 10. It has never ben so easy to repair a hard drive or recover lost files
- Plug and Play type usb - Just boot up the usb and then follow the onscreen instructions for ease of use
- Boots up any PC or Laptop model and brand.
- Virus and Malware Removal made easy for you
- This is your one stop shop for PC Repair of any need!
Close open installers and save work before stopping update services. Record the original error and any command output so that you can explain exactly what changed. If the computer is managed or contains critical business data, involve the administrator before attempting the advanced sequence.
Apply Microsoft’s documented permission and ownership sequence
From an elevated Command Prompt (search for Command Prompt, right-click it, and choose Run as administrator), Microsoft’s sequence can include:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Resetting permissions on the WinSxS component store and the
SoftwareDistributiondirectory with the exacticaclscommands in Microsoft’s current procedure. - Restoring TrustedInstaller ownership of WinSxS when the procedure requires it.
- Stopping the relevant Windows Update services, renaming
SoftwareDistributionandcatroot2, and starting the services again to rebuild those caches.
These steps are deliberately described as a sequence rather than a collection of interchangeable commands. Services must be handled in the order Microsoft specifies, and the ownership of protected files must be restored rather than left assigned to an administrator account. The renamed folders are rebuilt by Windows; they are not permission targets to edit at random.
Do not substitute commands from a forum post or remove inherited permissions by guesswork. The command syntax, service names, and ownership steps must match the Windows version you are running. If you cannot verify the current Microsoft procedure, stop at the low-risk checks and contact Microsoft Support rather than experimenting with the registry or protected folders.
Repair the component store and system files
After the documented permission and component-reset steps, run these commands in the elevated Command Prompt, one at a time:
- Enter
DISM /Online /Cleanup-Image /RestoreHealthand wait for it to finish. - Enter
sfc /scannowand allow the verification to reach 100 percent. - Restart Windows, open Store, and repeat the operation that originally failed.
DISM repairs the Windows component image that SFC uses; SFC then checks protected system files. Closing the window early or restarting during either scan can leave the repair incomplete. If either command reports that it could not complete the operation, preserve the exact message for support instead of repeatedly rerunning it. The result saying files were repaired, files could not be repaired, or no integrity violations were found is all useful diagnostic evidence.
Branch B: Fix error 0x80070057 (invalid argument or configuration)
What this code means
Microsoft’s AppX deployment diagnostics define 0x80070057 as One or more arguments are not valid.
Microsoft’s Windows troubleshooting guidance also associates the code with corrupted files, permission issues, or incorrect system configuration. The context matters: an AppX registration or package-installation failure points toward deployment diagnostics, while a broader Windows servicing failure may need file and configuration repair.
This code does not automatically mean that the Store package itself is defective. A malformed configuration value, damaged system file, or invalid parameter passed during registration can produce the same hexadecimal result. Capture the package name and the operation before removing anything.
Run the built-in troubleshooter and SFC
- Open Settings > System > Troubleshoot > Other troubleshooters.
- Run the troubleshooter relevant to Windows Update or Store availability on your Windows release, and apply only the changes it recommends.
- Open an elevated Command Prompt and run
sfc /scannow. - Restart Windows and retry the Store action.
If SFC reports that it found and repaired files, retry after the restart. If it reports that some files could not be repaired, run the DISM command from the previous branch, restart, and run SFC again once; retain the final result for escalation. Do not interpret a clean SFC result as proof that Store registration or network access is healthy—those are separate checks.
Collect AppX deployment evidence before invasive changes
When the failure occurs during package installation, registration, or an update, inspect the related AppX deployment event details in Event Viewer before changing permissions. Look for the timestamp matching the failed attempt, the package name, the user account, and the full error text. This can distinguish an invalid package argument from a Store-wide networking or servicing problem.
Recommended Free Tools
Keep the event details in a text file, including the event source and error code. A warning that occurs at another time may be unrelated. Do not delete AppX packages, reset permissions, or edit the registry solely because an event log contains a warning. Match the event to the exact failed operation and keep a copy of the details.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.If the Store still fails after the correct branch
Check that you are not mixing Store and Windows Update symptoms
The same hexadecimal prefix can appear in Windows Update, AppX deployment, and Store messages. If Windows Update itself fails with the code, follow the Windows Update troubleshooting path rather than repeating Store cache resets. If only one app fails while other Store apps install normally, the package or its account requirements may be the narrower problem.
Try one unrelated free app only as an isolation test, not as a permanent workaround. If the unrelated app installs, document the original app’s name and version and focus escalation on its package or account requirement. If every app fails at the same stage, the Store, network, registration, or servicing environment is more likely involved.
Rank #3
- Fresh USB Install With Key code Included
- 24/7 Tech Support from expert Technician
- Top product with Great Reviews
Prepare an escalation record
- The complete hexadecimal code and the full text beside it
- The operation that failed: launch, download, install, or update
- Windows edition, version, and build
- Whether
wsreset.exe, Windows updates, and Store updates completed - Whether Store is registered for the affected user and whether a different network changed the result
- The output from DISM and SFC, including any lines saying that repairs were incomplete
- Relevant AppX deployment or firewall/proxy event entries with matching timestamps
Use Microsoft Support when the documented sequence does not resolve the problem, when permission or ownership commands produce unexpected output, or when the device is managed by an organization. Support can match the exact build and servicing state to the current procedure. Include whether the issue is reproducible in another account and whether it affects Store alone or Windows Update as well.
Common mistakes to avoid
- Treating 0x800700 as a complete code: always capture the final digits.
- Starting with registry cleaners or permission resets: these are not low-risk substitutes for cache reset, updates, and diagnostics.
- Disabling antivirus or firewall protection permanently: inspect logs and use documented, temporary troubleshooting steps instead.
- Renaming system folders without stopping services: follow the Microsoft component-reset order exactly.
- Repeating DISM or SFC without recording results: the output is evidence that helps identify whether the component store or protected files remain damaged.
- Using an old Store-registration command: registration procedures and interface labels can vary by Windows release.
- Assuming a paid utility is required: the built-in cache reset, updates, troubleshooter, DISM, and SFC are the documented starting tools.
As an optional shortcut after the manual checks, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements, invalid redirects, shared DLL files, settings that increase CPU, RAM or disk load, temporary and cache files, privacy warnings, vulnerability checks, and app-crash logging. It runs on Windows 11, 10, 8 and 7; its category-based free trial lasts at least two days before a paid subscription. It complements antivirus software, does not replace it, and results vary—no repair tool fixes every crash.
No physical product is required for the documented Store fixes. A generic repair USB, registry cleaner, or antivirus purchase would not address the specific permission, registration, configuration, or AppX evidence described here and could add risk instead of solving the underlying failure.
Frequently Asked Questions
Is 0x800700 a complete Microsoft Store error code?
No. It is truncated. Copy the complete hexadecimal code and the accompanying message before selecting a repair. The final digits determine whether the documented branch is access denied, invalid arguments, or another condition.
What does Microsoft Store error 0x80070005 mean?
Microsoft defines 0x80070005 as E_ACCESSDENIED. It usually indicates a permissions problem involving the component store, SoftwareDistribution, related system resources, security software, SYSTEM rights, or policy.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhat does Microsoft Store error 0x80070057 mean?
AppX diagnostics define it as E_INVALIDARG, meaning one or more arguments are not valid. Microsoft also associates it with corrupted files, permission issues, or incorrect configuration, so the failed operation and event details matter.
Will wsreset.exe uninstall my Store apps?
No. The command resets the Microsoft Store cache. Run it from Win + R, wait for the blank Command Prompt window to close, and retry the operation when Store opens again.
Should I disable my antivirus or firewall to fix the error?
Do not permanently disable protection. Review security and firewall logs for blocked Store or update traffic and use only a vendor-documented, temporary troubleshooting step. On a managed device, ask the administrator first.
Do I need administrator rights for every step?
The cache reset, updates, and basic Store checks are ordinary user tasks. An elevated Command Prompt is required for DISM, SFC, and Microsoft’s advanced permission or component-reset sequence.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →What if only one Store app fails?
Test another app and record the original package name, operation, and code. If other apps work, the issue may be specific to that package or account requirement rather than a Store-wide failure.
What should I send Microsoft Support?
Provide the complete code and message, failed operation, Windows edition and build, Store and Windows update results, registration and network findings, DISM and SFC output, and matching AppX, firewall, or proxy events.
Do I have to buy a repair program or physical product?
No. Microsoft’s built-in wsreset.exe, updates, troubleshooter, DISM, and SFC are the documented starting tools. Optional repair software should be considered only after those checks, with claims and subscription terms verified.
The Bottom Line
Capture the full code before repairing. Run wsreset.exe, install Windows and Store updates, and verify registration and network access. For confirmed 0x80070005, treat the problem as access denied and use Microsoft’s protected-permission sequence only with a backup and exact current commands. For confirmed 0x80070057, start with the troubleshooter, SFC, and AppX event evidence. If the documented steps fail or produce unexpected results, contact Microsoft Support with your complete diagnostic record.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
