New
#181
Oops, my mistake. You weren't talking to me and were using @Matthew Wai's changes. Ignore what I told you before then.
Stop Windows 10 Updates Properly and Completely
-
-
New #182
As pf100 said above, he was talking about his Wrapper Script, which is different from Matthew's VBScript.
Yes, you will be notified. A dialog box will pop up. If you select "Yes", Windows Update MiniTool will be run, and you can decide what to do.
Yes, Windows Defender will get a definition update every day according to the scheduled task. I can add another task so that definition updates will be performed as frequently as you want, e.g. every 6 hours.
Last edited by Matthew Wai; 17 Nov 2018 at 07:58.
-
New #183
Deselect it after selecting "Automatic Update". See the screenshot shown in the post below:
Something BETTER than WUMT: Meet WUMgr!! - Windows 10 Forums
The zipped file contains wumt_x64. Is your Windows 64-bit? If not, I have to replace wumt_x64 with wumt_x86.
-
New #184
-
New #185
-
New #186
I have added something to the scripts, so please click here to download the zipped file again.
The correct version of WUMT will be used whether your Windows is 32-bit or 64-bit.
If you want to undo the changes made by the scripts, run "Undo everything".
If you want to re-install Update Assistant, click here.
Note that "Disable hijackers" was plagiarized from pf100's Wrapper Script. However, if you run Wrapper Script, my VBScript cannot be run because the former will disable the "Windows Update" service.
Feel free to ask as many questions as you want.Last edited by Matthew Wai; 29 Nov 2018 at 07:43.
-
New #187
-
New #188
Do you think stopping updates constitutes a breach of the license mentioned below?
A post on another forum.
-
-
New #189
That's an excellent question, but they will never be able to enforce that. They've breached their own contract after breaking some systems through forced updates. Some examples are:
1) The disastrous, for some, update to 1809 which deleted their user profile or documents or other folders.
2) Owners of Clover Trail processors who were on 1607, where a forced 3GB Windows Update kept trying to update them to 1703 only to find the message that "this app is not compatible" where the "app" was 1703, so they had to roll back to 1607. Then it kept trying to force them onto 1703 again. Over and over again. That problem has since been fixed by Microsoft, but it was hell for those users when it first started happening
3) The June 2018 update for .NET Framework 4.7.2 is installed on the computer, and the Azure AD Connect Health for Sync monitoring agent does not fully support this update.
4) 1803 CU KB4103721 "bricked" some systems and the only solution was to roll back.
5) The uproar over forced updates causing so many problems that Susan Bradly wrote an open letter to Microsoft.
I'm leaving out lots more examples but the common theme here is that the Windows Update process needs to be more controlled. Microsoft by now is fully aware of the need by a rather large percentage of users and system administrators to be able to have more control of updates, and that users are having to devise their own methods of controlling updates. You, me, and many others are being forced to do this.
*********************
Also, I like what you're doing by using parts of the wrapper script with your own code to do things differently than what I'm doing. Have you considered making your project public? Because if you think it would be useful, you should. I wrote the wrapper script for myself after studying ideas and code I found on the net, just like what you're doing. Others saw my script and asked me to make it public, just like I'm asking you. And as I might have mentioned before, you're welcome to use any parts of the script you find useful in controlling updates. I don't care if you use 90% or all of the wrapper script, changing it, adding your own code, and making it your own project. Open source all the way!
I think it's something you should consider.
-
Quote
Related Discussions
