0x800700 is not a complete Windows error code. It is a hexadecimal prefix, and the characters after it determine what failed and which repair is appropriate. For example, 0x80070005 normally indicates access denied in the documented Windows Update case, while 0x80070070 indicates insufficient disk space. Those errors do not have the same fix.
Before changing permissions, deleting update caches, reinstalling drivers, or retrying an installation, copy the complete code and note where it appeared: Windows Update, Windows Setup, activation, app deployment, printing, or another task. Then use the matching procedure below.
As an Amazon Associate I earn from qualifying purchases.
What “0x800700” actually tells you
Windows reports errors in hexadecimal notation. The beginning of the value identifies a broad family, but 0x800700 by itself omits the final hexadecimal characters that identify the specific failure. A message such as “Microsoft failed 0x800700” therefore does not identify one defect or one universal repair.
Microsoft’s Windows Update documentation lists several different errors beginning with this prefix. The same prefix can appear in unrelated components, so the operation that failed matters as much as the number. A Windows Update failure, a Windows installation failure, an activation problem, and an application-deployment failure may require different logs, privileges, and recovery steps.
#1 Best Overall
- Fresh USB Install With Key code Included
- 24/7 Tech Support from expert Technician
- Top product with Great Reviews
- Record every character, including leading zeroes.
0x80070005and0x8007005should not be treated as interchangeable. - Copy the exact message around the code. Words such as “access denied,” “not enough space,” or “the path cannot be found” provide useful confirmation.
- Write down the Windows edition and version, the component involved, and whether the failure happened once or on every attempt.
- Note recent changes, such as a policy change, security product installation, disk cleanup, storage replacement, or interrupted update.
Do not apply a permission reset because a search result mentions 0x800700, and do not delete update folders until you know the suffix. A wrong repair can remove useful evidence or create a second problem.
Repair map for the most important suffixes
| Complete code | Typical meaning in the documented case | First evidence to collect | Privilege and reversibility | External media |
|---|---|---|---|---|
0x80070005 |
Access denied | WindowsUpdate.log or CBS.log; the exact file, folder, registry key, or servicing resource named there | An elevated account may be required for inspection or a documented change. Broad permission resets are difficult to reverse. | Not normally required |
0x80070070 |
Insufficient disk space | Available space on the Windows drive and the operation that ran out of room | Removing selected files or applications is generally reversible only if you have a backup; avoid deleting unknown system files. | For a supported upgrade, an external USB drive may be allowed; Microsoft specifies NTFS, at least 8 GB, with 16 GB recommended. |
Other 0x800700xx values |
Depends on the final characters and the component | The complete message and the log for the failing component | Not stated until the suffix and target are known | Not stated until the exact operation is identified |
The table is a triage tool, not a substitute for the complete code. Microsoft also documents distinct values such as 0x80070003; the shared prefix does not prove that the cause is permissions or storage.
Capture the code and context before changing anything
- Preserve the message. Take a screenshot or copy the text from Settings, the installer, or the application that displayed the error. Include the complete hexadecimal value.
- Identify the operation. State whether the failure occurred while downloading or installing a Windows Update, upgrading Windows, activating Windows, installing an app, printing, or performing another task.
- Record the Windows version. Open Settings > System > About and note the Windows edition and version. On a managed computer, also note whether an organization controls updates or security settings.
- Check whether the failure is repeatable. Restart once, retry the same operation, and record whether the code and the surrounding message remain identical. A transient interruption should not be diagnosed as a permissions defect without confirmation.
- Save relevant logs. For Windows Update and servicing failures, Microsoft directs troubleshooting toward WindowsUpdate.log and CBS.log. Copy the relevant portion before clearing caches or making changes.
If the message changes after a restart, use the newest complete code rather than assuming the original diagnosis still applies.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →How to fix 0x80070005: access denied
In the documented Windows Update scenario, Microsoft says, “This error generally means that access was denied.” Windows may be unable to read or write a file, folder, registry key, or servicing resource because its permissions changed, a security product blocked the operation, or a policy restricted it.
1. Find the object that was denied
Start with the log, not with a global permission command. Windows Update writes diagnostic information to WindowsUpdate.log, while component servicing records details in CBS.log. Search the relevant log for 0x80070005, “access denied,” or an entry immediately preceding the failure. The useful line may identify a path, registry key, package, or servicing operation.
On current Windows versions, Windows Update information can be assembled into a readable WindowsUpdate.log with the built-in PowerShell command Get-WindowsUpdateLog. CBS.log is normally found under C:WindowsLogsCBSCBS.log. Reading these files may require an administrator account, but do not edit them.
2. Check the named file, folder, or registry key
Once the log identifies a target, inspect that target’s permissions and ownership. The relevant servicing identities commonly include TrustedInstaller and SYSTEM; Microsoft’s guidance is to verify that they have the access required for the particular Windows servicing location. Check the exact object named in the log rather than applying permissions to the entire Windows directory.
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 & 11If you cannot determine what access the object should have, stop before changing it. A blanket “take ownership,” inherited-permission reset, or registry-wide edit can break servicing and is harder to undo than the original error. Create a backup and use an established Microsoft procedure for the specific object if one exists.
3. Review security software and policy restrictions
Antivirus and endpoint-security products can lock a file while Windows Update is replacing it. Group Policy or device-management rules can also deny access to update locations or registry areas. Review the security product’s event log and the organization’s policy before changing settings.
On a personally managed PC, you can test whether a security product is interfering only if its documentation provides a safe, temporary method. Keep protection enabled whenever possible, make the test brief, restore the original setting immediately, and retry the update. On a work or school device, ask the administrator instead of bypassing policy.
4. Retry with the required privilege
Use an administrator account only when the documented procedure requires it. If the error appears in an installer or maintenance command, right-click that specific program and choose Run as administrator only when you trust the program and understand what it will change. Elevation cannot repair a missing permission on a servicing resource by itself, and it should not be used as a reason to grant every account full control.
Recommended Free Tools
5. Recheck the log after one controlled retry
Restart Windows, run the same update once, and compare the new log entry with the original. If the denied object is different, treat the new entry as the current failure. If the same object is repeatedly denied after policy and security checks, obtain the exact Microsoft procedure for that object or involve your system administrator.
How to fix 0x80070070: insufficient disk space
Microsoft describes 0x80070070 as typically indicating insufficient disk space. The immediate goal is to create enough usable space on the Windows drive for the download, temporary files, unpacked packages, and the installation’s rollback data.
1. Confirm which drive is full
Open Settings > System > Storage and inspect the Windows drive, normally the drive containing the Windows folder. Do not assume that a second drive with free space solves the problem; the installer may need space on the system drive unless its instructions explicitly support another location.
Check the free-space figure immediately before retrying. Large downloads, update caches, temporary extraction files, and rollback files can consume additional space during setup, so leaving only a few megabytes free is not a reliable fix.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- Dual USB-A & USB-C Bootable Drive – compatible with nearly all Windows PCs, laptops, and tablets (UEFI & Legacy BIOS). Works with Surface devices and all major brands.
- Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
- Complete Windows Repair Toolkit – includes tools to remove viruses, reset passwords, recover lost files, and fix boot errors like BOOTMGR or NTLDR missing.
- Reinstall or Upgrade Windows – perform a clean reinstall of Windows 7 (32bit and 64bit), 10, or 11 (amd64 + arm64) to restore performance and stability. (Windows license not included.). Includes Full Driver Pack – ensures hardware compatibility after installation. Automatically detects and installs drivers for most PCs.
- Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
2. Remove only items you can identify
- Uninstall applications you no longer use from Settings > Apps > Installed apps.
- Use Settings > System > Storage > Temporary files to review temporary categories and select only items you understand.
- Move personal videos, photos, archives, and game installers to another storage device after confirming that the copies open correctly.
- Empty the Recycle Bin only after checking its contents.
Do not manually delete files from C:Windows, C:WindowsInstaller, or an unfamiliar servicing folder merely because they are large. Those files can be needed for uninstall, repair, or rollback.
3. Restart, then retry
After freeing space, restart Windows. A restart can release files held by a previous update and lets Storage recalculate available space. Retry the same update or setup operation and record whether the complete code changes.
4. Use an external USB drive when supported
For a supported Windows upgrade, Microsoft documents using an external USB drive when the device and upgrade workflow allow it. The cited guidance specifies an NTFS-formatted drive with at least 8 GB of capacity and recommends 16 GB. Connect the drive before starting the upgrade and follow the installer’s prompt; do not assume that every update or every computer can redirect installation files to USB storage.
An external drive is not a substitute for identifying a damaged or unavailable internal drive. If the Windows drive reports incorrect capacity, I/O errors, or disappears, resolve the storage hardware or file-system problem first.
Free tools Windows power users keep installed
One-click scans. No signup required.
What to do with other 0x800700xx values
For any suffix other than the documented access-denied and low-space cases, treat the value as a separate error. Microsoft’s common-error material includes distinct entries such as 0x80070003, and the correct remedy depends on the full code and the component that produced it.
- Copy the complete value and message again.
- Identify the component: Windows Update, Setup, activation, app deployment, printing, or another service.
- Open the log belonging to that component and locate the first meaningful failure, not just the final rollback line.
- Use Microsoft’s documentation for that exact suffix and operation. Do not substitute a fix for
0x80070005or0x80070070because the first six characters look similar. - Apply one documented change at a time, restart if instructed, and record the result.
If the final characters are missing from the dialog, check the update history, installer log, event details, or the application’s error report. A partial code is not enough to select a safe repair.
When the failure happened during Windows installation or upgrade
An installation failure is not automatically a Windows Update failure. Setup may be running from installation media, an upgrade assistant, a mounted image, or a recovery workflow. Start by writing down whether the process was a clean installation, an in-place upgrade, a feature update, or a recovery operation.
For an upgrade that reports 0x80070070, use the storage procedure above and confirm the external-drive requirements before restarting setup. For an upgrade that reports 0x80070005, investigate the denied servicing object and any policy or security software that can block it. For every other suffix, keep the installation context attached to the code when looking up the procedure; the same hexadecimal ending can have different implications in different components.
Do not begin a clean installation simply because an in-place upgrade failed. A clean installation can remove applications and personal data. Back up important files and confirm the exact recovery plan before choosing a destructive option.
Using Windows logs safely
WindowsUpdate.log
Use WindowsUpdate.log to correlate the time of the failure with the update operation. On current systems, Get-WindowsUpdateLog can assemble readable information from Windows Update traces. Search for the complete code and inspect nearby lines for the package, path, or operation that was refused or could not complete.
CBS.log
CBS.log records component-based servicing activity. Its entries can be verbose, so begin at the timestamp of the failure and look for the first access, package, or file error. Preserve a copy before attempting cleanup. If a support technician asks for the log, provide the surrounding entries rather than editing the file.
Interpreting repeated failures
A repeated identical code against the same object is stronger evidence than a single transient message. A new code after cleanup, a restart, or a policy change means the next step should be based on the new code. Keep a short timeline containing the attempt time, complete code, operation, change made, and result.
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 problemsCommon mistakes that make 0x800700 problems worse
- Searching only for “0x800700.” The missing suffix is the part that distinguishes access denial from low storage and other failures.
- Resetting all Windows permissions. This can damage servicing and application access while leaving the original cause unknown.
- Deleting update caches first. Cleanup may remove evidence needed to identify the denied path or failed package.
- Disabling security controls indefinitely. A temporary, documented test is different from leaving protection or policy disabled.
- Assuming more free space always fixes setup. Storage helps only when the suffix and the failing operation point to a capacity problem.
- Running every repair command at once. Mixing unrelated commands makes it impossible to tell which change helped and can create new failures.
- Using an external drive without checking the workflow. The documented upgrade allowance requires NTFS and at least 8 GB, with 16 GB recommended, and is not universal.
When to escalate
Ask a system administrator or qualified support technician for help when the computer is managed by an organization, the log names a protected servicing resource you cannot identify, storage hardware reports errors, or the failure persists after the suffix-specific procedure. Provide the complete code, exact message, Windows version, operation, relevant log excerpt, and a timeline of changes.
Escalation is also appropriate before editing the registry, taking ownership of system folders, deleting installer or servicing files, or starting a clean installation. Those actions can be difficult to reverse and are not justified by the incomplete prefix alone.
Quick Recap
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 and shared DLL problems, while also offering cleanup, settings adjustments, vulnerability checks, real-time boost, file shredding, and app-crash logging. It runs on Windows 11, 10, 8, and 7, includes a category-based free trial of at least two days, and then requires a subscription. It complements antivirus software rather than replacing it; results vary, and no utility repairs every crash.
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.
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 →
