0X0000006E

Fix ERROR_OPEN_FAILED 0X0000006E on Windows

This error means Windows can't open a device or file. The culprit is almost always a corrupted driver or a bad storage path. Here's how to nail it fast.

Quick Answer

Run chkdsk /f /r on the drive, then sfc /scannow in an admin Command Prompt. If that doesn't stick, update or reinstall the device driver triggering the error.

Why This Happens

Error 0X0000006E shows up when Windows tries to open a file or device and fails. I've seen this mostly in two places: during driver installation (especially printers, USB devices, or graphics cards) or when a service tries to access a corrupted file. The real cause is almost always a bad driver, a file system corruption, or a registry entry pointing to a path that doesn't exist anymore. Users running Windows 10 21H2 or Windows 11 22H2 tend to hit this after a failed driver update or a sudden power loss.

Fix Steps

  1. Run chkdsk on the affected drive
    Open Command Prompt as admin. Type chkdsk C: /f /r and hit Enter. If it asks to schedule at next reboot, type Y and restart. This fixes file system corruption that blocks file access.
  2. Run System File Checker
    In the same admin Command Prompt, type sfc /scannow. Let it finish — takes 10-15 minutes. It replaces corrupted system files. If it finds stuff it can't fix, run DISM /Online /Cleanup-Image /RestoreHealth first, then sfc again.
  3. Update the problem driver
    Open Device Manager (right-click Start > Device Manager). Look for any device with a yellow warning triangle. Right-click it, select Update driver > Search automatically. If Windows finds nothing, go to the manufacturer's site and download the latest driver. For graphics cards, use the vendor's tool (GeForce Experience or AMD Adrenalin).
  4. Check the registry path
    This one's for advanced users. Press Win+R, type regedit. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. Look for the service tied to the error (check Event Viewer for clues). Find the ImagePath value — make sure the file exists at that path. If not, you can fix the path or delete the key (backup first).

Alternative Fixes

If the main steps don't work, try these in order:

  • Run a clean boot — use msconfig to disable all non-Microsoft services and startup items. If the error stops, a third-party service is the culprit. Re-enable services one by one to isolate it.
  • Restore to a previous point — open System Restore and pick a restore point before the error started. I've had this save my ass more than once after a bad driver update.
  • Reinstall the device — in Device Manager, right-click the device and select Uninstall. Check the box to delete the driver software. Reboot and Windows will reinstall the default driver.
  • Check for malware — run a full scan with Windows Defender or Malwarebytes. Some rootkits cause this error by blocking access to system files.

Prevention Tips

Don't skip Windows updates — they include driver fixes. Also, use a UPS if you're on an unstable power grid. A sudden power loss during a driver install is a classic way to corrupt files. And for god's sake, stop using driver updater tools like Driver Booster — they cause more issues than they fix. Stick to Windows Update or the manufacturer's site.

Related Errors in Windows Errors
0XC0262323 Fix 0xC0262323: Graphics No Recommended VidPN 0X00000FDA PEERDIST_ERROR_ALREADY_EXISTS (0x00000FDA) Fix 0XC00D12C1 Fix NS_E_WMP_DRM_NOT_ACQUIRING (0XC00D12C1) in Windows Media Player 0X80290111 Fix TPMAPI_E_INVALID_KEY_PARAMS (0X80290111) on Windows 10/11

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.