“0x800700” is not a complete Windows Update error code. The final characters identify the failure and determine the safe fix. For example, 0x8007000D usually points to damaged update files or cache data, 0x80070005 means access is denied, 0x80070002 indicates an update failed to install, 0x80070057 or 0x80080005 can involve corruption, permissions or configuration, and 0x8007000E indicates insufficient disk space. Start by recording the complete code and the KB update name, then work through the least-invasive repair steps below.
Why the full code matters
Windows displays hexadecimal codes in several places, and the shared 0x800700 prefix is only the beginning of a larger diagnostic value. The suffix changes both the likely cause and the remedy. Applying a permission reset to a disk-space problem, or deleting the update cache for a policy block, can waste time and create new problems.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
| Complete code | What it commonly indicates | Best starting point |
|---|---|---|
0x8007000D |
Windows Update files or cache corruption | Run the troubleshooter, then rebuild the update cache if needed |
0x80070005 |
Access denied or insufficient permissions | Check whether security software or policy is blocking writes; use the documented permission reset only after backing up |
0x80070002 |
The update failed to install | Confirm the update identity, services, connectivity and logs before choosing a repair |
0x80070057 |
Corruption, permissions or configuration problems | Use the general troubleshooting sequence and inspect logs if it persists |
0x80080005 |
Corruption, permissions or configuration problems | Use the general troubleshooting sequence and escalate when policy or security software is implicated |
0x8007000E |
Insufficient disk space | Free space on the Windows drive and retry; do not start with permission changes |
These categories come from Microsoft’s Windows Update troubleshooting guidance. They are starting points, not guarantees: the same suffix can have different underlying causes on a personally managed PC, a work or school device, or different Windows releases.
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 matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall1. Record the exact code and update
Find the complete error
Open Settings > Windows Update > Update history and locate the failed entry. Copy the full hexadecimal value, including every character after 0x800700. Also note the KB number or update name, the date of the failure and whether the update is a quality, feature, driver or security update. If Settings shows only a shortened value, check the installation message or update log for the complete code.
#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)
Why the KB number is useful
Two updates can fail for different reasons on the same computer. Recording the KB identifier lets you confirm that you are retrying the same package and gives support staff a precise target if the standard repairs do not work. Do not repeatedly install or remove random updates while the original failure is still unidentified.
2. Restart and run the built-in troubleshooter
Restart before changing anything
Save your work and restart Windows. A pending reboot can leave update services or files in an intermediate state. After Windows starts, connect to a reliable network and try Windows Update once. If the same code returns, continue with the troubleshooter rather than immediately changing permissions or the registry.
Current Windows path
- Open Settings.
- Select System, then Troubleshoot.
- Choose Other troubleshooters.
- Find Windows Update and select Run.
- Apply any repair the troubleshooter recommends, restart if prompted, and retry the recorded update.
Older Windows path
On older releases, the same tool appears under Settings > Update & Security > Troubleshoot. Labels can vary by edition and build. If the path on your PC differs, search Settings for troubleshoot Windows Update rather than downloading an unofficial fixer.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems3. Check the three conditions that commonly block updates
Connectivity
Confirm that ordinary websites load and that you are not switching between networks during the installation. A captive portal, unstable wireless link or filtering proxy can interrupt downloads. If the computer belongs to an organisation, its network policy may intentionally restrict update traffic; do not bypass that policy without the administrator’s approval.
Available disk space
Open Settings > System > Storage and check the free space on the drive containing Windows, normally C:. The 0x8007000E variant specifically points to insufficient disk space. Remove only files you recognise, empty the Recycle Bin if appropriate, and retry after Windows reports adequate free space. Do not assume that deleting unrelated system folders is safe.
Windows Update service
Press Win+R, enter services.msc, and press Enter. Locate Windows Update. Its status should not be permanently disabled while you are trying to install updates. If it is stopped, start it; if it is running but appears stuck, restart the service and retry. On a managed PC, a policy may control this setting, so record the result instead of forcing a change that immediately reverts.
4. Rebuild the Windows Update cache when the code points to damaged files
Cache rebuilding is most appropriate for 0x8007000D and for failures where the troubleshooter reports missing or corrupted update files. It is less invasive than changing system permissions, but it still requires an administrator account.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Stop the service
- Sign in with an account that has administrator rights.
- Open the Services console with
services.msc. - Right-click Windows Update and choose Stop. Leave the Services window open so you can start the service again.
Remove only the cache contents
- In File Explorer, enter
C:WindowsSoftwareDistributionin the address bar. - Delete the contents inside that folder, not the unrelated directories around it. If Windows says a file is in use, confirm that the Windows Update service is stopped and close other update-related windows.
- Do not delete
C:Windowsitself or other system folders.
Start the service and retry
- Return to services.msc.
- Right-click Windows Update and select Start.
- Restart the PC, open Windows Update, and retry the exact KB update you recorded.
Windows recreates the required cache data as it downloads the package again. If the same code returns, stop repeating the deletion and move to log inspection; repeated cache clearing will not correct a permissions or policy failure.
5. Follow the documented path for 0x80070005 (E_ACCESSDENIED)
Microsoft describes 0x80070005 (E_ACCESSDENIED) as an access-denied or insufficient-permissions failure during update installation. Incorrect permissions on %windir%WinSxS, %windir%SoftwareDistribution, the Component Based Servicing registry key or the Windows directory can prevent the installer from writing. Third-party antivirus, Group Policy and management agents can also block those writes.
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
Check for an external block first
- If the PC is managed by an employer or school, ask the administrator whether an update policy or management agent is enforcing the failure.
- Review recently changed security software or endpoint controls. Do not permanently disable protection as a first step; obtain approval and follow the product’s documented maintenance procedure.
- Confirm that your account can open an elevated Command Prompt. If it cannot, a permission reset is not an appropriate self-service repair.
Back up before resetting permissions
Before changing operating-system permissions, back up the Windows system drive or make sure you have a verified recovery method. A permission reset is more invasive than clearing a cache. If you cannot make a backup, stop here and use Microsoft support or a qualified administrator.
Run Microsoft’s reset commands
- Open Command Prompt as administrator. Search for Command Prompt, right-click it, and choose Run as administrator.
- Run the following command exactly, then wait for it to finish:
icacls "%windir%WinSxS" /reset /t /c /q - Run the second command:
icacls "%windir%SoftwareDistribution" /reset /t /c /q - Restart Windows and retry the recorded update.
The switches reset permissions recursively, continue when an item cannot be processed and suppress routine output. A command that reports errors does not prove the update is fixed; note the output and use the logs if the installation still fails.
Do not keep changing permissions blindly
If 0x80070005 remains after the documented reset, do not apply registry scripts or take ownership of additional folders from random websites. The cause may be Group Policy, a management agent or security software rather than damaged ACLs. Capture the exact code and logs and escalate.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.6. Match other suffixes to the least-invasive remedy
0x80070002: installation failure
This suffix tells you that the update did not install, but it does not identify one universal repair. Confirm the KB number, restart, run the troubleshooter, check connectivity and free space, and verify that the Windows Update service is operating. If the package fails again, inspect the Windows Update and Component Based Servicing (CBS) logs before attempting a cache rebuild or permission change.
0x80070057 and 0x80080005: corruption, permissions or configuration
These codes can arise from more than one category. Start with the general sequence: restart, troubleshooter, network and storage checks, then service status. Use cache rebuilding only when the evidence points to damaged update data. Treat a permission reset as a separate, backed-up step rather than a default response.
0x8007000E: insufficient disk space
Free space on the Windows drive, restart and retry. If storage is already adequate, record that fact and investigate the exact KB and logs. Deleting update folders cannot substitute for the disk-space check and may remove useful diagnostic information.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
7. Inspect logs after a repeat failure
When the same update fails after the appropriate manual steps, capture the complete code, KB number, time of failure and any message shown by Settings. Inspect the Windows Update and CBS logs for entries at that time. Look for indications of denied access, policy enforcement, missing files, corruption or storage exhaustion. The goal is to identify the category of failure, not to delete every line that looks like an error; Windows logs often contain expected retries and warnings.
Keep a copy of the relevant log excerpts before making another change. This gives Microsoft support or an organisation’s administrator enough context to distinguish a damaged cache from a policy block.
Choosing the next step
| Situation | Preferred action | Risk and preparation |
|---|---|---|
| Exact code is unknown | Check Update history and installation logs first | None; identification prevents the wrong repair |
| 0x8007000D or evidence of cache corruption | Stop Windows Update, clear the contents of SoftwareDistribution, restart the service and retry | Low to moderate; use an administrator account and avoid unrelated folders |
| 0x80070005 on a personally managed PC | Check security software and policy, back up, then run Microsoft’s two icacls commands |
Higher; elevated prompt and verified backup required |
| 0x8007000E | Free space on the Windows drive | Low; remove only files you recognise |
| Managed work or school computer | Contact the administrator with the code, KB and logs | Do not override policy or security controls |
| Same update still fails after the matching steps | Escalate with the recorded evidence | Further blind changes can obscure the original cause |
When to stop troubleshooting yourself
- The computer is controlled by an employer, school or other organisation.
- Logs point to Group Policy, a management agent or security software.
- You cannot create or verify a backup before a permission change.
- The same KB fails after restart, the troubleshooter and the remedy appropriate to its suffix.
- You are being asked to run registry scripts, take ownership of broad system directories or disable protection permanently.
Microsoft’s upgrade guidance recommends identifying the failed update and contacting Microsoft support when standard remedies do not resolve it. Provide the full code, KB name, Windows edition and version, the steps already completed, and the relevant log entries. No authoritative source establishes a success-rate percentage for these procedures, so treat a repeat failure as a diagnostic signal rather than evidence that one more cache deletion will guarantee a fix.
Quick Recap
Optional shortcut
Outbyte PC Repair is an optional shortcut for common Windows problems, including broken system elements, invalid redirects and shared DLL issues. It can also adjust settings, clean temporary and cache files, check Windows settings and missing updates, flag potentially unwanted applications, provide a real-time boost, shred files and record app crashes. It runs on Windows 11, 10, 8 and 7; a free trial is available by category for at least two days, followed by a subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every update failure.
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.
