Ha - I misunderstood you, thinking that you were proposing locking the program folder then deleting the files. (And having a program folder with no files could cause the program to be uninstallable after the script was uninstalled and the folder unlocked.) But you meant "deleting the files" to refer to the current method. So I have no issues at all with the proposal, because the locked anomaly would be fully explained by the script action and fully reversible. And then I wasn't clear enough in my statement, because I meant to lock the original program folder, not the .old copy, thus preventing reinstallation by MS. (Ignore "delete as proposed" since I misunderstood as noted above -- which was the whole reason for making a copy, to restore the files to be able to uninstall it if you were deleting the originals. And round and round. Sorry.) Sounds like maybe the creation of relevant Update Assistant folders when they don't exist and then locking them to prevent MS reinstalling in the future might have merit, though. Bottom line: Don't worry about people freaking out. Explain it just like the SFC errors. And it's fully reversible when the uninstaller undoes the script effects.
I heard of this happening once about a year ago. WUMT itself doesn't behave any differently in my script as it does by itself without the script. I just include this statement for the chance an update could be installed next time if it's not hidden first. It's not likely to happen, but if there's a chance it can I'm going to mention it. And besides that, I think it's just good practice to either hide or install any offered updates. And as far as a way to stop auto installing an update without hiding it first, I really don't know. That is a question that could be better answered in the WUMT thread.
@Lars220 I'm dropping support for anything but Windows 10 in the script starting with v2.5.3. I really don't have time to keep up with what's going on with Windows 7, 8 and 8.1 and I think allowing the script to run with anything but Windows 10 just gives a false sense of security. I would recommend using abbodi's script with Windows 7. Windows 8 and 8.1 I have no idea anymore. And v2.5.3 will definitely be posted at Major Geeks, and is out of beta, and is ready now. I just have to update the documentation for it.
OK, understood, makes sense, thanks for informing all of us here. I will give the abbodi script a try, and attempt to keep the GWX Control Panel up to date if possible. I have no problems with my Win 10 computer updates thanks to the Wrapper Script. I think that I read a post at Ask Woody about someone using Steve Gibson's "Never 10" along with GWX Control Panle. Belt and suspenders type of hopeful 'Safety' (?) I appreciate your and Whistler4 work on the ver 2.5.3. script window arrangements, good job!
I've just been informed that this is only an issue in a VM, which was how I was running RS5. Either way, the script will work in a VM or a bare metal install of RS5.
I don't mean to get too far into the weeds, but why would file permissions be able to be successfully set for a physical machine but not a VM?
That's a great question, and is one I don't know the answer to. This is the first time it happened to me. Edit: I will say I'm glad it happened, because the script will now rename the update hijacker files if it can't lock them. It'll work in more scenarios. And the uninstaller has been edited to handle either situation too. Edit 2: I'm preparing to release this version by tomorrow sometime give or take a day or two. Still working on documentation, and I need to send screenshots and other info to Major Geeks and Softpedia.
September 28, 2018 WUMT Wrapper Script 2.5.3 -Supports Windows 10 1809 -Script now only supports Windows 10. -Windows Update Service is disabled after running script and closing WUMT no matter how you set the Update Service in Configurator. -Lots of cosmetic improvements. Screen doesn't change size or flicker. -Numerous code improvements with extensive testing and error checking. -In addition to supporting English, Western European, and Latin language script path, script now provides helpful error message in case of tasks creation error in unsupported path. -WDU (Windows Defender Update) and wub_task tasks are now created before first screen. -WDU task now shows correct last run error code. -Changed Windows Defender update frequency to every six hours. -Added 5 minute delay to WDU (Windows Defender Update) task to minimize resource hogging after reboot with missed Windows Defender update. -All Windows Update tasks are now disabled. -Added FAQ to readme -As always, uninstaller undoes all script changes. -At bottom of script, you can edit it to use WuMgr (Windows Update Manager) instead of WUMT if you want. I haven't fully tested this, so you're on your own if you do this. Huge thanks to @rpo for the input, ideas, and code help with this version. Thanks to @Whistler4 for making an almost complete FAQ, @maka213 for suggesting creating tasks before first screen, @Lars220 and @ShiningDog for some good ideas (sorry, the bin folder idea didn't make it into this version but I haven't forgotten).
Love your work, works great. Just one question WUMT only shows this update KB4457128 not the recent one KB4458469 maybe its because I only have KB4343909 installed However I thought Microsoft's latest release's incorporates past released updates no matter what version you have and just updates in the package what's missing. Hence I thought WUMT would just show the latest release KB4458469 maybe I'm wrong Cheers
UUP fetch offers this for 1803: Code: 19:44:43 FETCH 17134.320 CU/SSU for amd64 19:44:43 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:44:45 Found: windows10.0-kb4456655-x64.cab 19:44:45 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 19:44:45 Found: windows10.0-kb4458469-v2-x64.cab 19:44:45 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Yes, and why it's not showing up for some people I have no idea. Personally, I'm just going to wait until it's offered. There's too much Patch weirdness going on right now. Day Date 1607 1703 1709 1803 Thursday 9/20/2018 KB4457127 KB4457141 KB4457136 KB4458469 Monday 9/17/2018 KB4464217 KB4464218 Tuesday 9/11/2018 KB4457131 KB4457138 KB4457142 KB4457128