I'd love to learn something from this exercise - like how to stop this system behavior of running an App I don't want running in the first place.ĪpplicationFrameHost.exe and SystemSettings.exe are the newly started processes left running after the 5 minute mark. I've already removed a scheduled run of provtool at 5 minutes after bootup, but that didn't stop the run of SystemSettings.exe. What I don't know is whether most folks have enough Apps that this stuff always starts right up after login normally. I will be sweeping through the Task Scheduler looking for what it is that's starting SystemSettings.exe after 5 minutes of idle time, but if you have any ideas - or if you also see this happen on your Win 10 system - please let me know. Since mine is a system on which I don't normally expect to run an App of any kind, I sure as hell don't want a copy of SystemSettings.exe sitting in the background. With BigMuscle's ModernFrame-圆4-Debug.dll in place it's obvious when it happens because a debug console window opens for ApplicationFrameHost.exe. SystemSettings.exe goes immediately to Suspended state. If I boot my Win 10 test VM, and leave it completely alone for 5 minutes, SystemSettings.exe and ApplicationFrameHost.exe are automatically started.
0 Comments
Leave a Reply. |