sodcalculator

10 Tech How-To

High CPU on Windows Cross Device Service: Fix It

Guide 10-21318 · Updated · Step by step

If you’ve noticed your Windows PC’s fan spinning up or the system feeling sluggish, the Cross Device Service (also known as cdpsvc) might be the culprit. This service powers features like Phone Link, Nearby Sharing, and cross-device clipboard syncing. When it misbehaves, it can consume a large chunk of your CPU. This guide walks you through practical steps to reduce its CPU usage, from quick restarts to more permanent fixes.

What You’ll Need

  • Administrator access to your Windows PC (to run commands and change services).
  • Approximately 10–15 minutes of your time.
  • Optional: a second device (phone or PC) if you want to test syncing after the fix.

Step-by-Step

  1. Confirm it’s actually the Cross Device Service. Press Ctrl+Shift+Esc to open Task Manager. Go to the Processes tab and look for Cross Device Service (or Phone Link). Click the CPU column header to sort by usage. If it’s consistently above 10–20% with no active transfers, proceed.
  2. Restart the service. Press Win+R, type services.msc, and hit Enter. Scroll to Cross Device Service. Right-click it and select Restart. This often clears temporary glitches. Check Task Manager again—if CPU drops, you’re done.
  3. Check for pending updates. Go to Settings > Windows Update and click Check for updates. Install any available updates, especially for the Cross Device Service or Phone Link. Reboot if prompted.
  4. Repair the Phone Link app. Open Settings > Apps > Installed apps. Search for Phone Link (and Cross Device Experience Host if present). Click the three-dot menu and choose Advanced options. Scroll down and click Repair. If that doesn’t help, click Reset (this will unpair your phone, so you’ll need to set it up again).
  5. Adjust the service’s startup type. If the service is set to Automatic, it starts at boot and runs constantly. Open services.msc again, right-click Cross Device Service, select Properties. In the Startup type dropdown, choose Manual (not Disabled). Click Stop if it’s running, then Apply. This way, it only runs when a feature actually needs it.
  6. Disable unnecessary cross-device features. Open Settings > Bluetooth & devices > Phone Link. Turn off features you don’t use, like Clipboard history sync or Instant hotspot. Each disabled feature reduces background activity.
  7. Run a clean boot to isolate conflicts. Press Win+R, type msconfig, and Enter. Under the Services tab, check Hide all Microsoft services, then click Disable all. Under Startup, click Open Task Manager and disable all startup items. Restart. If the CPU is normal, re-enable services one by one to find the culprit (likely a third-party app conflicting with the service).
  8. As a last resort, disable the service entirely. If you don’t use Phone Link or Nearby Sharing, you can disable it. In services.msc, set Cross Device Service to Disabled. This will break those features, so only do this if you’re okay losing them.

Common Mistakes

  • Disabling the service instead of setting to Manual. Disabling breaks Phone Link and Nearby Sharing completely, and some Windows updates may re-enable it anyway.
  • Skipping the repair step. A corrupted app install is a frequent cause; repairing is quick and often fixes the issue without losing data.
  • Not checking for updates first. Microsoft regularly patches known CPU leaks; missing updates means you’re troubleshooting an old bug.
  • Assuming it’s malware. High CPU from this service is a known issue, not a virus. Don’t waste time with third-party scanners.

Tips

  • After any change, wait a few minutes and then check Task Manager again. The service may spike briefly when syncing, which is normal.
  • If you use Phone Link, keep your phone’s companion app updated too—outdated phone apps can cause constant reconnection attempts.
  • Use the Power & battery settings to see if the service is draining battery as well; that’s another sign it’s misbehaving.

Troubleshooting

If the steps above don’t reduce CPU usage:

  • Check event logs. Open Event Viewer (search for it in Start). Navigate to Windows Logs > System and filter for errors related to cdpsvc or CrossDeviceService. The error details can point to a specific cause.
  • Try a different user account. Create a temporary local admin account and see if the issue persists. If it doesn’t, a corrupted user profile is likely.
  • Run the Windows built-in troubleshooters. Go to Settings > System > Troubleshoot > Other troubleshooters and run Windows Update and Bluetooth troubleshooters.
  • If nothing works, consider a system restore. Use a restore point from before the issue started (search for “Create a restore point” in Start).

Frequently Asked Questions

Is the Cross Device Service safe to disable?

Yes, it’s a legitimate Microsoft service. Disabling it only affects cross-device features like Phone Link and Nearby Sharing; it won’t harm your system.

Why does it use high CPU even when I’m not using any cross-device features?

The service runs in the background to keep connections ready. A bug or a stuck sync loop can cause it to spin without user action.

Will setting it to Manual break anything?

No. The service will start automatically when you use a feature that needs it (like opening Phone Link). It just won’t run at boot, which reduces background CPU.

How do I know if it’s a CPU spike or a constant high usage?

Watch Task Manager for a few minutes. A spike that drops back down is normal; constant usage above 20% is not.

Can a third-party antivirus cause this?

Yes, some security suites can interfere with Windows services. Try temporarily disabling your antivirus (if it’s not Windows Defender) to test, but re-enable it immediately after.

Will resetting the Phone Link app delete my data?

It will unpair your phone and clear app settings, but it won’t delete files on your PC or phone. You’ll need to re-link your phone.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →