On line 348 of "WUMTWrapperScript.cmd" you can change the number in "PT6H" (if you're editing with notepad just search for "PT6H") that checks for updates every 6 hours. So if you want it to check for defender updates every hour, change it to "PT1H", every 24 hours "PT24H", etc. About a year ago, the script had an option to choose the defender update frequency (see below edit) but it just confused people, so I just settled for every 6 hours. By default without the script, I believe Defender checks for updates every 24 hours. Edit: it wasn't update frequency but time to start. It made no sense to tell it when to start, so I just made it start at 12:01 a.m.
So, I changed the "PT6H" to "PT1H" and I'm not sure, but seems nothing has changed. After the change I left the laptop running now for about five hours. As you can see by the screen shots, if I run the script it does in fact find the Defender update, but I thought that it would install those Defender updates automatically in the background. Am I misunderstanding how its suppose to run, it is it just not doing what its suppose to be doing. Thanks for working on this with me.
Just a follow up to the above, decided to check Event Viewer and I have a couple of these errors that I have not seen before: The WaaSMedicSvc service terminated with the following error: Access is denied.
I'll post three images of items in my Task Scheduler that look like they pertain to the script. The one I don't see in your image is the WuMgrNoUAC. Edit: Just took a closer look (very early, no coffee yet!) and WuMgrNoUAC is a leftover from when I had WUMgr 0.9b installed. I'll just delete that entry.
It looks like something you've done separately with Windows Update Manager (WuMgr) may be blocking the defender updates. You need to undo whatever that is. The script calls WuMgr with the "-provisioned" switch with all the options greyed out when it runs just so you can't break anything. What I was looking for is out of sight to the right of your pics under "last run result" that shows whether the operation completed successfully or not along with the error code (0x0), or (0x1), etc. You don't have to post a pic if it'll make it easier, you can just tell me what it says. But I already know what it's going to say, (0x1).
@Homer712, the task hasn't run yet. Right click the WDU task, click "run", wait 5 minutes for the task to finish. (You'll have to refresh with F5 because the window doesn't auto refresh.) And tell me what the resulting error code is.
Success!!! I originally booted the laptop very early this morning and checked to see if any Defender updates were done by running the script. Yesterday I was stuck at 123 updates and no Defender updates since the 29th. The image shows that a Defender update was installed sometime before 5:33 AM. When I followed your instructions to run the WDU task, it again succeeded sometime before 8:16 AM and is scheduled to run again at 9:01 AM. So, thank you, everything seems to be up and running as per the script.
Well, thought we had it, but no. Ran the script a little after 11:00 AM to see if there were any Defender updates. There was one. Quit without installing to see if the script would pick it up and install it on the next run, noon. Nope, it ran but nothing was installed and the next run is scheduled for 1:00 PM. At a loss but will help in any way you may want me to "experiment."
Just noticed that both WDU and Wub_task are configured for Windows Vista and Windows Server 2008. I'm on Windows Home 1809, would that make any difference?
When you run the script, it deletes and re-creates the wub_task and WDU tasks and resets the start time. The WDU tasks in your screenshots have just been created and haven't run yet. So are you saying that the WDU task never runs? Or are you saying that the WDU tasks runs and fails? Because it has to be one or the other. Wait at least 5 minutes after the WDU task's next scheduled run time without running the script and then tell me what the WDU task does or doesn't do, along with the error code. It's supposed to be a Vista/Server 2008 task. It has no effect except to allow it to run on Windows 7/8/10. I could change it to be a Windows 10 task, but I know of someone who helped me with a lot of code with the script who modifies the script to use it on Windows 7 and i want to allow that if someone knows what they're doing. The script checks if you're running Windows 10, and if not it exits. But no, that has no effect. I use the script on all of my windows 10 installs and it works fine. If it turns out that the WDU task won't run, something has been modified on your system that's preventing it from running. The WDU task runs the file WDU.cmd in the wrapper script folder which you can't run directly because it checks to see if you're running as system (you aren't), but the task does run it as system. But if there was a problem with WDU.cmd then the task would give an error code of (0x1).
Will do. Also, I have O&O ShutUp 10 installed. If you're familiar with that program (seems almost a silly question) I could post screen shots of my settings (basically, whatever they have as "recommended", nothing I would select on my own) to see if something there jumps out at you. Just a thought.
I use ShutUp10 too and none of its settings interferes with the script in any way. What I do suspect is if you you made a bunch of changes with WuMgr as a standalone program that affected the operation of the script. The way I use WuMgr in the script it can't hurt anything, but using WuMgr by itself and changing a bunch of options with it without knowing the repercussions could possibly break stuff. I'm not sure because I don't push the options of WuMgr to its limits. Also, I don't know if you've seen the current update problems caused by DNS issues with Comcast (an internet provider). It could possibly be that. But we'll know more when you wait until the WDU task's next scheduled run time result.