The failure pattern is specific: update installation reports 0x80070020 while another application is using a required file. A useful repair starts by determining which part of that path still works.
Identify the scope
Primary symptom. Update installation reports 0x80070020 while another application is using a required file. Record the precise point of failure and whether the same input, account or connected device succeeds in another supported mode. That working comparison establishes the scope of the repair.
Explain the likely failure layers
The first hypothesis is a mismatch in the failing path. Record the failed KB and perform one clean reboot with no other installers running. The second is a lower-level state that the interface may not show: read servicing logs to identify the lock holder and distinguish security filtering from an actual file handle conflict. A third possibility is a feature or version limitation, which should be checked against supported documentation before a reset.
For this Windows issue, capture Windows edition, device management status and the before/after Event Viewer timeline and compare configuration applied to the signed-in Windows profile. Preserve the last known working configuration so you can tell whether a successful retry came from an actual correction or a temporary recovery.
Which observation matters
| What you observe | What it suggests | Focused response |
|---|---|---|
| Update installation reports 0x80070020 while another application is using a required file | The failure affects the specific workflow described here; the entire system is not necessarily broken. | Record the failed KB and perform one clean reboot with no other installers running. |
| The basic comparison exposes a difference between a working and failing configuration. | A local setting, version, account context or device route deserves attention. | Pause overlapping application upgrades and retry the update with ordinary protections intact. |
| The same failure persists after a reversible correction. | A deeper dependency or compatibility issue may remain. | Read servicing logs to identify the lock holder and distinguish security filtering from an actual file handle conflict. |
Before changing anything: Keep a recovery path for settings and files; never weaken security controls or erase the only copy of personal data as a first repair. Save a screenshot or anonymized log line, record the previous setting, and back up relevant user data. Do not reset every related service just because one test fails.
Choose a recovery route. The Beginner path checks record the failed KB and perform one clean reboot with no other installers running. The Advanced path investigates read servicing logs to identify the lock holder and distinguish security filtering from an actual file handle conflict. They address different evidence; use the path that matches your result.
Step-by-Step Troubleshooting
Choose the Beginner route for reversible checks or Advanced for evidence-driven diagnosis.
Recognize the affected configuration
Update installation reports 0x80070020 while another application is using a required file. Before editing settings, note the exact time, affected account or device, and whether it started after an update, move, hardware change or network change. This is the baseline for the Windows Update Error 0x80070020: Identify the Process Blocking Installation guide.
Check the failed KB and perform one clean reboot with no other
Record the failed KB and perform one clean reboot with no other installers running. Observe whether the symptom changes. A clean comparison tells you which part of the process is healthy and avoids unnecessary resets.
Adjust pause overlapping application upgrades and retry the
Pause overlapping application upgrades and retry the update with ordinary protections intact. Change only this variable, record its former value, and try the failing action once. If there is no improvement, restore the prior configuration before exploring the Advanced route.
Verify the KB installs without a sharing-violation error and the
The KB installs without a sharing-violation error and the competing application still works. Repeat using the same account, network, file, title or hardware condition that previously failed. Do not count a different test as confirmation.
Inspect supporting logs
Collect the error text or state relevant to Windows Update Error 0x80070020: Identify the Process Blocking Installation. Record Windows edition, device management status and the before/after Event Viewer timeline; anonymize account IDs, public IPs and secret-bearing log fragments before sharing.
Inspect read servicing logs to identify the lock holder and
Read servicing logs to identify the lock holder and distinguish security filtering from an actual file handle conflict. Record the difference between successful and failed cases and keep the first meaningful error rather than the last cascade message.
Get-WindowsUpdateLogRule out related configuration drift
Where practical, compare configuration applied to the signed-in Windows profile. If the alternate case works, return to the single configuration difference instead of changing multiple services. Use the vendor-supported method for your current version.
Verify and record results
The KB installs without a sharing-violation error and the competing application still works. Leave the previous value documented for rollback, then monitor one normal operating cycle. If symptoms recur, attach the sanitized evidence to a vendor or administrator support request.
Avoid making the problem worse
After the first corrective action, interpret the result carefully. If the original task now works, leave the other settings unchanged. If it still fails, read servicing logs to identify the lock holder and distinguish security filtering from an actual file handle conflict. Compare configuration applied to the signed-in Windows profile rather than adding random fixes on top of one another.
For escalation, retain Windows edition, device management status and the before/after Event Viewer timeline, the original output, and a single before/after comparison. Redact passwords, tokens and personal data. A support agent can then distinguish configuration applied to the signed-in Windows profile from a general outage without repeating risky actions.
Optional targeted diagnostic
Reconstruct the Windows Update client log for the current PC; inspect and redact sensitive environment data. Commands below are illustrative and must be run only on systems you are authorized to inspect.
Get-WindowsUpdateLogSuccessful recovery looks like
Pass condition: The KB installs without a sharing-violation error and the competing application still works. The validation must exercise the same path that failed originally. A successful settings screen, single ping, application homepage or idle system is not enough if the original failure appears during a different action.
Repeat the test under the original conditions once after a safe relaunch, reconnect or new session. For intermittent failures, record the time and the difference between a clean result and a failed one instead of claiming success from a single attempt.
Ongoing maintenance
If the problem persists, restore any test-only settings, preserve the evidence and stop before destructive reset, firmware flash or credential recreation. Give official support the exact symptom, the first failing timestamp and what the comparison established. Keep a recovery path for settings and files; never weaken security controls or erase the only copy of personal data as a first repair.
Prevent recurrence: Document the working correction: Pause overlapping application upgrades and retry the update with ordinary protections intact. Retain the accepted result (the KB installs without a sharing-violation error and the competing application still works) as a future regression test after configuration, software or hardware changes.
Solution Checklist
Questions specific to this fault
How do I know the symptom is actually resolved?
The KB installs without a sharing-violation error and the competing application still works. A generic diagnostic test outside the affected workflow is not a substitute.
Should I reset or reinstall everything first?
No. Record the failed KB and perform one clean reboot with no other installers running. Then choose the smallest supported intervention: pause overlapping application upgrades and retry the update with ordinary protections intact. Preserve recoverable settings and user data.
What should I include in a support request?
Provide the exact failing action, product and version, time, non-sensitive log evidence, and this deeper observation: Read servicing logs to identify the lock holder and distinguish security filtering from an actual file handle conflict. Do not include credentials or private customer data.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.