I suppose that MS really, really, really doesn’t like anyone to change anything. I attempted to alter the name of shutdown cmd in regedit, but Windows disallowed, so I attempted to gain permission by altering or adding myself as a user, but Windows blocked me from being able to do anything. Then, I created a blank shutdown.exe via notepad & placed it into system32, & eliminated all users from having any rights, but Windows still found a way to auto-shutdown on a timer. A monumental task in itself, because Windows tried to block me via “security rights” meaning I had to add myself as a user & give myself permissions in order to change this file. Win 10 LTSB has an annoying shutdown timer, which I attempted to block by renaming shutdown.exe in sytem32 to -shutdown.exe. No such luck, & after enabling Defender, it was impossible to disable again without re-visiting gpedit.msc to re-apply the disable settings. So, I ran services.msc in admin mode by locating services.msc in system32 folder & enabled Windows Defender to see if perhaps MS relented with settings I adjusted to give me back control. Sure, I disabled in the policy editor (gpedit.msc) but then I noted in services.msc where previously Windows Defender had NO options you could disable, here it enabled the enable box. Win 10 also made it all but impossible to totally disable Windows Defender, which resulted in Windows Defender proactively suggesting that I may have a ‘dangerous’ file on my flash drive, despite disabling real time defense. On the downsides, I was unable to uncheck ANY of the ‘security center’ msg boxes, where perhaps Win 8.0 was the last OS that allowed a user to have any kind of control. I was interested in Win 10 LTSB release, because it does NOT come with Cortana or Metro app garbage.Īdditionally, it uses IE as default & Edge isn’t even included.Ĭalc is standard (non-Metro), & performance seems ok.ĭefault Apps included ability to set Windows Photo Viewer as default, so no worries there.

Win 10 enterprise activator