Resolve Task Manager process might continue to run in background after app is closed

uncyler825 · Nov 2, 2025

dacrone said:
There are simpler solutions than what you’ve implemented. As long as you’re happy though, boss.

So what? How could I not know that I can use the "End Task" button or something way to terminate the process?

dacrone · Nov 2, 2025

uncyler825 said:
I don't need help.

You really don’t want a measuring contest around here. I’d be down the list and still tiers above. Time to run along now.

uncyler825 · Nov 2, 2025

You can add me to your blacklist.That way you won't see this article.

I'm share my results. I don't think it's worth spending time arguing about this.

You have a simpler solution, you can continue using your own method to solve your problem. You don't need to complain about what solutions others use to solve problems.

In fact, you only need to import the registry file to resolve TM issue. I have already shared the results, so you don't need to spend any more time. You don't need to use the [End Task] button or a BAT file to solve the problem.

tistou77 · Nov 3, 2025

uncyler825 said:
You seem to not know how to save it as a REG file. It will automatically create .\FeatureManagement\Overrides\14 registry path.

I know how to do it, thanks.
It's just that it says to delete this registry key, which I don't have.

uncyler825 said:

Code:

Windows Registry Editor Version 5.00
# Resolve Task Manager process might continue to run in background after app is closed
# Undo - Delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14 Registry Key and restore default values.
# You will need to open CMD as administrator. Type the following command in CMD to Undo:
# REG DELETE "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14" /f

hader · Nov 3, 2025

I seem to be affected to. I have something what needs to be cleared; I don't have the registry key HKLM\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14. The rest of this section of the overrides tree's are 0, 1, 15, 3, 4, 5, 8 and 9. So no 14.

TLDR I know. But I am going into the specifics. Not Interested? Skip to the bold part. This will fix the issue immediately.

Why do I see a difference? I have an NL-ISO of 25H2 installed, updated to 26200.7019. And I don't have this entry. I have installed the US-ISO 25H2 inside a VM and this installation (updated to 26200.7019) does not have this 14 also. (only 15 also) Where does this difference come from? In all clue's I see only 14 mentioned.

Diving deeper into the solution; I see a CFR RKey number linked to a ViVetool number in order to solve this issue;
CFR RKey number: 1318466191, ViVetool number: 57048231
CFR RKey number: 4188347533, ViVetool number: 49407484 (Requires 1318466191 to be "set" or "enabled" to work.

The CFR RKey number 1318466191 does not appear in the #14/15 Tree. It appears only in the ControlSet001 and CurrentControlSet other trees:
- ControlSet001\Control\FeatureManagement\Overrides\0\1318466191 (not very important entry; Enablestate=1, EnabledStateOption=0. Does not change before and after)
- ControlSet001\Control\FeatureManagement\Staged\10.0.26200.7019\Overrides\4\1318466191 (important entry)

- CurrentControlSet\Control\FeatureManagement\Overrides\0\1318466191 (not very important entry; Enablestate=1, EnabledStateOption=0. Does not change before and after)
- CurrentControlSet\Control\FeatureManagement\Staged\10.0.26200.7019\Overrides\4\1318466191 (important entry)

The next CFR Rkey is creepy. It is not present on my NL-ISO PC, but present on the US-ISO VM.
- ControlSet001\Control\FeatureManagement\Overrides\4\4188347533
- CurrentControlSet\Control\FeatureManagement\Overrides\4\4188347533

Rebooting: There lies the reason for a reboot; CurrentControlSet is aways the current one. ControlSet001 is the previous one, also called the Last Known Good Configuration boot option. At a reboot thing are taken over from ControlSet001 to CurrentControlSet. (CurrentControlSet is a symbolic link to ControlSet001. Some have also ControlSet002. The target here is CurrentControlSet) I think this is the reason why ViVetool must reboot to make the change possible. The CurrentControlSet setting can't be altered by a program because Windows is running. Changing the backup-set is the alternative. To get it current it must reboot.

My conclusion: Many things are vague and does not match what I see. So altering the registry is not a viable solution. The only thing what may solve the problem is using the ViVetool.

So; (Using ViVeTool-v0.3.4-IntelAmd.zip: Releases · thebookisclosed/ViVe)
Start a CMD-box as admin. Goto the dir where you unpacked the .zip file
ViVeTool.exe /enable /id:57048231
ViVeTool.exe /enable /id:49407484
Reboot.

After this reboot the problem on my VM seems to be solved. Can call the Taskmanager and closing it as much as I want; No ghost processes are left behind. My system with no 4188347533 entry? Despite no entry it does solve the problem as well. (Entry 4188347533 can now be found in the 8-tree.)

Looking at what had happend. It seems that it's taking a copy of CurrentControlSet\Control\FeatureManagement\Staged\10.0.26200.7019\Overrides\4\1318466191 to
CurrentControlSet\Control\FeatureManagement\Overrides\8\1318466191 and changes it's values EnabledState=0->2 and EnabledStateOptions=1->0.
This 8-tree is now populated with some ViVetool changes (1318466191 and 4188347533) and a menu change (menu category look; "# Simplify toggle on New Start Menu. ViVetool ID: 47205210 (CFR RKey: 3036241548)") I have enabled yesterday. It seems that 0-15 override system is a priority system where 0 is the lowest priority and 14/15 the highest. As already suggested by uncyler825.

So to solve the issue on a safe manner: Use the ViVeTool! I am not familiar with (Who is?) this CFR system. So entering the wrong keys can have negative consequences of which we are not aware off. Or just wait until MS fixes this issue through an update. The second failure in a row.

Where are these canary, dev, beta channels else for? MS is getting sloppy and this is not very good news.

uncyler825 · Nov 3, 2025

hader said:
I seem to be affected to. I have something what needs to be cleared; I don't have the registry key HKLM\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14. The rest of this section of the overrides tree's are 0, 1, 15, 3, 4, 5, 8 and 9. So no 14.

1. CFR technology designed by Microsoft for controlling and telemetry of features status.
2. Vivetool obfuscates the CFR Key. Vivetool ID corresponds to CFR Key.
3. Priority is 0-15, with higher numbers indicating higher priority. Higher priority will override lower priority. You don't need to care whether the path exists or not. You can also use Vivetool to set the priority to 14.
4. Performing Windows Update will trigger a CFR synchronization with Microsoft servers. Windows Update access priority 4 path.
5. Entering an incorrect CFR ID will have no effect, as not all IDs are valid.
6. Unusable CFR IDs have been prioritized by Microsoft as level 15 and forcibly disabled. You cannot change the priority of protected access if you do not have the corresponding permissions.
7. If your system crashes severely due to an experimental feature, the system will temporarily undo all CFR states and revert to the initial state.
8. Microsoft has never publicly disclosed any labels or describe for all CFR IDs.

uncyler825 · Nov 3, 2025

Microsoft uses CFR technology to gradual rollout all features and improvements under "Gradual rollout" section. And not every user will receive the same CFR ID status. I think this is how Microsoft wants to confirm whether a feature is affecting users, because the system will report the CFR status to Microsoft.

tistou77 · Nov 3, 2025

hader said:
So; (Using ViVeTool-v0.3.4-IntelAmd.zip: Releases · thebookisclosed/ViVe)
Start a CMD-box as admin. Goto the dir where you unpacked the .zip file
ViVeTool.exe /enable /id:57048231
ViVeTool.exe /enable /id:49407484
Reboot.

Tested and it works, thanks
However, the process display is slightly slower when opening Task Manager (compared to before the change, almost instantaneous).

2 keys added:

Code:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\1318466191]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000
"Variant"=dword:00000000
"VariantPayload"=dword:00000000
"VariantPayloadKind"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\4188347533]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000
"Variant"=dword:00000000
"VariantPayload"=dword:00000000
"VariantPayloadKind"=dword:00000000

uncyler825 · Nov 3, 2025

tistou77 said:

Tested and it works, thanks
However, the process display is slightly slower when opening Task Manager (compared to before the change, almost instantaneous).

2 keys added:

Code:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\1318466191]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000
"Variant"=dword:00000000
"VariantPayload"=dword:00000000
"VariantPayloadKind"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\4188347533]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000
"Variant"=dword:00000000
"VariantPayload"=dword:00000000
"VariantPayloadKind"=dword:00000000

Basically, manually importing the registry keys the same result as using Vivetool. Differences in Vivetool default use priority 8. (You can also set the priority 14)

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\*Priority Number*\*CFR ID*]

uncyler825 · Nov 3, 2025

hader said:
The next CFR Rkey is creepy. It is not present on my NL-ISO PC, but present on the US-ISO VM.
- ControlSet001\Control\FeatureManagement\Overrides\4\4188347533
- CurrentControlSet\Control\FeatureManagement\Overrides\4\4188347533

BTW. Only need to change "ControlSet001\Control", and "CurrentControlSet\Control" will also be changed synchronously without you having to change it manually.

Priority 4 is not present on your ISO or any ISO. You need to connect to the internet and run the Windows Update service to obtain the CFR table.

hader · Nov 3, 2025

uncyler825 said:
1. CFR technology designed by Microsoft for controlling and telemetry of features status.
2. Vivetool obfuscates the CFR Key. Vivetool ID corresponds to CFR Key.
3. Priority is 0-15, with higher numbers indicating higher priority. Higher priority will override lower priority. You don't need to care whether the path exists or not. You can also use Vivetool to set the priority to 14.
4. Performing Windows Update will trigger a CFR synchronization with Microsoft servers. Windows Update access priority 4 path.
5. Entering an incorrect CFR ID will have no effect, as not all IDs are valid.
6. Unusable CFR IDs have been prioritized by Microsoft as level 15 and forcibly disabled. You cannot change the priority of protected access if you do not have the corresponding permissions.
7. If your system crashes severely due to an experimental feature, the system will temporarily undo all CFR states and revert to the initial state.
8. Microsoft has never publicly disclosed any labels or describe for all CFR IDs.

Ok nice to know. I prefer the ViVeTool alternative. I don't want inject keys into my registry if they don't already are already there. If they exists I only want to change them and revert back to them if they don't function. ViVeTool fixed the problem without messing around with #14 or #15. The real reason I've already mentioned before. It just copied 2 staged overrides #4 to the current location; #8 (and not into #14 or #15) and changed their values in order to get effective. I see a complete listings with #14 entry's. I am not gonna touch them let alone inject this entry's into my registry. The registry is a very complex beast. If anyone doesn't understand that changing value's can have impacts; the should delete regedit.exe. It is dangerous to change values not knowing it's impact.

The main goal here is to help other people with this complex problem without becoming al to technical. The average user don't even understand the values inside the registry let alone CFR's. So the solution by using the ViVeTool is a safer way than injecting registry keys.

I tried an other thing. Reverting to the previous situation with the ViVeTool.
ViVeTool.exe /disable /id:57048231
ViVeTool.exe /disable /id:49407484

It functions! But it don't deletes the copied entry's to #8. It changes value from EnabledState=2->1 and EnabledStateOptions=0 (stays as it was). So the problem is back again.

ViVeTool.exe /enable /id:57048231
ViVeTool.exe /enable /id:49407484
Solves the situation again. Alters just the value EnabledState from 1 to 2 again.

One thing is for sure. ViVeTool has a limited usage as CFR RKeys come and go with MS updates. That's why this solution is linked to 26200.7019 because the entry's inside the staged part makes it so. With the next Build update this entry will be deleted and replaced by the than current build.

I also wonder what the link is between CFR RKey and Vivetool ID.....? There must be some sort MS internal database that translates the CFR RKey to a Vivetool ID. And why is this tool translating? To keep things secret? I suspect they are otherwise the ViVeTool would accept the CFR Rkey as an id......

hader · Nov 3, 2025

uncyler825 said:
BTW. Only need to change "ControlSet001\Control", and "CurrentControlSet\Control" will also be changed synchronously without you having to change it manually.

Priority 4 is not present on your ISO or any ISO. You need to connect to the internet and run the Windows Update service to obtain the CFR table.

Uhm.. I already mentioned that CurrentControlSet is a symbolic link to ControlSet001. Altering something in ControlSet001 will change the same value in CurrentControlSet also. Yes. A reboot is only necessary to make things active.

My build is at the latest build; 26200.7019. That was already visible inside the staged part of the override section inside the registry; CurrentControlSet\Control\FeatureManagement\Staged\10.0.26200.7019.

CFR Rkey 4188347533 wasn't there. There is now thanks to the Vivetool. So no need to update again. Searched for an update and none was found.

uncyler825 · Nov 3, 2025

I don't want inject keys into my registry if they don't already are already there.

Using Vivetool will also inject into the registry. Remember! The path preset for priority 8 is also empty.

Using priority 14 can also remove priority and 14 to undo all changes, without actually messing up the registry. No need to change the priority (0, 1, 3, 4, 5, 9, 15). In fact, you can manage your registry key quite well. Even if you use Vivetool, you can directly delete priority 8 to undo all changes.

I also wonder what the link is between CFR RKey and Vivetool ID.....?

The calculation method for obfuscated CFR IDs in Vivetool can be found in the Vivetool open-source community on Github.

And why is this tool translating?

Microsoft does not disclose the details of CFR ID, so the obfuscation is intended to prevent you from finding it easily. However, you can actually decode the Vivetool ID to CFR ID, or convert a CFR ID to Vivetool ID.

uncyler825 · Nov 3, 2025

# Undo - Delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14 Registry Key and restore default values.<br># You will need to open CMD as administrator. Type the following command in CMD to Undo:<br># REG DELETE "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14" /f

If you have read my article content. I have clearly stated that you can delete the priority 14 Path to undo the changes. I have also provided converted Vivetool IDs for users to choose.

You can also use the Vivetool tool to enable these features.

garlin · Nov 3, 2025

uncyler825 said:
2. Vivetool obfuscates the CFR Key. Vivetool ID corresponds to CFR Key.

Incorrect. MS (not ViveTool) deliberately obfuscates the Feature ID <--> Overrides value.

Without the reverse-engineering from ViveTool and Mach2's devs, you're stuck with polling for reg changes.

hader · Nov 3, 2025

Looking at Vivetool and their commands; Vivetool /query show us a list of features which can be enabled or disabled.
In this query each time the same set is present: Priority, State and Type. To make a matrix I found the following:

See attachment.....

Each priority category can be fetched by: Vivetool /Query /Priority:<0-15>

It seems that Priority is not a list of priority's 0=Low and 15=highest but more a category assignment. 0=ImageDefault and is in many cases the standard settings as you would expect from a change build image. An ImageOveride overrides the intention for the ImageDefault. Services and Security are other category's. Because the TM fix don't belong to any other category's and it is initiated by the User. This fix goes under already mentioned #8 override section.

That ControlSet001 has a great importance; it shows that the vivetool uses this info with
- /lkgstatus Prints the current 'Last Known Good' rollback system status (It just says: "LKG status: LKGPending" Is this good or bad?)
- /fixlkg Fixes 'Last Known Good' rollback system corruption

Using vivetool /dictupdate (get the latest update of features) is reacting that I am already to the last known version: "You're using the latest version".

BrandonR · Nov 3, 2025

antspants said:
This forum hosts many members and visitors, it's not all about you.

Seems pointless changing registry keys when Microsoft is obviously going to address this.

If at all helpful to you:

Temp fix, kill switch for Task Manager, killtask.bat
Save to desktop, click to run, will restart with a UAC prompt to run as admin and Kill all Task Manager instances.

Code:

@echo off :: Check for admin rights fsutil dirty query %systemdrive% >nul 2>&1 if %errorlevel% neq 0 ( :: Relaunch as admin powershell -Command "Start-Process '%~f0' -Verb RunAs" exit /b ) :: Kill Task Manager taskkill.exe /im taskmgr.exe /f >nul 2>&1 if %errorlevel% equ 0 ( echo Task Manager was successfully terminated. ) else ( echo Task Manager could not be terminated or was not running. ) timeout /t 3 >nul exit

Thanks for this! will be using this til they fix this in a WIndows update.

hader · Nov 4, 2025

Well Something different. Since 7019 I have experienced after some time my keyboard goes crazy. Special keys like <>{}[]()=- etc. trade key places. I have a keyboard; An Steel-Series APEX 7 that lives up to the standard of MS. I wonder if anybody experincied the same bizar issue after a while. Never had any issue with it until 26200.7019 came along. Had some issues with it once on a rare occasion but It's now with 26200.7019 more prominent. To solve it; Sign off and sign on.

Anyone else seen/experienced this ????

Dark Knight · Nov 4, 2025

Personally, IMO , I would just leave well enough alone, it will probably get addressed in the next update. Whether you do or don't use TM often it only takes two seconds to run the command:

Code:

taskkill.exe /im taskmgr.exe /f

hader · Nov 4, 2025

hader said:
Looking at Vivetool and their commands; Vivetool /query show us a list of features which can be enabled or disabled.
In this query each time the same set is present: Priority, State and Type. To make a matrix I found the following:

See attachment.....

Each priority category can be fetched by: Vivetool /Query /Priority:<0-15>

It seems that Priority is not a list of priority's 0=Low and 15=highest but more a category assignment. 0=ImageDefault and is in many cases the standard settings as you would expect from a change build image. An ImageOveride overrides the intention for the ImageDefault. Services and Security are other category's. Because the TM fix don't belong to any other category's and it is initiated by the User. This fix goes under already mentioned #8 override section.

That ControlSet001 has a great importance; it shows that the vivetool uses this info with
- /lkgstatus Prints the current 'Last Known Good' rollback system status (It just says: "LKG status: LKGPending" Is this good or bad?)
- /fixlkg Fixes 'Last Known Good' rollback system corruption

Using vivetool /dictupdate (get the latest update of features) is reacting that I am already to the last known version: "You're using the latest version".

Any thoughts? This is exact what MS meant with "Introducing slowly some feature" (Forget the25H2 hype and bla. bla. It's basically still 24h2!!) You have to give it them. Genius in some way. It it's a way to lay dormant while your system is already prepped for it through updates. All it takes is to "pull-the-switch" to enable features. I still look at the 7019 issue that they forgot to enable a "feature" to turn on. Their mistake. They have already stick an solution into us and forgot to turn it on. The next build update will deal it. Again. I have said it once Canary, Dev, Beta builds? They didn't saw this coming? Unlikely. I know a lot of users that scrutinize everything. They are the real Guinea pigs before any release. What went wrong here I wonder?

Resolve Task Manager process might continue to run in background after app is closed

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

Attachments

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer