Windows System Errors
Path Not Found
0x80070003Reviewed for reference consistency: August 11, 2026
a directory referenced by the operation is missing from the disk
What 0x80070003 Means
The 0x80070003 error on the Windows System Errors indicates path not found — a directory referenced by the operation is missing from the disk. This typically occurs due to a directory on the route to the target was renamed, moved, or deleted.
0x80070003 is the HRESULT wrapper around Win32 error 3, ERROR_PATH_NOT_FOUND, whose system text reads 'The system cannot find the path specified'. Where error 2 names a missing file, error 3 means the lookup failed earlier — one of the directories on the way to the target does not exist. Windows Update debugging guides tie the code to the servicing stack failing to access a specific path, with the detail sitting in CBS.log.
How to fix 0x80070003
General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.
Locate the failing path in CBS.log
The servicing log records the exact path next to each failure line, which turns a generic code into a specific directory.
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern ", error" | Select-Object -Last 20Scan the component store deeply
ScanHealth walks the store and reports any corruption it finds, without repairing or downloading anything.
Dism.exe /Online /Cleanup-Image /ScanHealth
Technical Background
The failure point is what separates this code from its file-level twin. A path lookup walks segment by segment; error 3 is the walk failing on a directory component, while error 2 is the final name missing after every directory resolved. The distinction matters when reading logs, because the two failures usually have different owners — a missing parent folder versus a missing payload file.
In servicing contexts the code often reflects state rather than a permanently absent directory: the component store, a log, or a staging folder was expected at a specific location and was not there at that moment. The mitigation documented for update scenarios is CBS.log analysis — locating the ', error' entries and matching them against timestamps to identify which path the stack could not reach.
Common Causes
- A directory on the route to the target was renamed, moved, or deleted
- A servicing operation resolved a target directory that the component store no longer lists
- Environment-variable expansion produced a path that does not exist on this machine
- A mapped drive or mount point behind the path is unavailable
Typical Scenarios
- A cumulative update stops mid-install and CBS.log records a path access failure for a servicing operation
- An installer or script references a folder that a cleanup or rename removed between the check and the use
- An application builds a path from an environment variable that is not defined on the machine running it
What to Know
A recurring 0x80070003 on one machine usually narrows to one vanished directory, so the log timestamp plus the logged path tend to answer the question faster than any system-wide repair.
Frequently Asked Questions
Common questions about Windows 0x80070003 error
Error 2 is ERROR_FILE_NOT_FOUND: every directory on the route resolved and the final file name did not. Error 3 is ERROR_PATH_NOT_FOUND: the walk failed on one of the directory components themselves.
It is the HRESULT framing — severity bit set to failure, facility 0x0007 (FACILITY_WIN32) — with the low 16 bits holding the Win32 code, 3. The same pattern maps every 0x8007XXXX value onto a WinError.h constant.
Update troubleshooting guidance routes 0x80070003 to CBS.log analysis: search the log for ', error' entries, align them with timestamps, and the failing path is recorded next to the failure.
Related Error Codes
Element Not Found — Windows could not locate a required servicing component
File Not Found
Out of Memory — an allocation request exceeded what the system could commit
Module Not Found — a required library file could not be located at load time
Related Errors From Other Categories
Similar error codes documented across different platforms and systems
Git paused the merge because it cannot automatically resolve overlapping changes.
Git aborted the merge to protect uncommitted changes in your working directory.
Git prevented a branch switch because it would overwrite unsaved changes in your working directory.
Git aborted the merge because it would overwrite untracked files in your working directory.