0x80070005 — Access denied
Windows or an installer could not access a required resource. The exact permission or component depends on the task.
Read the guide →Error-code library
Search the exact hexadecimal error or stop-code text. Codes narrow the search but rarely prove the cause on their own. Match the Windows version, operation and full message.
Write down the full code and where it appeared. Do not download a “code fixer,” edit registry settings blindly or reset Windows before backing up files.
Code family
Windows or an installer could not access a required resource. The exact permission or component depends on the task.
Read the guide →Code family
An operation could not find a file or path it expected. The cause depends on the update or application.
Read the guide →Code family
An operation received data it could not use. In Windows Update this may be associated with update data or cache problems.
Read the guide →This code can have different causes depending on the operation, including servicing or system-reserved partition conditions in some cases.
Read the guide →Code family
A Windows operation exceeded its time limit. The cause may involve update progress, connectivity, storage or another component.
Read the guide →Code family
Windows could not find source files needed for a servicing or repair operation. The source depends on the feature being repaired.
Read the guide →Code family
This code often appears when an operation needs a Windows service that is disabled or unavailable.
Read the guide →Code family
Microsoft associates this error family with driver-related Windows upgrade failures. The full suffix and setup logs can narrow the cause.
Read the guide →Code family
The operation received an invalid parameter or value. The meaning depends on which Windows component returned the code.
Read the guide →Code family
An operation could not obtain the resources it needed. This does not prove the PC needs a RAM upgrade.
Read the guide →Code family
A broad, nonspecific error code used by different Windows components and applications. The action and full message are essential.
Read the guide →Code family
Windows detected a memory-management-related condition. Drivers, system files and hardware may be involved; the code alone does not prove bad RAM.
Read the guide →Windows encountered an invalid memory access. Drivers, system files and hardware may require investigation.
Read the guide →A system service or kernel transition encountered an exception. Driver/software interactions may be involved.
Read the guide →A driver did not handle a power-state transition as expected. Sleep, wake, shutdown and new devices are useful clues.
Read the guide →Windows detected a driver or interrupt-processing condition that exceeded expected limits. Storage and chipset drivers can be relevant.
Read the guide →Code family
Windows cannot access the boot device during startup. Causes may involve boot configuration, storage access or a recent system change.
Read the guide →Code family
Windows received a hardware error reported through WHEA. It may indicate hardware or firmware instability and requires careful diagnosis.
Read the guide →