New
#121
My WUMT did not show that KB4023814 denoted Update Assistant, which subsequently installed version 1803 automatically.
My WUMT did not show that KB4023814 denoted Update Assistant, which subsequently installed version 1803 automatically.
Did you run the script to the first screen after you updated? It should have removed Update Assistant if you did.
Also, does anyone have any idea why I'm not getting email notifications from this thread anymore?!? I would have helped you sooner if I'd seen your post earlier @Matthew Wai.
Also, new release.
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. (previously "Automatic App Update" task was left on)
-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. WuMgr github link.
Last edited by pf100; 29 Sep 2018 at 08:44.
Does "the script" refer to "WUMTWrapperScript.cmd"? Do you mean running it immediately after installing KB4023814 should have removed Update Assistant? I did not see any "first screen" after installing KB4023814.
I did receive email notification of your reply hours ago. I have subscribed to this thread.
I should have said, re-run "WUMTWrapperScript.cmd" to the first screen after you updated and closed WUMT and/or rebooted. The script deletes the folders "%systemroot%\UpdateAssistant" and "%systemroot%\UpdateAssistantV2" before the first screen appears every time it runs which are the folder(s) that start the chain reaction that installs "%systemdrive%\Windows10Upgrade" and at that point it's game over. I recently posed a question at MDL about instead of deleting those folders, to lock them instead, and if they don't exist, to create and lock them, which would have prevented you getting updated to 1803, and you wouldn't have needed to re-run the script again after updating. The only downside to that is people might freak out if they see "C:\Windows10Upgrade" in their root folder and not be able to delete it, and you wouldn't be able to uninstall Update Assistant from Control Panel if it's really installed. The only way you'd be able to delete it is to uninstall the script. But the upside is it would prevent Update Assistant from ever being installed and/or run. I think for the next version I will lock/create and lock, those folders with a big warning, "This script makes your PC to appear to have Update Assistant installed, and it may be, but it can't run!" Would you be okay with that, because it would finally fix the Update Assistant issue for good. I really hate that Update Assistant blind-sided you like that.
I've been subscribed to this thread since I discovered it. I got an email notification of your post this time and I think I see a pattern. Obviously, I'm not a regular here. So, it seems that if I post here, I get notifications for a few weeks and then they stop until I post again and then I get notifications for another couple of weeks, then they stop again. Could an admin look into that please?
Hi, notification emails end thus:
That said, occasionally I receive a few from the same thread without re-visiting it.There may also be other replies, but you will not receive any more notifications until you visit the forum again.
All the best,
Ten Forums Team
@Matthew Wai You getting hijacked by Update Assistant has convinced me to go ahead and create empty Update Assistant folders if they don't already exist, and then lock them so Update Assistant can't run. That feature will be in the next version of the script.
Thanks for your report, and my sincerest condolences.
Out of curiosity why do some users want to block 1803 so bad? I really liked the feature updates and overall UI enchantments that it brought. Updates messing with other applications?
It's not so much about blocking updates or upgrades as it is having control of what updates or upgrades you want, like Windows 7 used to be. To have control of updates in windows 10 you have to 1) first block Windows 10 forcing updates down your throat, and 2) have a method of selecting the updates you want. If you don't do number 1, you can't do number 2.
Some people need Windows Media center and that can only be installed on early versions of Windows 10, and an upgrade will kill it permanently.
Some people have a certain CPU or other hardware that won't work past a certain version of 10, even though Windows tries to upgrade anyway, effectively bricking your device until you do a clean reinstall of the last supported version, or do a rollback over and over again.
I literally could go on and on. The bottom line is that people have their reasons. In a perfect world everyone would be on the latest version, it's just that it doesn't work like that sometimes.