- Software and systems
- Operating system
0x80070020
Windows Update 0x80070020: InstallFileLocked
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
Medium
Quick answer
Microsoft defines 0x80070020 as: Windows Update could not access a required file because another process was using it. Do not reset Windows Update from the code alone. First preserve the failed KB, update source and time, then discriminate which process owns the file at the failure time and whether the lock returns after a clean restart.
Safety first
Stop and check this first
- Do not disable antivirus, delete system files or install a registry cleaner on speculation.
Safe checks you can perform
- Preserve the failed update before changing state
- Run one controlled discriminator
- Stop before the generic reset loop
Leave these tasks to a qualified professional
- Do not attempt this professional task: Evidence-led Windows Update handoff for 0x80070020
What a technician must be able to justify
A technician is coming
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Evidence-led Windows Update handoff for 0x80070020
What they doCorrelate the KB timestamp with WindowsUpdate.log, CBS.log and Process Monitor or endpoint telemetry; identify the exact handle owner before changing exclusions.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Checks and evidence, step by step
Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
- 1
Preserve the failed update before changing state
No special tools
Procedure
In Settings > Windows Update > Update history, record the exact KB/title, 0x80070020, timestamp, Windows edition/build, restart-pending state and whether the source is Microsoft Update, WSUS or another managed service.
Do not disable antivirus, delete system files or install a registry cleaner on speculation.
Evidence: Windows Update error reference
- 2
Run one controlled discriminator
No special tools
Procedure
Restart once, pause only the ordinary backup or scan job that visibly overlaps the same timestamp, and retry that KB once. Keep endpoint protection enabled unless its own administrator proves the file lock.
Do not disable antivirus, delete system files or install a registry cleaner on speculation.
Evidence: Windows Update error reference
- 3
Stop before the generic reset loop
No special tools
Procedure
If the same owner and file recur, diagnose that integration. If no owner is captured, the code does not justify disabling security software or buying a cleaner.
Do not disable antivirus, delete system files or install a registry cleaner on speculation.
Evidence: Windows Update error reference
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and systems
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x80070020
- InstallFileLocked
- Windows Update 0x80070020
What it means
InstallFileLocked is the Windows Update Agent result for this condition: Windows Update could not access a required file because another process was using it. The useful boundary is which process owns the file at the failure time and whether the lock returns after a clean restart. Before paid repair or a managed-IT change, require this evidence: Correlate the KB timestamp with WindowsUpdate.log, CBS.log and Process Monitor or endpoint telemetry; identify the exact handle owner before changing exclusions.
Warnings and stop conditions
- Mediumsource verified
Do not disable antivirus, delete system files or install a registry cleaner on speculation.
Evidence: Windows Update error reference
Symptoms and causes
Probable causes · in order
- What the Microsoft code establishesConfirmed
Microsoft’s Windows Update reference maps 0x80070020 to InstallFileLocked: Windows Update could not access a required file because another process was using it.
Evidence: Windows Update error reference
- The observation that changes the next branchPossible
Discriminate which process owns the file at the failure time and whether the lock returns after a clean restart. If the same owner and file recur, diagnose that integration. If no owner is captured, the code does not justify disabling security software or buying a cleaner.
Evidence: Windows Update error reference
Virtual technician
Does 0x80070020 still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Windows Update error reference
Microsoft · 2026 · official_doc
Was this entry useful?