( I was on build 1709, the POS updated while I was doing something else despite doing all the 'usual tricks' to keep it from updating. After figuring out it snuck in updates on me due to an icon on desktop missing, I had to roll back to prior version of windows. )
Now to assure myself this wouldn't be happening again while I was downloading a game and away from the computer, I went through over the course of 2 nights hunting around and killing anything associated with ANY form of windows updates. Because clearly there is backdoors all over this POS OS.
I'm not writing this to rant, really, I've cussed at windows 10 enough that I think it is out of my system. I'm writing this for anyone that would like to try and do the same to their PC.
I do not know how it will effect every individual computer, nor individual build. Before trying any of this, make a back up and rescue of your PC just in case.
If you're not sure how to do that...I recommend not trying the below.
blaugh Starting out under
Component Services:
-Update Facilitation Service -- when looking under properties there is the file "osrss.dll" ( more on this later )
-Update Orchestrater Services Properties
-Windows Push to install service
-Windows Insider Program
-Windows Remediation Service Properties
-Windows Modules Installer Properties
-Windows Store Install Services
The ones I could stop and disable by right clicking on them and doing so, I did.
For those that I couldn't, I looked at their program dependencies or where they stemmed and operated from more or less.
Example, above you have osrss.dll
After much searching found the little thing in the windows system32 folder.
To break it, I tried to rename it. It kept telling me I THE ADMIN, GOD OF THE MACHINE, did NOT have access to this file. ...Uh. Don't tell me I can't break my own s**t, windows. Hell no.
scream Right click the file, properties > security > advanced - owner - ( you can type in your username on the computer of the account you're on with in the big blank box, or you can type in everyone to save yourself some backtracking just incase ) You can also click the button to the side that says advanced - find now - scroll to everyone - apply.
Now, back under the properties > security > first button that says edit > should be then able to click on the names ( admin / users / system etc ) down a list, and there are check boxes below, one says allow, the other says deny, you want to always click on allow all, under admin and users ( makes breaking s**t easier, though yes, less secure, but lets face it...you're sacrificing 'security' by breaking s**t too, kinda, right? So windows would tell you anyway.
Once you've managed to get that done, keep how to do those steps in mind, you'll be seeing them in your sleep repeatedly with the following files below in a moment.
Back to the issue! Osrss.dll file, what to do about this little s**t?
RENAME IT! I usually make it look like this osr--ss.dll That's it, it keeps the original name, and just adds -- in it, this way if I have to go back later I can take out the -- easily with out having to remember what the hell the thing was called.
You'll be doing the same thing to the following files in the system 32 folder:
-osrss.dll ( mentioned above )
-wups2.dll
-wusa
-wups.dll
-wudriver.dll
-wuapi.dll
-wuapihost
-wuauclt
-wuaueng.dll
-wuautoappupdate.dll
-usoapi.dll
-usoclient
-usocore.dll
-updatehandlers.dll
-updatepolicy.dll
-updateagent.dll
Once you finished breaking those, you'll want to goto
regedithkey_local_machine/software/policies/microsoft/windows
right click the windows folder New > key: Name the key windows update, hit enter
Right click windows update New > Key; name it AU
Right click AU, New > Dword 32bit >Change value to 2
Save all that and now locate on the harddrive the Windows folder.
You may have one that says WINDOWS and one that says Windows10Upgrade
After going through the 2094387 steps above to rename things, just add a - in there on the windows 10 upgrade folder, juuust to break the path of everything in it.
Now, under WINDOWS
You'll see a folder called
PantherIt's a sneaky little s**t where windows seems to have maybe stored more update s**t. I broke the folder path once again by just adding a - ( making it look like Pant-her ) Not intentional!
--breaking the original folder created a new one today but with another smaller folder in it called Panther > UnattendGC
It doesnt seem to have anything important in it, but if windows is going to keep adding it, will probably make a short cut to the POS to monitor it easier just incase.
Moving on down, farther down the list, you'll see UpdateAssistant I added -- in there too, just to make sure, you may have to again allow permissions to break it. Was falling asleep last night breaking things. By now you should be an expert on the steps!
That was the only things I killed off in the windows folder.
3nodding For good measure and because I hate it, killed cortana too, if you want to know how to break her you'll need to go back to
regedit. ( Registry Editor Location: HKEY_LOCAL_MACHINE/SOFTWARE/Policies/Microsoft/Windows
) -- click link to see video, not too difficult to explain; easier to send a link.
lazy 4laugh Only other place to keep watch on for updates would be the windows defender, long suspected they're sneaking s**t in through that way when it checks itself for updates. Not broken anything dealing with it yet, but going to keep watch. If suspicions are right, that will be the next thing that I break. Will post about it if anyone else interested in breaking things too.
blaugh 
<---wondering what this says
<---product it was found in