I just use the "Print Screen" key at top right of the keyboard, which copies a picture to the Clipboard, then I Paste into the Paint program and use Paint text editor to make my notes, then 'Save As' a jpg picture in the Pictures folder. Hope that helps.
pf100, I apologize in advance, I have again been 'exploring' around my Win 10 computer, and I think that I may have stumbled into the forbidden land of Ravenholm befuddlement (again). Have you had an opportunity to do any research on the 'fast startup' enabled situation with 'wub_task' ? I have been waiting for the Samsung 850 EVO SSD price to come down, but holding my breath is turning me blue. With an older HDD Hard Disk Drive, the 'fast startup' really does increase Startup times, but it is a 'Hibernate' type of function. Anyway, check out these pictures, I think a third 'wub_task' may be needed ? I meant to say fast startup shortens start times, not increases, fast startup is good for HDD, but not for Solid State Drives SSD. I do not understand the 'At log on' Trigger, it appears to me that using fast startup goes to the "Lock Screen" when I start the computer, and I have to type in my Password to get to the Desktop and use the computer. My question is: do you know if the 'Lock Screen' sign in is not the same as "log on" ? I do not know. When I get my SSD and use Macrium Reflect (Free version) to 'Clone' the HDD to SSD, then I guess all my concerns about 'fast startup' will disappear ! yay !
I reckon you know this, but the User Accounts Wizard is where you change the setting to bypass the logon screen if you trust the security of physical location of your computer - good for HTPCs, for example. If you set it to automatically enter your password, you will no longer have the issue of whether the lock screen comes up (assuming you don't want it to). It's not as easy to find since XP, so I keep a shortcut in my "+ Utilities" folder in All Programs of the Start Menu (I'm a StartIsBack fan) where I have all my favorite or frequently used utilities: C:\Windows\System32\Netplwiz.exe. (Sorry if I'm cluttering up the main topic of this forum.)
Thank you Whistler4, but with me, take nothing for granted, I am still learning, a lot. It appears to me that the 'log on' is not the same as the 'Lock Screen' sign in. and I like the Lock Screen with sign in, I have it set that if I am away from computer for 5 minutes, it goes to Lock Screen, and then must sign in with password to continue. Cheers.
@Lars220 When the system starts up, it is possible that WU is still disabled. The reboot should not change the state of WU (before shutdown it is normaly disabled. Hence there is no contradiction with the state of WU and the fact that the scheduled task has not yet started. The logon trigger was introduced to ensure the WU is still disabled to prevent an eventual activation by Windows. Other additional triggers could be considered (rescheduling the task afer a specified time interval, etc..). @pf100 sorry i didn't see your post (i was preparing the mine).
Thank you pf100 and rpo. I have an SSD on order and coming shortly, hopefully by next Wednesday. I look forward to playing with Macrium Reflect Free and Cloning this HDD to SSD. Been reading all about that. I am not concerned anymore with the 'fast startup' issue that I have been mentioning. New toy coming, old problems dropped. Thank you for your compliments and replies.
I recommend that you should disable Fast Startup feature and restrict Hibernate using to increase your SSD lifespan.
August 20, 2018 WUMT Wrapper Script 2.5.0 Fixed condition where if Windows Defender update task (WDU) ran while performing updates with WUMT, it would disable the Windows Update service stopping the update.
When I press any key to run Windows Update Minitool it takes ages to launch only has happened in the latest version 2.5.0 Thanks
Thanks for your report. In 2.5.0, I added a powershell command just before WUMT runs in an attempt to help detect updates better and that's what's slowing down WUMT starting. The resulting slow starting of WUMT isn't worth any advantage gained by the powershell command so I'll remove it in 2.5.1. In the meantime you can edit "WUMTWrapperScript.cmd" to remove line 278 which is: Code: PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow() >nul 2>&1 or just search for powershell in the file and you'll find it that way too, then delete that command. Let me know if that fixes the problem.
It's not your OS, it's definitely the powershell command in the script making WUMT take a long time to open. I have 2.5.1 that I'm about to release to fix this issue. Thanks guys for your feedback.
Thanks @s1ave77. I would pursue speeding up the powershell command, but in this case it's not really helping anyway.