try with this file reg
it should unlock system updates if you don't have antivirus in your system to support the spectre e meltdown bugsCode:https://tinyurl.com/y9apfppa
if you have only windows defender windows has block the security updates
for info check this link
[it is also valid for windows 7 and 8.1]Code:https://support.microsoft.com/en-us/help/4072699/windows-security-updates-and-antivirus-software
Actually, I receive no notification from Windows Update MiniTool.
I do receive notification from my VBScript.
I think having it set to "Notification mode" does something behind the scenes in Windows to stop updates from happening automatically, but I don't know what specifically it does. I mention it because it could be making you think that the UsoClient hack is still working on your machine, when, in reality, WUMT is what's keeping updates from getting automatically installed. Just a hunch. Otherwise, I can't explain why my machine automatically updated itself while having applied the UsoClient hack.
I think the "Notification mode" does nothing on my Home Edition. I have just set "Automatic Updates" to "Automatically" as shown below. Let's see what will happen tomorrow.
In reality, besides the "UsoClient" hack, I have been using the following registry hack:
How to prevent downloading updates? - Windows 10 Forums
Last edited by Matthew Wai; 21 Mar 2018 at 08:21.
Thanks for testing this. Make sure to restart the system at some point, too! I look forward to seeing what happens. One additional thing that has me thinking WUMT does some different things behind the scenes is that the Windows Update settings panel starts showing "some settings are managed by your system administrator" once WUMT has been modified and I haven't figured out a way to bring that back to normal, even after setting WUMT back to what I thought were the defaults. I've looked at the settings in Group Policy Management, setting them all back to their defaults, but I was still left with "some settings are managed by your system administrator".
It is metered connection that has prevented Windows Update from downloading updates according to the following screenshot:
Actually, I have already manually downloaded KB890830 (Malicious Software Removal Tool).
Yeah, that would make sense, too, though people have said that even that hasn't been enough recently, but maybe your metered connection tweak has an additional piece to it that others weren't using?
That's because WUMT takes care of update checks and the Windows Update message relates to the last time an actual check was made by "Windows Updates" which I think you have disabled by running WUMT. Anyway if you didn't update WUMT then you should delete the old version and download the new one and run the configurator script before running Windows Update MiniTool.cmd
You would normally choose Y as default but when installing updates that require a reboot you must choose N in order to leave windows update service enabled on reboot so that the install can complete. Once completed you can run configurator script again choosing Y
Reason: When you close WUMT window it automatically disables update service but if installing updates it's required to be left running.
From the help file:
RE:How it works:This script auto-elevates, renames the %programfiles%\rempl folder disabling remsh.exe, resets and removes permissions from and disables UsoClient.exe, WaaSMedic.exe, and SIHClient.exe, makes sure the task "wub_task" is installed that runs wub at boot (to stop updates from turning updates back on), *runs wub and enables and starts the windows update service (wuauserv) if disabled (*wub can be disabled using the included WUMTWrapperScriptConfigurator.cmd script, leaving Windows Updates always running), then runs the correct version of the Windows Update MiniTool in "auto search for updates" mode for your OS version's architecture (x86 or x64), then disables and stops wuauserv giving you full control. No more forced automatic updates or surprise reboots. This was written for Windows 10 Pro and Home, but works with all versions of Windows 10. (Recent changes not tested on versions earlier than 10). Don't change any settings in WUMT while running the script.
That's because you didn't leave WU service running when installing an update that requires a reboot.
RE:
Delete these registry subkeys (if they exist) and reboot.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
additionally on a 64bit machine delete:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\WindowsUpdate\AU
Only delete the AU subkeys.
Quote
