Wushowhide2.diagcab is being put out to pasture.


This batch script can be use to hide or unhide Windows updates.




Code:
@Echo off & Cls

(Net session >nul 2>&1)||(PowerShell start """%~0""" -verb RunAs & Exit /B)


:_CHOICE

Cls & Mode CON  LINES=11 COLS=60 & Color 0E & Title Created By FreeBooter
Echo.
Echo.
Echo.
Echo        1 - Hide Windows Updates
Echo.       
Echo        2 - Unhide Windows Updates
Echo.


Set /p input=:^>

If Not %input%==1 (Goto :_Ex) Else (Goto :_Hide)

:_Ex
If Not %input%==2  (Goto :_CHOICE) Else (Goto :_Unhide)




:_Hide

Cls & Mode CON  LINES=30 COLS=90 & Color 0E & Title Created By FreeBooter

powershell Set-Executionpolicy unrestricted

Cls

PowerShell Install-Module PSWindowsUpdate

Cls

PowerShell Get-WindowsUpdate

Echo.
Echo.
Echo Enter KBNUMBER with the update number you want to block

Set /p KBNUMBER=:^>

Cls

PowerShell Hide-WindowsUpdate -KBArticleID %KBNUMBER% -AcceptAll


ping -n 5 localhost > Nul


Goto :_CHOICE





:_Unhide

Cls & Mode CON  LINES=30 COLS=90 & Color 0E & Title Created By FreeBooter

powershell Set-Executionpolicy unrestricted

Cls

PowerShell Install-Module PSWindowsUpdate


Cls

PowerShell Show-WindowsUpdate

Echo.
Echo.
Echo Enter KBNUMBER with the update number you want to Unhide

Set /p KBNUMBER=:^>

Cls

PowerShell Show-WindowsUpdate -KBArticleID %KBNUMBER% -AcceptAll


ping -n 10 localhost > Nul

Goto :_CHOICE
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Pavilion
    CPU
    AMD Ryzen 7 5700G
    Motherboard
    Erica6
    Memory
    Micron Technology DDR4-3200 16GB
    Graphics Card(s)
    NVIDIA GeForce RTX 3060
    Sound Card
    Realtek ALC671
    Monitor(s) Displays
    Samsung SyncMaster U28E590
    Screen Resolution
    3840 x 2160
    Hard Drives
    SAMSUNG MZVLQ1T0HALB-000H1
weird. I do not get the troubleshooter being "deprecated" message, when running wushowhide.diagcab in Win10.
maybe it occurs only in Win11
Correct. the deprecation only applies to Windows 11. The 'Learn more' link takes you here:

Microsoft is retiring the Windows legacy inbox Troubleshooters, such as Keyboard troubleshooter and Speech troubleshooter, and the Microsoft Support Diagnostic Tool (MSDT) that runs them..... MSDT Troubleshooters will be deprecated in the next Windows 11 release, with the date to be determined.
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Hi folks
Seems Ms is trying to remove every possible tool in Windows to hinder users from even being able to fix simple problems.

I suspect Ms has been reading Harry Harrison's Sci-Fi novel "The ethical Engineer" where bits of science and technology are restricted only to very few people with each tribe owning the secrets of just 1 piece of technology.

I find though these days I use a physical Windows machine less and less and find I can get nearly everything done that I need Windows for by using a VM. Using a VM with "Virtual hardware" avoids these sorts of driver problems in most cases.

I agree though especially for those using sophisticated gaming rigs with specialized GPUs etc using a VM is generally not an acceptable option. I've also used that tool for blocking / removing etc failed updates.

I'm not sure why Ms would deprecate this without first having an alternative doing a similar function. However I'm sure some Windows Guru will come out with an appropriate tool.

cheers

jimbo
 

My Computer

System One

  • OS
    Windows XP,7,10,11 Linux Arch Linux
    Computer type
    PC/Desktop
    CPU
    2 X Intel i7
Correct. the deprecation only applies to Windows 11. The 'Learn more' link takes you here:


But of course "The elephant in the Room" is that W10 itself will be reaching EOL in the not to distant future and therefore the problem is only academic.

cheers
jimbo
 

My Computer

System One

  • OS
    Windows XP,7,10,11 Linux Arch Linux
    Computer type
    PC/Desktop
    CPU
    2 X Intel i7
Correct. the deprecation only applies to Windows 11. The 'Learn more' link takes you here:



even weirder. I do NOT get the deprecation message when running wushowhide.diagcab on original/RTM Win11 (21H2) version {os build 22000.x}.
guess the deprecation seems to apply only to Win11 22H2 & newer
 

My Computer

System One

  • OS
    windows 10 ltsc
even weirder. I do NOT get the deprecation message when running wushowhide.diagcab on original/RTM Win11 (21H2) version {os build 22000.x}.
guess the deprecation seems to apply only to Win11 22H2 & newer
Not really surprising when you take into account that Win11 21H2 reaches end of support on Oct 10, 2023. It's not going to in support when MS get round to removing MDST.
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Not really surprising when you take into account that Win11 21H2 reaches end of support on Oct 10, 2023. It's not going to in support when MS get round to removing MDST.

only the home & pro editions of win11 21h2 go out of support this October 2023. the enterprise & education editions of 21h2 get one more year of support 'til October 2024.

forgot to mention last time that I tested wushowhide.diagcab on Win11 21H2 Education edition (don't ask why I have that specific edition installed on one of my PCs)
 

My Computer

System One

  • OS
    windows 10 ltsc
Back
Top Bottom