Copy/Cut/Paste delayed but context menu feels fine

Published October 2026, Windows 11 24H2 / 25H2 and Windows 10

The right-click menu appears instantly. You click Copy, switch folders, click Paste, and wait. Or keyboard Ctrl+C / Ctrl+V on files hitch for seconds. This is easy to misread as “context menu lag” when the menu itself is not the bottleneck.

IContextMenu builds the menu. The shell copy engine, clipboard, cloud placeholders, and copy-hook extensions run afterward. Fix the wrong layer and you waste time disabling WinRAR for a OneDrive placeholder problem.

Split the timeline

Write down four timings:

1. Time to open the menu on a local file.
2. Time from clicking Copy until the menu closes and Explorer feels idle.
3. Time from clicking Paste until the copy dialog finishes (or small file completes).
4. Time for Ctrl+C / Ctrl+V on the same file without opening the menu.

If (1) is slow, use Windows 11 context menu slow fix instead of this article.

Plain clipboard sanity check

1. Open Notepad. Copy a short string. Paste into another Notepad window.
2. If that is slow, look at clipboard managers (Ditto, Windows Clipboard history with huge history, enterprise DLP tools) before blaming Explorer.
3. Settings → System → Clipboard: toggle Clipboard history off for a test on Windows 11.

File paste can still be slow when text paste is fine. Continue below.

Cloud placeholders and “online-only” files

OneDrive, Dropbox, and Google Drive often show files that are not fully local. Paste into or from those trees triggers hydration:

1. Confirm file status icons (cloud vs checkmark).
2. Right-click → always keep on this device (OneDrive) for a test file.
3. Retry Copy/Paste on the now-local file.
4. Pause sync client and retry.

If pause sync fixes paste delay, keep sync but avoid treating Explorer lag as an IContextMenu problem. Disable cloud context menu handlers only if menu open time is also bad.

Copy hook handlers in ShellExView

ShellExView lists Copy Hook Handler as its own type. These DLLs get a say when folders are copied or moved.

1. Open ShellExView as Administrator.
2. Do not hide Microsoft yet if you suspect OneDrive; include vendor filters.
3. Sort or filter Type for Copy Hook Handler.
4. Disable non-essential third-party copy hooks (F7).
5. Restart Explorer. Retest Paste on a local folder.

Use binary search if several copy hooks exist: disable half, test paste, narrow. Same idea as Disable shell extensions on Windows 11, but keep your eyes on paste timing, not menu open timing.

Unknown DLLs: DLL checker.

Antivirus and controlled folder access

On-access scanners inspect every file you copy.

1. Temporarily exclude a test folder (if your security policy allows) or copy between two folders on a RAM disk / local path outside protected areas.
2. Watch whether paste delay drops.
3. If yes, adjust AV realtime exclusions carefully; do not turn off protection permanently without a plan.

Windows Controlled Folder Access can also prompt or slow writes into protected directories. Check Windows Security → Ransomware protection for blocks during paste.

Network paths and Offline Files

Paste to \\server\share waits on SMB latency and server AV. Test:

1. Copy the same file to C:\Temp.
2. If local paste is fast and network paste is slow, fix the network path (not shell menus).
3. Disable Offline Files temporarily if CSC (Client Side Caching) is in play on domain PCs.

Shell extension crashes during paste

If Explorer restarts mid-paste, that is not delay; that is a faulting module.

1. Event Viewer → Application → faulting explorer.exe.
2. Note the module.
3. Disable it in ShellExView.

Follow Find which shell extension is crashing Explorer.

What not to blame

• Disabling random Context Menu handlers will not fix a hydration stall.
• “Repairing” the clipboard with random registry tweaks rarely helps file copy.
• Classic context menu tweaks (24H2/25H2) change menu UI, not the copy engine.

Explorer vs File Explorer search / Home quirks

On Windows 11 24H2/25H2, pasting into Home, gallery-style views, or heavily virtual folders can feel slower than pasting into a plain C:\Temp directory even when handlers are clean. Always include a boring NTFS folder in your tests so you do not chase shell extensions for a UI surface problem.

Also try Paste using the keyboard only, then using the ribbon / command bar Paste button. If only one UI path is slow, note it; most extension issues affect both.

Practical fix order

1. Prove menu open is fast (this article’s premise).
2. Retest on local, fully hydrated files.
3. Disable third-party Copy Hook handlers via ShellExView binary search.
4. Pause cloud sync for A/B.
5. Check AV / Controlled Folder Access.
6. Only then dig into context menu DLLs if you discover (1) was slow after all.

Keeping Copy/Cut/Paste snappy is usually about data path and hooks, not the list of verbs in the menu.

Related guides

• Disable shell extensions on Windows 11
• Windows 11 context menu slow fix
• Find which shell extension is crashing Explorer
• ShellExView download
• DLL checker