Interactive Troubleshooter

Published: Oct 28, 2026

Clipboard History Not Working Windows 11: Sync Service Tree

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

An exhaustive troubleshooting tree designed to resolve Windows 11 clipboard history and cloud sync failures by diagnosing clipSvc states, Group Policy blocks, corrupt Registry hives, and account permission mismatches.

Full Diagnostic Tree & Step-by-Step Overview

What is the primary symptom of your Windows 11 clipboard history failure?

Win+V opens, but is completely empty or displays 'Can't show history'
Win+V shortcut does not open the clipboard interface at all
Clipboard items fail to sync across other Windows devices
Clipboard history works temporarily, but resets or clears after reboot

Select the specific condition related to your empty clipboard history panel:

Clipboard service (clipSvc) is stopped or disabled in Windows Services
Group Policy or Intune MDM policy has explicitly disabled clipboard history
Corrupted User Registry hive keys controlling window telemetry and history
Third-party security software or aggressive clipboard manager interfering

Select the specific condition related to the non-responsive Win+V shortcut:

Explorer.shell process failure or shell window hook obstruction
Keyboard shortcut mapping conflict with third-party macro or gaming software
Corrupted Windows ShellExperienceHost or SystemApp packages
Keyboard hardware filter keys or gaming mode locking Windows key combinations

Select the specific condition affecting your cross-device clipboard cloud synchronization:

Microsoft Account authentication token corruption or sync consent revocation
'Sync across devices' setting disabled in Windows System Settings
Connected User Experiences and Telemetry service (DiagTrack) disabled
Enterprise firewall or DNS sinkhole blocking Microsoft sync endpoints

Select the specific condition causing your clipboard history to wipe upon reboot:

Storage Sense or automated disk cleaner aggressively purging local user temp caches
Corrupted Access Control Lists (ACLs) on the LocalAppData Packages folder
Third-party registry cleaner or registry tweak utility deleting cache pointers
Active user profile corruption or temporary profile login state

Restart and Reconfigure the Clipboard User Service (clipSvc)

Solution:

Root Cause: Clipboard User Service (clipSvc) Malfunction

The Windows Clipboard User Service (clipSvc) manages clipboard history caching and synchronization. When this service fails to initialize automatically, crashes due to unhandled pointer exceptions, or has its startup type changed to manual/disabled by optimization scripts, the Win+V interface cannot fetch cached clipboard payloads from user space memory.

Diagnostic Verification:

Open PowerShell as Administrator and run: Get-Service -Name clipSvc

Verify if the Status is 'Running' and StartType is 'Automatic'.

Check Windows Event Viewer under Applications and Services Logs > Microsoft > Windows > Clipboard for Event ID errors indicating service initialization failures.

Step-by-Step Fix:

1Open PowerShell with administrative privileges and execute the following command to reset the service startup type:

Set-Service -Name clipSvc -StartupType Automatic

2Start the service immediately by running:

Start-Service -Name clipSvc

3Verify service operation status by checking active processes bound to the service instance.

4Press Windows Key + V to confirm the clipboard history interface now renders correctly.

Prevention & Long-Term Monitoring:

Avoid utilizing aggressive Windows debloater or registry optimization scripts that alter core Windows background service startup dependencies.

Enable Clipboard History via Group Policy / Registry

Solution:

Root Cause: Group Policy or Registry Restriction

Enterprise Group Policy Objects (GPO) or local registry keys can explicitly disable clipboard history collection to prevent data leakage in secure environments. If a corporate policy was applied or left over from a domain join, the clipboard history feature remains administratively blocked.

Diagnostic Verification:

Open Registry Editor (regedit) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System.

Inspect the DWORD value for AllowClipboardHistory. If set to 0, the feature is disabled by policy.

Step-by-Step Fix:

1Open PowerShell as Administrator and run the following command to enable clipboard history at the system level:

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\System" -Name "AllowClipboardHistory" -Value 1

2Configure the user-level setting by executing:

Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer" -Name "ClipboardHistory" -Value 1

3Restart the Windows Explorer shell to apply changes immediately:

Stop-Process -Name explorer -Force

4Verify functionality by pressing Windows Key + V and clicking 'Turn on'.

Prevention & Long-Term Monitoring:

Document local group policy changes and review domain-level GPO configurations if your machine connects to an organizational network.

Repair Corrupted User Registry Keys for Clipboard History

Solution:

Root Cause: Corrupted User Registry Hive Caches

User registry hive keys governing explorer extension states can experience corruption, preventing Windows from writing or reading string elements to the clipboard database stored in user profiles.

Diagnostic Verification:

Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\Cache\DefaultAccount\ in Registry Editor.

Check for missing or malformed subkeys corresponding to clipboard data stores.

Step-by-Step Fix:

1Open PowerShell as Administrator and clear corrupted clipboard cache registry entries using clean commands:

Stop-Process -Name explorer -Force

2Reset the Clipboard configuration flags by running:

Set-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer" -Name "EnableClipboardHistory" -Value 1

3Restart your computer to force Windows to rebuild user hive cache pointers.

4Open any text editor, copy multiple snippets, and test the Win+V interface.

Prevention & Long-Term Monitoring:

Regularly maintain system stability and prevent forced power interruptions during active user hive write cycles.

Resolve Third-Party Software and Security Hook Conflicts

Solution:

Root Cause: Third-Party Clipboard Manager Interference

Third-party clipboard extension tools (such as Ditto, ClipboardFusion, or custom macro utilities) hook into Windows message loops and global keyboard hooks, sometimes intercepting or blocking native Windows 11 Win+V API calls.

Diagnostic Verification:

Boot your system into Safe Mode or check Task Manager startup apps for competing clipboard utilities.

Review Event Viewer application logs for unhandled exception faults originating from third-party binary hooks.

Step-by-Step Fix:

1Open Task Manager (Ctrl + Shift + Esc) and navigate to the Startup tab.

2Temporarily disable any third-party clipboard management utilities or macro software.

3Open PowerShell as Administrator and re-register Windows application packages:

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

4Reboot your system and test native Windows clipboard history functionality.

Prevention & Long-Term Monitoring:

Ensure third-party productivity software is updated to versions fully compatible with Windows 11 API standards.

Restart Windows Explorer Shell and Process Hooks

Solution:

Root Cause: Explorer Shell Keyboard Hook Lockup

The Windows Explorer process (explorer.exe) manages desktop window hooks, taskbar notifications, and global keyboard shortcuts including Win+V. When the shell hangs or loses hook registration, shortcut triggers fail silently.

Diagnostic Verification:

Press Ctrl + Shift + Esc to open Task Manager and check if Windows Explorer is responding or experiencing high CPU utilization.

Test whether other Windows key shortcuts (like Win+I or Win+X) function normally while Win+V fails.

Step-by-Step Fix:

1Open PowerShell as Administrator and restart the shell process cleanly:

Stop-Process -Name explorer -Force

2If explorer does not restart automatically, initiate a new instance via terminal:

Start-Process explorer.exe

3Clear the active clipboard cache buffer via command line:

echo off | clip

4Test the shortcut by pressing Windows Key + V.

Prevention & Long-Term Monitoring:

Keep graphics and display drivers updated to prevent shell rendering lockups.

Resolve Keyboard Shortcut and Gaming Software Mapping Conflicts

Solution:

Root Cause: Gaming Mode and Macro Software Key Interception

Gaming keyboards, companion peripherals software (such as Razer Synapse, Logitech G HUB, or Corsair iCUE), and Windows Game Mode often intercept the Windows Key or disable specific key combinations to prevent accidental interruptions during gameplay.

Diagnostic Verification:

Check physical keyboard hardware switch indicators (e.g., Win-Lock LED light active).

Open peripheral configuration software and inspect custom key bindings assigned to the Windows Key or 'V' key.

Step-by-Step Fix:

1Open your peripheral configuration software (e.g., Razer Synapse or Logitech G HUB).

2Disable any active 'Game Mode' profiles or custom macro assignments targeting the Windows key.

3Unplug and reconnect your keyboard to reset hardware microcontroller state flags.

4Test Windows Key + V in a standard application like Notepad.

Prevention & Long-Term Monitoring:

Configure software profiles to automatically disable gaming macros when launching productivity applications.

Re-register Windows Shell Experience Packages

Solution:

Root Cause: Corrupted ShellExperienceHost Package

Windows 11 UI flyouts, including clipboard history and emoji panels, are rendered by modern Universal Windows Platform (UWP) shell packages. Corruption within these packages prevents UI dialog initialization.

Diagnostic Verification:

Open PowerShell as Administrator and run system file checker to scan package integrity: sfc /scannow

Check Event Viewer for application crashes related to ShellExperienceHost.exe.

Step-by-Step Fix:

1Open PowerShell with administrative privileges and re-register core shell packages:

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

2Re-register Windows Start and System packages:

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

3Restart your PC to finalize package re-indexing.

Prevention & Long-Term Monitoring:

Run regular system maintenance scans using deployment image servicing and management tools (DISM).

Disable Keyboard Filter Keys and Accessibility Obstructions

Solution:

Root Cause: Sticky or Filter Keys Interference

Windows Accessibility features such as Filter Keys or Sticky Keys can alter key combination timing thresholds, causing simultaneous multi-key shortcuts like Win+V to register incorrectly.

Diagnostic Verification:

Check the system tray for the Filter Keys notification icon.

Open Windows Settings > Accessibility > Keyboard and verify if Filter Keys or Sticky Keys are toggled on.

Step-by-Step Fix:

1Open Windows Settings by pressing Windows Key + I.

2Navigate to Accessibility > Keyboard.

3Toggle both Filter Keys and Sticky Keys to the Off position.

4Press Windows Key + V to verify that the clipboard panel now opens without timing lag.

Prevention & Long-Term Monitoring:

Disable the shortcut that turns on Filter Keys (pressing the right Shift key for 8 seconds) in accessibility settings if triggered accidentally.

Re-authenticate Microsoft Account and Refresh Sync Tokens

Solution:

Root Cause: Expired or Corrupted Microsoft Account Auth Tokens

Cross-device clipboard synchronization relies on valid OAuth tokens tied to your Microsoft Account (MSA). When authentication tokens expire or become corrupted in the Credential Manager, cloud clipboard sync halts silently.

Diagnostic Verification:

Open Windows Settings > Accounts > Your info and look for any warning banners stating 'Sign in required to fix your account'.

Check Credential Manager for outdated generic credentials associated with MicrosoftAccount.

Step-by-Step Fix:

1Open Windows Settings (Windows Key + I).

2Go to Accounts > Your info and select Sign in with a Microsoft account instead (or re-verify your current credentials).

3Open PowerShell as Administrator and restart the Microsoft account sign-in assistant service:

Restart-Service -Name AmazSS, TokenBroker -Force

4Reboot your computer and confirm account sync status in system settings.

Prevention & Long-Term Monitoring:

Promptly address any security notification alerts regarding Microsoft account password changes across all linked Windows devices.

Enable Cross-Device Clipboard Sync in Windows Settings

Solution:

Root Cause: Disabled Cloud Sync Settings

Even when local clipboard history is enabled, the secondary setting permitting text and items to sync across devices via the cloud must be explicitly turned on in Windows system configurations.

Diagnostic Verification:

Open Windows Settings > System > Clipboard.

Inspect the Sync across your devices toggle status.

Step-by-Step Fix:

1Press Windows Key + I to open Settings.

2Navigate to System > Clipboard.

3Ensure Clipboard history is toggled On.

4Under Sync across your devices, select Automatically sync text that I copy.

5Verify account connection status beneath the sync options.

Prevention & Long-Term Monitoring:

Verify that identical Microsoft account credentials are active on all devices intended for clipboard sharing.

Enable Connected User Experiences and Telemetry Service (DiagTrack)

Solution:

Root Cause: Disabled DiagTrack Telemetry Service

Windows cloud sync features, including cloud clipboard and cross-device sharing, depend on the Connected User Experiences and Telemetry service (DiagTrack) to transmit encrypted sync payloads to Microsoft cloud infrastructure.

Diagnostic Verification:

Open PowerShell as Administrator and check service status: Get-Service -Name DiagTrack

Verify if the service startup type is set to Disabled.

Step-by-Step Fix:

1Open PowerShell with administrative privileges and set DiagTrack startup to Automatic:

Set-Service -Name DiagTrack -StartupType Automatic

2Start the telemetry service immediately:

Start-Service -Name DiagTrack

3Restart the clipboard user service to re-establish cloud binding:

Restart-Service -Name clipSvc -Force

4Test cross-device pasting after 2 minutes of synchronization time.

Prevention & Long-Term Monitoring:

Exercise caution when utilizing heavy telemetry blocking utilities that disable core cloud synchronization dependencies.

Check Firewall and Endpoint DNS Resolution for Microsoft Sync Endpoints

Solution:

Root Cause: Network Filtering Blocking Sync Endpoints

Corporate firewalls, aggressive Pi-hole DNS sinkholes, or third-party VPNs can block connection requests to Microsoft cloud sync endpoints (*.smartscreen.microsoft.com and Microsoft Graph APIs), preventing cloud clipboard propagation.

Diagnostic Verification:

Temporarily disconnect from corporate VPN or third-party firewall protection.

Test whether cloud clipboard sync resumes on an unrestricted standard network connection.

Step-by-Step Fix:

1Open PowerShell and flush local DNS resolver cache to clear corrupted records:

Clear-DnsClientCache

2Verify outbound connectivity to Microsoft sync servers by running:

Test-NetConnection -ComputerName login.live.com -Port 443

3Whitelist required Microsoft identity and sync URLs in your network security filter or VPN settings.

4Restart your network adapter via PowerShell:

Restart-NetAdapter -Name "*"

Prevention & Long-Term Monitoring:

Ensure network administrators authorize required Microsoft Graph and sync endpoints on enterprise network perimeters.

Configure Storage Sense and Temp Cache Retention Rules

Solution:

Root Cause: Aggressive Storage Sense Temp File Purging

Windows Storage Sense or automated disk cleanup utilities configured to purge temporary user files daily can accidentally wipe local cloud store and clipboard database caches stored within AppData directories.

Diagnostic Verification:

Open Windows Settings > System > Storage > Storage Sense.

Check whether automatic user content cleanup frequency is set to run daily or upon low disk space.

Step-by-Step Fix:

1Open Windows Settings (Windows Key + I).

2Navigate to System > Storage > Storage Sense.

3Adjust the Run Storage Sense frequency dropdown from daily to During low free disk space or Monthly.

4Ensure Keep Windows running smoothly by automatically cleaning up temporary system and app files allows app cache preservation.

5Restart your system to apply storage retention policies.

Prevention & Long-Term Monitoring:

Exclude critical user application directories from aggressive third-party disk cleaner deletion lists.

Repair File Permissions on LocalAppData Packages Folder

Solution:

Root Cause: Corrupted ACL Permissions on AppData Packages

When NTFS Access Control Lists (ACLs) on the AppData\Local\Packages directory become corrupted or lose write permissions for the current user security identifier (SID), Windows cannot persist clipboard history data across reboots.

Diagnostic Verification:

Open PowerShell and inspect folder ACL permissions:

Get-Acl "$env:LOCALAPPDATA\Packages"

Verify whether your user account maintains Full Control over the directory tree.

Step-by-Step Fix:

1Open PowerShell with administrative privileges and reset inheritance and permissions on the Packages folder:

icacls "$env:LOCALAPPDATA\Packages" /reset /t /c

2Grant explicit full control to the current user profile:

icacls "$env:LOCALAPPDATA\Packages" /grant "$($env:USERNAME):(OI)(CI)F" /t

3Restart your computer to initialize write access to the database store.

Prevention & Long-Term Monitoring:

Avoid executing unauthorized permission stripping scripts across system user profile folders.

Remove Registry Cleaner Deletion Rules Targeting Clipboard Keys

Solution:

Root Cause: Third-Party Registry Cleaner Deletion Rules

Overzealous third-party registry cleaner tools (such as CCleaner or similar utilities) often flag dynamic CloudStore cache keys as 'obsolete MRU lists' and delete them during system startup or maintenance scans, wiping clipboard history.

Diagnostic Verification:

Open your third-party registry cleaner quarantine or exclusion logs.

Search for deleted registry keys matching CloudStore\Store\Cache or ClipboardHistory.

Step-by-Step Fix:

1Open your registry optimization or cleaning software.

2Navigate to Settings > Exclusions / Ignore List.

3Add an exclusion rule for registry path: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore

4Re-enable clipboard history via Windows Settings > System > Clipboard.

5Reboot your system to verify settings persist across reboots.

Prevention & Long-Term Monitoring:

Disable automated registry cleaning tasks entirely on modern Windows 11 installations to protect volatile user hive data.

Repair Corrupted User Profile and Temporary Account States

Solution:

Root Cause: Temporary User Profile Login State

If Windows logs you into a temporary user profile upon boot due to a locked or corrupted user hive registry file, all clipboard history caches and user settings will fail to save permanently upon session termination.

Diagnostic Verification:

Open PowerShell and check your current profile path:

echo $env:USERPROFILE

If the path points to C:\Users\Temp or contains .000, your profile is loaded in a temporary state.

Step-by-Step Fix:

1Open Registry Editor (regedit) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.

2Identify subkeys ending in .bak and corresponding correct user SID keys.

3Rename the corrupted profile key and restore the original profile key suffix according to official Microsoft profile recovery procedures.

4Reboot your system and log into your fully restored permanent user account.

Prevention & Long-Term Monitoring:

Ensure proper system shutdowns to prevent user hive file locking and profile corruption.

Related Diagnostic Guides

Windows Update Error 0x80070002 Missing Files Diagnostic Guide

System Restore Failed 0x80070005 Antivirus Conflict Tree

Windows Photo Viewer Not Showing Thumbnails: Codec Diagnostic

Safe Mode Password Not Working With Microsoft Account Fix

Windows Shows Wrong Time After Reboot Despite Sync Enabled

Subscribe to StepDiag

Embed Guide on Your Website