Really? So it seems it doesn't intercepts the system call anymore? Damn! Perhaps @Painter7 is working on a fix now.
I have tried Windows Update Blocker instead and found that it works and also protects the Windows Update service from being re-enabled from even shutting down and re-booting. Give it a go everyone and hopefully if it works for everyone and it can be incorporated into the script. By the way its usage in text form is below. Usage: <command> Commands: /E : Enable Windows Update Service /D : Disable Windows Update Service /P : Protect Windows Update Service Samples: Wub.exe /E Wub.exe /D Wub.exe /D /P
It seems to protect the status of the Windows Update Service from being altered. So if it set to Disabled then somehow no process can alter this not even the Operating system itself. Don't quite understand how it does this. It could be something to do with permissions. Not sure though. The author does not explain. But no trace on the pc remains according to the author when it is removed. The tool is also completely portable.
Thanks for the help and glad to have been part of finding a solution that vexed many of us. Cheers, The Fly.
@pf100 : My last constribution here : https://forums.mydigitallife.net/th...pite-being-disabled.75779/page-4#post-1393938
I would suggest replacing : %~dp0wub.exe /e /p by : "%~dp0wub.exe" /e /p at line 75 since this statement fails if the path to the script contains space(s). Edit : forget since statement 3 specifies : "No spaces in Folder name! ex: C:\WindowsUpdate"
I have to start WUB manually and enable services to get it working. Edit: There doesn't seem to be a problem when I run it directly from my desktop.
Did you try running it from C:\WindowsUpdate? Edit: Try the edited script in the first post and see if it fixes it.
I can run it from C:\ but not from D:\ Can't get the script working but no big deal. It's working from C and that's great. Thanks a lot for your work.