How to Fix Windows Update Error 0x800F020B
What error 0x800F020B means
Error 0x800F020B is one of Windows Update's more confusing codes because everything else on your PC looks fine while it keeps appearing in your update history. Microsoft support engineers describe it as a "device instance does not exist" condition: Windows Update has a driver package ready for a piece of hardware, but when it goes to install it, the hardware is not there. The device is typically turned off, unplugged, or no longer attached to the computer at all.
Printers are by far the most common trigger — HP printer driver updates failing with this code fill support forums going back years. But it can involve any accessory: scanners, webcams, Bluetooth dongles, external DACs, network adapters, and even wireless cards. In most reports, the device works perfectly or the user does not even use it anymore; Windows Update simply keeps offering the optional driver update and keeps failing on it.
The reassuring part is that 0x800F020B is not a sign of system damage. It blocks only that one driver package. Your files, apps, security updates, and everything else keep working. Think of it as Windows Update being overeager rather than your PC being broken: it is trying to service hardware that is not present, and all you have to do is either give it the device or tell it to stop asking.
Common causes
- The device is off or unplugged during the update: printers in sleep mode, disconnected USB accessories, or Wi-Fi devices out of range make the driver install fail every time.
- You no longer use the device: Windows Update still offers its driver because the old driver files are on the system, even though the hardware is long gone.
- An outdated or corrupted driver conflicts with the new package: a broken existing driver can block the replacement from installing cleanly.
- Corrupted update cache files: damaged SoftwareDistribution or catroot2 folders can turn a simple driver update into a repeated failure.
- Third-party security software interference: some antivirus and firewall products block the driver staging process, especially for network-connected printers.
How to fix error 0x800F020B — step by step
Work through these fixes in order. Most people clear this error by step 3.
- Identify the failing update and reconnect the device. Open Settings, go to Windows Update, then Update history, and find the entry showing error 0x800F020B. Note the device name listed next to it — it is often a printer, scanner, or other accessory. Plug that device in or turn it on, give Windows about a minute to recognize it (you should hear the connection sound for USB devices), then go back to Settings, then Windows Update, and click Check for updates. A driver update that had no target can now install against the real hardware.
- Run the Windows Update troubleshooter. Open Settings, go to System, then Troubleshoot, then Other troubleshooters. Click Run next to Windows Update and follow the prompts. The tool checks the update engine's health, re-registers update components, and repairs common stuck states. Let it apply any repairs it finds, restart your PC, and check for updates again. This alone resolves the error when the failure came from a glitch in the update pipeline rather than the device itself.
- Hide the update if you no longer use the device. If the hardware is gone — an old printer you replaced, a webcam you threw out — the cleanest fix is to stop Windows from offering the update. Download Microsoft's "Show or Hide Updates" troubleshooter, run it, choose Hide updates, and select the problem driver update from the list. Once hidden, Windows Update will not retry it, and the 0x800F020B entries stop appearing in your history permanently.
- Install the driver manually from the manufacturer. Go to the support website of the device maker — HP, Canon, Epson, Brother, or whoever made your hardware — search for your exact model, download the newest driver package for your version of Windows (10 or 11), and install it by following the on-screen instructions. A fresh manufacturer driver usually replaces whatever Windows Update was trying to install, so the failing offer disappears. For printers, the full driver package from the maker's site is almost always better than the stripped-down driver Windows Update delivers.
- Reinstall the device in Device Manager. Press Win + X and choose Device Manager. Expand the category for your device — Print queues for a printer, Imaging devices for a scanner, Bluetooth for a dongle — right-click the device, and choose Uninstall device. You can leave the "Attempt to remove the driver" option checked for a fully clean state. Restart the PC; Windows detects the hardware on boot and installs a fresh driver automatically. This clears broken driver states that were blocking the update from installing.
- Repair system files with DISM and SFC. Right-click Start and choose Terminal (Admin). First run
DISM.exe /Online /Cleanup-image /Restorehealthand wait for it to finish — it repairs the component store that driver packages draw from. Then runsfc /scannow, which scans protected system files and replaces damaged ones. Restart afterward and check for updates again. This step matters most when the error appears for several different driver updates at once, which points to damaged update machinery rather than one bad device. - Reset the Windows Update components. In an admin terminal, stop the update services one at a time:
net stop wuauserv,net stop cryptSvc,net stop bits,net stop msiserver. Then rename the caches withren C:\Windows\SoftwareDistribution SoftwareDistribution.oldandren C:\Windows\System32\catroot2 catroot2.old. Restart the services withnet start wuauserv,net start cryptSvc,net start bits, andnet start msiserver. Windows rebuilds both folders with fresh files on the next update check, which wipes out corrupted downloads that were failing repeatedly with this code.
Did this fix it? Quick checklist
- The driver update installs successfully with no 0x800F020B in update history
- The device appears in Device Manager with no yellow warning icons
- Settings, then Windows Update shows "You're up to date"
- The device itself (for example, the printer) works normally after updating
If the error persists after all seven steps, try a clean boot to rule out software conflicts: press Win + R, type msconfig, go to the Services tab, check "Hide all Microsoft services," disable everything else, restart, and check for updates. Third-party security tools are the usual culprits here — temporarily disabling them during the update often lets a stubborn driver install complete. If it still fails, check the manufacturer's support site for a firmware update for the device itself; some printers and network adapters need newer firmware before their drivers can update.
Frequently asked questions
What does error 0x800F020B mean?
Error 0x800F020B means Windows Update tried to install a driver for a device it cannot reach. Microsoft support engineers describe it as a "device instance does not exist" condition: the hardware the update targets is turned off, unplugged, or no longer part of the PC, so the installation cannot complete.
Is error 0x800F020B dangerous for my PC?
No. It only blocks that one driver update; your system, files, and other updates are unaffected. Your Windows installation is not damaged. The error is Windows Update being too eager, offering a driver for hardware that is not there, rather than a sign of a serious problem.
I do not own that device anymore. How do I stop the error?
Hide the update so Windows Update stops retrying it. Download the "Show or Hide Updates" troubleshooter from Microsoft, run it, choose Hide updates, and select the failing driver update. Once hidden, Windows will not offer it again and the 0x800F020B entries disappear from your update history.
Why does my HP printer keep triggering 0x800F020B?
Printers, especially HP models, are the most common trigger. Windows Update periodically pushes printer driver packages, and if the printer is off, asleep, or disconnected by USB or Wi-Fi when the update runs, the install fails with this code. Keep the printer powered on and connected during updates, or install the full driver package from the maker's support site instead.