How to Restart the Clipboard User Service

The Clipboard User Service, internally named cbdhsvc and shown in services.msc as Clipboard User Service, is the user-level Windows service that hosts Win+V clipboard history. When the service stalls — typically after a long sleep, a multi-monitor reconnect, or a clash with a third-party clipboard manager — Win+V stops showing new copies, the Clipboard history toggle becomes unresponsive, and the standard "turn it off and on again" via Settings does not help. Restarting the service is the targeted fix.

This guide covers the safe procedure for restarting the Clipboard User Service on Windows 11, what to do when the service will not restart, and when to escalate to a full reboot or an explorer.exe restart. For related problems, see clipboard history grayed out by organization for the case where a group policy is the cause, explorer.exe restart to unstick copy-paste for the next-level fix, and the broader Win+V not working on Windows 11: 9 fixes and when new copies never appear in Win+V guides.

What the Clipboard User Service does

The Clipboard User Service hosts the per-user clipboard history infrastructure. It runs in the user session (not as a system-wide service) and is started automatically when the user logs in. Each user on a machine has their own instance of the service, which is why the service name in services.msc often appears with a per-user suffix like Clipboard User Service_12345.

The service is responsible for:

• Capturing clipboard events and storing them in Win+V history (up to 25 items, 4 MB each, text/HTML/bitmap formats).
• Hosting the Win+V UI process on demand.
• Coordinating cloud sync when the user has enabled it.

If the service is stopped or stalled, Win+V does not open, new copies do not land in history, and the Settings toggle reflects a state that does not match reality. Restarting the service is the most targeted fix because it clears the service's internal state without touching the rest of the user session.

Method 1: services.msc (the GUI approach)

The simplest restart path is through services.msc:

1. Press Win+R to open the Run dialog.
2. Type services.msc and press Enter.
3. In the list, find Clipboard User Service. Note that there may be a per-user suffix.
4. Right-click the service and choose Restart.
5. If Restart is greyed out, choose Stop, wait a few seconds, then right-click again and choose Start.

After restart, test Win+V. If history appears and new copies land, the fix worked.

This method is the safest because it requires no command-line knowledge and shows the service status in real time. It is the recommended approach for users who are not comfortable with PowerShell.

Method 2: PowerShell (the repeatable approach)

For users who want a repeatable command — for example, to run as a scheduled task or to share with a colleague — PowerShell is the cleaner option.

Run PowerShell as the current user (no elevation needed):

Get-Service -Name cbdhsvc* | Restart-Service -Force

The wildcard is intentional because the actual service name includes the per-user suffix. Restart-Service -Force stops and starts the service in one step, including any dependent services.

To check the service status without restarting:

Get-Service -Name cbdhsvc* | Format-Table Name, Status, StartType

The status should be Running and the start type should be Automatic. If the status is Stopped, the service crashed and was not restarted; if it is Starting or Stopping, the service is stuck mid-transition.

What to do if the service will not restart

If Restart-Service returns an error like "Cannot stop service" or "Service did not respond," the service is stuck in a state where it cannot be cleanly stopped. The escalation path:

1. Try Stop-Service -Force, then Start-Service. Sometimes a stop-then-start works when a restart does not.
2. Kill the host process. The Clipboard User Service runs inside a svchost.exe process. Killing the host process is risky because svchost hosts many services. The safer approach is to identify the specific svchost that hosts cbdhsvc:

Get-WmiObject Win32_Service -Filter "Name LIKE 'cbdhsvc%'" | Select-Object Name, ProcessId

1. End the identified process in Task Manager. Windows will restart the service automatically because the start type is Automatic.

1. If Windows does not restart the service automatically, log off and log back in. The user session restart starts a fresh instance of the service.

1. If logging back in does not help, reboot. Rebooting is the catch-all that resolves stuck service states.

When restarting the service is the right fix

Restarting cbdhsvc is the right fix when:

• Win+V was working and recently stopped.
• New copies do not land in history, but the existing history is still visible.
• The Settings → System → Clipboard toggle is unresponsive.
• The service status (via Get-Service) is Stopped, Paused, or Starting.

It is the wrong fix when:

• A group policy is blocking clipboard history. See clipboard history grayed out by organization.
• A second clipboard manager is fighting Win+V. See when two history tools hook the same copy.
• The clipboard itself is locked by another app. See clipboard stuck until you paste.
• The user has not enabled clipboard history in the first place. See how to enable clipboard history in Windows 11.

Restarting the service in these cases will not produce the expected result and may make the diagnosis harder.

When to escalate to an explorer.exe restart

If restarting cbdhsvc does not restore Win+V, the next escalation is to restart explorer.exe. The Windows shell holds a clipboard viewer registration, and a stuck shell can interfere with the service. Restarting explorer.exe clears the shell's state without logging out.

To restart explorer.exe:

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.

After explorer.exe restarts, test Win+V. For the full breakdown of when this helps and when it is cargo cult, see explorer.exe restart to unstick copy-paste.

When to escalate to a reboot

If neither restarting cbdhsvc nor restarting explorer.exe resolves the problem, the practical answer is to reboot. Rebooting:

• Clears all clipboard handles across all processes.
• Restarts all services including cbdhsvc.
• Re-initializes the shell and the clipboard viewer chain.

The goal of this guide is not to avoid rebooting entirely. It is to identify whether the simpler restart steps would have worked, so that future occurrences can be fixed faster. A reboot without prior diagnosis is a temporary fix; a reboot with prior diagnosis builds a mental model that lets the next fix be quicker.

Prevention

A few habits reduce the frequency of cbdhsvc stalls:

• Run only one clipboard manager at a time. Two managers fighting is a common trigger for service stalls.
• Keep the OS updated. Several cbdhsvc bugs have been fixed in cumulative updates; running an out-of-date build is a known trigger.
• Reboot weekly. Weekly reboots clear accumulated state before it accumulates enough to cause a stall.
• Avoid aggressive power-saving on laptops. Aggressive sleep states can stall cbdhsvc; see after sleep, the first copy is ignored.

What happens to history and pins during a restart

Restarting cbdhsvc does not delete Win+V history. The history is persisted on disk and reloaded when the service starts back up. Specifically:

• Unpinned items — preserved across a service restart (they are only cleared by an OS restart, an explicit "Clear all" from Win+V, or the Clear clipboard data button in Settings).
• Pinned items — preserved across a service restart and across an OS restart. Pinned items survive everything except explicit deletion.
• Cloud sync state — preserved across a service restart. If sync was on, it resumes when the service comes back. If sync was off, it stays off.

This means restarting cbdhsvc is safe from a data-loss perspective. The 25-item cap and the 4 MB per-item cap also continue to apply after the restart. For more on what survives and what does not, see clipboard history cleared after restart — that is normal.

A note on the per-user suffix

The cbdhsvc service name in services.msc often appears with a per-user suffix such as Clipboard User Service_12345. The numeric suffix is the user's logon ID, assigned by Windows at login. This suffix is why the PowerShell wildcard cbdhsvc* is necessary: the exact service name is not predictable across users or sessions.

On a single-user machine, there is typically one cbdhsvc instance and the wildcard matches exactly one service. On a multi-user machine (Terminal Services, fast user switching), there may be multiple cbdhsvc instances — one per logged-in user — and Restart-Service -Force restarts all of them. This is usually the desired behaviour, but on a Terminal Services server it can briefly interrupt every user's Win+V. On a server, restart one instance at a time by name rather than using the wildcard.

A short checklist

If only one thing is done, it should be the services.msc restart (method 1). If two, add the PowerShell status check. If three, add the explorer.exe restart. Most cases resolve at method 1 or method 2. Escalation to a reboot is for the stubborn cases.

Related reading

• Explorer.exe Restart to Unstick Copy-Paste
• Paste Works in Notepad but Not in Word
• 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 the underlying service
• Microsoft Learn — Restart-Service — PowerShell cmdlet reference for restarting Windows services including cbdhsvc
• Microsoft Learn — Get-Service — PowerShell cmdlet reference for inspecting service status
• Microsoft Learn — Win32_Service class — WMI class documentation used to map a service to its host process
• Microsoft Learn — Services management — Windows services command reference covering sc.exe, the command-line alternative to services.msc

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