s1ave77, what are the windows update related scheduled tasks and also windows update related services?
July 25, 2018 WUMT Wrapper Script 2.4.6 Changelog from version 2.4.5 Fixed store problems. Thanks @jmdbox Uninstall previous version before installing this one.
Task Scheduler/Library/Microsoft/Windows/Windows Update EDIT: Service is wuauserv only i disable and since there are no other triggers it stays disabled so far.
Just the 1 task then, i didnt know if there were others, thanks . Is that really a dog in a balaclava?
Either that, or limp along until LTSC and do a clean install of that. It's my gaming computer, so a repair install would probably wreak havoc on the games. Better to leave it alone for now. It's working okay. I think I know what happened to it (using two privacy utilities) and I won't do it again. You should see a vet immediately
It's not a public project and so far only available via my JATD tool. In JATD main menu (X) and (2), path to work folder is optional, pressing Enter will use the \files\ sub folder of the tool, work path can be changed in the WU TOOl likewise. In WU TOOL i use mostly (U) then (R) to get all available info, some Flash and other Updates are listed for all supported Windows versions.
July 26, 2018 WUMT Wrapper Script 2.4.7 Changelog from version 2.4.6 Had error in uninstaller that unnecessarily enabled "\Microsoft\Windows\WindowsUpdate\Scheduled Start" task. Not a big deal but is now fixed. Now the script disables and locks all "\Microsoft\Windows\WindowsUpdate\" tasks thanks to a remark made by @s1ave77 plus I was already thinking of doing it. The uninstaller unlocks the tasks, but leaves them disabled. You can enable them manually if you want to unless they turn themselves back on first. This is absolutely all I can do to help those who choose to leave the windows update service running in the script to use the Store. The Store and Windows Update are so tied together that you can't have one without the other so I've come up with the best compromise I can without harming the operation of the store or allowing unwanted updates. This is the best version ever. I hope.
"\Microsoft\Windows\WindowsUpdate\Automatic App Update" task runs %SystemRoot%\System32\wuautoappupdate.dll. So I'm wondering if that'll hurt any Pro or Home users if it's disabled since no auto app updates...? We'll find out because I disabled it. Updates should work from the store, but not through automatic updates, and since that's disabled anyway I see no problem.
Just checking in, I am using the latest version 2.4.7 on Windows 10 Pro version 1709 build 16299.522 back from around June 21, or thereabouts. I had just downloaded todays definition update for old Malwarebytes Free version 2.2.1.1043 and ran a scan and Windows crashed with Blue Screen, but recovered quickly with a full Restart. I have IT Samples Network Activity Indicator and it immediately took off downloading something, so I unplugged the Ethernet cable to stop internet activity. I checked Services.msc and was surprised to see that the Windows Update service was enabled and set back to Automatic Delayed Start, Triggered Start. The WUMT Wrapper Script ver 2.4.7 had previously Disabled Windows Update, but Blue Screen Recovery turned it back on. I can not duplicate the Malwarebytes crash or the Blue Screen, but thought I would comment here about Windows Update getting turned back on. If the Wrapper Script disables WU, will a system restore re-enable it? Anyway, thanks for all your work on this great project.
A crash, system repair, system restore, or an update could turn the windows update service back on again. I've done what I can to keep it off and it stays off 99.9% of the time. The script creates "wub_task" that disables the update service after every reboot (I think I'll make it I run it at login too), and running the script disables the update service. But if the service somehow gets started at any other time it can't be force stopped until you notice it like you did and, a) you run the script, or b) reboot. I'm hoping this is a rare event and that it never happens to you again, but if it does please let me know and I'll do my best to work with you to fix it. I appreciate any input about the script because it makes it better. Thanks.
Thank you pf100 for your fast response and helpful explanation. I am a beginner / novice with Win 10 and probably caused the crash myself. And thinking about it, a system restore would probably re-set everything, so I paniced earlly, sorry. But now I have new info to report, I have the Win10 "Fast Start" enabled, so 'Shut Down' does not really shutdown, only puts computer into 'Hibernate' - writes status to disc, etc. Anyway, this morning on start up the Windows Update Service was running - Automatic (Delayed Start, Triggered Start). This is after yesterdays crash and I re-ran the Wrapper Script to Disable WU. As a side note, the Windows Defender definition updates are working ok. Right after starting computer this morning I checked Services.msc, re-ran the Script, and Win Defender did do its update when I connected to internet. I have some Screenshots of the Reliabilty Monitor Problem Reports, and a copy/paste wordpad text with Blue Screen 0.000 error codes, but not sure how to upload / attach, if you might request them. This morning after noticing WU on, re-running Script to turn it off, I did 'Shut Down' the computer again, then re-start to see if WU was still Disabled, and it was. So, maybe overnight something turned WU back on? I'll keep reporting in daily with reports of ON or Off WU just to let you know if this is rare.
I've never tested the script with fast start enabled since i use a NoFastStart script that makes a task that disables fast start on every machine I own. Maybe why I never noticed it. I'm going to try the script with fast start enabled and then turn it off and some other things to see if I can get the update service to turn on. And let me know what you find.
After 3 cups of coffee this AM, re-read pf100 recent posts, and I must thank you again, I enjoy learning from this MDL forum, I checked the 'Task Scheduler LIbrary' and found the 2 new Wrapper Script tasks, i.e. WDU = Windows Defender Updater, and the 'wub_task' = the 'wulb_task' had never been run !?! authors pf100/rpo, Triggers At system startup. If the Task Library says it has never been run, but after running the Script, Services.msc says WU is Disabled, I could not understand the task not running. So, I 'Restarted' the computer, (not 'Shutdown'), let things stabillize, and re-checked the Task Scheduler, and lo and behold, the 'wub_task' says that 'Last Run Time' 2018-07-27 8:05:26 AM, The operation completed successfully. (0x0). Sorta confusing to me, I guess the Script runs wub, then puts a task in scheduler, but it didn't schedule task run until today? I am not complaining about anything, I really like this Wrapper Script, I am just sharing some unusual (?) information.