RepairMyOS
live db
C:\Windows\System32\winevt\Logs > Event 0x80070020
Warning

0x80070020_

Update Failed � Sharing Violation

Windows 10/11 · Windows Update

When Windows 10/11 throws 0x80070020, the system diagnostics have flagged a condition known as "Update Failed � Sharing Violation". Most fixes for this error are straightforward and don't require wiping your drive.

What Actually Happened

Windows 10/11 tried to install an update and the specific system condition behind it was 'the process cannot access the file because it is being used by another process'. Clearing the update cache and retrying resolves the majority of cases.

Symptoms

A Windows Update install fails or rolls back with error 0x80070020, sometimes after a restart loop

Common Causes

  • The underlying Win32 condition ERROR_SHARING_VIOLATION (the process cannot access the file because it is being used by another process) was raised while staging or applying the update
  • The Windows Update cache (SoftwareDistribution) holds a stale or corrupted entry
  • Insufficient free disk space to stage the update package
  • A third-party antivirus or a Group Policy restriction is blocking the installer

How to Fix It

  1. 01
    Run the built-in Windows Update Troubleshooter (Settings > System > Troubleshoot)
  2. 02
    Stop the Windows Update service:
    net stop wuauserv && net stop bits
  3. 03
    Rename the cache folder:
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  4. 04
    Restart services:
    net start wuauserv && net start bits
  5. 05
    Run system repair:
    sfc /scannow && DISM /Online /Cleanup-Image /RestoreHealth
⚡ INSTANT REFERENCE KIT

System Administrator Emergency Kit

Stop searching for syntax under pressure. Get 100+ verified, battle-tested emergency recovery commands for Windows & Linux in one printable PDF guide.

Root Cause Breakdown

0x80070020 is the HRESULT wrapping of Win32 error 32 (ERROR_SHARING_VIOLATION): the process cannot access the file because it is being used by another process. The servicing stack (CBS) failed to complete the staging phase.

Should You Worry?

Safe to keep using your PC normally while working through the fix.

Power-User Tip

Before running DISM, renaming C:\Windows\SoftwareDistribution to SoftwareDistribution.old clears 80% of 0x80070020 failures instantly.

Estimated Fix Cost USD
$0 $90

DIY fix: $0; Paid remote tech support if DISM repair fails: $40�$90