Tripredacus Posted September 27, 2016 Share Posted September 27, 2016 I have not been able to see either of those processes running in Task Manager in these scenarios: - Pro 1511, Audit Mode, no internet connection - Pro 1511, local user, no internet connection, not activated - Pro 1511, local user, internet connection, not activated I can try 1607, but I can't do a test with a system activated right now. Link to comment Share on other sites More sharing options...
NoelC Posted September 28, 2016 Author Share Posted September 28, 2016 Thanks for checking. That's good feedback. It tends to make me think even more that it could have to do with one of the things I do that are fairly far off the reservation, e.g., Disable Windows Update service. Disable Windows Firewall service (I have the 3rd party Sphinx firewall). Disable a number of other services I don't believe I need. Remove all Apps including Cortana. Run with UAC disabled. Use a local account. A dozen other significant tweaks to try to undo most of what's "Modern" in Windows 10. Thing is, this is no more than an annoyance as everything works. I just don't understand what's starting SystemSettings then almost immediately having it go to Suspended status. -Noel Link to comment Share on other sites More sharing options...
tfw2002 Posted July 19, 2017 Share Posted July 19, 2017 (edited) As a Windows user from Version 3.0, Win10 could've been better optimised without the Metro/Modern interface. Anyhow, there is a way to stop SystemSettings.exe from ever starting at startup. I will attach a copy of the modified registry entries for Win10 1703 64-bit. You will need to launch Regedit with TrustedInstaller permissions using PsExec or NSudo. Save a copy of this registry location... HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\ActivatableClassId And compare with the attached tweaked version. This works with a local account, untested with a Microsoft account since I have no need to use one. Hope this helps. 10actclsidsrs2.zip Edited July 19, 2017 by tfw2002 Added additional info Link to comment Share on other sites More sharing options...
NoelC Posted July 20, 2017 Author Share Posted July 20, 2017 Does that stop SystemSettings from running entirely? Or just from being auto-started? This behavior seems to be gone from version 1703 anyway, so it's kind of a moot point going forward. -Noel Link to comment Share on other sites More sharing options...
tfw2002 Posted July 20, 2017 Share Posted July 20, 2017 Noel, it stops SystemSettings from starting up every 5 minutes after being killed and it doesn't start on startup. SystemSettings still starts up for me on the Creators Update around the 5 minute mark, so I took a deeper inspection in the registry to see what was causing it. The critical 3 keys are the SystemSettings ones under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\ActivatableClassId\] and delete the Activatable named entries. 1 Link to comment Share on other sites More sharing options...
UCyborg Posted July 20, 2017 Share Posted July 20, 2017 @NoelC I can confirm it still happens on non-tweaked version 1703. Link to comment Share on other sites More sharing options...
NoelC Posted July 23, 2017 Author Share Posted July 23, 2017 (edited) Wow, so the question becomes: What have I done this time around to avert it? Whatever it is, it's in my re-tweaker script. The only difference this time around is that I did NOT choose to remove all the Apps, since updates start to fail if they're removed. Having left them in, I did still kick the legs out from under the UWP table (e.g., by disabling the Unistack services). It uses more disk space this way, and SearchUI.exe does run so it uses a tiny bit more memory and another process, but it's still silent online and is pretty well optimized for desktop operations. Finding just how much one can carve back out and still end up with a viable, manageable system is the trick, isn't it? -Noel Edited July 23, 2017 by NoelC Link to comment Share on other sites More sharing options...
Rbert Posted September 24, 2017 Share Posted September 24, 2017 (edited) Hi, i extra register here because i also was searching for a solution (sorry for my bad english). I hope that i have understand the problem correct. I think, i found the solution in the Dexpot-Forum (i use Dexpot and first i thought it is a Dexpot Problem) In this Forum the user paracanary wrote here Quote disable superfetch in services and metro or microsoft apps do not preload. To disable, find superfetch and in properties choose disable. All problems solved. I also changed in regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters "EnablePrefetcher" from 3 to 0 (i use a SSD) My problem is solved. Hope it helps you. Greetings Edited September 27, 2017 by Rbert 1 Link to comment Share on other sites More sharing options...
tfw2002 Posted November 9, 2017 Share Posted November 9, 2017 On 24/09/2017 at 10:01 AM, Rbert said: Hi, i extra register here because i also was searching for a solution (sorry for my bad english). I hope that i have understand the problem correct. I think, i found the solution in the Dexpot-Forum (i use Dexpot and first i thought it is a Dexpot Problem) In this Forum the user paracanary wrote here I also changed in regedit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters "EnablePrefetcher" from 3 to 0 (i use a SSD) My problem is solved. Hope it helps you. Greetings Doesn't make any difference I'm afraid, SystemSettings.exe and a few other UWP apps like Microsoft Store still preload even after killing them manually. There must be some way to stop these. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now