Thank you pf100. You mentioned something about setting 'wub_task" to Trigger at Log in, I think maybe that is a good idea. Personally, when I am done using computer for awhile, I click Start - Power - Shutdown. Rarely do I click "Restart". What with Microsoft trying to send out 3 Cumulative Updates a month, and their "Reboot / Restart" - I got in the habit of just clicking Shutdown. So, Triggering 'wub_task' to run at Log in sounds like a good idea. Also, I want to thank you for the link to Core Technologies Consultants "Service Tray" utility to indicate when Windows Update is Enabled / Disabled, big thanks to Whistler4 also, for bringing this to our attention. I will download 'Service Tray' utility and experiment with it, and report back later. Gotta go now, thanks.
But keep a task to trigger WUB at startup. Windows update service will update before any logins, as we all know.
A task can have many triggers : one trigger for startup AND one trigger for login. After line 298 of WUMTWrapperScript.cmd 2.4.7 (i.e. betwween echo ^</BootTrigger^> and echo ^</Triggers^> ), add : Code: echo ^<LogonTrigger^> echo ^<Enabled^>true^</Enabled^> echo ^</LogonTrigger^>
I am just listing some notes to think about, I installed the Service Tray utility from Core Technologies about an hour ago, and it is very nice. I have Win10 1709.522 on a HP EliteBook 8570w laptop, and mostly use Wi-Fi for internet. I have the Wi-Fi set to be 'Disconnected' until I tell it to Connect. With the Service Tray icon showing in the 'System Tray' / Notification Area, my computer color is Orange instead of Red when Windows Update is Off. This morning when starting computer from the "Fast Start" Hibernation mode, WU was Disabled, I ran the Wrapper Script yesterday. The Service Tray icon was Orange/red meaning Windows Update was Off, - Here is the interesting part: = when I clicked the Wi-Fi icon in System Tray near clock, once I told it to "Connect", the Service Tray WU icon turned Green, with an official Notification that the Windows Update service has started. - So, Windows knows to turn on the Update service when first connecting to internet. Sneaky devils. I ran the WUMP Wrapper Script and the first window after initalization said the WU service was Enabled and Running, yikes. It only happened after first start of computer in morning and first connect to internet with Wi-Fi. Not sure about Ethernet. I will report back after more experimentaion. Thanks all.
Hi @rpo. I'm going to update the task in the next release and increase the windows defender update check frequency from 4 hours to 2 hours plus some other things suggested. I just haven't had time to get to it yet. Hopefully tomorrow.
July 30, 2018 WUMT Wrapper Script 2.4.8 Changelog from version 2.4.7 Windows Defender Updates frequency changed to every 2 hours from 4 hours. wub_task now forces off the update service at login as well as on reboot. Thanks @rpo, @Lars220, and @Whistler4
I agree that for the tray indicator, simpler is better. I haven't used it for anything but notification of status, not even to stop the service. You gave a good explanation of the behavior of WUS and how it runs and stops automatically. I have ServiceTray installed on one computer that, so far, has enjoyed every Windows 10 update that's been thrown at it, so I haven't bothered to use WUMT or your script on it yet. On that computer, I'm often seeing the ServiceTray icon go from green to orange to red and back. Thanks, that's good to know. I'll start using WUB 1.0 exclusively, then.
I'll bet that's fun to watch. I can see a time when I might need WUB 1.1. Wub.ini would have to be specially crafted. It definitely has potential and I'll be testing with it to disable things. But, yeah, I'll probably switch to WUB 1.1 when I can leverage its usefulness. I rule nothing out. If it can help keep updates manual only, well, that's the whole point isn't it.
I was wondering why cumulative updates weren't showing up. I think they would mostly be desirable. My main concern is to block feature updates and the other updates that facilitate unhiding of feature updates ("hijackers") for computers that have a problem with them. For clarification, once the real Windows Update has detected a CU, WUMT will also detect it and install it? The big risk, though, is that when you go to get a cup of coffee, Windows Update will do more damage than you expect while enabled, am I right? I still don't understand 100% all the interactions. When the script has WUS enabled and as long as WUMT is running, it appears that Windows Update does not (cannot?) perform any detections or downloads. I've seen some apparent misinformation posted at AskWoody saying that WUMT hides updates only from the user, not Windows Update. I don't think that's correct, but I have seen updates previously hidden with WUMT be made available again, and I suspect that's because of new update facilitators. (Since I've been running your script, I think hidden have stayed hidden so far.) It's difficult to know what future updates are going to try to force feature updates until people start posting their experiences and knowledge of them. So this all appears to be a running gun battle requiring lots of staying on top of the situation with continual modifications of what to block.
Kudos with a capital K for both Whistler4 and pf100 for great research and posting links. Did not know about Session 0, that is why I like this forum. Learning is a lifetime event. Thank you for the great education! Keep up the good work. Thanks.
If suggestions, ideas, and requests are allowed, I have some ideas concerning the 2.4.7 Uninstaller pages:
Good suggestions, but concerning disconnecting from internet, that's why I have WUB (1.0) pinned to the taskbar (therefore, a copy located separately in its own folder) so I can disable WUS immediately on uninstalling the wrapper script - similar protection functionality in between script versions. A minor complication is that both methods require additional non-script action by user. But the wrapper script is basically a great product.