@pf100, is this an easy-to-do suggestion? If you add the actual version number to the shortcut name "Version" in the Windows Start Menu for version.txt, a user wouldn't even have to click it to see it. For example, it would be very convenient to see the shortcut name "Version 2.6.0" after opening the Wrapper Script section of the Start Menu. (The user can rename the shortcut as I did below, but it would be better to have it built into the installer.)
Downloaded and installed. Working perfectly and the new additions are both welcome and informative. So far, working flawlessly. One small strange occurrence, no idea if it's connected or not. After installing and running (once, just to check things out) and then doing a restart, Windows tells me that my system is being updated. Lasts only a few seconds and once the reboot happens, I again get the system being updated message, again, few seconds. Running the script again and checking the updates history there are no notations of anything being changed and/or updated. Is there anything during the running of the script that would cause the system to think that an update/change has been performed?
No. I know what you're talking about but it has nothing to do with updates. If you haven't done any updates and the computer acts like it installed something during reboot/shutdown/etc, it could be a Windows Defender update (not definitions) or many other things. The log file for Windows Update is "%systemroot%\logs\cbs\cbs.log" and will tell you the last time an update was performed.
Overall, I like the interface. The AskWoody MS-DEFCON rating is value added except as I note below. Recommend you put the first use of "MS-Defcon" on the first screen in all caps for consistency. (I'd like to see a graph of the AskWoody MS-DEFCON rating trend since it was implemented. Do you think it's ever been "5" All clear? It's sort of like the Homeland Security threat colors: Never green, so it becomes background noise after a while. Still, it gives your script something a little extra.) It's very much faster -- Good job!
If everybody's okay with it, I'm going to release 2.6.0 in a few days after triple-checking everything and updating the documentation (the part I hate). Thanks for the input.
After seeing your post I thought I'd just give Task Scheduler a quick check and this is what I found. I started my laptop this morning about 6:30 AM and as of now, 8:25 AM no Defender updates have been installed. Any ideas?
@Homer712 I have to leave for a few hours but in the meantime google "0x800710E0". I see that" Wub_task" ran but "WDU" didn't, even though the only real difference between the two in this case is that WDU ran at startup, and Wub_task ran at startup and logon. I'll be back in a few hours and I'll do my best to help you figure it out. In the meantime, try running the WDU task manually to see if that works. Remember, there's a 5 minute delay between the task starting and it actually updating defender.
That means the WDU task is valid and you have permissions to run it. Can you add a new "at logon" trigger while leaving the existing triggers to the WDU task and give it 24 hours and let me know if that fixed it? This really makes no sense why this is happening to you. Anyway, let me know how it goes.
Will do. In the meantime, after the manual run I did a Restart and it seems to have gotten back on schedule without issue.
Adding "at logon" to the task worked perfectly this morning after power on. Of course I had to remember to add "at logon" back in again last night prior to shut down because every time you run the script it recreates the tasks and the "at logon" is again gone. Edit: pf100, I was able to add the "at logon" to your script successfully, so, unless you feel the need to add it for everyone, I'm okay with adding it myself to follow on scripts.
Unbelievably, your revised script and mine are identical. Does that now officially make me a programmer? Okay, maybe a junior, not quite officially but working at it programmer?
Sure, why not? If you can edit a script to make it work better, then that's programming. The only difference between you and I programming-wise is that I've been doing it longer. I'm not even that good of a programmer, I just keep trying different things until I get the results I want.