I had hope that with the introduction of 25H2 this problem was solved. They call it 26200.xxxx but looking at the Component Store and the packages in there; They are still all called 26100.xxxxx. Basically it's then under the hood still 24H2. So I would call 25H2 not a version but it's more a servicepack for 24H2. It looks that 25H2 has issues from the start. First the WinRE issue that was introduced with 26100/26200.6899, solved with 26100/26200.6901 and now the problem with the taskmanager issue producing ghost processes when closed. Introduced with 26100/26200.7019. No solution for it yet but can be fixed by using the Vivetool at Github. Can be solved by turning on some features that MS forgot to roll out; The fix is already there inside 26100/26200.xxxx!!
ViVeTool.exe /enable /id:57048231
ViVeTool.exe /enable /id:49407484
And those 2 packages? They are still there. I don't bother anymore. It's just is a cosmetical problem. When you do an In-Place-Installment they will be back again. There are more pressing issues that are popping up the during the last 2 builds.
In the mean time 25H2 also introduced a CA2023 issue. The old certificate issued in 2011 is expiring in 2026. Saw some TPM errors in my system logbook. Came from the source: TPM-WMI. That CA2023 update is not automatically implemented in Windows 11 26100/26200.xxxx for some reason. Can be fixed manually. Found the solution at:
[INFORMATION] Secure Boot : Windows UEFI CA 2023 Update Downloaded some scripts. Read the manual and by running a few steps and those TPM errors disappears. Not a well know issue....
All with all more pressing matters are popping up with 25H2. Those 2 packages are there and are not that important anymore. We have to watch which problems are introduced with the next builds that MS is pushing through our throats.