CrossDeviceResume.exe is a Windows 11 component for Resume, the feature that offers to continue supported Android phone activities on your PC. It can appear as Resume in Task Manager. If Windows works normally, seeing it run is not by itself a reason to repair the PC or remove malware. To stop using the feature, go to Settings > Apps > Resume. An error at sign-in needs a different check: record its exact wording and whether Start, Settings, or other apps also fail. Do not delete the executable to silence it.
Which CrossDeviceResume.exe problem do you have?
- The process runs, but Windows works normally. Check its location and Microsoft signature. Its presence alone does not require repair or malware removal.
- You do not use phone-to-PC Resume. Turn off Resume in Settings. This changes the feature preference; it does not uninstall a Windows component.
- An error appears at sign-in, but other apps work. Record the full message, named DLL or package, and Windows build. Update and restart, then test whether the error returns.
- Start, the taskbar, or Settings also fails. Use Task Manager to reach diagnostic tools. A Resume toggle is unlikely to explain or repair the whole symptom.
- Several packaged apps report the same error. Follow the Windows repair branch. Keep the app names and exact error together when requesting support.
- A copy runs from Downloads or another unexpected location. Check the file’s publisher and origin. Scan a suspicious copy; do not delete the legitimate system file by name.
What is CrossDeviceResume.exe in Task Manager?
The Windows component is reported inside the MicrosoftWindows.Client.CBS system-app package. A Microsoft Q&A identity report gives this full path:[5]
C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\CrossDeviceResume.exe
Compare that with Open file location on the process you actually see. A matching name or folder is useful context, not a certificate of safety; the signature and origin checks below apply to the actual file. The package name also explains why deleting a single EXE is different from turning off a feature.
What Resume does—and how to turn it off
Microsoft describes Resume as a taskbar handoff between a linked Android device and a Windows PC. Supported activities depend on the app and device setup. Its current documentation lists Windows 11 or later, Android 10 or later, an internet connection, Link to Windows, and a phone listed under Mobile devices as prerequisites.[1]
For example, an activity in a supported phone app can produce a taskbar icon with a phone badge; clicking it continues that activity on the PC. Microsoft lists examples such as Spotify playback and WhatsApp chats. This is an app-supported handoff, not a promise to transfer every open phone app. Turning Resume off disables these offers; it does not uninstall Phone Link or unlink the phone.
- Open Settings > Apps > Resume.
- Turn Resume off, or turn off only the supported apps you do not want to hand off.
- Sign out and back in or restart, then check your original symptom.
This is the supported feature control. It is not a promise that every related background process disappears on every Windows build. If Resume is already off and the process still appears without an error, that observation alone is not a reason to remove system files. If you want to unlink the phone itself, use the separate Phone Link startup and unlinking guide.
Do not confuse CrossDeviceResume.exe with CrossDeviceService.exe or PhoneExperienceHost.exe. Copy the exact name from your own error before following a fix aimed at another component.
If the busy process is CrossDeviceService.exe rather than a Resume launch error, use the Cross Device Service memory and CPU checks to test phone-file browsing and compare the result before removing cross-device components.
If Resume uses high CPU or memory
First expand the Resume group in Task Manager, if it has an expansion arrow, and identify which child process is busy. A group’s total is not necessarily the usage of CrossDeviceResume.exe alone. Use the exact executable name when deciding which guide to follow.
- Record the starting point. Note CPU and memory while the PC is idle, then while using the phone activity that seems to trigger the load. Watch several readings rather than one momentary spike.
- Test one feature change. If you do not need Resume, turn it off under Settings > Apps > Resume, restart normally, and compare the same workload. Keep other settings unchanged so the comparison has a useful meaning.
- Follow the result. If the load drops and the PC works normally, leave Resume off if you prefer. If it stays high, record the busy process, Windows build, and when the load starts; update Windows and the involved apps, then retest. If app-launch errors also appear, continue with the repair branch below.
A process returning after you end it does not show that malware recreated it. Ending a running instance is not a persistent feature setting. Avoid automatic task-killing scripts, package deletion, and undocumented registry overrides just to make Task Manager look empty. No single RAM figure or CPU percentage identifies this file as malicious.
Record the error before changing Windows
Keep the full error text, any DLL or package path, the time it appears, and what still works. Run winver to record the Windows version and build. Note whether the problem began after an update, a cleanup utility, manual package removal, or an unfamiliar installation. Timing can guide investigation without proving which change caused it.
- Bad Image or a missing DLL: copy the DLL name and error code as well as CrossDeviceResume.exe. The program named in the title may be failing to load a dependency; replacing that EXE alone is not a diagnosis.
- Interface not registered or The application has not been provisioned: check whether other packaged Windows apps show the same message. Several affected apps point the investigation toward shared components or the user environment, rather than only the Resume preference.
- The operation was not completed because an unexpected host ID was encountered: retain the complete dialog and Windows build. This wording alone does not identify a malware family or establish a specific repair. Use the isolated-error versus multiple-app distinction above, and include the exact text if you need Microsoft or IT support.
Do not replace the EXE or a named DLL with a download from a file repository. That can introduce an unsafe or incompatible file without resolving the underlying package or dependency problem.
For an isolated error, install available Windows updates, allow any pending restart to complete, and retest. Avoid repeated forced shutdowns during an update. If the same error remains, use the repair steps below and retain their results for support.
If Start or Settings will not open
Press Ctrl + Shift + Esc to open Task Manager. Select Run new task; older layouts may place it under File. You can launch winver there without relying on Start search. If the shortcut fails, try Ctrl + Alt + Delete > Task Manager.
For the repair commands, enter cmd and select the option to create the task with administrative privileges. Approve the normal Windows elevation prompt. On a managed work or school PC, involve your administrator if you lack that access. If Task Manager and the desktop are both unusable, get Windows recovery assistance; deleting a system application from another environment is not a substitute for diagnosing the failure.
Repair Windows components when errors persist
Microsoft’s System File Checker instructions run DISM first, then SFC after DISM succeeds.[2] In the administrator Command Prompt, run DISM.exe /Online /Cleanup-Image /RestoreHealth. Let it finish. After successful completion, run sfc /scannow and wait for verification to complete. Restart and test the same apps again.
Save any error code if a repair fails. Repeating the commands indefinitely or downloading the named DLL is not a diagnosis. For servicing that remains busy or fails to settle, see the DISM troubleshooting guide.
If several packaged apps fail together, treat that pattern as a broader problem. A July 2026 Microsoft Q&A report described the same registration error across Paint, Notepad, Outlook, and CrossDeviceResume. The original poster later reported that reinstalling the current Windows version fixed their affected machines. That is a useful case report, not proof of a single cause or a guaranteed fix for every PC.[4]
When ordinary repairs do not resolve the problem and Settings still opens, Microsoft’s Settings > System > Recovery > Fix problems using Windows Update > Reinstall now option reinstalls the current version and repairs components while preserving apps, files, and settings.[3] Back up important files first and keep the PC connected to power and the internet.

Choose that specific repair option, not Reset this PC. It may be unavailable on older installations or devices whose updates are managed by an organization. If it is missing, or Settings will not open, ask Microsoft support or your IT administrator for the appropriate repair-install route. Do not bypass company update policies to reveal it.
Check a suspicious copy without damaging Windows
In Task Manager, right-click the process and use Open file location, then inspect the file’s Properties and digital-signature details. Compare the full path with the Client.CBS example above. Treat the full package path and a valid Microsoft signature as evidence to check together, rather than relying on a familiar filename or folder alone.
A copy downloaded separately, launched from an unrelated user folder, or carrying an unexpected publisher deserves investigation. An error or CPU spike by itself does not establish malware. If an untrusted installer preceded the suspicious process, other bundled files or startup entries may also need checking.
For that suspicious-copy branch, download and install Gridinsoft Anti-Malware from the official site, update it, and run a Full Scan. Review detections, apply the recommended cleanup to confirmed threats, restart, and check whether the unwanted activity returns. A malware scan does not repair Windows package registration and cannot prove that no account information was exposed.
Keep the repair reversible
Do not take ownership of SystemApps, rename its executable, disable security protection, or run a blanket package-removal or re-registration script just to silence this message. Use the Resume setting for an unwanted feature, Windows repair for a repeatable system failure, and a malware check for evidence of an unexpected file. That distinction keeps a small preference change from becoming a damaged Windows installation.
References
- Microsoft. “Cross-device Resume Feature.” Microsoft Support, accessed November 5, 2026.
- Microsoft. “Using System File Checker in Windows.” Microsoft Support, accessed November 5, 2026.
- Microsoft. “Fix issues by reinstalling the current version of Windows.” Microsoft Support, accessed November 5, 2026.
- Andy Cannon and Microsoft Q&A contributors. “Interface not registered error on Paint, Notepad, Outlook and crossdeviceresume.exe.” Microsoft Q&A, July 23–August 6, 2026; accessed November 5, 2026.
- Gonn Alex and Lychee-Ng. “crossdeviceresume.exe.” Microsoft Q&A, January 27, 2026; accessed November 5, 2026. Reported Client.CBS path and Windows-component identification.

