After Sleep, the First Copy Is Ignored

After the PC wakes from sleep, the first copy is often ignored. The user wakes the machine, copies a snippet, switches to another app, and tries to paste — but the clipboard still has whatever was on it before sleep. The second copy works. Sometimes the third or fourth is needed. The pattern is consistent across Windows 11 builds and has a specific cause: the clipboard listener in the Clipboard User Service (cbdhsvc) stalls during the wake transition and does not re-subscribe to clipboard events until it sees a successful write.

This guide covers the diagnostic order for the "first copy after sleep is ignored" symptom on Windows 11. For related problems, see OneDrive / Office clipboard taking over for a different clipboard-takeover case, clipboard sync says on but devices disagree for the cross-device variant, and the broader Win+V not working on Windows 11: 9 fixes and Win+V Says 'Nothing Here'? How to Fix Clipboard History on Windows 11 guides.

Why the first copy is lost

When Windows enters sleep, all user-mode services are suspended, including cbdhsvc. When Windows wakes, the services resume, but the wake transition is not atomic. cbdhsvc has to re-register as a clipboard listener with the shell, and on some wake paths — particularly Modern Standby (S0 low-power idle) on laptops — the re-registration can lag behind the user's first copy by a few hundred milliseconds. The first copy is written to the live clipboard by the source app, but cbdhsvc's listener is not yet subscribed, so the copy is not added to Win+V history.

The symptom has two variants:

• Win+V-only failure. The first copy lands on the live clipboard (Ctrl+V works) but does not appear in Win+V history. The second copy appears in Win+V normally.
• Total clipboard failure. The first copy does not land on the live clipboard at all. Both Ctrl+V and Win+V are stale. The second copy works for both.

The first variant is more common and is the typical "first copy after sleep is ignored" complaint. The second variant is rarer and usually indicates a deeper stall in the shell's clipboard infrastructure.

Layer 1: confirm with a second copy

The fastest diagnostic is to copy the same text a second time. If the second copy appears in Win+V history and Ctrl+V works, the cause is the listener-stall pattern described above. No fix is needed for the immediate case — the user can simply re-copy.

This is also the workaround: after waking the PC, copy once into Notepad (or anywhere) to "prime" the listener, then copy the actual content for use. The priming copy wakes the listener; the real copy lands in history.

Layer 2: toggle clipboard history off and back on

If the listener stall persists beyond the first copy, the next step is to toggle clipboard history in Settings. Toggling forces cbdhsvc to re-subscribe to clipboard events cleanly.

To toggle:

1. Open Settings → System → Clipboard.
2. Toggle Clipboard history to Off.
3. Wait a few seconds.
4. Toggle Clipboard history back to On.
5. Test with a fresh copy.

After the toggle, the listener is in a clean state and should capture subsequent copies normally. Existing history is preserved during a toggle (it is only cleared by an OS restart or an explicit Clear).

Layer 3: restart the Clipboard User Service

If toggling does not help, the next step is to restart cbdhsvc. This clears any stall in the service's internal state and forces a fresh listener subscription.

To restart:

1. Open PowerShell as the current user.
2. Run Get-Service -Name cbdhsvc* | Restart-Service -Force.
3. Test with a fresh copy.

For the full procedure and what to do if the service will not restart, see how to restart the clipboard user service.

Layer 4: rule out Modern Standby issues

Modern Standby (S0 low-power idle) is the sleep mode used by most modern laptops. Unlike traditional S3 sleep, Modern Standby keeps the system in a low-power but partially-on state, and the wake transition is faster but less predictable. The first-copy-after-sleep symptom is more common on Modern Standby devices than on S3 devices.

To check which sleep mode the device uses:

1. Open a command prompt as administrator.
2. Run powercfg /a.
3. Look at the available standby states. If Standby (S0 Low Power Idle) is listed as available, the device uses Modern Standby. If only Standby (S3) is listed, the device uses traditional sleep.

If Modern Standby is the cause and the symptom is severe, the workaround is to disable Modern Standby in the BIOS or UEFI settings (the setting is usually called Modern Standby, Connected Standby, or S0ix). Disabling Modern Standby forces the device to use S3 sleep, which has a cleaner wake transition but uses slightly more battery during sleep.

Disabling Modern Standby is a significant change and should be tested for battery impact. For most users, the priming-copy workaround (layer 1) is sufficient and Modern Standby can stay enabled.

For more on sleep interactions, see sleep wake false copy events and clipboard history and fast startup odd wipes explained.

Layer 5: rule out Fast Startup

Fast Startup is a Windows feature that performs a partial hibernation on shutdown to speed up the next boot. Fast Startup can produce a similar first-copy-ignored symptom because the system state on boot is not a clean cold boot.

To disable Fast Startup:

1. Open Control Panel → Power Options.
2. Click Choose what the power buttons do on the left.
3. Click Change settings that are currently unavailable (requires admin).
4. Uncheck Turn on fast startup (recommended).
5. Save changes.

After disabling, the next shutdown is a true cold boot, and the first copy after boot should land normally. For more on Fast Startup and its interactions with clipboard, see clipboard history and fast startup odd wipes explained.

Layer 6: rule out a third-party clipboard manager

A third-party clipboard manager with its own listener can compound the first-copy-after-sleep problem. If both cbdhsvc and the third-party manager are stalled, neither captures the first copy. The diagnostic is to exit the third-party manager and test — if the first-copy problem goes away with the manager exited, the manager is contributing to the stall.

For the wider topic, see when two history tools hook the same copy.

Layer 7: update Windows and drivers

The first-copy-after-sleep symptom has been the subject of several Windows updates. Keeping the OS current is the most reliable long-term fix. Specifically:

1. Open Settings → Windows Update.
2. Click Check for updates.
3. Install any available cumulative updates.
4. After installation, restart the PC.

In addition, update the device's chipset and power management drivers from the manufacturer's website (Dell, HP, Lenovo, etc.). Outdated power management drivers can cause Modern Standby wake issues that manifest as clipboard stalls.

Prevention

A few habits reduce the frequency of first-copy-after-sleep stalls:

• Prime the clipboard with a throwaway copy after waking. Copy a single character into Notepad, then copy the real content. The priming copy wakes the listener.
• Keep Windows and drivers updated. Several cbdhsvc bugs have been fixed in cumulative updates.
• Reboot weekly. A weekly reboot clears accumulated state and reduces the chance of a stall building up over time.
• Consider disabling Modern Standby if the symptom is severe and battery life allows. See layer 4.

What does not help

A few commonly suggested fixes do not help with first-copy-after-sleep:

• Disabling Win+V. Disabling history does not fix the underlying listener stall; it just hides the symptom.
• Clearing Windows clipboard history. Clearing history does not affect the listener state.
• Reinstalling Windows. Never the answer to a sleep-wake clipboard stall.
• Running an SFC scan. SFC repairs corrupted system files; a clipboard stall is not caused by corrupted system files in the vast majority of cases.

What about cloud sync state after sleep

Cloud sync (when enabled) resumes after cbdhsvc recovers, but the resume can lag the local listener recovery by several seconds. The practical pattern:

1. Wake the PC.
2. Prime with a throwaway copy (layer 1).
3. Wait 10–15 seconds before copying content meant to sync to another PC.
4. Confirm the synced copy arrives on the other PC within a minute or two.

If the synced copy does not arrive on the other PC, the cause may be cloud sync state rather than local listener state. See clipboard sync says on but devices disagree for the cross-device diagnostic.

A short checklist

If only one thing is done, it should be the priming-copy workaround (layer 1). If two, add the Settings toggle (layer 2). If three, add the service restart (layer 3). Most cases resolve at layer 1 or 2. Layer 4 (Modern Standby) is for cases where the symptom is severe enough to justify changing sleep modes.

Related reading

• Clipboard Sync Says On but Devices Disagree
• iPhone to Windows Paste: What Works in 2026
• 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 architecture
• Microsoft Learn — Modern Standby — Windows hardware design documentation covering Modern Standby (S0 low-power idle) and its wake behaviour
• Microsoft Learn — Restart-Service — PowerShell cmdlet reference for restarting the cbdhsvc service
• Microsoft Learn — Powercfg command-line options — Windows documentation covering powercfg /a and other power configuration commands
• Microsoft Learn — Fast Startup — Windows driver documentation covering Fast Startup and its interaction with system state on boot

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