Support Expert › Windows Repair Guides › Error Codes

Windows Error Codes: A Complete Troubleshooting Guide

Learn how to read Windows error codes, identify which component produced them, and choose a safe repair path for update, application, driver, permission, storage, and system-file failures.

Windows 10 & 1120-minute readUpdated September 17, 2026

Start with the context, not just the number.An identical-looking code can surface during Windows Update, app installation, activation, file access, or driver setup. Record the complete message, the failing action, and the affected program before changing the system.

Decode the format

Separate HRESULT, Win32, NTSTATUS, update, Device Manager, and stop-code families.

⌕

Trace the source

Use Reliability Monitor, Event Viewer, update history, and device status to preserve context.

✓

Repair safely

Apply the narrowest supported fix before escalating to system-wide repair.

What a Windows error code actually tells you

An error code is a structured result from a Windows component, application, service, driver, or installer. It narrows the failure category, but it does not always identify the root cause. For example, 0x80070005 represents access denied, yet the blocked object might be an update folder, registry key, application file, licensing component, or policy-controlled resource.

Code family	Where it commonly appears	What to capture
HRESULT `0x80070005`	Apps, installers, COM, Windows Update	Full message, operation, app, inner error, and timestamp
Win32 `5`, `87`, `126`	System tools, services, APIs, setup logs	Decimal and hexadecimal forms plus the failing file or service
Windows Update `0x800F081F`	Settings, setup, servicing, CBS logs	KB number, update phase, update history, CBS/DISM result
NTSTATUS / application `0xC0000005`	Crashes, startup failures, Event Viewer	Faulting application, module, exception code, version
Device Manager Code 10, 28, 43	Device Properties → General	Device name, problem code, hardware IDs, driver provider/version
Bug check / BSOD	Blue-screen stop page and dump files	Stop code, parameters, dump, recent driver/hardware change

Do not search only the last digits.Keep the complete prefix and all eight hexadecimal digits. Code 5, Device Manager Code 5, HRESULT 0x80070005, and a bug-check parameter containing 5 are different contexts.

Capture the error before attempting a repair

Record the complete code and message
Take a screenshot. Note whether the code begins with 0x8007, 0x800F, 0xC000, or is shown as a decimal Device Manager code. Record the exact action that failed.
Confirm the scope
Determine whether one app, one user profile, one device, Windows Update, or the entire PC is affected. A single-app failure should usually be repaired at the application level first.
Review recent changes
Check update history, recently installed software, driver changes, security quarantines, storage events, power loss, and hardware changes. Avoid undoing unrelated security updates.
Find the matching evidence
Use Reliability Monitor for a timeline, Event Viewer for the faulting source, Device Manager for hardware problem codes, and Windows Update history for failed KB numbers.

Common Windows codes and the safest first action

Code	Usual meaning	Best first action
`0x80070005`	Access denied / permissions	Identify the blocked resource; run the task with appropriate authorization and review security or policy restrictions. Do not broadly reset permissions.
`0x80070057`	Invalid parameter	Verify the command, installer options, regional/data format, destination, and the specific operation that rejected input.
`0x80070002` / `0x80070003`	File or path not found	Repair or reinstall the affected app; for updates, run the troubleshooter and verify update components and storage.
`0x800F081F`	Servicing source files unavailable	Run DISM, install pending servicing updates, or use a matching supported Windows repair source.
`0x80070643`	Installer reported a fatal installation error	Identify the exact MSI/update package, review its log, restart, and repair its prerequisites before retrying.
`0x80004005`	Unspecified failure	Use the surrounding event or setup log; the code alone is intentionally nonspecific.
`0xC0000005`	Access violation	Repair/update the affected app, remove incompatible add-ons, review the faulting module, then test memory/storage if failures vary.
`0xC000007B`	Invalid image format / architecture mismatch	Repair the affected application and its official x86/x64 runtime dependencies; never substitute random DLL files.
Device Code 10	Device cannot start	Restart, reconnect if applicable, install the PC/device maker’s supported driver, and review device events.
Device Code 28	Drivers not installed	Install a supported driver through Windows Update or the hardware/PC manufacturer.
Device Code 43	Driver/device reported a failure	Power-cycle, reconnect, reinstall or roll back the supported driver, and test the hardware.

Safe troubleshooting path

1. Restart and reproduce once

A restart clears pending servicing, locked files, and temporary device states. Reproduce the same action once and confirm the code is unchanged.

2. Use the repair path for the failing component

One application: use its Repair option, verify its files, or reinstall from the publisher.
Windows Update: run the Windows Update troubleshooter, restart, check storage and connectivity, then retry.
Device or driver: inspect Device Manager status, Events, provider, version, and hardware IDs before updating or rolling back.
File access: confirm ownership, account authorization, file location, encryption, and security history—do not grant Everyone full control.
Repeated system-wide failures: back up data and check Windows files, storage, memory, malware, heat, and power stability.

3. Repair Windows servicing and protected files

When several Windows components fail or the evidence points to servicing corruption, open Terminal or Command Prompt as administrator and run DISM first:

DISM.exe /Online /Cleanup-Image /RestoreHealth

After DISM completes successfully, run:

sfc /scannow

Restart if repairs were made. These commands are not the first fix for every application or hardware error.

4. Escalate with evidence

If the same error persists, preserve the code, logs, dump files, application version, Windows build, driver versions, and a list of attempted fixes. That evidence is far more useful than repeatedly resetting Windows components.

Device Manager codes are a separate system

Open Device Manager, right-click the device, and select Properties. The General, Driver, Details, and Events tabs help distinguish a missing driver from a failed start, blocked driver, disconnected device, resource conflict, or hardware failure.

Code 10 is not a universal “update the driver” instruction.Firmware, power, USB/PCIe connection, security policy, incompatible filters, and failing hardware can all prevent a device from starting. Use the device events and hardware identity.

Reduce recurring Windows errors

Keep Windows and supported device drivers updated.
Install apps, runtimes, and drivers only from Microsoft or the original publisher.
Maintain current backups before updates, driver changes, or hardware work.
Keep adequate free storage for Windows servicing and updates.
Avoid registry cleaners, random DLL downloads, and broad permission resets.
Investigate recurring corruption as a possible storage, memory, malware, thermal, or power problem.

Frequently asked questions

Can one error code have multiple causes?

Yes. A code describes the failure reported at one boundary. The failing resource and root cause depend on the operation, component, logs, and recent changes.

Should I paste an error code into a command I found online?

No. Verify that the instructions apply to the same Windows version, component, and context, and prefer Microsoft or the original vendor’s documentation.

Will DISM and SFC fix every Windows error?

No. They repair Windows servicing and protected system files. They do not repair every third-party app, driver, permission, network, storage, memory, or hardware failure.

Where can I find more detail about an application crash?

Use Reliability Monitor and Event Viewer → Windows Logs → Application. Capture the faulting application, module, exception code, and timestamp.

References and further reading

Scope and safetyThis guide explains supported diagnostic paths. Back up important data before system repair. Business-managed PCs may require an administrator, and hardware instability should be evaluated before repeated software repair.