Windows 10: Difference Between WSUS and wushowhide.diagcab (Show/Hide)

So we did... *Smile
Changed Windows Update Assistant Settings and Have a Question

 

Ever since I was unceremoniously "upgraded" earlier this year to 1709 from 1703 I have been meticulously running wushowhide.diagcab (Show/Hide) before shutdown. It seems to be working quite well. However a cursory read about Windows Server Update Services (WSUS) has left me confused. Is one better then the other. WSUS seems to be for administrators though I could be mistaken. Should I take a closer look at WSUS or is wushowhide.diagcab (Show/Hide) a good enough solution. My concern is to be able to forestall any and all updates of my choosing.

Also what about Windows Update MiniTool?

Thanks.

https://support.microsoft.com/en-us/...ling-in-window

https://docs.microsoft.com/en-us/win...e-catalog-site

http://www.majorgeeks.com/files/deta..._minitool.html

:)

 

Windows Update Catalog driver update package corrupted

for now, I have uninstalled the HP printer driver and disconnected the device.

when I try and uses the show/hide update troubleshooter (wushowhide.diagcab) it can find both of the remaining two updates which bear the same name, but are different, but i can only hide one of them. I am not sure why this is, since they are two different
printer drivers. It might be because the updates have the same list name. changing the name of the detected update to indicate whether its for the 'Print to PDF' or the 'XPS document writer' might solve that issue. Only way I could determine the difference
between the updates as downloaded from the update catalog, (besides a minor difference in filenames,) was to look inside the .inf included in the downloaded .cab

 

Windows DVD Player (KB3081704) offered repeatedly

Try this ...

Download the "Show or hide updates" troubleshooter package now.

http://download.microsoft.com/download/F/2/2/F22D5FDB-59CD-4275-8C95-1BE17BF70B21/wushowhide.diagcab

and hide KB3106246.

...

 

RE: Windows Update Minitool. Use the WUMT Wrapper Script instead:

Stop Windows 10 Updates Properly and Completely Solved - Windows 10 Forums

 

You could also use the following reg file but you'd need to delete the subkeys when upgrading in future:
Upgrade1.reg
Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\Windows10Upgrade.exe]"Debugger"="mshta \"javascript:var sh=new ActiveXObject( 'WScript.Shell' ); sh.Popup( 'This operation has been cancelled due to restrictions in effect on this computer. Please contact your system administrator', 10, 'Message!', 64 );close()\"" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\Windows10UpgraderApp.exe]"Debugger"="mshta \"javascript:var sh=new ActiveXObject( 'WScript.Shell' ); sh.Popup( 'This operation has been cancelled due to restrictions in effect on this computer. Please contact your system administrator', 10, 'Message!', 64 );close()\""[/quote]

 

These two were responsible for installing W10 Upgrade app to autmatically upgrade to newer version:

 

WSUS service is a component of Windows Server, used in domain environment with centralized patch management. It is not targeted to home users.

Instead of MiniTool, you can use "WSUS Offline Update" - replacement of WSUS for home or unconnected computers: WSUS Offline Update - Update Microsoft Windows and Office without an Internet connection

 

Why? Your specs say you are running Pro, so you should be able to switch from the 'Semi-Annual Channel (Targeted)' (aka CB) to 'Semi-Annual Channel' (aka CBB), doing so would have meant you wouldn't have got 1709 until the next version (1803) was released. In addition, you can also defer Features Updates like 1709 for up to 365 days.

Windows Update - Defer Feature and Quality Updates in Windows 10

 

said:


Ever since I was unceremoniously "upgraded" earlier this year to 1709 from 1703 I have been meticulously running wushowhide.diagcab (Show/Hide) before shutdown...

Snip

You might recall that MS ignored many users settings earlier this year when they against user settings and wishes went ahead and installed 1709 WITHOUT permission.

https://www.computerworld.com/articl...k-updates.html

 

True, but it's not a mistake they are likely to make again. Their Enterprise customers would crucify them *Smile

Did you not try to roll back, as MS suggested?

https://support.microsoft.com/help/4023814

 

Snip

>"...but it's not a mistake they are likely to make again.

You know I think (maybe it was not you) we might have had this conversation in another thread. I said I was a cynic and you said you were not : )

>Did you not try to roll back, as MS suggested?

No, I did not. While I was aware that 1703 had been released earlier in 2017 and this was now the beginning of 2018 I was most upset that my PRO preferences were completely ignored and while no fault of MS I had purchased the computer in DEC of 2017 so I was just getting used to WIN 10 and I did not appreciate the changes. That being said I can be a realist too and with 1703 coming to an end some time this year and considering that my NEW notebook did BOOT up after the update I decided to leave well enough alone.