Instructions for un-hiding an update using wushowhide

Topic

New Reply

I have a home PC running Windows 10 Pro 22H2 with GPEDIT=2.

I’ve used wushowhide many times to hide Windows updates. The instructions for doing so appear in many places, including the advice to click Advanced and uncheck Apply repairs automatically.

However, I’ve never needed to un-hide an update until possibly now, but I cannot find explicit instructions on how to do it. How do I use wushowhide to un-hide an update so that it appears again in the Windows Update queue ready for me to click Download?

PS. If the un-hidden update does not appear in the Windows Update queue immediately, I don’t need instructions on how to speed up the process. I’m happy to wait until the next day for it to appear. When hiding updates, I never use Matador’s method, or any other method, to speed up the process. I just wait for the update to disappear from the Windows Update queue (usually by the next day) before clicking Download. I’m a retiree with time on my hands!

Reply | Quote

Replies

When you un-hide an update using wushowhoide it does not immediately appear in the Windows update queue. It will appear the next time that WU checks for updates by itself.

What I have done if I want to immediately install an update that I have un-hidden is to 1) run wushowhide again to see if there are any other updates that can be hidden other than the one that I want to install and 2) if nothing else is available to be hidden I close wushowhide and click to check for updates. At that point WU will detect the update that has just been un-hidden and install it.

Reply | Quote

Thanks Eric, but I don’t think my situation is the same as yours. I’m running Windows 10 Pro with GPEDIT=2. Consequently, I don’t see a Check for updates button on the Windows Update page, only a Download button.

I am assuming that using wushowhide to un-hide an update is relatively straightforward. But I would be interested to know whether it is equally important to click Advanced and uncheck Apply repairs automatically for un-hiding an update as it is for hiding an update.

Reply | Quote

TonyC wrote:

I don’t see a Check for updates button on the Windows Update page, only a Download button.

The reason you are seeing a Download button is that WU has refreshed itself, has found an update waiting in the queue, and is following the GP=2 setting by presenting a Download button to you. That update is waiting to be downloaded because you did not hide it in time or did not know that it was coming down the pike or you purposely unhid it. You should see the name(s) of the update(s) waiting for you to download/install.

If you don’t want to download/install it/them, go to WUSHOWHIDE and hide it/them, then wait for WU to refresh itself, after which the Download button will disappear and the Check for updates button will replace it.

If you DO want to install it/them, then go ahead and click on the Download button.

As said elsewhere, do not click on Check for updates unless you know what’s in the queue because you are not checking: ‘Check for updates’ really means ‘Install updates’ — whatever they are –there is never a Download button after you click on Check for updates because you’ve given it free rein to do its thing.

Reply | Quote

I still maintain that, on my system (home PC running Windows 10 Pro 22H2 with GPEDIT=2), I have never seen the Check for updates button.

When it is time to do the monthly updates, I review the offered updates on the Windows Update page. If I need to hide any of them, I use wushowhide and then wait until Windows Update refreshes itself, typically by the next day. After Windows Update has refreshed itself, I use the Download button to install the updates that remain. After the updates have been installed, if I return to the Windows Update page, I see a message informing me that my system is up to date. I do not see the Check for updates button.

Reply | Quote

TonyC wrote:

However, I’ve never needed to un-hide an update until possibly now, but I cannot find explicit instructions on how to do it. How do I use wushowhide to un-hide an update

Start wushowhide and click Next.

Click the Show hidden updates option.

Check the particular update you want to unhide and click Next.

Once it’s finished Resolving problems, click Close and then, as pointed out by @EricB, wait for Windows Update to perform another update check (~24 – 48 hrs.)

Note: DO NOT click the Check for updates button, wait until the update shows up as available for download!

If you do, it may also download/install any “preview updates that may be pending unless you’ve either hid them already or set your PC to ignore them.

1 user thanked author for this post.

TonyC

Reply | Quote

Yes, I am aware of the problem of clicking the Check for updates button prematurely but, as I am running Windows 10 Pro with GPEDIT=2, I don’t encounter that problem.

Reply | Quote

TonyC wrote:

Yes, I am aware of the problem of clicking the Check for updates button prematurely but, as I am running Windows 10 Pro with GPEDIT=2, I don’t encounter that problem.

It sounds like you mean:

Yes, I am aware of the problem of clicking the Check for updates button instead of waiting for the Download button, but, as I am running Windows 10 Pro with GPEDIT=2, I always wait for the Download button.

With GPEDIT=2, you will get the Download button when WU has refreshed itself and has found an update waiting in the queue.

There will be an update waiting in the queue, if:

1. You have unhidden an update, WU has refreshed itself, (and has found it there in the queue).
2. MS has delivered one or more updates and you did nothing to hide it/them (or you did not hide it/them in time–in which case they will hidden in the NEXT refresh).

Reply | Quote

n0ads wrote:

Note: DO NOT click the Check for updates button, wait until the update shows up as available for download! If you do, it may also download/install any “preview updates that may be pending unless you’ve either hid them already or set your PC to ignore them.

That’s why I always run wushowhide again after un-hiding an update to see if it detects any updates that WU would install besides the one that I just used wushowhoide to un-hide.  If it does, then I have the opportunity to hide them.

Of course, if there is already something in the WU queue that is unwanted and the available choice is “Download” instead of “Check for Updates” hiding the unwanted thing and waiting for WU to update its queue is the way to go.

 

1 user thanked author for this post.

TonyC

Reply | Quote

TonyC wrote:

But I would be interested to know whether it is equally important to click Advanced and uncheck Apply repairs automatically for un-hiding an update as it is for hiding an update.

Its always a good idea to uncheck the Apply repairs automatically box.  After all, you don’t know what it might find or what it might do if left to its own devices. 🙂

Reply | Quote

Recently (I actually think it started after my last updates last month that I followed up with DISM /RestoreHealth and SFC /SCANNOW) my WUshowhide has been behaving very strangely.  No matter how many times I run it, it keeps saying there’s nothing to hide.

 

This is notwithstanding the fact that there actually are updates!

 

 

Please help!  Thank you

Reply | Quote

I have had the same experience with wushowhide and this month’s updates. I’m beginning to wonder if Microsoft has finally retired the tool as the notice on it has been warning. As the month progresses, I guess we will find out for sure.

1 user thanked author for this post.

Felix

Reply | Quote

See solution here: #2697540.

1 user thanked author for this post.

jburk07

Reply | Quote

PKCano wrote:

I have had the same experience with wushowhide and this month’s updates. I’m beginning to wonder if Microsoft has finally retired the tool as the notice on it has been warning. As the month progresses, I guess we will find out for sure.

Wow.  On the one hand, I’m glad it’s not something unique to me, on the other hand I’m really worried now — please keep us informed!

Reply | Quote

I’ve been using WUmgr since Dec 2019 to hide updates so hadn’t try wushowhide.diagcab in a LONG time.

Just did and found it worked just fine to display the pending August CU KB5041580 on my Windows 10 Pro 22H2.

BTW, the .NET CU KB5042352 update didn’t show up because I already successfully installed it.

Reply | Quote

Interesting — I wonder why @PKCano and I (and possibly others) are having this issue then, starting fairly recently

1 user thanked author for this post.

Bob99

Reply | Quote

My experience was within a short time of the initial Patch Tues. release. I have to say that I also did not see updates in the WU queue at the time. (I do not use Pause)

1 user thanked author for this post.

Felix

Reply | Quote

Wushowhide functioned as expected on my system with respect to the various August updates for Windows 10 22H2, the .Net Framework and .Net.

Also, the warning about retirement is not present when it runs.

Reply | Quote

EricB wrote:

Also, the warning about retirement is not present when it runs.

Didn’t really pay attention to that particular detail but you’re right!

As my above screenshot shows, I didn’t get it either.

Wonder if that’s related to which version of Windows it’s being used with?

Windows 10 = no retirement alert.

Windows 11 = retirement alert.

Or maybe which version of wushowhide.diagcab is being used?

I downloaded mine on 12/17/19 but all the files inside it are date stamped 06/15/15.

BTW, you can determine the date stamp of the files it contains by temporarily changing the extension to .zip and view it as a compressed folder.

Once done, change the extension back to .diagcab to run it.

Reply | Quote

Are you using the newer version of wushowhide that Microsoft reissued using SHA256?

1 user thanked author for this post.

Bob99

Reply | Quote

Yep!

1 user thanked author for this post.

Bob99

Reply | Quote

n0ads wrote:

Yep!

Same here

Reply | Quote

n0ads wrote:

EricB wrote:

Also, the warning about retirement is not present when it runs.

Didn’t really pay attention to that particular detail but you’re right!

As my above screenshot shows, I didn’t get it either.

Wonder if that’s related to which version of Windows it’s being used with?

Windows 10 = no retirement alert.

Windows 11 = retirement alert.

Or maybe which version of wushowhide.diagcab is being used?

I downloaded mine on 12/17/19 but all the files inside it are date stamped 06/15/15.

BTW, you can determine the date stamp of the files it contains by temporarily changing the extension to .zip and view it as a compressed folder.

Once done, change the extension back to .diagcab to run it.

Can’t duplicate the .zip method for some reason, but mine’s Win 11 and matches @EricB ‘s screenshot above, and I am seeing the retirement warning.

Reply | Quote

A big Thanks go out to you, @Felix for asking the question about wushowhide in the first place, and to @EricB and @n0ads for mentioning the signature algorithm for wushowhide that has been updated from sha1 to sha256.

I’ve been using wushowhide since 2020 on what is now Windows 10 Pro 22H2 (but started as Windows 10 Pro 2004) and haven’t seen any retirement warning at all, so I’m with @n0ads in that I now think that the warning is for those running it under Windows 11, even the sha256 version.

The discussion between @EricB and @n0ads about the digital certificate being changed prompted me to look at the version I’ve been using all this time and it was the sha1 version, signed back in 2015. Upon discovering that, I promptly got myself a copy of wushowhide with the sha256 cert signed in 2021.

1 user thanked author for this post.

Felix

Reply | Quote

But isn’t the newer version the one with the issues?

Reply | Quote

Felix wrote:

But isn’t the newer version the one with the issues?

Both @EricB and I are using the newer version with the sha256 cert signed in 2021 and neither of us are seeing the Retirement notice.

Since you indicated you’re using the same version, it seems that notice is only for Windows 11 users.

Reply | Quote

I can confirm that the notice does not show on my Win10.
Win11 only Notice.

1 user thanked author for this post.

Bob99

Reply | Quote

Now, one final question about this pending retirement of wushowhide for those running Windows 11. In PK’s (and @Felix ‘s) screenshots, at the end of the yellow highlighting at the bottom of the window is a blue colored link that says “Learn more”.

Just where does this link lead to, which webpage? Is it possible to click the link and then copy/paste the resulting URL from your browser to a post here for us to see?

Reply | Quote

Learn more:

https://support.microsoft.com/en-us/windows/deprecation-of-microsoft-support-diagnostic-tool-msdt-and-msdt-troubleshooters-0c5ac9a2-1600-4539-b9d0-069e71f9040a

2 users thanked author for this post.

Felix, Bob99

Reply | Quote

PKCano wrote:

I have had the same experience with wushowhide and this month’s updates. I’m beginning to wonder if Microsoft has finally retired the tool as the notice on it has been warning. As the month progresses, I guess we will find out for sure.

By the way, so what’s the plan going forward then?

Reply | Quote

Felix wrote:

By the way, so what’s the plan going forward then?

After wushowhide stops working for those ion Windows 11 23H2 and newer versions, there will be two other choices for controlling the monthly windows updates: WUMgr and Windows Update Mini Tool (WUMT). Both are available from https://blockapatch.com/, which is an offshoot site of Askwoody.

2 users thanked author for this post.

jburk07, Felix

Reply | Quote

On the Win11 I had the problem of no-show updates, I was still using the sha-1 version of wushowhide.
Ooops, my bad.
Updated to the sha256 version. All OK now.
It’s a wonder it had been working this long!

2 users thanked author for this post.

jburk07, Bob99

Reply | Quote

PKCano wrote:

On the Win11 I had the problem of no-show updates…

Was this the first time that had happened to you, or did it happen a couple/three months ago?

Your experience definitely shows that MS is enforcing the sha256 encryption for the newer version of wushowhide with Windows 11. Maybe it’s just a matter of time before they do the same with Windows 10. Or, maybe they won’t bother.

Reply | Quote

First time it happened, I think. Rest are sha256. Don’t know how I missed that.
Senior moment!

Reply | Quote

OK, I’m really confused now.

I still have the issue described above — https://www.askwoody.com/forums/topic/instructions-for-un-hiding-an-update-using-wushowhide/#post-2696506 , or as @PKCano said, no-show updates.

And, I have Win11 and the sha256 version (and have had it the whole time this issue arose about a month or so ago).

Reply | Quote

Felix wrote:

And, I have Win11…

Exactly which version of Windows 11, 23H2, or 24H2? At this point, it just might make a difference.

Reply | Quote

23H2

Reply | Quote

Well, if you haven’t clicked the “Pause updates for 7 days” icon (or paused updates in another way) since your last successful use of wushowhide, then it sounds to me like your machine has been “sunsetted” by MS with respect to using wushowhide.

PK just found out that using the sha1 version of wushowhide with Windows 11 was the reason in that case, and upon trying wushowhide’s sha256 version, it worked again. In your case, you’re already using the sha256 version, so the only other reason I can think of for wushowhide not working is either you’ve paused updates or your copy of it and the infrastructure it needs in order to work has been retired, just as the warning says.

Click the “Learn more” link in the warning. That will bring up a webpage describing the retirement of the troubleshooting tools like wushowhide and the way its being done. There are timelines on that page for some of the other tools, but the info is basically the same…at a point that in some cases has yet to be determined, the troubleshooting tools like (and including) wushowhide will be retired, with some being redirected to the Get Help part of Windows 11. Wushowhide isn’t named as one of them that is being redirected.

Reply | Quote

Felix wrote:

Interesting — so you’re saying that when you had the same issue as me, you had the sha1 version (not the sha256 version like me)?  And then you upgraded your sha1 version to the sha256 version?

Should I:

1. Delete my WUShowhide (sha256) and then install it (sha256) again?  (Is that something that’s advisable?  And if so, how exactly should I do it?)
2. Somehow try to get sha1 (if that’s even possible)?
3. Or just wait till I do the August updates?
4. Or just just wait till the September update?

Thank you!

By the way, you won’t believe what just happened!

Before we get to my original questions of what to do next, I now have a more immediate issue.

While I did not have it on pause this whole time, because I’ve been looking at it so often now and going back and forth, etc., I accidentally just set it to a 1 week pause!

So, I’m now probably in an even worse place than I was before, because if I hit Resume, it’ll start downloading/installing immediately everything, because my WUShowhide isn’t working, right?

And, if I keep it on pause, I’ll never know if/when WUShowide or a replacement is working or not, right?

Anything I can do now?

Reply | Quote

After replacing it, I had a Defender update show up today.
Dunno.
No other updates at the moment, b/c I installed Aug updates the other day.

Reply | Quote

Interesting — so you’re saying that when you had the same issue as me, you had the sha1 version (not the sha256 version like me)?  And then you upgraded your sha1 version to the sha256 version?

Should I:

1. Delete my WUShowhide (sha256) and then install it (sha256) again?  (Is that something that’s advisable?  And if so, how exactly should I do it?)
2. Somehow try to get sha1 (if that’s even possible)?
3. Or just wait till I do the August updates?
4. Or just just wait till the September update?

Thank you!

Reply | Quote

According to the info at that link in @PKCano ‘s post just above, a date has yet to be determined for redirecting the Windows Update troubleshooter.

So, this means that, some time after the official release of windows 11 24H2, wushowhide will no longer work for those running Windows 11 versions newer than 22H2. The info on that page does say that the platform that helps the troubleshooters run will not be removed from Windows 11 22H2, but some items (troubleshooters) will be redirected to the Get Help area instead.

1 user thanked author for this post.

Felix

Reply | Quote

Felix wrote:

Delete my WUShowhide (sha256) and then install it (sha256) again?  (Is that something that’s advisable?  And if so, how exactly should I do it?)

Wushowhide is portable. Nothing to install.

With portable you just delete the software’s folder and create a new one with the new version.

1 user thanked author for this post.

Felix

Reply | Quote

Hi @Bob99,

I am new to this post and am having trouble following what has come before, mostly because I’m not clear on whether the posts concern Win11 or Win10.

I am Win10/Pro 22H2. I use WUSHOWHIDE and GP=2.

I do not see the yellow warning.

My version of WUSHOWHIDE.diagcab is dated 2/08/2020. The Digital Signature is ‘sha1’. When I click on the ‘Details’ button under the ‘Digital Signature’ tab, it says the files were signed Jun 15, 2015.

WUSHOWHIDE seems to be working OK
Evidence: I was able to hide the Aug 13 patches and they are still hidden. (BTW: I have changed my network adapter connection to IPv4 {I checked at the IPv6 Site and I have no IPv6 connection right now}. I will keep it at IPv4 until just before I do the Aug 13 patches this coming weekend, at which time I will change the network adapter connection back to IPv6). I also just checked WUSHOWHIDE and there is a Defender file in the queue, but it hasn’t shown up yet in the WU screen with a ‘download’ button, but I am almost certain it will, b/c one showed up with a ‘download’ button this morning.

So, even though WUSHOWHIDE is working fine, are you suggesting that I find one with a ‘sha256’ digital signature. If so, where do I find the ‘sha256’ version that works with Win10 22H2 with no yellow warning?

And more to the point, are you saying that even with this newer ‘sha256’ digital signature, WUSHOWHIDE on a Win10 22H22 might stop working in the future?

Reply | Quote

The sha256 version is available through a download link in AKB2000016 and at BlockaPatch.

Check the version you are using by right-clicking the file, choose Properties\Digital Signatures. See screenshot above.

The notice only shows in Win11.

3 users thanked author for this post.

jburk07, Felix, Bob99

Reply | Quote

PKCano wrote:

The sha256 version is available through a download link in AKB2000016 and at BlockaPatch.

If the ‘sha1’ version is working on a Win10/Pro 22H2, is there reason to get the newer ‘sha256’ version?

Reply | Quote

WCHS wrote:

If the ‘sha1’ version is working on a Win10/Pro 22H2, is there reason to get the newer ‘sha256’ version?

Yes, in case the sha1 version stops working for some reason. I would imagine that there are probably various different ways Microsoft could change the code within Windows 10 to make the sha1 version obsolete and non-working.

I would thing that they would, most likely, just make the whole tool obsolete, just like they have for Windows 11, rather than disallow the sha1 version and still allow the sha256 version to run. BUT, we are talking about MS after all, so anything’s possible.

Reply | Quote

By the way, as a Win11 user, it seems that at least in my case, the sha256 version is already at least partially obsolete — it only picks up at best some updates, but definitely not all, starting about a month ago.

Reply | Quote

Bob99 wrote:

Felix wrote:

By the way, so what’s the plan going forward then?

After wushowhide stops working for those ion Windows 11 23H2 and newer versions, there will be two other choices for controlling the monthly windows updates: WUMgr and Windows Update Mini Tool (WUMT). Both are available from https://blockapatch.com/, which is an offshoot site of Askwoody.

Just curious —

Windows Update MiniTool (WUMT) v04.22.2022 was last updated on 04/22/2022

WuMgr (Update Manager for Windows) is even older — it’s still only on 1.1, all the way back from 2019-12-11 !

I do notice an option that’s not on https://blockapatch.com that has been updated much more recently — WAU Manager (Windows Automatic Updates Manager) 3.5.3.0 — 2024-03-19.  Any thoughts?  It’s been mentioned here before — https://www.askwoody.com/forums/topic/how-to-delete-wua-manager/ , https://www.askwoody.com/forums/topic/is-anybody-familiar-with-wau-manager/ , https://www.askwoody.com/forums/topic/wumgr-vs-wau-manager-results/

Any other options? ( https://www.elevenforum.com/t/how-to-hide-unwanted-updates-after-retiring-windows-update-show-hide-tool.15811/ , https://www.majorgeeks.com/mg/sortdate/windows_update.html ?)

Reply | Quote

Felix wrote:

Windows Update MiniTool (WUMT) v04.22.2022 was last updated on 04/22/2022

WuMgr (Update Manager for Windows) is even older — it’s still only on 1.1, all the way back from 2019-12-11 !

Both are just fine and running Windows update. So far there is nothing in these apps that needs updating.

1 user thanked author for this post.

jburk07

Reply | Quote