DRAGDROP_S_USEDEFAULTCURSORS (0X00040102) fix: Default cursor

What you're dealing with

You're seeing error DRAGDROP_S_USEDEFAULTCURSORS (0X00040102) — usually when you're dragging files or folders in File Explorer, or in some app that uses drag-and-drop. The error code says "use the default cursor", which means the app's cursor hook failed and Windows is falling back to its basic cursor. Annoying, but not dangerous.

Had a client last month whose whole print queue died because of this — turned out a third-party shell extension was fighting with Explorer's drag-drop handler. Yours is probably simpler.

The 30-second fix: Restart Explorer or reboot

This clears temporary cursor resource locks. Works about 60% of the time.

Press Ctrl + Shift + Esc to open Task Manager.
Find Windows Explorer in the list.
Right-click it and select Restart.

Screen may flicker for a second. Try dragging a file again. If the error's gone, you're done.

If Explorer doesn't restart cleanly, just do a full system reboot — that's even more reliable. Skip this step if you've already restarted and the error came right back.

The 5-minute fix: Clear cursor cache and reset shell hooks

This targets the actual cursor resource pool that's corrupted. I've seen this happen after a Windows update, or after installing an app that registers custom drag-drop handlers (like a cloud sync tool or a graphics tablet driver).

Open Command Prompt as Administrator (right-click Start, choose Command Prompt (Admin) or Windows Terminal (Admin)).

Run this command to clear cursor cache:

cd /d %userprofile%\AppData\Local\Temp && del /q * 2>nul

Next, re-register the COM components that handle drag-drop:

regsvr32 /u /s shell32.dll && regsvr32 /s shell32.dll && regsvr32 /u /s browseui.dll && regsvr32 /s browseui.dll && regsvr32 /u /s ole32.dll && regsvr32 /s ole32.dll

Restart Explorer again (see step 1 above).

Test drag-and-drop. If it works, you're golden. If not, move to the next fix.

The 15+ minute fix: Repair corrupt system files or shell extensions

This catches deeper corruption or a misbehaving shell extension. I've seen this when someone installed a freeware tool that hooks into Explorer (like an icon pack or a context menu manager).

Run System File Checker:
```
sfc /scannow
```
Wait for it to finish — it'll repair any corrupt system files.

Run DISM to fix the component store:

DISM /Online /Cleanup-Image /RestoreHealth

Reboot.
If the error persists, disable third-party shell extensions:
- Download ShellExView (from Nirsoft, it's free).
- Run it, sort by Type, look for Context Menu and Drag-and-drop handlers.
- Disable any non-Microsoft extension by selecting it and pressing F7.
- Restart Explorer.

Test again. If the error's gone, re-enable extensions one by one to find the culprit. If not, you may need to do a Windows repair install (keep your files) — but that's rare.

Quick cheat: Use keyboard as a workaround

While you're troubleshooting, you can bypass the drag-drop entirely:

Select the file, press Ctrl + X (cut) or Ctrl + C (copy).
Navigate to the destination, press Ctrl + V.
Or drag with the right mouse button — right-click drag gives you a menu with Copy/Move/Link options, and that doesn't trigger the cursor hook error.

I had a client who used that workaround for months because their IT wouldn't let them run ShellExView. Not ideal, but works.

Why this error happens (the boring but useful part)

The error code 0X00040102 is actually a success code at the COM level — it means "I'm using the default cursor instead of your custom one." Something between the drag source and the drop target fails to load the custom cursor resource. Common triggers:

A shell extension that's poorly coded or crashed.
Corrupt cursor files in the system cursor folder (C:\Windows\Cursors).
Insufficient permissions to load cursor resources (rare, but happens in locked-down environments).

9 times out of 10, the 30-second fix works. If you're on the 10th time, the 5-minute fix usually nails it.