Stop Windows 10 Updates Properly and Completely

pf100 said:

I don't have access after clicking continue.

But I do. See below.

pf100 said:

Try my script without your modifications and tell me what happens.

I ran your script without my modifications, and the following has happened.

Download WUMT Wrapper Script 2.5.5

I downloaded the above zipped file, extracted all files, and ran "WUMTWrapperScript.cmd" without any modifications. The results are shown in the screenshot in my post #291 above.

Why are you clicking continue to get access when you're trying to prevent access? I still don't know what version of Windows 10 you're doing this on, but in 18309.1000 this is what happens if I click continue.

pf100 said:

Why are you clicking continue to get access when you're trying to prevent access?

For testing only. If I can get access, a hijacker may get it too.

pf100 said:

I still don't know what version of Windows 10 you're doing this on, but in 18309.1000 this is what happens if I click continue.

My Windows is Version 1809 (OS Build 17763.107) in Oracle VM VirtualBox 5.2.20. I can create a new file after clicking on "Continue".

pf100 said:

Code:

%nsudovar% -ShowWindowMode:Hide -Wait -U:T -P:E "%systemroot%\System32\icacls.exe" %systemroot%\UpdateAssistant /inheritance:r /remove:g *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1
%nsudovar% -ShowWindowMode:Hide -Wait -U:T -P:E "%systemroot%\System32\icacls.exe" %systemroot%\UpdateAssistantV2 /inheritance:r /remove:g *S-1-5-32-544 *S-1-5-11 *S-1-5-32-545 *S-1-5-18 >nul 2>&1

I don't know whether the following "SID" is relevant.

Matthew Wai said:

If I can get access, a hijacker may get it too.

I don't see how it could.
The way to be sure is to run the script to lock the folders, then try to install update assistant from here.

I dare not install it. I did the following tests instead.
Before clicking on "Continue", I got the following:

Code:

C:\Windows\system32>Copy "C:\Testing.rtf" "%systemroot%\UpdateAssistant\"
Access is denied.        
0 file(s) copied.

Access was denied even if the command was run via PowerRun v1.3.

After clicking on "Continue", I got the following:

Code:

C:\Windows\system32>Copy "C:\Testing.rtf" "%systemroot%\UpdateAssistant\"        
1 file(s) copied.

I assume that no one can access it as long as no one clicks on "Continue".

[QUOTE=Matthew Wai;1568841I assume that no one can access it as long as no one clicks on "Continue".[/QUOTE]
Correct. I installed Windows Update Assistant in my VM. It threw an error because it couldn't write to the UpdateAssistant(V2) folders, but it created the %systemdrive%\Windows10Upgrade folder and ran anyway. The %systemroot\UpdateAssistant(V2) folders are where updates create files that installs Update Assistant, but blocking them doesn't prevent you from manually downloading and installing Windows Update Assistant. So your observations just made the script better. Thanks, buddy. The next version will make a blocked %systemdrive%\Windows10Upgrade folder.

The first two screenshots below is from trying to install Update Assistant manually. The %systemroot\UpdateAssistant(V2) folders were blocked, but it ran from the %systemdrive%\Windows10Upgrade folder anyway.





If I create a blocked %systemdrive%\Windows10Upgrade folder you can't even manually install it as shown in the screenshot below.



So, thanks again. The improvements will be in the next version 2.5.7

I wonder why an update can be found when access is denied.
I have never clicked on the "Check for updates" button.

Matthew Wai Maybe because of your modifications allowing notifications? There's no other way that I know of to allow notifications without checking for updates first. Run the script and hide the 1809 update. I've gotten no reports of this happening with the unmodified script. It's definitely never happened to me.