Skip to main content
When the standard troubleshooter, an SFC scan, and a SoftwareDistribution reset all fail to clear error 0x80070003, the problem lies deeper — inside the Windows component store, the registry, or the file system’s symbolic link structure. These advanced fixes target exactly those root causes. They require a bit more care than the basic steps, but each one is safe to run on a healthy Windows installation and can resolve corruption that lighter tools simply cannot reach.

​
Fix 1: Analyze the CBS Log for Clues

Before throwing more tools at the problem, read what Windows has already written about it. The Component Based Servicing (CBS) log at C:\Windows\Logs\CBS\CBS.log records every action the servicing stack takes — including the exact file or directory path that is failing. Pinpointing the broken path lets you target your repair precisely instead of guessing.
1

Open Command Prompt as Administrator

Right-click Start → Terminal (Admin) and confirm the UAC prompt.
2

Extract SFC entries from the CBS log

Run the command below. It filters the log down to System File Checker lines only and saves them to your Desktop as sfcdetails.txt.
3

Open the output file

Navigate to your Desktop and open sfcdetails.txt in Notepad.
4

Identify the failing paths

Search for lines containing Cannot repair member file. Each matching line names the exact file or directory that Windows cannot access — note these paths before proceeding to the next fixes.

​
Fix 2: Run DISM to Repair System Image

Deployment Image Servicing and Management (DISM) operates one level below SFC — it repairs the Windows component store that SFC itself draws from. If SFC found errors but could not fix them, running DISM’s RestoreHealth command first and then re-running SFC is the correct sequence.
1

Open an elevated Command Prompt

Right-click Start → Terminal (Admin).
2

Run CheckHealth

Run the first command. This checks the local store for flags that indicate corruption without scanning every file — it completes in seconds.
3

Run ScanHealth

Run the second command. This does a full scan of the component store and reports whether corruption is present. It may take 5–10 minutes.
4

Run RestoreHealth

Run the third command to download and replace any corrupted components. This step requires an active internet connection and can take 15–30 minutes depending on your connection speed.
5

Re-run SFC and restart

After RestoreHealth completes, run sfc /scannow one more time, then restart your PC and retry Windows Update.
The RestoreHealth option contacts Windows Update servers to download genuine replacement files. Make sure you are connected to the internet and that no VPN or firewall is blocking Windows Update traffic before you run it.
Windows uses junction points (a type of directory symbolic link) extensively in its folder structure — for example, C:\Users\Default User is a junction pointing to C:\Users\Default. If the target of any junction no longer exists, every process that follows that path receives error 0x80070003. Listing all junctions on the drive lets you spot the broken ones.
1

Open an elevated Command Prompt

Right-click Start → Terminal (Admin).
2

List all symbolic links and junctions

Run the command below. The /AL flag shows only reparse points (junctions and symlinks); /S recurses all subdirectories. Redirect to a file if the output is large.
3

Identify broken junctions

Look for entries whose target path no longer exists on disk. Cross-reference with the CBS log findings from Fix 1 to prioritise which ones to fix.
4

Recreate missing junctions

Use mklink /J "broken_path" "correct_target_path" to recreate any junction whose target you can identify with certainty.
Only recreate a junction if you are certain of the correct target path. Pointing a system junction at the wrong location can cause Windows to become unbootable. If you are unsure, skip to Fix 5 (in-place upgrade) instead.

​
Fix 4: Clear Pending File Rename Operations

The registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations stores a queue of file move and rename tasks that are scheduled to run on the next reboot. If a previous failed update left stale or invalid entries in this queue — pointing to paths that no longer exist — Windows throws 0x80070003 every time it processes the queue.
1

Open Registry Editor

Press Win + R, type regedit, and press Enter. Confirm the UAC prompt.
2

Navigate to the Session Manager key

Expand the tree to: HKEY_LOCAL_MACHINE → SYSTEM → CurrentControlSet → Control → Session Manager.
3

Export a backup of the key

With Session Manager selected in the left pane, go to File → Export, choose a safe location, and save the backup. This lets you restore the key exactly if anything goes wrong.
4

Inspect the PendingFileRenameOperations value

Double-click PendingFileRenameOperations in the right pane. Review each path pair. If you see paths pointing to folders that no longer exist, the entire value is safe to delete.
5

Delete the value and restart

Right-click PendingFileRenameOperations and choose Delete, then confirm. Restart your PC and try Windows Update again.
Always export a registry backup (Step 3) before deleting any value. If removing this entry causes unexpected behavior, double-click the exported .reg file to restore it instantly.

​
Fix 5: Perform an In-Place Windows Repair Upgrade

An in-place upgrade reinstalls Windows on top of itself using the latest installation media. It replaces every system file — including broken paths, junction points, and corrupted DLLs — while keeping your personal files, installed applications, and settings completely intact. This is one of the most powerful repairs available short of a clean install.
1

Download the Windows Media Creation Tool

Visit the Microsoft Windows download page and download the Media Creation Tool for your version of Windows.
2

Launch the tool and choose to upgrade this PC

Run the downloaded tool, accept the license terms, and select Upgrade this PC now.
3

Select keep files and apps

When prompted, choose Keep personal files and apps. Do not select the option to remove everything.
4

Complete the upgrade

Let the process run to completion. Your PC will restart several times. Windows rebuilds all system paths during this process.
5

Check Windows Update

After the upgrade finishes, go to Settings → Windows Update and verify that updates now apply without error.
The in-place repair upgrade is one of the most effective fixes for path-level corruption and very rarely results in any data loss. If you have already tried Fixes 1–4 without success, skip straight to this step.

​
Fix 6: Recreate a Corrupt User Profile

In some cases, the broken path is not a system directory but the current user’s profile folder (for example C:\Users\YourName). A corrupted profile path causes Windows Update — and other system processes — to fail when they try to write temporary files to the profile.
1

Create a new local administrator account

Go to Settings → Accounts → Family & other users → Add someone else to this PC. Create a new local account and assign it Administrator rights.
2

Sign in with the new account

Sign out of your current account and sign in with the newly created one.
3

Migrate your data

Copy the contents of C:\Users\OldUsername\Documents, Desktop, Pictures, and any other folders you need into the equivalent directories of the new profile.
4

Delete the old profile (optional)

Once you have confirmed all your data is safe in the new profile, go to Settings → System → About → Advanced system settings → User Profiles → Settings, select the old profile, and click Delete.
5

Retry Windows Update

With the new profile active, open Settings → Windows Update and check for updates.

​
Frequently Asked Questions

No — in the vast majority of cases, you do not need a clean reinstall. Tools like SFC, DISM, and the in-place repair upgrade fix path-level corruption while keeping all your files and applications intact. A full wipe-and-reinstall is only necessary if the system drive itself is physically failing.
The Component Based Servicing (CBS) log at C:\Windows\Logs\CBS\CBS.log is a detailed record of every action the Windows servicing stack performs — including every file it checks, every patch it applies, and every error it encounters. When SFC reports that it cannot repair a file, the CBS log contains the exact path and error code, which makes targeted repairs far faster than trial-and-error.
Both errors indicate something Windows expected is missing, but they target different things. 0x80070002 means Windows cannot find a specific file — the directory exists but the file inside it does not. 0x80070003 means Windows cannot find the directory path itself — the folder (or a junction pointing to it) is absent or inaccessible. That distinction determines which repair tool to reach for first.
Several fixes work completely offline: the Windows Update troubleshooter, SFC (sfc /scannow), renaming the SoftwareDistribution folder, re-registering DLLs, and clearing the PendingFileRenameOperations registry value all require no internet connection. However, DISM RestoreHealth downloads replacement files from Windows Update servers and requires a working internet connection. The in-place upgrade also requires downloading or providing installation media.

Basic Fixes

Start with the simpler, faster fixes — troubleshooter, SFC, and SoftwareDistribution reset — before trying the advanced steps.

What Causes Error 0x80070003?

Learn why Windows throws this path-not-found error so you can prevent it from returning after you fix it.