This is my daughter's Win10 Acer laptop, new as of last September.
it came with Win10 natcherly..... and she is not happy with that.
a few weeks ago, I followed this page to edit the Registry
https://www.windowscentral.com/how-stop ... windows-10
Fast Forward to today:
Win10 over-rode those settings and downloaded a passle of updates, requesting that Cyndi chose Update/Restart....
well, good ole me, just up and deleted the entire ~/download/updates folder, poof!
So now, I jump to the Registry again and modify the new command 'AU' for Automatic Updates and set it to never '01'
I made a mistake the first time, and entered '02'
today, I changed that to just the single digit '1'
Group Policy Editor is not available on home editions.
so we have to use the Registry instead.
some of this page works, most of it don't
https://superuser.com/questions/1030085 ... ng-updates
I created a text document named Shutdown, and in it gave instructions to Cyndi to:
Windows Key R type cmd <enter>
type
shutdown /p
and down she blows, like right now!!!!!!!
this is a trick I use on my Win7 desktop when I want it to shutdown "right now" because some damn application has hung up.
works like a champ, and has never caused me any problems.
on Win7, you can click on the .BAT file and it goes down.
on Win10 you must copy or type the word 'shutdown /p'
it will not allow you to run a file as an Administrator.... crap!!!
Now, more interesting things happen.....
even though, I had deleted the updates folder, when it restarted, it insisted on Updating the System..... took about a minute, then it rebooted again, and was up in 10 seconds. it must have stored some minor updates in a folder I don't know about... the Acer has a ( SSD ) so it is fast with a 2.3gHz cpu and 8gB RAM
shut it down 3 more times, and that did not occur again.
now we wait, to see if the new modifications prevent the Updates from happening.
IIRC, I read somewhere, that MicroSoft has code that will over-ride our registry settings and force updates anyway.... wondering if that is what happened, or was it because I used the wrong setting for AU ?