Stop Windows 10 Updates Properly and Completely

pf100 said:

an update already can't unlock a locked update hijacker system file.

No update can unlock a file already locked by either PowerRun v1.3 or NSudo 6.1.
Have I understood correctly?

Matthew Wai said:

No update can unlock a file already locked by either PowerRun v1.3 or NSudo 6.1.
Have I understood correctly?

Removing permissions from system files locks the files whether you use PowerRun or NSudo or not.
In 1803 and earlier you could remove permissions with your normal Administrator account and they would stay locked.
Starting in 1809, the Administrator account doesn't have enough permissions to remove system file permissions, so now you have to do it as TrustedInstaller.
NSudo or PowerRun just gives you the ability to remove system file permissions in 1809 and later, so it's not PowerRun or NSudo that makes the files locked, they just give you the ability to remove system file permissions to lock them in 1809 and later.

pf100 said:

NSudo or PowerRun just gives you the ability to remove system file permissions in 1809 and later, so it's not PowerRun or NSudo that makes the files locked, they just give you the ability to remove system file permissions to lock them in 1809 and later.

Once the files have been locked (by whatever means), no update can restore the permissions—i.e. unlock the files. Have I understood correctly? Sorry for my poor English comprehension.

Matthew Wai said:

Once the files have been locked (by whatever means), no update can restore the permissions—i.e. unlock the files. Have I understood correctly? Sorry for my poor English comprehension.

Correct. Removing permissions from system files (by whatever means) locks them and Windows cannot read them, execute them or overwrite them, repair or restore them. They are effectively locked permanently. Updating, upgrading from iso, nothing can restore the default permissions back unless the owner of the file (whoever runs the uninstaller script), resets the permissions to default.
Funny story, I was talking to the author of NSudo and I told him I needed NSudo to hide command prompts. He wanted to know exactly what I meant so I showed him my script. I just expected him to look at it but he ran it! He was freaking out because a bunch of his system files were locked and he was about to do a restore from backup. I gave him the uninstaller script and it repaired the locked files. He told me I was playing with fire, and I told him that I know what I'm doing. He got pretty mad at me at first but we're friends now.

Sorry about the continual questions but this has me stumped. I get a notification asking me if I want to run the mini update tool so I click yes. It runs and says that it has succeeded in finding one update but nothing shows up in the screen. What am I missing please?

@Pedro147 I think you should specify that you're using @Matthew Wai's fork of the script when you're asking for assistance to eliminate any confusion.

Sorry about that @pf100 I you will try and remember that in the future.

I obviously wrongly assumed that Matthew's was just preferences, albeit unknown to me what the nature of these were, of your script.

I was not meaning to be rude to you and I once again thank you for this excellent work.

EDIT - Just re reading the first posts and I find it quite confusing as to the real origins of this script. Now there is no doubt that the work is by @pf100 but the OP @EdTittel references MajorGeeks but then later someone else rightly points out that the author is pf100. If this were my thread I would definitely want there to no be ambiguity about the origins of this fine work that has been done to tidy up Microsofts sloppy implementation. I also note that Ed did point out to me that pf100 was the author in one of his later replies to me which I thank him for.

Pedro147 said:

Sorry about the continual questions

Feel free to ask as many questions as you please.
Note that the "Check_for_updates.vbs" file was not written by pf100.
Please run the "# Show_update_titles.vbs" file in this zipped file and post a screenshot of the result showing the update title. Also specify what updates have been hidden via Windows Update MiniTool. There are times when my VBScript and WUMT get different results.

pf100 said:

@Pedro147 I think you should specify that you're using @Matthew Wai's fork of the script when you're asking for assistance to eliminate any confusion.

He is innocent because he does not know which part of the script was created by you and which was by me. BTW, have you taken a look at "Check_for_updates.vbs"?

EdTittel said:

@pf100: To get to know you, is to become friends with you, Gary.

Shamefully, some hate me after getting to know me.