80072EFE on fresh install of Windows Vista

[1337xp]

The problem is that Vista cannot install updates, even though it's a fresh install with SP2 intergrated in it. It also always throws this error: 80072EFE.
Does anyone know if this is a common problem?

 

[lmacri]

Hi 1337xp:

Microsoft deactivated the Windows Update servers for computers with Win XP and Vista operating systems that do not support SHA-2 code signing on 03-Aug-2020. The Microsoft support article Windows Update SHA-1 Based Endpoints Discontinued for Older Windows Devices warned that Win XP and Vista users would likely see error codes code 80072ee2 or 80244019 (The device cannot connect to Windows Update) or 8024402c (The device is unable to locate Windows Update) when they ran Windows Update after 03-Aug-2020 but your error 80072EFE (a generic error that usually means there are issues making an internet connection) seems to be a common error code these days for Vista SP2 users trying to perform a clean reinstall and/or patch their VIsta SP2 OS back to end of extended support (11-Apr-2017).

See the FAQ What To Do if Windows Update Hangs or Throws an Error [UPDATED August 2020] pinned at the top of this Windows Update board for additional information.
----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * Malwarebytes Premium v3.5.1-1.0.365
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

 

[1337xp]

I see, so the only way is to install the updates manually from Microsoft's update catalog right?

 

[Vistaar]

...your error 80072EFE (a generic error that usually means there are issues making an internet connection) seems to be a common error code these days for Vista SP2...

I believe the latest error code is actually 80072EFF, and suspect that Microsoft made further changes because hackers found a way to get automatic updates for Windows XP etc. The Microsoft link about SHA-1 based endpoints appears to be rather disingenuous: a fresh install of Windows 7 with SP1 can receive Windows updates without manually installing any updates from the year 2019 that added SHA-2 support. I believe Microsoft is simply tired of being helpful to freeloaders who still haven’t bought Windows 10 and has artificially blocked Windows updates for systems older than Win7.

An interesting question is why some people running old versions of Windows still think they need security updates that were issued in previous decades and no longer have any real security value? If you are concerned about online security, I’m sure the good folks at Microsoft would tell you that you should’ve upgraded years ago.

 

[Vistaar]

I see, so the only way is to install the updates manually from Microsoft's update catalog right?

Unless you are a good hacker, that is the only way to get updates for Vista from Microsoft. This link to another forum might prove helpful: Download links for all Vista SP2 32-bit and 64-bit updates from Windows Update.

 

[lmacri]

I see, so the only way is to install the updates manually from Microsoft's update catalog right?

Hi 1337xp:

I've posted a few other suggestions in the first section of the FAQ What To Do if Windows Update Hangs or Throws an Error [UPDATED August 2020]. If you don't mind performing another clean reinstall, for example, SIW2 has created "fully updated" ISOs (both 32-bit and 64-bit, English only) that are slipstreamed with SP1 and SP2 as well as all ~200 Vista security updates released after May 2009 (the release date of SP2) that will automatically patch your OS up to the end of extended support on 11-Apr-2017. If you post in the thread Vista ISO Download and ask SIW2 to share a "fully updated" ISO (be sure to address your request to SIW2 and state if you have a 32-bit or 64-bit OS) then SIW2 will likely contact you via a private message with a download link.

I believe the latest error code is actually 80072EFF, and suspect that Microsoft made further changes because hackers found a way to get automatic updates for Windows XP etc.

I've seen a few recent threads from other Vista SP2 users who are seeing an error code 80072EFE. See VanessaEhredt's 19-Jan-2021 thread 80072EFE? in the MS Answers Vista board (where I post as user Great White North) for one example.
----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * Malwarebytes Premium v3.5.1-1.0.365
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

 

[Vistaar]

I've seen a few recent threads from other Vista SP2 users who are seeing an error code 80072EFE. See VanessaEhredt's 19-Jan-2021 thread 80072EFE?

VanessaEhredt never actually mentioned Windows Update (although Great White’s reply assumed that was the topic), and someone running Windows 8 evidently got the same error code even though Microsoft does not claim to have blocked Windows Update for that OS.

I don’t believe that Microsoft has granted redistribution rights to anyone, and the risks associated with acquiring Microsoft products from a third party are greater than running Vista without old patches that offer no protection against current threats in any event.

 

[1337xp]

I recently watched a YT video where they actually got WU working on Vista. Not sure how it works but somehow they got it working even after Microsoft's "patch".

 

[Vistaar]

I recently watched a YT video where they actually got WU working on Vista. Not sure how it works but somehow they got it working even after Microsoft's "patch".

If you’re that interested, I believe the hackers who found a way around Microsoft’s block can be found at My Digital Life forums. You might have to register there to read all of their posts. I would of course expect Microsoft to take defensive measures against this hack, I don’t know if it still works, and I would not recommend trying it.

I would be interested in knowing if you always get the exact error code that you mentioned above when checking for updates on Vista? That is not the exact error code that I get.

 

[1337xp]

If you’re that interested, I believe the hackers who found a way around Microsoft’s block can be found at My Digital Life forums. You might have to register there to read all of their posts. I would of course expect Microsoft to take defensive measures against this hack, I don’t know if it still works, and I would not recommend trying it.

I would be interested in knowing if you always get the exact error code that you mentioned above when checking for updates on Vista? That is not the exact error code that I get.

Fun fact, I already have an account for that forum. I actually already tried it, and it does seem to work, but it was not really of any use since i used SIW2's disc which already had 99% of all the updates. The error code before using that hack was always 80072EFE, no matter what i tried.

 

[Vistaar]

Fun fact, I already have an account for that forum. I actually already tried it, and it does seem to work...

It would be a pity if Microsoft decides to remove all updates for Windows Vista from their servers just to stop a few hackers. I’ve seen posts indicating that the Windows XP version of the hack no longer works, and that is probably why Vista users are seeing novel error codes now.

There were hardly any real improvements for Vista after SP2 was released in 2009 - just oodles of security updates that offer no real security in 2021. Granted, Platform Update for Windows Vista could have been very important if browsers and certain other software had continued to support Vista long after they ended support for XP, but that did not happen because Vista never had very many users. A legacy browser such as Firefox 52 x86 does not require Platform Update because it was designed to work on Windows XP. The only major browser that required Platform Update was IE9. Fun fact, the IE9 standalone installer includes the needed Platform Update components, so there is no real need to install Platform Update separately - especially since IE9 is not a good browser for use in 2021 anyway.

 

[lmacri]

... it was not really of any use since i used SIW2's disc which already had 99% of all the updates...

Hi 1337xp:

Glad to hear that SIW2's slipstreamed ISO was able to patch you back to 11-Apr-2017 during your Vista SP2 reinstall.

I should add that there were five emergency out-of-band updates (KB4018271 / KB4018466 / KB4021903 / KB4024402 / KB4019204) released for Vista SP2 in June of 2017 (i.e., after end of extended support on 11-Apr-2017) that were posted in the Microsoft Update Catalog but were never released via Windows Update. These security updates will patch vulnerabilities for three NSA-leaked exploits (EnglishmanDentist, EsteemAudit and ExplodingCan) and if you would like to install these patches manually see the MS Answers thread More Shadow Brokers Exploits Patched June 2017 for Win XP and Vista for download links and installation instructions. I believe that SIW2's slipstreamed ISO includes Vista SP2 updates released up to 11-Apr-2017 (except the .NET Framework 4.5.2) so none of these out-of-band updates are likely installed on your system yet, but if you want to confirm you can search your installed updates at Control Panel | Programs | Programs and Features | View Installed Updates [search for the full KB number in the search box (e.g., "KB4018466" and not a partial string like "4018446")] to see if they're already installed.



Microsoft also released a Windows Server 2008 / Vista security update KB4499180 in May 2019 that patches the BlueKeep remote desktop vulnerability CVE-2019-0708. See Microsoft's special advisory for Vista SP2 and other out-of-support OSs at Customer Guidance for CVE-2019-0708 | Remote Desktop Services Remote Code Execution Vulnerability: May 14, 2019 for more information. That patch is available for download from the Microsoft Update Catalog at Microsoft Update Catalog, but unlike the June 2017 out-of-band updates for the Shadow Brokers exploits, this KB4499180 Windows Server 2008 / Vista security update for the BlueKeep exploit will change your Vista SP2 OS from Build 2 (6.0.6002.xxxxx) to Build 3 (6.0.6003.xxxxx) - see the Microsoft support article Build Number Changing to 6003 in Windows Server 2008 for more information.

When KB4499180 was first released the change to Build 3 (6.0.6003.xxxxx) caused some unexpected problems with Avast / AVG Antivirus v18.8 and a few other third-party programs (see PKCano's Are Bluekeep Patches Causing BSODs with Server 2008 SP2 and Vista? in the AskWoody forum as well as the MSFN post <here> about Avast's "micro-update" fix), so if you decide to install this security update be sure to monitor your system for any unexpected glitches or software conflicts and uninstall KB4499180 if necessary. Even better, use Macrium Reflect Free or some other disk imaging software to create a full disk image and emergency recovery media before you install KB4499180 so that you can perform an emergency recovery if this update triggers a BSOD.
----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * Malwarebytes Premium v3.5.1-1.0.365 * Macrium Reflect Free v7.3.5555
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

 

[1337xp]

Hi 1337xp:

Glad to hear that SIW2's slipstreamed ISO was able to patch you back to 11-Apr-2017 during your Vista SP2 reinstall.

I should add that there were five emergency out-of-band updates (KB4018271 / KB4018466 / KB4021903 / KB4024402 / KB4019204) released for Vista SP2 in June of 2017 (i.e., after end of extended support on 11-Apr-2017) that were posted in the Microsoft Update Catalog but were never released via Windows Update. These security updates will patch vulnerabilities for three NSA-leaked exploits (EnglishmanDentist, EsteemAudit and ExplodingCan) and if you would like to install these patches manually see the MS Answers thread More Shadow Brokers Exploits Patched June 2017 for Win XP and Vista for download links and installation instructions. I believe that SIW2's slipstreamed ISO includes Vista SP2 updates released up to 11-Apr-2017 (except the .NET Framework 4.5.2) so none of these out-of-band updates are likely installed on your system yet, but if you want to confirm you can search your installed updates at Control Panel | Programs | Programs and Features | View Installed Updates [search for the full KB number in the search box (e.g., "KB4018466" and not a partial string like "4018446")] to see if they're already installed.

View attachment 30885

Microsoft also released a Windows Server 2008 / Vista security update KB4499180 in May 2019 that patches the BlueKeep remote desktop vulnerability CVE-2019-0708. See Microsoft's special advisory for Vista SP2 and other out-of-support OSs at Customer Guidance for CVE-2019-0708 | Remote Desktop Services Remote Code Execution Vulnerability: May 14, 2019 for more information. That patch is available for download from the Microsoft Update Catalog at Microsoft Update Catalog, but unlike the June 2017 out-of-band updates for the Shadow Brokers exploits, this KB4499180 Windows Server 2008 / Vista security update for the BlueKeep exploit will change your Vista SP2 OS from Build 2 (6.0.6002.xxxxx) to Build 3 (6.0.6003.xxxxx) - see the Microsoft support article Build Number Changing to 6003 in Windows Server 2008 for more information.

When KB4499180 was first released the change to Build 3 (6.0.6003.xxxxx) caused some unexpected problems with Avast / AVG Antivirus v18.8 and a few other third-party programs (see PKCano's Are Bluekeep Patches Causing BSODs with Server 2008 SP2 and Vista? in the AskWoody forum as well as the MSFN post <here> about Avast's "micro-update" fix), so if you decide to install this security update be sure to monitor your system for any unexpected glitches or software conflicts and uninstall KB4499180 if necessary. Even better, use Macrium Reflect Free or some other disk imaging software to create a full disk image and emergency recovery media before you install KB4499180 so that you can perform an emergency recovery if this update triggers a BSOD.
----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * Malwarebytes Premium v3.5.1-1.0.365 * Macrium Reflect Free v7.3.5555
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

Thanks for telling me! This is going to come in handy!

 

[SIW2]

Thanks lmacri.

Those 5 (KB4018271 / KB4018466 / KB4021903 / KB4024402 / KB4019204) can be integrated easily into my updated media.
Mount the image with e.g. dism++ and they integrate fine. They are pending and complete during vista installation.

 

[Deleted member 198782]

THIS GUIDE should be helpful to you.

 

[Vistaar]

THIS GUIDE should be helpful to you.

Welcome, but I’m afraid your guide was posted in March 2019. Windows Update ended support for Vista in August 2020. We were familiar with Dalai’s speed-up patch method during the years when it worked, but thanks for trying to help!

 

[SIW2]

Abbodi's tool that flavallee linked to still works.

 

[Deleted member 198782]

Vistaar:

SIW2 is correct.
The Vista_SHA2_WUC tool with option #1 works fine to get Windows Vista SP2 64-bit up to date to its EOL date of April 2017.
I may have originally posted the guide in March 2019, but it has been tested on a regular basis and was last tested in November 2021.

 

[Vistaar]

Abbodi's tool that flavallee linked to still works.

So the Russian URL in the guide that Imacri likes is a direct link to the MDL hack!? OP 1337xp was an MDL member anyway (see post #10, Feb 18), but I’m sure that someone will be interested (perhaps even our administrators).

 

[erpster4]

Vistaar:

SIW2 is correct.
The Vista_SHA2_WUC tool with option #1 works fine to get Windows Vista SP2 64-bit up to date to its EOL date of April 2017.
I may have originally posted the guide in March 2019, but it has been tested on a regular basis and was last tested in November 2021.

your guide also works with 32bit Vista x86 as I tested it on a friend's old eMachines T5048 media center PC running Vista Home Premium SP2 x86 - the guide should not be limited to just the x64/64bit edition