What happened to the Win7 Windows Update Troubleshooter?

Topic

New Reply

I have an old Win7 virtual machine that I’d like to get updated – but Windows Update keeps throwing an error 80092004. Normally, that means Win7 still
[See the full post at: What happened to the Win7 Windows Update Troubleshooter?]

Reply | Quote

Replies

It should be available via https://aka.ms/diag_wu, because that’s where Windows Update Troubleshooter links to.

But I get the impression that Microsoft recently broke a bunch of useful links while shuffling documents around.

I’ve used aka.ms/w10info for years, and that too is now broken.

2 users thanked author for this post.

Charlie, woody

Reply | Quote

Blast! even our askwoody link don’t work.
Oh, neither does the Win8.1 link: https://aka.ms/diag_wu

Windows - commercial by definition and now function...

2 users thanked author for this post.

Charlie, woody

Reply | Quote

Try via technet – https://gallery.technet.microsoft.com/Troubleshooting-Windows-55a0058b

Tony H.

Bristol, UK

2 users thanked author for this post.

John, woody

Reply | Quote

This TN link for WindowsUpdate.diagcab downloads the exact same version of the Windows Update troubleshooter for Windows 7, which I downloaded in December 2015 and again in December 2016.

1 user thanked author for this post.

woody

Reply | Quote

I remember Microsoft also pulled Windows Phone Recovery Tool after ending support for Windows 10 Mobile.

The broken links were removed, fixed, removed again, and finally fixed after users complained.

I just pinged Microsoft support staff about the broken link and they’ve passed the feedback to their engineers.

 

1 user thanked author for this post.

woody

Reply | Quote

Hi Woody,

Have you also installed KB4490628 or a later version of the WU Servicing Stack update?

Best regards,
–Michael

Reply | Quote

Nope – but I shouldn’t have to, because I was using Windows Update….

1 user thanked author for this post.

Charlie

Reply | Quote

Also, it’s not KB4490628 or a later version.

It’s strictly KB4490628.

Not only is any later version of the SSU no substitute for KB4490628, but KB4490628 is a prerequisite for any later version.

Reply | Quote

Hi Woody,

I tried the Internet Wayback Machine and was able to download it.

Reply | Quote

Yes, but the clickable link in post 2290457 works as well, but without all the digging necessary for the Wayback Machine.

I clicked the link in the post, and was taken directly to a page in MS’s TechNet forums that had a clickable link to either directly run the troubleshooter or save it as a download for later use. I clicked the link on the page, to see what would happen, and I was prompted with a box to select either running directly from the site, or save it as a download for later use.

BTW, this was just a couple of minutes before writing this post.

Reply | Quote

Easy answer.  Windows 7 went end of life January 2020 – 7 months ago.  This is very common for tools to go missing or taken down for end of life software.

Reply | Quote

Windows 7 is not EOL. It’s still supported with an extended update plan.

And it is not actually all that common for Microsoft to screw things up like this. They kept old redirects forever for previous version of Windows. And they are maintaining the update servers for Windows 7. As long as you have updates, why wouldn’t you also have the update troubleshooter?

Reply | Quote

[woody]

anonymous wrote:

This is very common for tools to go missing or taken down for end of life software.

I can’t think of an analogous situation when XP hit EOL. ‘Course it’s been a while.

Win7 isn’t exactly EOL. Some folks have paid for Extended Security Updates.

• This reply was modified 4 years, 9 months ago by woody.

1 user thanked author for this post.

Charlie

Reply | Quote

Like i said, removing the so called SHA-1 content from Microsoft Download Center was a very bad and selfish decision

anyway, the lost WindowsUpdate.diagcab is still available (exact same file) via another link with slightly different name
http://download.microsoft.com/download/F/2/2/F22D5FDB-59CD-4275-8C95-1BE17BF70B21/WindowsUpdateDiagnostic.diagcab

there are also other recent WU troubleshooters

http://download.microsoft.com/download/F/2/4/F24D0C03-4181-4E5B-A23B-5C3A6B5974E3/wu170509.diagcab
http://download.microsoft.com/download/F/2/4/F24D0C03-4181-4E5B-A23B-5C3A6B5974E3/latestwu.diagcab

you could also try the built-in troubleshooter
msdt.exe -ep WindowsHelp id WindowsUpdateDiagnostic

3 users thanked author for this post.

Pim, PKCano, woody

Reply | Quote

[Volume Z]

Maybe so, but this error isn’t due to it. The same would have occurred a month or two ago, because Windows Update will put any and all SSUs last in queue. It simply doesn’t work with KB4490628 since Patch Day August 2019.

• This reply was modified 4 years, 9 months ago by Volume Z.

1 user thanked author for this post.

Charlie

Reply | Quote

[E Pericoloso Sporgersi]

I have two different versions of Windows Update Troubleshooter:

1. downloaded today from Technet : WindowsUpdateDiagnostic.diagcab , size 307 KB (as in post #2290457)

2. downloaded 2019 06 15: wu10.diagcab , size 656 bytes.

When I run 1, it tells me there is a more recent version available and suggests to run it. I assume wu10.diagcab is meant.

When I run 2, I first get
https://www.cisken.be/AskWoody/2020-08-23_Win10diagcab.jpg
and when it finishes I get
https://www.cisken.be/AskWoody/2020-08-23_troubleshootreport.jpg
though I didn’t notice anything wrong before I ran it.

You can download wu10.diagcab from https://www.cisken.be/AskWoody/wu10.diagcab

1 Desktop Win 11
1 Laptop Win 10
Both tweaked to look, behave and feel like Windows 95
(except for the marine blue desktop, rgb(0, 3, 98)

• This reply was modified 4 years, 9 months ago by E Pericoloso Sporgersi.

Reply | Quote

I have not re-tested the sequence but my Win7 install notes show that my experience was that you need to manually install both the March 2019 Servicing Stack Update (KB4490628) and the September 2019 Servicing Stack Update (KB4516655) or the SHA-2 Code Signing Update (KB4474419) will not function during use of Windows Update. WU will find updates and download them but is unable to validate them and generates the 80092004 error.

Of course it could be something else causing the error – but I always try to eliminate the simple possibilities first. I’ve wasted far too much time by saying “but it should not need me to do that”.

1 user thanked author for this post.

GoneToPlaid

Reply | Quote

[woody]

I ran the Troubleshooter from Technet. Tried updating again, same error code.

If I have time today I’ll try manually installing the Servicing Stack Update KB 4490628. (I already have KB 4474419. the SHA-2 update.)

UPDATE: Sure enough, I had to manually install the SSU. Everything working now.

• This reply was modified 4 years, 9 months ago by woody.

1 user thanked author for this post.

Cybertooth

Reply | Quote

What a surprise – Microsoft making things difficult again – happy to have assisted.
I am still installing a few Win7 systems for my older customers – and have a checklist of all the steps required to navigate the pitfalls of getting Win7 installed and updated. And this manual install of the various SSU’s – at the required points in the sequence – avoids WU falling flat on its face for no good reason.

1 user thanked author for this post.

woody

Reply | Quote

[Volume Z]

This has been default Windows Update behavior for about a year now. If KB4490628 wasn’t installed before the deadline that was Patch Day August 2019, Windows Update fails to offer it. There is a conflict going on between prerequisite priorities of Servicing Stack and SHA-2 code signing support.

Also, 80092004 cannot be fixed with KB4490628 missing, and I’m pretty sure the Troubleshooter has no idea of it all.

Regards, VZ

• This reply was modified 4 years, 9 months ago by Volume Z.

2 users thanked author for this post.

abbodi86, DougCuk

Reply | Quote

Like i said, removing the so called SHA-1 content from Microsoft Download Center was a very bad and selfish decision

Now it’s getting really interesting. Turns out 6.1.7601 is not at all affected by the SHA-1 code signing deprecation.

https://answers.microsoft.com/en-us/windows/forum/all/windows-7-update/93e4168e-1d59-4c90-b9d3-9a2106256933

Reply | Quote

There are two SHA-1 deprecation cases:

1- Removing SHA-1 content from Microsoft Download Center

2- Removing SHA-1 endpoints for Windows Update

do you mean vanilla Windows 7 SP1 OS can connect to WU without installing KB4474419/KB4490628 manually?

Reply | Quote

Yep, abbodi. No change at all has occurred when checking for updates.

1 user thanked author for this post.

abbodi86

Reply | Quote

I think all that Microsoft Answers post says is that you can’t install the SHA-2 update onto the original RTM version of Win7 – you need the SP1 version. I always install the SP1 version as my starting point – original ISO’s are still available if you know where to look.

From my experience the SP1 version can connect to WU and install older updates but hits a brick wall where the updates have been replaced with SHA-2 versions. I have a collection of the original MSU files including the “unofficial SP2” Rollup KB3125574 which gets you updated to April 2016 in one step (almost all the issues with this update were fixed by later KB updates). After that you have to install the SHA-2 update (and various SSU’s) to be able to collect more recent updates via Windows Update.

Reply | Quote

Right, but it also means Microsoft is giving wrong advice regarding Windows 7 at help article 4569557.

https://support.microsoft.com/en-us/help/4569557/windows-update-sha-1-based-endpoints-discontinued

“Can be mitigated by manually installing KBs” neither applies to RTM nor to SP1, where the issue doesn’t exist in the first place.

Reply | Quote

This one is still out there, live and working!

Thanks for those who posted the link originally

https://gallery.technet.microsoft.com/Troubleshooting-Windows-55a0058b

Reply | Quote

Good news everyone

Microsoft continues its anti-SHA1 witch-hunt and remove important additional packages for Windows 7 (and probably Vista) from Download Center, without providing alternative

including Service Pack 1 (KB976932) itself (but that’s available from MU catalog)

Remote Server Administration Tools
Windows Media Services Remote Server Administration Tools
Active Directory Lightweight Directory Services
Windows Management Framework 4.0
DirectAccess Connectivity Assistant 2.0
Windows NT Backup Restore Utility
Windows Media Feature Pack for Windows 7 N and for Windows 7 KN
Windows Media Format Feature Pack for Windows 7 N and for Windows 7 KN
Desktop Experience Decoder Update for Windows Server 2008 R2
Windows Media Services 2008 for Windows Server 2008 R2
Microsoft Camera Codec Pack

2 users thanked author for this post.

SueW, Cybertooth

Reply | Quote