WUSHOWHIDE not showing pending update

Topic

New Reply

I have this pending download (with download button as per GP Edit setting) – 2020-07 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4562900)

wushowhide says there are no updates pending install!  I can clear the update Q, but I’d rather not lose my update history.  The last time I cleared the Q, I lost history. Why isn’t this showing up for me to hide?  How can I clear the update Q without purging history?  I could leave it there until the next update – my understanding from this forum is this update will be overwritten with the next one.  Or just install it? thanks.

Reply | Quote

Replies

Clearing the WU queue clears the WU cache, it doesn’t remove the History.

Clearing the Datastore (resetting Windows Update) clears the
C:\Windows\SoftwareDistribution folder which clears the Update History.

Reply | Quote

Thanks for explaining. This is what I have done in the past and have instructions for, so that why my history was deleted.

Clearing the Datastore (resetting Windows Update) clears the
C:\Windows\SoftwareDistribution folder which clears the Update History.

I don’t have instructions for this:

Clearing the WU queue clears the WU cache, it doesn’t remove the History

and couldn’t find exactly what I was looking for online (some of what I found was the same as clearing the datastore, although the instructions stated they were on how to clear the cache,  PK do you have the steps for how to clear the cache and will it get rid of the unwanted update? thanks.

 

 

Reply | Quote

https://www.askwoody.com/forums/topic/2000013-how-to-clear-the-windows-update-queue-in-win10/

If you have Win10 Pro and the “3” in Group Policy, you can skip the Metered connections. But don’t skip anything else.
If you hide something (and verify wushowhide lists it as hidden) and AKB2000013 doesn’t seem to work, wait until the next time Windows Update checks on its own and the updates should be gone.

Caution, the latest .NET Preview may be an exception.

Reply | Quote

I have Win 10 Pro.

If you hide something (and verify wushowhide lists it as hidden) and AKB2000013 doesn’t seem to work, wait until the next time Windows Update checks on its own and the updates should be gone. Caution, the latest .NET Preview may be an exception.

This is what is happening – 2020-07 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4562900) – is not coming up to select to hide when I run wushowhide.  So, I will leave it and hope it goes away with the next update, thanks.

Reply | Quote

I got also the .NET preview.
I ran wushowhide and the preview was listed. I hide it.

Reply | Quote

As I stated in a previous poast, the NET Preview update was not showing in wushowhide and I could not hide it, so I left it.  Well WU ran yesterday morning and now it’s gone! I checked history and it did not install. Magic!

Reply | Quote

I also noticed different behavior using wushowhide. In my case was ready install July updates (Win 10 pro 2004 with win update group policy set to option 2 notify to download and install) Selected install for the items in the queue – Defender, July .Net, and July cumulative. Defender and July.net installed without issue, but the July cumulative remained stuck at 100% download and a new .Net appeared. Mistakenly I selected download before I realized that it was a .Net preview. The .Net preview started to download and the July cumulative started to re-download.
I disconnected from the internet and ran wushowhide. In the past I could disconnect from the internet and hide whatever was seen in the queue even if it started to download. Nothing, however was seen in wushowhide. Through a little trial, came to the conclusion that the internet needed to be connected before running wushowhide. With internet connected could see silverlight, .Net preview, and July cumulative with wushowhide. Hid silverlight and the .Net preview using wushowhide; then went through a procedure of clearing the queue. All fine afterwards.
Sorry for long post, to sum things up a procedure I used successfully in the past, now required modification. The change for me was that I had to be online, while in the past wushowhide would detect what was already in the queue even when offline. Sighhh

Reply | Quote

wushowhide and Windows Update both use the Windows Update Service to scan for updates. The difference is, what you see in the Windows Update queue is in a cache from the last time WU scanned on its own, and the cache won’t be refreshed until the next time WU scans. wushowhide does a live (current) scan. So patches can still be lined up in the queue (cache) to be downloaded and installed for Windows Update even after you have hidden them with wushowhide.

3 users thanked author for this post.

Elly, Sueska, Coldheart9020

Reply | Quote

You are absolutely right! Thank you for your clear explanation of how wushowhide works. I reviewed my notes and see that running wushowhide is step one. If you want to delete my post so it won’t confuse other people it that’s fine.

Reply | Quote

An easy way to test how wushowhide works is to check for updates to hide, once a Windows Defender intelligence update is shown in Windows Update after it does its own automatic routine scan.

From the Windows Update screen, click on Windows Security > Virus & thread protection and then install the latest intelligence update from there. Then re-run wushowhide and you’ll see that that same update is not available to be hidden. Once WU rescans, it will be gone from the update cache.

You can also use wushowhide to pre-emptively look for an update before it appears in the WU cache, and/or before you search for intelligence updates in Windows Security. It’s a good way to demonstrate exactly how wushowhide and Windows Update are intrinsically tied via the Windows Update Service.

1 user thanked author for this post.

Sueska

Reply | Quote

By”Clearing the Datastore” do mean delete the Datastore? My Update History is really full and I was blindly hoping MS would eventually clear it on one of their monthly trawls through my computer – as did happen once in the past.  Not so.  So am I safe to delete this or leave well enough alone? I mean is 51 MS SE history reports really necessary? I follow your great advice religiously and thank you for it.  I recently changed from Home to Pro with your help.

Reply | Quote

Clearing the datastore (resetting Windows Update) is more involved than just deleting a folder. It is not necessary unless you are having problems with Windows Update not working correctly. The next time you do a version upgrade, that will be removed anyway. So I wouldn’t worry about it unless Windows Update stops working.

 

1 user thanked author for this post.

Cee Arr

Reply | Quote

PKCano wrote:

Clearing the WU queue clears the WU cache, it doesn’t remove the History.

Clearing the Datastore (resetting Windows Update) clears the
C:\Windows\SoftwareDistribution folder which clears the Update History.

long late for this but-

Clearing the Datastore files from the C:\Windows\SoftwareDistribution folder does NOT fully clear the update history in Win10 v2004 and greater but works with Win10 v1909 and older.

In 2004/20H1 & above the windows update history is also stored in a new location –
C:\ProgramData\USOPrivate\UpdateStore\store.db
this also needs to be removed in order to fully purge/clear the update history but that file is usually in use by the windows update services and can’t be easily deleted

see this:
https://winaero.com/clear-windows-update-history-windows-10/
and read one of Jeff Barrow’s comments that mention a powershell script that clears both the \SoftwareDistribution\DataStore\ and \ProgramData\USOPrivate\UpdateStore\ folders in Windows 10 versions 2004, 20H2, 21H1 & newer

Reply | Quote