Fix ERROR_SEM_USER_LIMIT 0X0000006A – insert disk drive %1

You see this error and it's annoying

You click a drive in File Explorer, and Windows says "Insert the disk for drive X:" with error code 0X0000006A. The drive is physically there, maybe an external SSD or internal partition. It worked yesterday. Now it's pretending to be empty air.

Direct fix – turn off indexing on that drive

The number one cause of ERROR_SEM_USER_LIMIT (0X0000006A) is the Windows Search Indexer locking the volume. It grabs a file handle and doesn't let go. Then any app – including Explorer – can't access the drive. The system thinks the drive is missing because it can't get past the lock.

1. Open This PC in File Explorer.
2. Right-click the problem drive (the one giving the error).
3. Select Properties.
4. At the bottom of the General tab, uncheck "Allow files on this drive to have contents indexed in addition to file properties".
5. Click OK.
6. When a dialog pops up, choose "Apply changes to drive X:\ subfolders and files".
7. Click OK and wait for Windows to finish. This can take a few minutes on a big drive.
8. Reboot the PC.

After the reboot, the drive should show up normally. No more insert disk nonsense.

Why this kills the error

What's actually happening here is the NTFS file system puts a semaphore lock on the volume when the indexer runs. That's the SEM_USER_LIMIT part – semaphore user limit. Windows has a hard cap on how many processes can simultaneously hold a handle to a volume's master file table. The indexer holds one, and if another app (like Explorer) tries to open the volume, it hits the limit and fails. The OS then reports the drive as not available, because technically it can't see the root directory. Disabling indexing frees that handle. Reboot clears any stale locks.

If indexing was already off – check the drive letter

Sometimes the error shows up after you plugged in a USB drive that took the same letter as a network drive or a mapped folder. The system gets confused about which device is at that letter.

1. Press Win + X and select Disk Management.
2. Find the drive that's showing the error. It might appear without a letter, or with a warning icon.
3. Right-click the partition and choose Change Drive Letter and Paths.
4. Assign a new letter – something far from the original. For example, if it was D:\, try V:\.
5. Apply and close.

The drive should pop up in Explorer immediately. The reason step 3 works is the old letter had a registry conflict. Reassigning forces Windows to rebuild the symbolic link between the letter and the device.

Less common causes

I've seen this error on Windows 10 22H2 and Windows 11 23H2 after a system update borks the volume mount point. Here's what to try when the above doesn't help.

Run chkdsk without the indexer running

Boot into Safe Mode (hold Shift while clicking Restart, then Troubleshoot > Startup Settings > Safe Mode). In Safe Mode, open Command Prompt as admin and run:

chkdsk X: /f /r

Replace X with the problem drive. Safe Mode prevents the indexer from loading, so chkdsk can fix file system errors that cause the lock. This is my go-to when the drive is an internal partition that won't mount at all.

Disable Superfetch / SysMain

Superfetch (SysMain service) also sometimes holds a handle to a drive. Stop it temporarily:

1. Press Win + R, type services.msc, hit Enter.
2. Find SysMain in the list.
3. Right-click, choose Stop.
4. Set its startup type to Disabled if the error persists.

I don't like disabling this long-term – it hurts performance on HDDs. But for troubleshooting, it tells you if the service is the culprit.

Prevention – keep your drive free of locks

• Don't let the search indexer run on external drives. Go to Control Panel > Indexing Options > Modify and uncheck any removable drives.
• Unplug USB drives safely before sleep or hibernation. A drive left plugged in when Windows goes to sleep can wake up with a stale lock.
• Keep your system updated. Microsoft fixed a related bug in Windows 11 23H2 KB5035853 – the update that addressed volume lock issues after driver updates.

One last thing – if you have a third-party antivirus (Norton, McAfee, even Malwarebytes), check if it scans removable drives on access. That scanning can also grab a volume handle and trigger the error. Turn off real-time scanning for removable media in your AV settings. If the error stops, you found your culprit.