To update to this new version do we just replace the wumt_X64.exe or to we remove the WUMT Integrator and redo it again? Thanks.
@shewolf,yep thanks a lot man good and amazing tool; yet only for vanity is possible someday you put this application on Control.CPL I think that stay fantastic
First occasion to use the new version (9.30) today with the slew of Office updates, and I found something that I'd never seen before: despite my having tagged all Office updates to install, it installed only one of them and skipped the rest. So I selected all the remaining ones again, thinking I made some mistake, and tried again. Same thing, just one. Anyone else see that? Rather than going through that a dozen times to install them one by one, I just installed all the remaining ones via Settings (W10).
Fantastic tool to recover some control over the new W10 update paradigm. Just a quick question, and apologies if I have missed the answer in the previous posts. I have WU Service disabled by default , and the WUMT does re-enable the service prior to scanning, but is there a way for WUMT to then dis-able the Service again after the updates are installed. Currently I am needing to manually disable the service again , which is not a problem, just wondering if I missed something obvious ? Also, on scanning, the WUMT listed all drivers associated with the Intel.inf chipset driver set, ( options are set to not include drivers ) despite me having the latest installed. Is anyone else noticing that as well, this is on a current X99 refresh based system ?
WUMT is not configured to disable the service yes, i got this too apparently the option doesn't work well by design from msft
Hi guys, a question: Using Windows 10 Anniversay Update, WUMT downloads two .CABS for the KB3196936 or the KB3194496 (a "regular" .CAB update and an "express" .CAB update with a smaller size). If I decide to install these KBxxxxxxx updates manually with the DISM.exe command, should I also include the "express" updates? In this case, What is the correct installation order that you suggest? Thank you in advance and congratulations for the tool!
I still have high hopes people STOP talking to themselves and elaborate for anyone here reading their comments. Hopefully you understand my words.
i have problems with AMD Crimson Drivers.. which Microsoft keeps trying to install. i was using the Troubleshooter prior to the Anniversary Update. available here: h.t.t.p.s://support.microsoft.com/en-us/kb/3073930 But after updating to the Anniversary Update, Windows Update no longer obeys the Troubleshooter. So i gave this a try. But this is not accurate. It installs unnecessary drivers. ie. HP Wireless Button Driver. With Windows Update, only x64 is installed. But with this, both x86 and x64 are installed. In addition, installed updates aren't reflected accurately. Lastly, actions taken by this are not reflected by Windows Update. Thus, the potential for repetitive, unnecessary updates is high. Also, even after using this.. AMD's driver i was trying to avoid was still installed. (Yes, it was hidden) The same problem i was experiencing with the Troubleshooter. Maybe others will have better luck.
WUMT (and wushowhide Troubleshooter) are ment to be used if automatic update in WU is disabled or set to Notification
Does work great here. Check that your copy of WSUSSCN2.CAB is signed, sometimes MS puts out bad ones.
I've just downloaded a copy of wsusscn2.cab from the link you posted in the other thread. But it has no digital signature...