Error 0x80070005 in Windows: What It Means and How to Fix It

1Identify where access was denied

0x80070005 is generic by design: it only means a write was refused. What changes everything is the context it appears in. Spending a minute identifying that context saves running half a dozen commands unrelated to your case.

1. If the error appears on the Windows Update screen, go straight to Solution 3, then to Solution 4 if it returns.
2. If it appears while installing or updating a downloaded program, start with Solution 2.
3. If it appears while opening or updating a Windows store app, Solution 7 is the specific route.
4. If it appears when trying to restore the system or run a backup, the most common cause is third-party antivirus, covered in Solution 4.
5. If the message quotes a folder path or a file name, note that path: Solution 5 fixes exactly that scenario.
6. If the error shows up in varied situations with no pattern, skip to Solutions 6 and 8, which cover system corruption and a damaged profile.

2Run as administrator and confirm your account type

Installers need to write into system folders and register settings, and none of that works with standard account permissions. Right-clicking and choosing run as administrator clears a large share of installation cases. If your account is not an administrator, even that option will not help, which is why both points are worth checking together.

1. Right-click the installer or the program shortcut and choose run as administrator.
2. If the confirmation window asks for an administrator password, that tells you your account is a standard one.
3. Open Settings, go to the accounts area and check whether your name is marked as administrator.
4. If it is a standard account and the computer is yours, change the account type in the accounts area, or ask whoever has administrator access to change it.
5. If the program is already installed and the error appears only when opening it, open the shortcut's properties, go to the compatibility tab and tick the option to run as administrator to make it permanent.
6. Avoid using the system's hidden administrator account to work around the problem. It switches off important protections and creates other risks.

3Fix Windows Update: troubleshooter and clearing the updates folder

When 0x80070005 shows up in Windows Update, the source is almost always the folder where updates are downloaded before installing. If a download stopped halfway or a file got stuck, every later attempt fails at the same point. Renaming that folder makes Windows build a fresh one, and it is safe: none of your data lives in there.

1. Open Settings, go to the troubleshooting area and run the Windows Update troubleshooter. It handles the simplest cases by itself.
2. If the error returns, open Command Prompt as administrator and run the commands alongside, in order, one line at a time.
3. Wait for each command to finish before running the next. The first two stop the update services, and without that the folder cannot be renamed.
4. Restart the computer and try updating again. The first download takes longer, because Windows rebuilds the folder from scratch.
5. If you would rather avoid commands, you can stop the services in the Services app and rename the folder in File Explorer, with the same result.
6. If it still fails, move on to Solution 4: third-party antivirus blocking that folder is the next most common cause.

net stop wuauserv
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits

4Pause third-party antivirus for a few minutes

This is the most common hidden cause of 0x80070005, and the one that shows up least in the error messages. Third-party protection software often includes a layer that blocks writes to system folders, and it stops installers and the update service without saying so clearly. The test is quick and reversible, and the result is conclusive.

1. Open your antivirus dashboard and look for the option to pause protection for fifteen or thirty minutes, rather than uninstalling it.
2. Disconnect the computer from the internet if protection will be off for longer than the test itself.
3. Repeat the operation that was failing. If it works now, you have found the culprit.
4. Turn protection back on immediately after the test, even if the operation took a while.
5. If the antivirus really is the problem, look in its settings for the exclusions list and add the folder of the program you are installing, rather than leaving protection off.
6. Optimisation and cleanup tools count here too: several of them alter system folder permissions and cause exactly this error.

5Fix permissions on the folder or file named in the error

When the message points at a specific path, the repair is direct: give ownership and full access back to the administrators group. This happens often with folders copied from another computer, files from an old disk, or after an old program changed the permissions. One warning: changing permissions on system folders without need can cause bigger problems, so do this only on the folder the error names.

1. Right-click the folder or file, open Properties and go to the Security tab.
2. Click Advanced and look at the owner at the top of the window. If it is neither your account nor the administrators group, click change and enter your account name.
3. Tick the option to replace the owner on subcontainers and objects when it is a folder with content inside.
4. Go back to the Security tab, click Edit, select the administrators group and tick full control.
5. Apply, close the windows and repeat the operation that was failing.
6. If you prefer to do it by command, open Command Prompt as administrator and use the two commands alongside, replacing the example path with the real one from the error message.

takeown /f "C:\path\to\folder" /r /d y
icacls "C:\path\to\folder" /grant Administrators:F /t

6Check and repair system files

If the error appears in varied situations with no clear pattern, Windows' own files may be corrupted, and with them the components responsible for applying permissions. The two system repair tools work as a pair: the first compares files against reference copies, and the second repairs the source of those copies.

1. Open Command Prompt as administrator. Right-click Start and choose the terminal or prompt option with administrator permission.
2. Run the first command and wait for the bar to reach one hundred per cent. It can take twenty minutes or more.
3. If it reports corrupted files it could not fully repair, run the second command, which needs an internet connection.
4. Once the second one finishes, run the first again. That order is what makes the pair effective.
5. Restart and repeat the operation that was failing.
6. Do not interrupt either command partway through. Interrupting can leave the system in a worse state than it was.

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

7Fix the error when it appears in the app store

Windows store apps keep data in their own area of the profile, and 0x80070005 in that context almost always comes from a damaged cache or an app with an incomplete installation. The route here differs from the rest of the guide, because it is not about folder permissions but about repairing the app itself.

1. Open Start, type the store reset command shown alongside and run it. An empty window opens and closes by itself, and the store restarts afterwards.
2. If the error is on one specific app, open Settings, go to the installed apps list and find that app.
3. Open its advanced options and use the repair option first, which keeps your data.
4. If that does not help, use the reset option, which deletes that app's local data and returns it to a freshly installed state.
5. Also confirm the computer's date and time are correct, including the time zone. A wrong clock causes validation failures that surface as access denied.
6. If the problem hits every store app rather than one, a damaged profile is the likely cause: go to Solution 8.

wsreset.exe

8Test on a new administrator account

This is the decisive test when nothing else explains the error. A damaged user profile applies permissions inconsistently and produces access denied messages with no pattern. Creating a new account takes two minutes and answers once and for all whether the problem is the system or that profile, without deleting anything from the current one.

1. Open Settings, go to the accounts area and add a new local user for this computer.
2. Once created, change that new account's type to administrator.
3. Sign out of your account, sign in to the new one and repeat the operation that was failing.
4. If it works on the new account, your profile is damaged. In that case, move your personal files across through the documents, pictures and desktop folders, and start using the new account.
5. If the error happens on the new account too, the problem is the system rather than the profile. Go back to Solutions 4 and 6, which cover external blocking and system file corruption.
6. If nothing works and the error blocks security updates, the next step is a Windows in-place repair upgrade, which keeps files and programs. Make a backup first, because any large repair deserves that precaution.