New
#241
I am using Home too, but Activity Center never notifies me of updates.
I am using Home too, but Activity Center never notifies me of updates.
Oh I see. Are you saying your Activity Center never shows new update notifications only from WUM or from all else?
For WUM, I enable only Manual Download/Install, Run in background (this depends on whether I want it or not for the period), Always run as Admin, and Disable Automatic Update.
For your reference: Action Center stopped working after 1809
December 30, 2018
WUMT Wrapper Script v2.5.5
SHA1 hash: 488f5e24609f0ef6f388cba334d9119b0e61f4e3
Version 2.5.5 supports 1809 and LTSC and is vastly improved from 2.5.4!
Uninstall 2.5.4 or any previous version before installing or running 2.5.5.
1) Script now includes WuMgr v0.9b along with WUMT giving you a choice of which to use in the menu.
2) Script now uses NSudo 6.1 instead of Powerrun (NSudo thread here) to lock update hijacker files. NSudo is faster and just works better.
3) Fixed accidental unicode in _readme.txt which caused strange characters to display in Oriental languages. (No, really, I fixed it this time!)
4) Script now in addition to uninstalling Windows 10 Update Assistant, creates and locks empty %systemroot%\UpdateAssistant and %systemroot%\UpdateAssistantV2 folders to stop Update Assistant from ever installing from an update. Now no need to run the script again after an update!
5) Fixed rare task creation error problem.
6) Not just some, but now all Update Hijacker folder and file permissions are now removed as TrustedInstaller as required by 1809.
7) Wrapper Script Start Menu folder now has a "Version" icon to easily see what version of the wrapper you have installed.
Script 2.5.6 1803 BSOD fix here
2.5.6 disables upfc.exe which BSOD's 1803. Uninstall it now and install 2.5.5
Due to new information about upfc.exe, I've pushed out an update just to disable it. More info about upfc.exe here.
December 31, 2018
WUMT Wrapper Script v2.5.6
SHA1 hash: 6f1063e6facb1d1a4e190d634d9873a9785b7cad
Version 2.5.6 supports 1809 and LTSC
Uninstall 2.5.5 or any previous version using that version's uninstaller before installing or running 2.5.6.
1) Now disables upfc.exe
2) Script includes Windows Update Manager (WuMgr) v0.9b along with Windows Update Minitool (WUMT) giving you a choice of which to use in the menu to perform updates.
3) Script uses NSudo 6.1 instead of Powerrun (NSudo thread here) to lock update hijacker files. NSudo is faster and just works better.
4) Fixed accidental unicode in _readme.txt which caused strange characters to display in Oriental languages. (No, really, I fixed it this time!)
5) Script in addition to uninstalling Windows 10 Update Assistant, creates and locks empty %systemroot%\UpdateAssistant and %systemroot%\UpdateAssistantV2 folders to stop Update Assistant from ever installing from an update. Now no need to run the script again after an update!
6) Fixed rare task creation error problem.
7) Not just some, but now all Update Hijacker folder and file permissions are now removed as TrustedInstaller as required by 1809.
8) Wrapper Script Start Menu folder now has a "Version" icon to easily see what version of the wrapper you have installed.
Last edited by pf100; 05 Jan 2019 at 09:10.
Script 2.5.6 1803 BSOD fix here.
2.5.6 disables upfc.exe which BSOD's 1803. Uninstall it now and install 2.5.5
Don't do updates if you're using the wrapper script! I have a report that updating 1803 to 17134.471 which from a quick google search appears to be KB4471324, I may have a problem here.
The report: I installed WUMT Wrapper Script v2.5.6 to 1803 with the December 2018 updates (17134.471). I got CRITICAL_SERVICE_FAILED BSOD at next reboot. Safe mode didn't help, and I had to manually revert the permission changes (using another OS) to the hijacker files in System32. Has Microsoft already tightened up 1803.. :-(
From Microsoft's website on KB4471324:
Security updates to Internet Explorer, Microsoft Scripting Engine, Windows App Platform and Frameworks, Microsoft Graphics Component, Microsoft Edge, Windows Storage and Filesystems, Windows Authentication, Windows Wireless Networking, and Windows Kernel.
My suggestion is: Don't do any more updates if you're using the script, or just uninstall the script right now and use another windows update control method until I sort this out. I'll work on finding out right now what happened. I'm on this like white on rice, folks. I will work on this tirelessly until I find out what happened here. It may be a bigger problem of a range of protected system files. I'm working on the problem now and will submit a report of my findings.
Thanks.
Last edited by pf100; 05 Jan 2019 at 09:12.
Hi All,
I forwarded the WMUT Wrapper Script information and download page to a friend so he could install and run it on his laptop. He did and rebooted and, apparently, it sort of killed Windows. Now the little blue window logo is as far as the poor laptop will go. It then displays the blue "Your PC ran into a problem" screen, and nothing works from there on (safe mode, allowing unsigned drivers, etc.).
Any way to undo whatever the script did?
Any help is appreciated
Hey pf100,
Just to help you out on this, I also had the same problem on 1803 (KB4462919), i had windows reset my PC back to 1803 orignal (10.0.17134.1) and then again, after installing the 2.5.6 wrapper script with no updates on, the laptop failed to get to Windows always crashing, so this might be something realted to the changes in general rather then the specific version.