Apps Enable or Disable Resume App from Device and Continue on Windows 11 PC

Techie007 · Sep 13, 2025

HarleyQuinn said:
Techie007 said:

@HarleyQuinn Execute the command below in an administrative command window—this is what I'm currently using:

Code:

schtasks /create /sc OnLogon /delay 0000:03 /tn "\Microsoft\Windows\Shell\Kill CrossDeviceResume.exe" /tr "taskkill /im CrossDeviceResume.exe /f" /ru SYSTEM /f

Click to expand...

I hesitate to run commands because of bad experience in past. I'd rather do it manually by following guide with visuals BUT unfortunately i couldnt find any so i had to dig reg keys by my own. Got help from forum a bit but stucked here.

Disable Cross Device Resume for All Users >>
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\Connectivity\DisableCrossDeviceResume]
"value"=dword:00000001

according to this should I double click on this "value" and change to 1?

All that command does is create a scheduled task in the "\Microsoft\Windows\Shell" folder to terminate CrossDeviceResume.exe upon the login of any user (which is when it gets started). It's much easier to run the command than to manually create the task. It's written out in plain English, so you can see exactly what it does. To undo, you just go to the Scheduled Tasks folder noted above and delete the new "Kill CrossDeviceResume.exe" task. Changes take effect after logging out and back in.

Yes. However, while the registry value you listed above does disable the feature, the program keeps launching and running in the background regardless, due to incompetent programming on Microsoft's part.

HarleyQuinn · Sep 13, 2025

@Techie007 I'm a bit newbie, thank you for explaining detailed. Does this system also work for turning off copilot or recall features?

Techie007 · Sep 13, 2025

@HarleyQuinn The command I gave only stops CrossDeviceResume.exe from constantly running in the background. There are policies you can put in place to disable the CoPilot and Recall features.

HarleyQuinn · Sep 13, 2025

Techie007 said:
@HarleyQuinn The command I gave only stops CrossDeviceResume.exe from constantly running in the background. There are policies you can put in place to disable the CoPilot and Recall features.

yeah i know haha im not that newbie

I meant does "creating a scheduled task" system also able to prevent copilot, recall or other microsoft features?. As i understand from your response they do, thank you.

Techie007 · Sep 13, 2025

No, you'd need to set policies to do that. And Recall only works with a very small subset of processors (mostly ARM), so I haven't had the opportunity to need to try to kill it.
All the Task Scheduler does is launch programs on a schedule or event. My command asks it to launch taskkill.exe three seconds after any user logs on, with a flag to terminate all instances of CrossDeviceResume.exe. Since SiHost.exe only launches CrossDeviceResume.exe once immediately upon user login, this trick works.

HarleyQuinn · Sep 13, 2025

yeah i understood, of course i'll change command script. I meant three seconds after I log in, can't i kill other programmes running in background using this method as well?

Techie007 · Sep 13, 2025

Ah, now I understand. Yes, you can modify the command to kill other programs running in the background. However, note a few caveats:

taskkill.exe filters processes by EXE name. So you won't be able to kill services hosted in a common container (such as svchost.exe) as it will terminate all of them, potentially crashing the computer (don't try that one—it could be difficult to remove the task!). rundll32.exe would be another container to be careful with (shouldn't interfere with the boot process, but it does cast a broad brush).
Some processes (such as CrossDeviceResume.exe) are launched once upon logon. This works well for those. However, other processes are launched in response to events. It will be harder to target those (you could try making the task recurring every few minutes—IFEO might be a better method to try to block those).
Some processes (such as StartMenuExperienceHost.exe—unnecessary if you're using a 3rd-party Start Menu) are automatically restarted if they exit unexpectedly. This will not work on those as a new one will immediately be launched to replaced the terminated one. I was able to successfully block that one by adjusting permissions to deny read access (results in a DCOM error being logged at login, but nothing further). Some however will throw a visible error message if you deny access (hence this taskkill trick with CrossDeviceResume.exe).
Some processes (such as TextInputHost.exe and mobsync.exe) are launched in response to a setting (HKCU\Software\Microsoft\input\IsInputAppPreloadEnabled) or a DCOM server (HKCR\CLSID\{1A1F4206-0688-4E7F-BE03-D82EC69DF9A5})—respectively. It is better to change the setting or unregister the server than to try to terminate the process after the fact.
You will need to change the task name if you're writing additional tasks, or the new task will replace the old one.

Best thing is to try manual termination (from Task Manager's Details tab, or using System Informer) and verify the outcome is as desired before writing a task to automate termination for you.

HarleyQuinn · Sep 14, 2025

@Techie007 thank you for your time i appreciate

emanon · Oct 6, 2025

Im testing windows 11 and noticed this 'resume' process running, over 180 MB at times and im not even going to come close to using this feature. Iv got a custom install of windows using Chris Titus windows utility that removed all onedrive features and online microsoft account requirements.

this is highly suspicious they would force a process like this to run that has to do with other devices speaking to each other, usually its common sense this would be a optional feature for obvious security reasons, the fact microsoft has gone to the lengths to make this, and other odd processes, (not to mention the blatant co pilot ai and recall etc) not be able to be switched off with ease tells you how far they are into this data collection and surveillance agenda.

looks like this tool Vive is the only way to actually stop this 'resume' process from running, i will continue to look into this

HarleyQuinn · Oct 8, 2025

@emanon It keeps coming back after every cumulative update. Good luck

emanon · Oct 19, 2025

https://www.reddit.com/r/WindowsHelp/comments/1lfu325/trying_to_stop_resume_and_search_from_running_in

follow the steps provided in the comment section, someone posted an easy to follow way to use ViveTool to disable this stubborn spy process.

garlin · Oct 19, 2025

That's the same answer as provided earlier (post #6). But the reg file provided on Reddit is for id 37926450 (SearchHost).

HarleyQuinn · Oct 20, 2025

hello guys is resume still running(background) for you after update 25h2 update?

Techie007 · Oct 20, 2025

@HarleyQuinn Not for me, using the tweak I provided earlier. Fresh boot looks like this for me on stock Windows 11 25H2 after tweaks have been applied:

HarleyQuinn · Oct 20, 2025

I want to share after clean install of 25h2, before laptop connects to internet i deleted some apps also disabled phone link and few other related bloatware apps to never run in background under power setting. So without using any third party tool or regedit, now it disappeared. Its been a week haven't seen single resume or crossdevice progress in task manager

Memory usage seem normal just like in 24h2 before september lol

Techie007 · Jan 21, 2026

garlin said:

Instead of using ViveTool, you can substitute the same reg changes:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\System\ControlSet001\Control\FeatureManagement\Overrides\8\1387020943]
"EnabledStateOptions"=dword:00000000
"EnabledState"=dword:00000001
"Variant"=dword:00000000
"VariantPayload"=dword:00000000
"VariantPayloadKind"=dword:00000000

garlin said:
You may have to re-apply the reg, and permanently disable the ReconcileFeatures task:

Code:

schtasks /Change /Disable /TN "\Microsoft\Windows\Flighting\FeatureConfig\ReconcileFeatures"

ReconcileFeatures phones home, and asks MS which Feature ID's to change on an user's machines. This is how "gradual rollouts" are staged.

It turns out that this understanding of ReconcileFeatures is actually what caused your registry tweak stop working on my machine. ReconcileFeatures is the solution, not the problem—those registry flags often do nothing without ReconcileFeatures—it is what applies them! When run, it doesn't "phone home"; rather, it reads through certain files already present in C:\ProgramData\Microsoft\Windows\OneSettings, and then adds/removes feature flags to the registry according to the changes found within, and then it scans through all the feature flag settings in the registry, applying/activating them.

After figuring this out (while trying to get the new NVMe storage stack working, actually!), I reimported that task from another machine, ran it, and CrossDeviceResume.exe once again no longer automatically starts on my machine—even on build 26200.7623—I no longer have to run my special task to terminate it after logging in because it's no longer launched (it also enabled the new NVMe storage stack). What broke the tweak (and also rendered the NVMe storage stack feature flags of no use) was disabling (and later removing) the ReconcileFeatures task! The correct order: You write your registry feature overrides tweaks (which do nothing by themselves). Then you manually run ReconcileFeatures (which reads your feature overrides and applies them). Then you reboot (so the changes can take effect). Profit!
Windows Update may change your features at a later time or download new components; to correct this, ReconcileFeatures has to run again (so if you disable it, certain features will revert in the future despite the flags still being set in the registry). Now, if Microsoft decides to flip the switch (i.e. a new feature goes out of preview and into release) ReconcileFeatures will flip the feature flag in the registry or remove it entirely. That's where you have to flip it back by rewriting the registry tweak. But you still have to run ReconcileFeatures to apply the tweak!

artins90 · Feb 25, 2026

What a sad state Windows is in.
The "feature" has an ON/OFF switch and yet the OS keeps launching the process even when the user explicitly asked to keep it disabled.

Techie007 · 2026-06-10T15:26:58-0400

Just a heads up, a couple months back, the feature flag noted in my post above stopped working again to disable CrossDeviceResume.exe, so I'm back to using the scheduled task tweak provided earlier.

Apps Enable or Disable Resume App from Device and Continue on Windows 11 PC

Turn On or Off Cross Device Resume for All Apps for Current User in Settings

Turn On or Off Cross Device Resume for All Apps for Current User using REG file

Turn On or Off Cross Device Resume for Specific Apps for Current User in Settings

Turn On or Off Cross Device Resume for Specific Apps for Current User in Registry Editor

Enable or Disable Cross Device Resume for All Apps for All Users using REG file

Attachments

Active member

My Computer

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computers

New member

My Computer

Well-known member

My Computers

New member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computer

Active member

My Computer

Similar Windows 11 Tutorials