Windows Update Error 0x80070246 — Fix the Shared Component Conflict

What Does This Error Mean?

Windows Update error 0x80070246 indicates a conflict with a shared Windows component. The update is trying to install or modify a file or component that another process is currently using or that is in a conflicting state. Restarting your PC, clearing pending operations, and repairing Windows components usually resolves this.

Affected Models

Windows 10
Windows 11
Windows Server 2016
Windows Server 2019

Common Causes

A pending Windows operation from a previous update or install is blocking the new update
Two updates are trying to modify the same shared component at the same time
Windows component store has conflicting version information for a shared file
A background program is holding a lock on a file the update needs to replace
A failed previous update left the system in a partially updated state

How to Fix It

Restart your computer fully (not sleep or hibernate — a full restart). Then try Windows Update again immediately before opening any other programs.

Many component conflicts are caused by pending operations from previous installs. A clean restart clears most of these.
Run the Windows Update Troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters and click Run next to Windows Update.

This tool detects and resolves pending operations and component conflicts automatically in many cases.
Run DISM to fix the Windows component store. Open Command Prompt as Administrator and type: DISM /Online /Cleanup-Image /RestoreHealth

This is the most important step for this error. DISM specifically repairs conflicts in the Windows component store where shared file versions are tracked.
After DISM finishes, run System File Checker. In the same elevated Command Prompt type: sfc /scannow — wait for it to complete, then restart.

Running both tools together gives the most thorough repair. Always run DISM first.
Close all background programs before trying the update. Open Task Manager (Ctrl+Shift+Esc), close any programs you do not need, and then run Windows Update.

Some programs like backup software, antivirus scanners, or cloud sync tools can hold locks on system files and block update installations.

When to Call a Professional

If this error appears after multiple failed update attempts and DISM does not resolve it, a technician can perform an in-place upgrade repair. This reinstalls Windows without removing your files or programs and resolves deep component conflicts.

Frequently Asked Questions

What is a shared component in Windows?

Windows uses many files that are shared between different programs and system services. For example, a single DLL file might be used by five different applications. When an update needs to replace one of these shared files, it has to coordinate carefully. If another process is using that file or if two updates want different versions, a conflict occurs.

Will I lose data if I run DISM?

No. DISM repairs system files only — it does not touch your personal files, documents, photos, or installed programs. It downloads replacement system files from Microsoft and replaces only the specific files that are damaged or in conflict.

How long should I wait between update retries?

After running the repair tools, wait for a full restart before trying the update again. If the update fails again, wait a few hours before another attempt — Microsoft's update servers are sometimes overloaded, especially after a major update release. Persistent failures after 24 hours usually indicate a local issue that needs further troubleshooting.