Interactive Troubleshooter

Published: Sep 12, 2026

Clipboard History Not Syncing Across Devices: Diagnostic & Repair Guide

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Exhaustive root-cause diagnostic tree for resolving cross-device clipboard history synchronization failures in Windows. Systematically addresses Clipboard User Service (cbdhsvc) crashes, Microsoft Connected Devices Platform Service (CDPSvc) token desynchronization, Enterprise GPO/MDM restrictions, and local SQLite clipboard database corruption.

Full Diagnostic Tree & Step-by-Step Overview

What specific behavior or error occurs when attempting to use Clipboard History (Win + V) and cloud synchronization?

Win + V opens and records local clips, but copied text/images never appear on second logged-in device.
Settings > System > Clipboard shows 'Sync across devices' as greyed out, disabled, or managed by organization.
Win + V window fails to load completely, displays 'Can't show history', or crashes upon pressing shortcut.
Clipboard sync works temporarily after reboot, but stops syncing after system sleeps or network switches.

What is the account status and service state on the devices where cross-device sync is failing?

Both devices use identical Microsoft Accounts, but Connected Devices Platform Service (CDPSvc) is stopped or failing authentication.
Accounts match and services run, but cloud sync payload fails due to item size limits or encrypted payload validation drops.
One device uses a Azure AD / Microsoft Entra ID corporate account while the other uses a Personal MSA.

Resetting Connected Devices Platform Service (CDPSvc) and OAuth Tokens

Solution:

Root Cause: Connected Devices Platform Service (CDPSvc) Token Desynchronization

Cross-device clipboard synchronization relies on the Microsoft Connected Devices Platform Service (CDPSvc) and its user-level instance (CDPUserSvc). These services negotiate TLS sockets with the Azure Cloud Relay using an OAuth 2.0 refresh token tied to your Microsoft Account (MSA). If the local token cache stored under C:\Users\[Username]\AppData\Local\ConnectedDevicesPlatform becomes desynchronized or corrupted during network transitions, CDPSvc fails silent authentication checks and drops outgoing clipboard payloads.

# Diagnostic Verification:

Open PowerShell as Administrator and run:

powershell
  Get-Service -Name CDPSvc, CDPUserSvc*

Confirm whether Status is Running.

Check Event Viewer under Applications and Services Logs > Microsoft > Windows > ConnectedDevicesPlatform > Operational for Event ID 102 or 109 indicating authentication token rejection.

# Step-by-Step Fix:

1. Stop Connected Devices Services:

Open Admin PowerShell and execute:

powershell
     Stop-Service -Name CDPSvc -Force
     Get-Service -Name CDPUserSvc* | Stop-Service -Force

2. Purge Local Connected Devices Cache Directory:

Navigate to the local CDP storage folder:

powershell
     Remove-Item -Path "$env:LOCALAPPDATA\ConnectedDevicesPlatform\*" -Recurse -Force -ErrorAction SilentlyContinue

3. Verify Account Identity Sign-in State:

Open Settings > Accounts > Your info.

If you see Verify under your account email, click it and follow the prompts to complete multi-factor authentication.

4. Re-enable Service Auto-Start and Restart:

Run the following in PowerShell:

powershell
     Set-Service -Name CDPSvc -StartupType Automatic
     Start-Service -Name CDPSvc

5. Toggle Cloud Clipboard Setting:

Go to Settings > System > Clipboard.

Toggle Clipboard history to Off and then back to On.

Ensure Sync across your devices is set to Automatically sync text that I copy.

# Prevention & Long-Term Monitoring:

Ensure corporate firewalls or third-party security software do not block outbound HTTPS traffic on port 443 to *.activity.windows.com and *.cdp.microsoft.com.

Configuring Large Payload Handling and Encrypted Bi-Directional Cloud Relay

Solution:

Root Cause: Clipboard Data Buffer Overflow and Transport Layer Cryptographic Rejection

Windows Cloud Clipboard imposes a hard size limit of 4MB per individual item (text or image) for cloud replication. When a user copies rich text, binary structures, or large images exceeding 4MB, the local Clipboard User Service (cbdhsvc) attempts to compute an SHA-256 hash for cloud staging. If the payload exceeds memory thresholds or contains unencapsulated OLE formats, the transmission buffer stalls and blocks subsequent clipboard items in the queue.

# Diagnostic Verification:

Inspect local clipboard data structures via PowerShell:

powershell
  Get-Clipboard -Format Text | Measure-Object -Character

Review Event Viewer logs under Applications and Services Logs > Microsoft > Windows > Clipboard-User-Service > Operational for error codes 0x80070057 (Invalid Parameter) or 0x8007000E (Out of Memory).

# Step-by-Step Fix:

1. Clear Local and Cloud Staged Clipboard Buffers:

Open Settings > System > Clipboard.

Scroll down to Clear clipboard data and click Clear.

2. Force Restart Clipboard User Service (cbdhsvc):

Open Admin PowerShell to restart the per-user service instance:

powershell
     $service = Get-Service -Name "cbdhsvc*"
     Stop-Service -Name $service.Name -Force
     Start-Service -Name$service.Name

3. Re-initialize Local System Memory Allocation Limits:

Open regedit and navigate to:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Ensure PoolUsageMaximum is not configured with restrictive non-standard limits.

4. Test Plain Text Synchronization:

Copy a small plain-text string (e.g., "Test Sync") on Device A.

Press Win + V on Device B within 5 seconds to verify real-time propagation.

5. Consult official configuration prerequisites in the Microsoft Official Support Guide for Windows Clipboard.

# Prevention & Long-Term Monitoring:

Avoid copying raw high-resolution image files directly to the clipboard; save images to disk or cloud drives when transferring between cross-platform machines.

Resolving Cross-Tenant Authentication Mismatches (MSA vs. Microsoft Entra ID)

Solution:

Root Cause: Identity Provider Realm Mismatch

Windows Cloud Clipboard history requires both endpoint devices to operate within the identical Identity Provider (IdP) boundary. Cloud clipboard items cannot bridge across a personal Microsoft Account (MSA) and a corporate Microsoft Entra ID (formerly Azure AD) tenant due to cryptographic isolation rules enforced by Azure Key Vault and Tenant Data Boundary compliance standards.

# Diagnostic Verification:

Check the logged-in user account types on both machines in Command Prompt:

cmd
  dsregcmd /status

Review the output under User State: If Device A shows AzureAdUser : YES and Device B shows AzureAdUser : NO, identity domain desynchronization is present.

# Step-by-Step Fix:

1. Align Primary Sign-in Identities:

Determine which primary identity (Personal MSA or Work/School Entra ID) will serve as the cloud relay anchor.

2. Add Secondary Work/School Account to Personal Device (if bridging work environments):

Open Settings > Accounts > Access work or school.

Click Connect and enter your organizational credentials.

3. Configure Cloud Clipboard Policy for Enterprise Tenants:

If using Entra ID, ensure the tenant admin has enabled AllowCrossDeviceClipboard in Microsoft Intune.

4. Verify Shared Identity State:

Navigate to Settings > System > Clipboard on both devices and verify that the listed user identity strings match identically.

# Prevention & Long-Term Monitoring:

Avoid combining personal laptops and enterprise-managed endpoints on separate tenant boundaries if cross-device cloud sync features are required.

Which administrative management scope is disabling or locking the Cloud Clipboard setting?

System shows 'Some of these settings are hidden or managed by your organization' in local Settings app.
Machine is enrolled in Microsoft Intune MDM or bound to an Active Directory Group Policy Object (GPO).

Clearing Local Registry Policy Overrides for Cloud Clipboard

Solution:

Root Cause: Local Group Policy or Registry Key Enforcement

Windows update cycles or third-party OS customization tools frequently apply security hardening templates that disable remote data telemetry. If AllowCrossDeviceClipboard or AllowClipboardHistory values are set to 0 under HKLM\SOFTWARE\Policies\Microsoft\Windows\System, Windows disables the cloud sync toggle completely.

# Diagnostic Verification:

Query local registry policy settings via PowerShell:

powershell
  Get-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\System" -Name "AllowCrossDeviceClipboard", "AllowClipboardHistory" -ErrorAction SilentlyContinue

If any returned value is 0, policy restriction is actively enforced.

# Step-by-Step Fix:

1. Open Local Group Policy Editor (gpedit.msc):

Press Win + R, type gpedit.msc, and press Enter.

Navigate to: Computer Configuration > Administrative Templates > System > OS Policies.

2. Re-enable Clipboard Policies:

Double-click Allow Clipboard History and set it to Enabled (or Not Configured).

Double-click Allow Clipboard synchronization across devices and set it to Enabled.

3. Remove Registry Override Keys via Admin PowerShell:

Execute the following commands:

powershell
     Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\System" -Name "AllowCrossDeviceClipboard" -ErrorAction SilentlyContinue
     Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\System" -Name "AllowClipboardHistory" -ErrorAction SilentlyContinue
     Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Clipboard" -Name "EnableClipboardHistory" -Value 1 -Type DWord

4. Force Policy Update and Restart Explorer:

Open Command Prompt (Admin) and run:

cmd
     gpupdate /force
     taskkill /f /im explorer.exe & start explorer.exe

# Prevention & Long-Term Monitoring:

Audit system tweaking utilities before execution to prevent unintended registry hardening of Windows OS Policy keys.

Updating Intune Configuration Profiles and Enterprise System Policies

Solution:

Root Cause: Intune MDM CSP Policy Lockdown (`System/AllowCrossDeviceClipboard`)

Enterprise security baselines push Configuration Service Provider (CSP) policies to protect corporate endpoints against data exfiltration. The System/AllowCrossDeviceClipboard policy restricts cloud-based clipboard synchronization to prevent sensitive data from leaking onto unmanaged personal devices.

# Diagnostic Verification:

Export active MDM diagnostic log in Command Prompt:

cmd
  mdmdiagnosticstool.exe -area "DeviceLock;System" -zip "C:\Users\Public\MDMReport.zip"

Inspect the generated MDMReport.html for AllowCrossDeviceClipboard setting blocked by administrator policy.

# Step-by-Step Fix:

1. Adjust Intune Endpoint Configuration Policy (For Administrators):

Log into the Microsoft Intune Admin Center.

Navigate to Devices > Configuration profiles.

Locate the baseline security profile assigned to the target device group.

Under Settings catalog > Administrative Templates > System > OS Policies, set Allow Clipboard synchronization across devices to Enabled.

2. Force Sync on the Local Client:

Open Settings > Accounts > Access work or school.

Select the corporate account, click Info, and click Sync.

3. Verify Client Registry Application:

Run PowerShell to confirm updated CSP registry keys:

powershell
     Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\System" -Name "AllowCrossDeviceClipboard"

Value must equal 1.

# Prevention & Long-Term Monitoring:

Create dedicated Intune device groups for users requiring cross-device continuity while maintaining strict conditional access policies on unmanaged endpoints.

What error or UI state occurs when pressing the Win + V shortcut?

Win + V window appears briefly and crashes, or displays 'Can't show history'.
Pressing Win + V produces no response on screen whatsoever.

Repairing Corrupted Local Clipboard SQLite Storage Database

Solution:

Root Cause: SQLite Database Corruption in Local AppData Staging Store

Windows stores local clipboard snippets and preview metadata in an internal SQLite database located inside C:\Users\[Username]\AppData\Local\Microsoft\Windows\Clipboard. Sudden system shutdowns, kernel panics, or write contention can corrupt the database file structure. When explorer.exe attempts to render the Win + V flyout interface, reading from corrupted database blocks triggers instant UI thread crashes.

# Diagnostic Verification:

Inspect Event Viewer under Windows Logs > Application for Event ID 1000 (Application Error) naming ShellAppRuntime.dll or Windows.UI.Clipboard.dll.

# Step-by-Step Fix:

1. Terminate Clipboard and Explorer Shell Processes:

Open PowerShell as Administrator and execute:

powershell
     Stop-Process -Name "explorer" -Force
     Get-Process | Where-Object {$_.Name -match "cbdh|clipboard"} | Stop-Process -Force

2. Clear Corrupted Clipboard Storage Directory:

Delete the contents of the local storage folder:

powershell
     $ClipPath = "$env:LOCALAPPDATA\Microsoft\Windows\Clipboard"
     Remove-Item -Path "$ClipPath\*" -Recurse -Force -ErrorAction SilentlyContinue

3. Re-register Windows Shell App Components:

Execute in PowerShell to re-register the clipboard flyout UI:

powershell
     Get-AppxPackage -AllUsers Microsoft.Windows.ShellExperienceHost | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

4. Restart Windows Shell:

Run start explorer.exe in PowerShell.

5. Press Win + V and click Turn on to re-initialize clean database tables.

# Prevention & Long-Term Monitoring:

Ensure systems are gracefully shut down and run regular disk integrity checks (chkdsk) to prevent database storage corruption.

Re-enabling System Clipboard Service and Win + V Hotkey Handler

Solution:

Root Cause: Clipboard User Service (`cbdhsvc`) Startup Disablement

The Windows keyboard shortcut handler (Win + V) relies on the per-user service cbdhsvc_[randomstring]. If the service startup type is set to Disabled, or if global hotkey hooks are intercepted by third-party desktop utilities (such as AutoHotkey or custom GPU overlay software), Windows drops the Win + V input signal.

# Diagnostic Verification:

Run PowerShell to check the service startup configuration:

powershell
  Get-Service -Name "cbdhsvc*" | Select-Object Name, Status, StartType

If StartType is Disabled, the hotkey interface cannot initialize.

# Step-by-Step Fix:

1. Re-enable Clipboard Service via Registry:

Because per-user services cannot always be modified directly in services.msc, edit the service template in the registry.

Open Admin PowerShell and run:

powershell
     Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\cbdhsvc" -Name "Start" -Value 2 -Type DWord

*(Value 2 sets startup to Automatic).*
2. Verify Windows Hotkey Registry Binding:

Check if Win + hotkeys are disabled globally:

powershell
     Remove-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer" -Name "NoWinKeys" -ErrorAction SilentlyContinue

3. Restart Computer to Apply Service State Changes.
4. Test Keyboard Input Hook:

Press Win + V to verify popup UI activation.

# Prevention & Long-Term Monitoring:

Avoid setting system per-user template services (cbdhsvc, CDPUserSvc) to Disabled when attempting to optimize system memory usage.

What is the primary trigger that causes cross-device clipboard sync to stop working?

Sync fails immediately after waking from Modern Standby (Sleep) or resuming from Hibernation.
Sync breaks when switching network adapters (e.g., disconnecting Ethernet and joining Wi-Fi/VPN).

Configuring Network Adapter Power Management for Modern Standby Resume

Solution:

Root Cause: Network Interface Card (NIC) Power State Stalls During Resume

When a system resumes from Modern Standby (S0 Low Power Idle) or Hibernation, the Network Interface Card (NIC) re-establishes physical links. If the network adapter enters D3 low-power states without properly restoring push-notification WebSockets, CDPSvc maintains a stale socket connection to the Azure Relay Server without sending real-time keepalive packets.

# Diagnostic Verification:

Check network adapter power drop events in Event Viewer under System logs from source NDIS or vendor network driver.

# Step-by-Step Fix:

1. Disable Energy-Efficient Ethernet Power Savings:

Open devmgmt.msc, expand Network adapters, right-click your active Wi-Fi/Ethernet adapter, and choose Properties.

Under the Power Management tab, uncheck Allow the computer to turn off this device to save power.

Under the Advanced tab, set Energy-Efficient Ethernet and Green Ethernet to Disabled.

2. Re-initialize Push Notification Services (WPNUserService):

Open Admin PowerShell and restart the Windows Push Notification user service:

powershell
     $WpnService = Get-Service -Name "WpnUserService*"
     Stop-Service -Name $WpnService.Name -Force
     Start-Service -Name$WpnService.Name

3. Configure Automatic Network Reconnect via Group Policy:

Open gpedit.msc and navigate to: Computer Configuration > Administrative Templates > Network > Windows Connect Now.

Enable settings that maintain active network polling during system state transitions.

# Prevention & Long-Term Monitoring:

Keep network adapter Wi-Fi and LAN drivers updated to the latest manufacturer versions to prevent TCP socket lockups across power states.

Adjusting VPN Split Tunneling and Firewall Network Location Rules

Solution:

Root Cause: VPN Tunneling Packet Dropping and Firewall Network Profile Blocks

Connecting to a Virtual Private Network (VPN) often redirects all system traffic through a remote security gateway. If the VPN vendor enforces strict split-tunneling policies or if Windows Firewall classifies the network profile as Public, outbound WebSocket packets sent to Microsoft CDP servers (*.cdp.microsoft.com) are dropped by local packet filtering rules.

# Diagnostic Verification:

Open PowerShell and test TCP socket connectivity to the cloud clipboard endpoint:

powershell
  Test-NetConnection -ComputerName "activity.windows.com" -Port 443

If TcpTestSucceeded returns False while connected to your VPN, packet routing is blocked.

# Step-by-Step Fix:

1. Configure Windows Defender Firewall Profile Rules:

Open Admin PowerShell and run:

powershell
     Set-NetFirewallRule -DisplayGroup "Connected Devices Platform" -Enabled True -Profile Any

2. Configure VPN Split Tunneling (For VPN Administrators):

Add Microsoft Cloud Clipboard service domain endpoints to your VPN split-tunneling bypass list:

*.activity.windows.com

*.cdp.microsoft.com

*.cloudapp.net

3. Switch Local Network Profile from Public to Private:

Open Settings > Network & internet.

Select your active network connection and change Network profile type to Private network.

4. Restart CDPSvc and test clipboard sync while connected to VPN.

# Prevention & Long-Term Monitoring:

Work with network security administrators to ensure real-time notification endpoints are excluded from aggressive SSL inspection and packet drops.

Related Diagnostic Guides

Windows 11 24H2 KB504 Failed to Install: Cleanup & Fix

User Profile Service Failed Logon: Create New Profile Without Losing Data

Windows Hello Fingerprint Not Available After Update: Diagnostic & Repair Guide

Embed Guide on Your Website