plangg: Assuming you used the guide in post #1: After completing step #25, did you complete step #26 before running Windows Update in step #27?
The purpose of Vista_SHA2 is to port the WUC client 7.7 from WS2008 to vista because you cannot install it on vista the normal way (no point installing it on ws2008). For ws2008 install the long scan related updates, sha2 update and latest servicing stack. (You will have to restart after sha2 update) After that it should work with the updates up to January 2020. For the esu you need the esu license preparation package (only the later, skip the first) and WS2008 ESU patch from Abbodi.
skorpion68: Thanks for the new March 2024 root certificate. It's been about a year since I last tested the guide from start-to-finish, so I plan to do it again in the next few days.
Today, I did a clean install of Windows Vista Business SP2 64-bit and got it completely up-to-date to March 2024. The current guide in post #1 still worked fine, so no changes needed to be made to it. Note: If you have an issue with getting all of the needed drivers to install, wait until AFTER you've installed KB4474419 for SHA-2 support. Those drivers should then install fine. Note: If you see a red code warning when doing a "check for updates" in Windows Update, try again. It should work okay and display and install the updates.
Updates for April 2024 "patch Tuesday" for Windows Vista SP2 (already up to date to March 2024): KB5036932 Security Monthly Quality Rollup For Windows Server 2008 KB5036607 Security & Quality Rollup For .NET Framework 4.6.2 For Windows Server 2008 SP2 There were no updates for Servicing Stack or Internet Explorer 9.
CaptainSpeleo, have you had any issues with Windows Update on Vista this past week? I have tried to do several clean installs on VMs and Windows Update fails to work on all of them throwing up error code 80072EFE. I've had no issues on previous VM installs following the same steps. I have 3 different Vista ISOs: One is SP2 without updates, one is updated to 2017 and one is updated to 2021 with Server 2008 updates, I can't get windows update to work on any of them from a clean install. This has only started happening this week for me. Trying to work out what is causing the issue but this seems to be affecting all of my Vista clean installs now. I'm not having any network issues or problems updating other OS. Just Vista.
Same here. Both VMs and laptops. Versions Ultimate, Enterprise and Server. I tried with datastore fix as well but seems to be irrelevant.
The guide in post #1 shows the entire list of steps that I used when I did a new clean install of Windows Vista Business SP2 64-bit in my 3rd generation Dell Precision M6700 17.3" laptop on April 7th. When April 9th patch Tuesday arrived 2 days later, I started the laptop and loaded Windows Update and did a "check for updates". It detected and installed the KB5036932 Security Monthly Quality Rollup for Windows Server 2008. It also detected the KB5037041 Security & Quality Rollup for .NET Framework 4.6.2, but it failed to install. I then obtained and manually installed KB5036607 Security & Quality Rollup for .NET Framework 4.6.2. As to your question, there were 2 times during the process that a red warning code appeared shortly after I did a "check for updates". I was afraid it was going to bring the updating process to a halt, but when I clicked "Try again", it worked fine. My laptop normally stays packed away during the month between patch Tuesdays, so I won't be using it again until May 14th.
I always got the red warning on the first update attempt every time I did a clean install, running it a second time always sorted out the issue. Now I get that error every single time and nothing I can do to get past it. I'm hoping this is just something temporary but seems I'm not the only one having this issue. Everything was working fine until this week. Now none of my Vista installs will update and can't get past the error no matter what I try. Previously working installs and clean installs, WU just won't work for me right now. Like I said, I hope this is a temporary issue on MS end. I have made no changes to the way I have always installed the updates. Will have to wait and see.
Hello Captain! You still have Business edition right? I am installing a VM with Business to check if there is any luck.
Burdus77: Now that I just recently did a test of the guide in post #1 from start to finish, I don't plan to do it again for several months. I'll keep this thread updated with what happens after every "patch Tuesday". xrononautis: Yes, I use a Windows Vista Business SP2 64-bit disc for all my testing. I obtained the ISO for it in November 2020 and created the disc at that time. The file size is 3.59 GB and is version 6.0.6002.18005 and is dated April 2009. I use DAZ 2.2.2 for activation after the initial clean install is done.
As a Temporary workaround I have installed Legacy Update which works fine and can detect and install updates without issue. I can switch between both Vista and Server 2008 updates using the Vista_SHA2_WUC patch. MS must have changed something on their end that is now blocking the update check from working on Vista. Not sure if it's a temporary issue or permanent.
May be you're right. I checked and installed updates from windows update on patch Tuesday, the next day I got the same error code as yours.
Looks like abbodi1406 has found the cause of the latest WU error. https://forums.mydigitallife.net/threads/restore-windows-update-for-vista.82336/page-15 Windows Update now requires more modern cipher suites that aren't currently available on Vista/Server 2008. I'll be using either the LegacyUpdate server or WSUS Proxy from now on, as these still work fine.