Skip to main content
Windows error 0x80070003 is a path-not-found error, and that classification is important. Unlike 0x80070002 — which tells you a specific file is missing inside a directory that does exist — 0x80070003 tells you the directory itself cannot be located. This narrower definition means the root causes are more predictable: something changed, removed, or corrupted a path that Windows or an application expected to find at a specific location. Identifying which path is broken is the key to a fast resolution.

​
Cause 1: Missing or Renamed Windows Update Temporary Folder

Windows Update downloads and stages update packages inside a specific directory tree:
Beneath this folder, the Windows Update Agent creates unique subfolders for each update package. If any folder in this chain is deleted, renamed, or moved — either manually or by a third-party cleaner tool — the Update Agent throws 0x80070003 because it cannot write to or verify the expected path.
Do not manually rename or delete folders inside C:\Windows\SoftwareDistribution\ while Windows Update is running or suspended. Doing so breaks the update agent’s internal path references and triggers 0x80070003. If you need to reset the SoftwareDistribution folder, always stop the Windows Update service first using net stop wuauserv before making changes.

​
Cause 2: Corrupted System Volume Information Folder

The System Volume Information folder, present on every NTFS volume, is used by:
  • System Restore — to store restore point snapshots
  • Volume Shadow Copy Service (VSS) — to manage shadow copies used by backup tools
If this folder becomes corrupted, has its permissions changed, or is inaccessible due to a failed disk operation or malware scan, any process that needs to read or write to it — including Windows Backup and System Restore — will fail with a path-not-found error. The path exists on disk but is effectively unreachable to the requesting process.

​
Cause 3: Changed or Moved System Drive Letter

Windows and most applications store paths as absolute references, meaning they include the full drive letter (e.g., C:\Windows\...). If your system drive letter changes — for example, from C: to D: after a disk re-partitioning, a new disk installation, or a dual-boot setup — every hardcoded path that began with C:\ is instantly broken. This is a particularly common cause of 0x80070003 in scenarios involving:
  • Cloning a Windows installation to a new drive
  • Expanding or re-partitioning disks using third-party tools
  • Adding a new drive that Windows assigns a lower drive letter, bumping the original system drive
You can verify and correct drive letter assignments in Disk Management (diskmgmt.msc). Right-click the volume and select Change Drive Letter and Paths to reassign the correct letter. Note that changing the system drive letter (usually C:) while Windows is running requires a registry edit and a restart — it cannot be changed directly through Disk Management.

​
Cause 4: Corrupted User Profile Path

Many Windows operations — especially Windows Update, app installations, and application settings — reference paths inside the current user’s home directory:
If a user profile becomes corrupted, is stored on a network share that goes offline, or the ProfileImagePath registry value under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList points to a directory that no longer exists, any process that resolves paths through the user profile will fail. You may see 0x80070003 alongside profile-related errors in the Event Viewer when this is the root cause. Windows relies heavily on junction points (a form of symbolic link for directories) to maintain backward compatibility. A well-known example is:
These junction points are created automatically by Windows and must remain intact. If a junction point is deleted, corrupted, or points to a non-existent target, any process that navigates through it will receive ERROR_PATH_NOT_FOUND (0x80070003). This can happen after:
  • Aggressive disk cleanup or defragmentation tools that misidentify junctions as empty folders
  • Manual deletion by an administrator unfamiliar with junction points
  • Failed migrations or upgrade procedures that did not recreate links correctly

​
Cause 6: Pending File Rename Operations

Windows maintains a registry key that queues file and directory rename operations to be executed at the next system boot:
If this key contains stale or malformed entries — left behind by a failed update, installer, or uninstaller — Windows may attempt to rename a path that no longer exists, or rename a path that other processes depend on, resulting in 0x80070003 during subsequent operations.
You can inspect the PendingFileRenameOperations value in Registry Editor (regedit.exe) by navigating to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager. If you find entries referencing paths that clearly no longer exist, you can delete the specific strings carefully — or clear the entire value if no updates are pending. Always back up the registry key before making changes: File → Export the key before editing.

​
Cause 7: Windows Update Database Corruption

The Component Based Servicing (CBS) engine manages Windows Update at a deeper level, maintaining a database of installed components and pending operations. If this database becomes inconsistent or corrupted — due to a sudden power loss during an update, a failed rollback, or disk errors — the CBS engine may reference update staging paths that were never fully created, producing 0x80070003. You can review CBS-related errors in the log file located at:
Look for lines tagged [SR] (System Resource checker) or path-related failures near the timestamp when the error occurred. Corruption at this level typically requires running DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow to repair the component store.

​
Quick Diagnosis Checklist

Before attempting any fix, run through these checks to identify which cause applies to your situation:
  1. Check Event Viewer — Open eventvwr.msc and look under Windows Logs → Application and System for errors timestamped near when 0x80070003 appeared. Note any path mentioned in the error details.
  2. Verify the SoftwareDistribution folder — Confirm C:\Windows\SoftwareDistribution\Download\ exists and is accessible. If it’s missing or empty unexpectedly, a reset is likely needed.
  3. Check your system drive letter — Open diskmgmt.msc and confirm the Windows partition is still assigned the drive letter C:.
  4. Inspect your user profile path — Open C:\Users\ in File Explorer and confirm your username folder exists and is accessible.
  5. Look for broken junction points — Run dir /aL C:\ in an elevated Command Prompt to list junction points at the root and verify their targets are valid.
  6. Review pending rename operations — Open Registry Editor and check HKLM\SYSTEM\CurrentControlSet\Control\Session Manager for a PendingFileRenameOperations value with stale entries.
  7. Check the CBS log — Open C:\Windows\Logs\CBS\CBS.log and search for 0x80070003 or path not found near the time the error occurred to identify which component triggered it.

What Is Error 0x80070003?

Understand the full meaning of error 0x80070003, its HRESULT breakdown, and how it differs from 0x80070002.

Fix Error 0x80070003

Follow step-by-step repair instructions to resolve error 0x80070003 on Windows Update, Backup, and more.