How to Use Safe Mode and Clean Boot to Diagnose Clipboard Bugs

When the basic round-trip tests fail — text does not survive a Notepad copy-paste, Get-Clipboard returns stale or empty data, and restarting Explorer does not help — the next diagnostic step is to take Windows down to its smallest running configuration and see if the clipboard works there. If it does, the cause is a third-party driver, service, or startup program. If it does not, the cause is in Windows itself, and a reset becomes a serious option.

This guide covers Safe Mode, the clean boot procedure via msconfig, and the bisection process that narrows down the offending component. For context, see how to test whether the OS clipboard itself is healthy first; this article is the next step when those tests fail. For the broader nine-fix playbook, see Win+V not working on Windows 11: 9 fixes, and for the question of when a full Windows reset is justified, see when to reset Windows because paste is haunted.

Safe Mode vs a clean boot: what each isolates

The two are different tools, and conflating them is the most common mistake in this kind of troubleshooting.

The order matters. Safe Mode first. If Safe Mode passes, clean boot next, then bisect.

Step 1: boot into Safe Mode and re-run the round-trip tests

To enter Safe Mode from a running Windows 11 system:

1. Open Settings → System → Recovery.
2. Next to Advanced startup, click Restart now.
3. After the restart, choose Troubleshoot → Advanced options → Startup Settings → Restart.
4. Press 4 for Safe Mode, or 5 for Safe Mode with Networking.

When the desktop loads in Safe Mode, re-run the round-trip tests from how to test whether the OS clipboard itself is healthy:

1. Notepad text round-trip.
2. Snipping Tool → Paint image round-trip.
3. PowerShell Set-Clipboard / Get-Clipboard probe.

If all three pass in Safe Mode, the OS clipboard is healthy and the cause is a third-party driver, service, or startup program. Move on to the clean boot.

If any of the three fail in Safe Mode, the OS clipboard itself is damaged. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated command prompt. Re-run the tests. If they still fail, the system image may be corrupted and a Windows reset or in-place upgrade becomes the next conversation — see when to reset Windows because paste is haunted.

Step 2: prepare for a clean boot

A clean boot starts Windows with only Microsoft services and no third-party startup items. The tool is msconfig (System Configuration), which ships with Windows.

Before starting, gather information:

1. List the third-party services currently running. Open services.msc and note any non-Microsoft services (the Manufacturer column is helpful).
2. List the startup items. Open Task Manager → Startup apps tab. Note every item.
3. Create a system restore point. Settings → System → About → Advanced system settings → System Protection → Create.

The restore point is the safety net. If a clean boot reveals that a specific service is the cause and you want to remove that service, having a restore point lets you roll back.

Step 3: disable third-party services in msconfig

1. Press Win+R, type msconfig, press Enter.
2. Go to the Services tab.
3. Check Hide all Microsoft services at the bottom. This is essential — disabling Microsoft services can break Windows.
4. Click Disable all. This disables every remaining (third-party) service.
5. Click Apply, then OK.
6. Do not restart yet.

Step 4: disable startup items

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Go to the Startup apps tab.
3. Right-click each item → Disable.

In current Windows 11 builds, msconfig's Startup tab redirects to Task Manager, which is why this step lives in Task Manager.

Step 5: restart and re-test

1. Restart the PC.
2. After restart, re-run the Notepad round-trip and the PowerShell probe.

If the tests now pass, the cause is one of the third-party services or startup items that were disabled. Move to bisection.

If the tests still fail, the cause is not a third-party user-mode service. Possible causes include:

• A kernel driver that loads regardless of msconfig settings (antivirus filter drivers, virtualisation drivers, graphics drivers).
• A Windows component that has been corrupted.
• A group policy or MDM policy that restricts clipboard access (see clipboard history grayed out by organization).

For kernel-driver issues, the next step is sigverif (File Signature Verification Tool) and reviewing recently installed drivers with pnputil /enum-drivers from an elevated command prompt.

Step 6: bisect by re-enabling services in halves

Bisection is the fastest way to find the offending service among many. The procedure:

1. Open msconfig → Services, hide Microsoft services.
2. Re-enable the first half of the third-party services.
3. Restart, re-test.
4. If the test passes, the culprit is in the second (still-disabled) half. If the test fails, the culprit is in the first (re-enabled) half.
5. Repeat: split the suspect half into halves, re-enable one half, restart, re-test.
6. Continue until one service remains.

For a starting list of 20 third-party services, this takes roughly 5 restarts. For a list of 100, it takes 7 restarts. The math is log2(N).

Common culprits in clipboard clean boots

When bisection lands on a single service, it is most often one of these:

• Antivirus or EDR agents — filter drivers that intercept clipboard writes. See third-party antivirus blocking clipboard access.
• Endpoint DLP (Data Loss Prevention) — enterprise agents that block clipboard copy of "sensitive" content. Often silent in the UI.
• Virtualisation hosts — VMware Tools, VirtualBox Guest Additions, Hyper-V Enhanced Session Mode all touch the clipboard. See VM guest clipboard integration broken.
• Remote desktop hooks — Citrix Workspace, VMware Horizon, AWS WorkSpaces client. See Citrix and VDI clipboard redirection.
• Graphics driver overlays — NVIDIA GeForce Experience, AMD Adrenalin overlay. Rarely the cause but not impossible.
• Input enhancers — Wacom, Logitech Options, Razer Synapse. These can register global hotkeys.
• Two clipboard managers — Ditto and Win+V together, or CopyQ and a shelf together. See two clipboard managers fighting each other.

The bisection will identify which one; the linked article for that category covers the specific fix.

Step 7: re-enable everything and apply the fix

Once the culprit is identified, the fix is one of:

• Uninstall the offending software.
• Update it to a version that does not break the clipboard.
• Change its settings to release the clipboard (most antivirus products expose a clipboard-scanning toggle).
• Keep it disabled at startup if it is not needed.

After applying the fix, re-enable all remaining third-party services in msconfig → Services (or simply undo "Disable all"), re-enable startup items in Task Manager, and restart. Re-run the round-trip tests one final time. If they pass, the troubleshooting is complete.

When to stop and consider a reset

A clean boot is the last serious diagnostic step before a Windows reset. If the round-trip tests fail in Safe Mode even after sfc and DISM repairs, the system image is damaged and the question becomes whether to reset. That decision is covered in when to reset Windows because paste is haunted and is almost never warranted for a clipboard problem alone — but it is the next conversation.

For most clipboard issues, the clean boot will identify a third-party service, and the rest of the C12 cluster will have a specific fix for that service. The discipline is to bisect rather than guess, and to keep a restore point so that any cleanup can be rolled back.

Related reading

• When to Reset Windows Because Paste Is Haunted
• Win+V Not Working on Windows 11: 9 Fixes
• Best Free Clipboard Manager for Windows
• How to Enable Clipboard History in Windows 11

Sources

• Microsoft Support — Using the clipboard on Windows — official statement of the 25-item / 4 MB / text-HTML-bitmap limits and the Win+V history toggle, used to define what "healthy" looks like in the round-trip tests
• Microsoft Learn — System File Checker (sfc) — official documentation for sfc /scannow, used to repair system files when round-trip tests fail in Safe Mode
• Microsoft Learn — DISM command-line options — official documentation for DISM /Online /Cleanup-Image /RestoreHealth, used to repair the component store
• Microsoft Learn — Win32 clipboard reference — official reference for the clipboard APIs that the PowerShell Get-Clipboard and Set-Clipboard cmdlets call
• Microsoft Learn — MDM clipboard policy — official MDM policy documentation for the clipboard sync setting, relevant when group policy or MDM restrictions are suspected

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