Explorer.exe Restart to Unstick Copy-Paste

Restarting explorer.exe is the classic Windows fix for a stuck copy-paste. The taskbar disappears for a second, the desktop flickers, and the shell comes back. Sometimes this resolves the clipboard; sometimes it does nothing; sometimes it makes things worse. The technique is widely shared online, but the reasons it works — when it works — are usually not explained. This guide separates the cases where explorer.exe restart is the right fix from the cases where it is cargo cult.

For related problems, see how to restart the clipboard user service for the more targeted fix, paste works in Notepad but not in Word for app-specific cases, and the broader Win+V not working on Windows 11: 9 fixes and clipboard history not saving items guides.

What explorer.exe actually is

explorer.exe is the Windows shell process. It hosts the desktop, the taskbar, the Start menu, File Explorer windows, and the notification tray. It also holds a clipboard viewer registration — a slot in the clipboard viewer chain that lets it react to clipboard changes for shell features like suggested actions on copied text.

When explorer.exe is restarted, the shell process is terminated and a fresh instance is launched. The new instance re-registers as a clipboard viewer, rebuilds the taskbar and tray, and reloads shell extensions. This is why restarting explorer.exe sometimes fixes clipboard problems: it clears the shell's stale state.

What explorer.exe is not:

• It is not the Clipboard User Service (cbdhsvc). That runs in a separate svchost process.
• It is not the clipboard itself. The clipboard is a kernel resource shared across all processes.
• It is not Win+V. Win+V is hosted by cbdhsvc, not by explorer.exe.

Restarting explorer.exe therefore fixes clipboard problems only when the shell's clipboard-related state is the cause. For other causes, it does nothing.

How to restart explorer.exe safely

The safe procedure on Windows 11:

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Find Windows Explorer in the Processes list.
3. Right-click and choose Restart. The taskbar and desktop will briefly disappear and return.

An older method — killing explorer.exe in Task Manager and then running explorer.exe from File → Run new task — also works but is more disruptive and not necessary on Windows 11, which has the Restart option built in.

From PowerShell or a command prompt:

Stop-Process -Name explorer -Force

explorer.exe will restart automatically because it is configured as the shell. If it does not restart, run start explorer.exe from a Command Prompt or PowerShell window.

When restarting explorer.exe is the right fix

Restarting explorer.exe is the right fix when:

• Right-click paste is missing in File Explorer. The classic context menu's Paste command depends on shell extensions that load into explorer.exe. A broken shell extension can remove the Paste entry; restarting explorer.exe reloads the extensions.
• Suggested actions on copied text stopped appearing. The suggested-actions feature runs through the shell; a stuck shell stops showing suggestions.
• The taskbar clipboard-related tray icons are stuck. A stuck tray icon for a clipboard manager is a shell problem, not a manager problem.
• Win+V opens but the flyout renders incorrectly. A corrupted shell state can interfere with the Win+V flyout's rendering; restarting explorer.exe clears it.

In each of these cases, the cause is in the shell, and restarting the shell is the targeted fix.

When restarting explorer.exe is cargo cult

Restarting explorer.exe does not help when:

• The Clipboard User Service (cbdhsvc) is stalled. The service runs separately; restarting explorer.exe does not touch it. See how to restart the clipboard user service.
• An app is holding the clipboard open. The lock is in the holding app's process, not in the shell. See clipboard stuck until you paste.
• A group policy is blocking clipboard history. The policy is enforced at the OS level; restarting the shell does not change policy. See clipboard history grayed out by organization.
• Two clipboard managers are fighting. Both managers run as separate processes; restarting the shell does not stop them. See when two history tools hook the same copy.
• Paste fails in one specific app. The cause is in that app, not in the shell. See paste works in Notepad but not in Word and paste works in Word but not in a browser.
• UAC is blocking paste into an elevated window. The integrity-level boundary is enforced by the OS, not the shell. See cannot paste into an admin window.

In each of these cases, restarting explorer.exe is a waste of time and may delay the actual fix.

Why the cargo cult persists

The reason "restart explorer.exe" is so commonly suggested — even when it does not help — is that it sometimes works by coincidence. When explorer.exe is restarted, several side effects occur:

• Any app that watches the shell for state changes gets a notification. Some apps re-initialise their clipboard viewer registration in response. If a stuck viewer registration was the cause, the restart fixes it indirectly.
• Some apps check for explorer.exe presence at startup and re-register hotkeys if they detect a new shell. If a hotkey conflict was the cause, the restart may resolve it.
• The clipboard viewer chain — the linked list of apps watching the clipboard — is rebuilt. A broken chain link is sometimes fixed by the rebuild.

These indirect effects are why restarting explorer.exe has a reputation as a universal fix. The reputation is overstated. For each indirect fix, there is a more targeted fix (restart the specific service, fix the specific app, disable the specific conflict) that works more reliably and does not disrupt the user's taskbar and open windows.

What to try before restarting explorer.exe

Before reaching for an explorer.exe restart, try the more targeted fixes:

1. Paste into Notepad once. If the clipboard is locked, pasting once may release the lock. See clipboard stuck until you paste.
2. Restart cbdhsvc. This is the targeted service-level fix. See how to restart the clipboard user service.
3. Close suspect apps. Specifically, close remote desktop clients, screen capture tools, and any third-party clipboard manager.
4. Test in a different app. If paste works in Notepad but not in Word, the cause is Word, not the shell. See paste works in Notepad but not in Word.

If none of those resolve the problem, restart explorer.exe as a second-tier escalation.

What to try after restarting explorer.exe

If restarting explorer.exe does not resolve the problem, the next escalation is a reboot. A reboot:

• Clears all clipboard handles across all processes.
• Restarts cbdhsvc, explorer.exe, and all clipboard viewers from scratch.
• Re-applies group policies and MDM profiles.
• Reloads shell extensions in their initial state.

A reboot is the catch-all that resolves stuck-clipboard cases that survive the more targeted fixes. For more on when this is the right answer, see when to reset Windows because paste is haunted.

Prevention

A few habits reduce the frequency of needing to restart explorer.exe:

• Keep shell extensions to a minimum. Every shell extension installed (Right-click enhancers, file previewers, etc.) is a potential source of shell instability. Review installed extensions periodically.
• Avoid running explorer.exe as administrator. Running the shell elevated causes UAC complications and can stall clipboard operations across integrity levels. See cannot paste into an admin window.
• Reboot weekly. Weekly reboots clear accumulated shell state before it accumulates enough to cause a stall.
• Keep the OS updated. Several shell bugs have been fixed in cumulative updates.

What restart explorer.exe does not lose

Restarting explorer.exe preserves:

• All open File Explorer windows return after the restart (their state is restored by the shell).
• The clipboard contents themselves — the kernel-level clipboard survives an explorer.exe restart because it is not owned by the shell.
• Win+V history — the history is held by cbdhsvc, not by explorer.exe. Pinned items remain pinned; unpinned items remain until the next OS restart.
• Cloud sync state — the sync toggle is held by cbdhsvc and is not affected.

What is lost or interrupted:

• Any in-progress File Explorer file operation (copy, move, delete) is interrupted if it has not completed. Files in transit may be left in a partial state.
• Any unsaved state in a shell-hosted dialog (a Save As dialog, a Properties window) is lost.
• Tray icons for apps that do not handle the "shell restarted" notification may disappear until the app is restarted.

These side effects are why explorer.exe restart is not the first tool to reach for. It is a second-tier escalation that should follow the more targeted fixes in the "what to try before" section.

A short checklist

If only one thing is done, it should be confirming the cause is in the shell (right-click paste missing, suggested actions missing, tray stuck). If two, add the safe restart procedure. If three, add the more-targeted alternatives in the "what to try before" section. The goal is to reach for explorer.exe restart only when the cause is actually in the shell, not as a reflex.

Related reading

• Paste Works in Notepad but Not in Word
• Paste Works in Word but Not in a Browser
• Win+V Not Working on Windows 11: 9 Fixes
• Best Free Clipboard Manager for Windows

Sources

• Microsoft Support — Using the clipboard on Windows — official description of the Win+V feature and how the shell interacts with the clipboard
• Microsoft Learn — Stop-Process — PowerShell cmdlet reference for terminating processes including explorer.exe
• Microsoft Learn — Explorer.exe command-line options — command reference for launching and controlling the Windows shell
• Microsoft Learn — Shell extension registration — Windows shell documentation covering how shell extensions load into explorer.exe
• Microsoft Learn — Clipboard viewer chain — Windows clipboard documentation covering the viewer chain that the shell participates in

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support