If xrononautis is too busy or unable to do it, can someone else go here (post #148) and replace the current code with the new code in this thread (post #400) that Burdus77 submitted? Changing both the "KB" number and the "mum" number resulted in the script working correctly and installing the new IE9 update - which brought it up to version 9.0.275. Once that is done, I will be able to edit and update step #18 in the guide. Burdus77, thanks! How did you determine the new "mum" number is 6.0.1.1?
Hello all! I have updated the post 148 with both old and new code with the parts that needs to be updated every time in bolt so that people can easily make it work in the future IE version updated to 9.0.275 with the latest CSU. In order to see the mum version you don't necessarily need to unpack it. Personally I am just opening the msu file with 7zip and then double click the main cab file to see the contents.
After following my update order from post #310 but with the new SSU and CSU and installing all the Vista updates, after switching to Server 2008 updates I get the C8000266 error when searching for updates unless I remove the ESU LPP.
xrononautis: Thanks for making the change to the code in post #148. I will be updating step #18 in my guide shortly. I saw these 2 additional lines in the new code. I only changed the "KB" number and the "mum" number, and the new code worked fine with installing the KB5011486 IE9 update. What is the purpose of the 2 additional lines?
ExtremeGrief: I plan to do a new clean install of Windows Vista Business SP2 64-bit later today or early tomorrow. I am still updating some of my Windows 7/10 computers with the March 2022 "patch Tuesday" updates, so I want to get that done first.
The latest SSU definitely seems to be causing some issues. Did a clean install today. Less updates were showing than previous installs I've done and no update past 2020 seem to show up in WU again. I'm setting up some more VMs and doing some more testing tonight!
I will do a clean install as well. So far I tried my old VMs of different versions and I got this error in two of them WS2008 and Ultimate 64bit. I couldn't get it to work even after resetting the Software Distribution folder. The rest of them VMs though detected everything correctly (Enterprise, Business, HomePremium). All of the above VMs were updated in February. I will do a clean install soon and see what happens. The first thing that I will try is with and without the newest servicing stack. Captain: The "echo" is just a way to present a comment on the screen. It will just show the message. It is not essential to the script. I should add that none of the above VMs had a root certificate newer than 2021-10 or the newest SSU.
xrononautis: Thanks for the explanation. I edited step #18 in the guide to include all 9 lines of the script. In reference to what I said to ExtremeGrief in post #408, I will be using the newly edited guide to do a clean install of Windows Vista Business SP2 64-bit. I plan to do it later this afternoon and evening, or after I wake up tomorrow morning. Hopefully, everything will go well like it did in January.
Looks like everyone had problems updating Windows Vista after March 2022 Patch Tuesday, it looks like Microsoft broke something. Hopefully we will be able to find a way to fix the problem.
I've tried doing another clean install without the latest SMQR and only using the SSU from Feb, but still having issues. The usual error code popping up now. So it isn't the latest SSU or SMQR causing the issue. Think this is something Server side that has changed. I haven't tried the latest Root Cert update yet, only the 2021-10 version. Removing the ESU licence prep package does allow updates to run again for me and picks up the server updates, but the latest SMQR doesn't show up again, same as it was a couple months ago. Back to manually installing that one!
Think I might just give up on that ESU licence prep update! It's the one that seems to cause the issues every time. If it means I have to manually install the latest SMQR every month, then it's no big deal for me.
I just finished updating the last of my dual boot Windows 7/10 computers with the March 2022 "patch Tuesday" updates. I will be starting a new clean install of Windows Vista Business SP2 64-bit shortly in my Dell Precision M6400 laptop. Hopefully, I will have good news later this evening or tomorrow morning. I will be following my guide exactly as it is currently posted.
I was successful with steps #1 through #22 of the current guide, then things went downhill from there. I have been at it for several hours, so I am going to take a break and get some sleep. I used the 02-2022 root certificate, so I am going to start over and use a different one that worked twice 2 months ago. Burdus77 may be correct about the KB4575904 ESU LPP update returning to haunt us.
I've just gotten into the habit now of manually downloading the SMQR, .NET Security Quality Rollup and IE9 CSUs every month, in case those error codes ever reappeared. I did all the same steps that l did that resolved the error previously and just can't get it to work properly with that ESU LPP installed. Once it's removed it's problem solved for me. And it's only the latest SMQR that doesn't show up. The latest .NET Rollup shows up fine. So, I'm just taking the ESU LPP out of the equation for me, as it's the only one that seems to cause me the error codes. I'm fine with just installing the SMQR and IE9 CSU manually every month if that's the worst case scenario. No problem, everything else seems to download and install fine. I've tried both the 2021-10 and 2022-02 Root Certificate updates and same issue with both.
Burdus77: I'm going to do another clean install today and leave KB4575904 ESU LPP out of the mix. The current KB5011942 SSU and KB5011486 IE9 CSU will still be manually installed. Without KB4575904 in the mix, Windows Update should work fine to obtain Vista and Server 2008 updates. The current KB5011534 SMQR will also be manually installed.
This month, on Server 2008 SP2 VM, it installed only KB5011543 (LCU). After rebooting, I checked IE9, and it was automatically updated to the latest version. Wouldn't that mean that, at least for legitimate Server 2008 installs, IE9 update is integrated into LCU?