"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --no-startup-window --win-session-start
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --no-startup-window --win-session-start
Did this pattern stop being a thing and we’re back to it now? Or was it just “forgotten”?
Now there’s scrolling through hundreds of scheduled tasks called dfddg.exe with no title or description and located in c:/windows or %appdata%. Disabling the wrong identically named one bricks your system or software licenses.
Then you also have to check the registry and group policy and environment variables and spot the unwanted item that is again often bundled into a critical windows dll. Usually with the same name as the dll and its permissions are set as SYSTEM so you can’t edit it by normal means.
Then after every change you have to do a full rebooting and review all steps again. Often, they will regenerate themselves if deleted in the wrong way or the wrong order.
After all the startup things are killed there may still be kernel level startup recovery processes for things like Adobe.
This sounds like Microsoft is failing spectacularly at enforcing strict limits on what software can do.
https://learn.microsoft.com/en-us/sysinternals/downloads/aut...
Uncheck one thing. Reboot. Test system.Proceed to the next item.
I bet that loop is way faster nowadays than when I was messing around as a teen trying to get our new 1Gb hard drive desktop to boot faster.