How to fix Microsoft Store error 0x8007000A?

Error 0x8007000A stops Microsoft Store from installing or updating apps. It is Windows error 10, "The environment is incorrect", and reports from users tie it to the Windows user account more than to the app. Reset the Store first, then test the install from a second account.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What error 0x8007000A means

Codes that start with 0x8007 carry a normal Windows system error inside them. The last four digits, 000A, are hexadecimal for 10. Microsoft's list of system error codes names error 10 ERROR_BAD_ENVIRONMENT and describes it in four words: "The environment is incorrect."

So the code does not say the app is broken or the download failed. It says the installer found the setting it works in to be wrong. Microsoft does not document which part of that setting the Store checks, and we could not confirm it. User reports on Microsoft Q&A do show where it lives. In one case every install failed with Code: 0x8007000A, while the same app installed fine from a new local account. The error ended once Windows built a fresh profile for the main account.

What users see

An install or update in Microsoft Store that stops with Code: 0x8007000A. Users name the Photos app, Screenshots and sketches, Windows app updates and Sea of Thieves.

The bad sign

If Get-AppxPackage in PowerShell fails with the same code, the problem is deeper than the Store: the app system cannot read your account's app list. Skip to Fix 2.

What it is not

Not a network error and not a licence problem. One user changed the network to a phone hotspot and the region to United States, and the error stayed.

Why 0x8007000A appears: the causes, ranked

Most often the Store's cache or app state is damaged, and a reset clears it. Less often the problem is your Windows user profile: its settings, folders or app registrations. Rarely the Windows installation itself is damaged. A second account tells the last two apart in ten minutes.

How to fix error 0x8007000A in Microsoft Store

Fix 1 takes five minutes and is the first thing to try. Fix 2 is a test, not a repair, and decides the rest: if the app installs from a new account, Fixes 3, 4 and 6 repair your profile. If it fails there too, Fixes 5, 7 and 8 repair Windows.

Fix 1. Restart, clear the Store cache and repair Microsoft Store

5 minutesLow riskEveryone, first. Most of all when installs fail but the Store itself opens and browses.

A damaged Store cache or an update that waits for a restart leaves the installer in a bad state. A full restart, wsreset and Repair put the Store back to a clean state without touching your apps or purchases.

Restart the PC with Start > Power > Restart, not Shut down: with fast startup on, Shut down does not start Windows fresh. Then clear and repair the Store.

1. Clear the Store cache. Press Windows + R, type wsreset.exe and select OK. A blank Command Prompt window opens; after a short while it closes and Microsoft Store opens by itself.

   

2. Open System components. If the problem stays, select Start > Settings > System > System components. Next to Microsoft Store, select the three dots and Advanced options. If Microsoft Store is not listed there, look for it in Settings > Apps > Installed apps.

   

3. Repair first. Scroll to Reset and select Repair. Repair keeps the app's data. Open the Store and check whether it works.

   

4. Reset if Repair did not help. Select Reset and confirm. This deletes the Store app's data on this PC; your purchases stay in your Microsoft account. Open the Store and sign in again.

These steps were written for Windows 11 26H2 (build 26300). The full page with the other versions and what each result means: Reset the Microsoft Store

On Windows 11 the Store is under Settings > System > System components. On Windows 10 it is under Settings > Apps > Apps & features > Microsoft Store > Advanced options. You can also run the Windows Store Apps troubleshooter in Settings > System > Troubleshoot > Other troubleshooters; it finds cache and registration problems, but in the Q&A case above it did not clear this code.

Fix 2. Test the install from a new local account

10 minutesNo riskFix 1 did not help, or Get-AppxPackage fails with the same code.

Error 10 says the setting is wrong, and the setting is mostly your user profile. A new account starts with a clean profile, so the result tells you whether to repair your profile or Windows itself.

1. Open Other users. Open Settings > Accounts > Other users. You can also press Windows key + R and run the command below.

   ms-settings:otherusers

2. Add an account. Next to Add other user, select Add account.
3. Skip the Microsoft account. Select I don't have this person's sign-in information.
4. Choose a local account. Select Add a user without a Microsoft account.
5. Name the account. Type a user name and, if you want one, a password. If you set a password, Windows also asks for answers to security questions. Select Next.
6. Make it an administrator (optional). Back in Other users, select the new account, then Change account type next to Account options. Choose Administrator and select OK. For testing a problem, a standard account is usually enough.
7. Sign in to the new account. Open Start, select your account picture and choose the new account. The first sign-in takes a few minutes while Windows sets up the profile.

These steps were written for Windows 11 24H2, 25H2 and 26H2. The full page with the other versions and what each result means: Create a new user account to test a problem

1. Sign in to the new account and wait until the desktop is ready.
2. Open Microsoft Store. You can install free apps without signing in; for a paid app or game, sign in with your Microsoft account inside the Store only.
3. Install the app that failed, or a small free app.
4. Write down the result, then sign out and back in to your own account.

Fix 3. Check the TEMP and TMP variables of your account

5 minutesLow riskThe app installed from the new account but not from yours.

TEMP and TMP are part of your account's environment, the thing error 10 names, and installers write there. Microsoft does not confirm them as the cause of this code, but a wrong path is quick to find and to fix.

1. Press Win + R, type cmd and press Enter.
2. Type echo %TEMP% and press Enter, then echo %TMP%. Both normally show C:\Users\<your name>\AppData\Local\Temp.
3. Type dir "%TEMP%" and press Enter. If Windows says it cannot find the path, the folder is gone.
4. Press Win + R, paste rundll32 sysdm.cpl,EditEnvironmentVariables and press Enter.
5. Under User variables, select TEMP, then Edit, and set the value to %USERPROFILE%\AppData\Local\Temp. Do the same for TMP.
6. Select OK twice, restart the PC and try the install again.

Fix 4. Re-register Microsoft Store for your account with PowerShell

5 minutesLow riskThe account test pointed at your profile, and Get-AppxPackage still works in your account.

The Store's registration is stored per account. Registering it again from its own install folder renews that part of your profile without downloading anything.

1. Close Microsoft Store.
2. Select Start, type PowerShell and select Windows PowerShell. Open it the normal way, not as administrator, so the Store is registered to your own account.
3. Paste the first command below and press Enter. If it shows Name Microsoft.WindowsStore and an InstallLocation, go on. If it fails with 0x8007000A, stop here and use Fix 6.
4. Paste the three lines of the second command and press Enter. No red text means it worked.
5. Restart the PC and try the install again.

PowerShell: check that the Store package is there

Get-AppxPackage -Name '*WindowsStore*'

PowerShell: register the Store again for your account

$InstallLocation = Get-AppxPackage -Name '*WindowsStore*' | Select-Object -ExpandProperty InstallLocation
$ManifestPath = $InstallLocation + '\Appxmanifest.xml'
Add-AppxPackage -Path $ManifestPath -Register -DisableDevelopmentMode

The same steps for any one app, with pictures: How to re-register Microsoft Store apps with PowerShell

Fix 5. Start Windows in a clean boot and install again

15 minutesLow riskFixes 1 to 4 did not help, in your account or in the new one.

A clean boot starts Windows without services and startup apps from other companies. If the install works then, one of them changes the setting the Store installer runs in. A Microsoft Q&A advisor suggested this test for 0x8007000A.

1. Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
2. Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.

   

3. Disable the remaining services. Select Disable all, then select Apply.
4. Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.

   

5. Disable the startup apps. On the Startup apps tab in Task Manager, select each item whose status is Enabled and select Disable. Write down or take a screenshot of the items you disable: you need the list to turn them back on.

   

6. Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
7. Restart and test. Restart the PC. Windows now starts in a clean boot environment: try again the thing that failed (run the app, install the update, uninstall the program).

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to perform a clean boot in Windows

When the test is done, turn the services and startup apps back on in the same two places. If the install worked in the clean boot, turn them on in small groups until the error returns: the last group holds the program to update or remove.

Fix 6. Move to a new user profile and keep your files

30 to 60 minutesRead the warningThe app installs from the new account but never from yours, or Get-AppxPackage fails with 0x8007000A in your account.

When the profile itself is damaged, no single setting brings it back. In the Microsoft Q&A case, SFC, DISM, wsreset and the troubleshooter failed, and the error ended only when Windows built a fresh profile for the account.

1. Sign in to the test account from Fix 2, or create one now. In Settings > Accounts > Other users, select it, then Change account type and choose Administrator.
2. Sign in to the new account. To use your Microsoft account there, open Settings > Accounts > Your info and select Sign in with a Microsoft account instead. First remove that Microsoft account from the old Windows account, as Windows lets one Microsoft account sign in to only one account per PC.
3. Open File Explorer and go to C:\Users\<old account name>. Allow access when Windows asks.
4. Copy the folders you need (Desktop, Documents, Pictures, Videos, Music, Downloads) into the same folders of the new account. If your files are in OneDrive, sign in to OneDrive instead.
5. Install your Store apps again from Library in Microsoft Store.
6. After a week without problems, remove the old account in Settings > Accounts > Other users > Remove.

The reader on Microsoft Q&A renamed the old user folder so Windows rebuilt it on the next sign in. That also needs a change in the registry and can lock you out of the account, so the copy method above is the safer way to the same result.

Fix 7. Install updates and repair Windows system files

20 to 40 minutesLow riskThe app fails with 0x8007000A in every account, also in a clean boot.

When every account fails, the damage is in Windows itself: the files and components the Store installer uses. Windows Update brings newer copies, DISM fetches good files and SFC puts them back.

Open Settings > Windows Update (Windows 10: Settings > Update & Security > Windows Update), select Check for updates, install everything offered and restart.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

   

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

   

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

   

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

Fix 8. Reinstall Windows over itself and keep your files

1 hour or moreRead the warningLast, when the error appears in every account and Fixes 5 and 7 failed.

A repair install puts a fresh copy of Windows, the Store and the app system under your existing files and programs. It replaces the parts that the other fixes cannot repair.

1. Open Recovery in Settings. Open Settings > System > Recovery. Next to Fix problems using Windows Update, select Reinstall now. This keeps your apps, files and settings.

   

2. Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
3. Wait and restart. Windows Update downloads and installs a repair copy of your current Windows version. Keep the PC plugged in and online, and restart it when asked.
4. If that did not help: Reset PC. Back in Settings > System > Recovery, next to Reset this PC, select Reset PC. This keeps your personal files but removes installed apps and settings.
5. Choose Keep my files. Select Keep my files. Do not select Remove everything.

   

6. Choose where Windows comes from. Select Cloud download to download a fresh copy of Windows, or Local reinstall to use the files already on the PC (faster, but may not include the latest updates).
7. Reset. Review the summary and select Reset. The PC restarts several times.

These steps were written for Windows 11 22H2 and later. The full page with the other versions and what each result means: Reinstall Windows without losing files

One reader reported that the repair install itself stopped with 0x8007000A, and that even a clean reinstall from USB did not end it, while a fresh profile did. So if the account test in Fix 2 pointed at your profile, use Fix 6 before this one.

If 0x8007000A is still there

The code says only that the setting was wrong. The step that failed is written in the Windows event log for app installs, with the package name and a more exact code.

1. Right-click Start and select Event Viewer.
2. Open Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational.
3. Select Filter Current Log, tick Error and select OK.
4. Open the errors from the time of the failed install. Write down the package name, the error code and the text.

• What to send to Microsoft Support: those log lines, your Windows version from Settings > System > About, the result of the account test (Fix 2) and the fixes you tried.
• A work or school PC: the organization may limit the Store or app installs by policy. Ask the administrator before you change anything.
• When it is not software: this code does not point to hardware. If Windows also crashes or files get damaged, check the disk with Check a disk for errors (chkdsk).

How to keep 0x8007000A from coming back

The error follows a damaged setting, most often in the user profile. These habits keep the profile and the Store in a clean state, and make a move to a new profile painless if it ever comes to that.

Frequently asked questions

What does error code 0x8007000A mean?

It is Windows system error 10, ERROR_BAD_ENVIRONMENT, which Microsoft describes as "The environment is incorrect." In Microsoft Store it means the installer found the setting it runs in to be wrong, not that the app is broken. User reports tie it to the Windows user profile. Reset the Store first (Fix 1), then test the install from a new account (Fix 2).

Why does the app install from another account but not from mine?

Because the problem lives in your user profile, not in Windows or the app. Each account has its own folders, settings and app registrations. In the Microsoft Q&A case on this code, the same apps installed from a new local account, and the error ended only when Windows built a fresh profile for the main account. Check TEMP and TMP (Fix 3) and re-register the Store (Fix 4) first. If they do not help, move to a new profile (Fix 6).

Will a clean reinstall of Windows fix 0x8007000A?

Not for sure. One reader on Microsoft Q&A reinstalled Windows from a USB drive and still got the error, then fixed it with a fresh user profile. A repair install (Fix 8) keeps your files and replaces Windows, so it helps when every account fails. When only your account fails, a new profile (Fix 6) is faster and targets the real problem.

Is 0x800700a the same error?

Yes, 0x800700a is the same code typed with one zero missing. The full code always has eight digits after 0x: 0x8007000A. Uppercase and lowercase letters mean the same, so 0x8007000a and 0X8007000A are the same error too. Do not confuse it with 0x8007000B (error 11) or 0x8007000D (error 13, "The data is invalid."), which have other causes.

Does the network or region cause 0x8007000A?

Rarely, if ever. On Microsoft Q&A an advisor suggested a phone hotspot and the region United States, and neither helped the reader. A network fault usually shows its own codes, such as 0x80072EFD. If browsing in the Store works and only installs fail, the network is fine, so start with Fix 1 and the account test in Fix 2.

La app no me sale después del error. ¿Qué hago?

This page is in English, but the fixes work on a Spanish Windows. If the app does not appear after 0x8007000A, the install stopped before the app was registered. Reset the Store (Fix 1), then install the app again from Library in Microsoft Store. If the code comes back, test the install from a new account (Fix 2), which shows whether your profile or Windows is at fault.

Should I turn off my antivirus to fix 0x8007000A?

No, not as a fix. One reader turned it off and the error stayed. A clean boot (Fix 5) is the safer test: it starts Windows without services and startup apps from other companies, while Microsoft Defender keeps running. If you want to test a third party antivirus alone, pause it for one install and turn it back on at once: Turn off Microsoft Defender protection for a moment.

Will I lose my apps or purchases?

No. Your purchases are tied to your Microsoft account, not to the PC, and you can install them again from Library. A Store Repair keeps everything; a Store Reset only signs you out of the Store. A new profile (Fix 6) needs your Store apps installed again and your files copied over, so back up first and keep the old account until the new one works.

Can winget or PowerShell install the app when the Store fails?

Usually not. winget and PowerShell use the same app install system as the Store, so they stop at the same setting. One reader saw Get-AppxPackage fail with 0x8007000A too, and winget removed itself. That is a strong sign the user profile is damaged: run the account test in Fix 2 and, if it confirms, move to a new profile with Fix 6.