Fix ERROR_SEEK_ON_DEVICE (0X00000084) in Windows
This error means the system can't move the read/write head on a drive or file. Usually a bad physical drive or corrupt file handle. Here's the fix.
You're staring at 0X00000084 and your file won't open. Don't panic.
That error means Windows tried to reposition the read/write head on your drive and couldn't do it. Most of the time it's a dying drive or a corrupt file handle. I've seen it on USB sticks, external hard drives, and internal SSDs. Here's the fastest way to deal with it.
First fix: Run CHKDSK on the affected drive
Open Command Prompt as Administrator (right-click Start, choose Command Prompt Admin or Terminal Admin). Then type:
chkdsk X: /f /rReplace X with the actual drive letter from the error. The /f flag fixes file system errors. The /r flag finds bad sectors and recovers readable data. This is your best shot.
If it's your system drive (C:), it'll ask to schedule on next reboot. Say Y and restart. Let it run. It can take hours on a large drive, but it's worth it. Had a client last year whose external 2TB drive threw this error on every file. CHKDSK found 200+ bad sectors, remapped them, and the drive worked for six more months.
What if CHKDSK won't run?
If CHKDSK says "The type of the file system is RAW" or just hangs, the drive is likely physically failing. Stop trying to scan it. Back up what you can immediately using Robocopy in "copy only" mode:
robocopy X:\ Y:\Backup /E /COPY:DT /R:1 /W:1Replace X with source, Y with a good drive. This copies files without retrying endlessly on bad sectors.
Second fix: Close the stuck file and reopen
Sometimes the file handle goes stale. Close all programs that might be using that file. Force-quit Explorer via Task Manager (right-click Windows Explorer, restart). Then try again. Sounds stupid, but I've fixed this exact error on a network share by just logging the user off and back on. The file pointer was stuck from a previous failed write. A fresh login cleared it.
Third fix: Check for USB or external drive issues
If the drive is external, try a different USB port, especially a USB 2.0 port (black, not blue). Power fluctuations can cause seek errors. Also try a different cable. I've seen a frayed USB 3.0 cable cause this error intermittently for weeks before it completely died. Swapped the cable, and the error vanished.
Less common variations of 0X00000084
You might see this error in three different contexts:
- On a network share: The remote file handle timed out. Reconnect the drive in Windows (net use Z: /delete, then net use Z: \\server\share).
- During a backup or copy operation: The source drive is flaky. Use a tool like Teracopy that handles errors gracefully, or switch to robocopy.
- On a virtual machine disk (VMDK/VHDX): The hypervisor can't seek on the virtual disk. Compact the VHDX or check the underlying storage for errors. Had a client whose Hyper-V VM threw this constantly—turned out the RAID5 array had a failed drive.
Prevention: Don't let this happen again
Three simple rules:
- Check drive health monthly. Use CrystalDiskInfo (free) to read S.M.A.R.T. data. If it flags anything in yellow or red, replace the drive.
- Eject USB drives properly. Never just pull them out. Windows caches writes, and pulling the plug corrupts the file table. Click the Safely Remove Hardware icon. It takes 2 seconds.
- Back up before you need to. Use the 3-2-1 rule: three copies, two different media, one offsite. A cheap external drive and Backblaze (or similar) will save your bacon.
One last thing: if you see this error on multiple files or drives, check your RAM. Faulty memory can corrupt file reads and cause phantom seek errors. Run Windows Memory Diagnostic (mdsched.exe) if you're suspicious.
That's the real fix. No fluff, just what works.
Was this solution helpful?