After the issues which I encountered yesterday, I started from scratch and made some changes and was successful. The new guide with several changes has been posted. Everyone may not agree with what steps I used, but it's what worked for me. I checked wuaueng.dll occasionally after deploying Vista_SHA2_WUC for the very first time. Its version remained at 7.7.6003.20555 until the very end of the update process. Now we wait until March 2023 "patch Tuesday" to see how well Windows Updates works at detecting and installing the newest Windows Server 2008 updates.
Vista_SHA2_WUC use patched wuaueng6.dll (which remain at 7.7.6003.20555) the original wuaueng.dll is not touched, although it would remain at 7.7.6003.20555 on Vista because WUA is exempted from installed components in Server 2008 updates i checked the latest wuaueng.dll 7.7.6003.21442, they still didn't backport the supersedence calculation fix (long scan issue) from Win7's KB3172605
abbodi1406: I got pretty frustrated yesterday, but I decided to give it one more effort. After getting Vista_SHA2_WUC option #1 to install a total of 197 Vista updates, I switched to option #2. After rebooting, I deployed WU_DataStore_Fix and selected the option to apply the datastore fix. After rebooting again, I loaded Windows Update and did a scan. After getting a total of 70 updates for Server 2008 to install, I was left with the KB5022734 NET Framework update which kept getting detected and kept failing to install. I then deployed BypassESU-v7-WS2008 and selected the option to apply the NET 4 bypass. After rebooting again, I loaded Windows Update and did a scan. This time the failed update successfully installed after it was detected. Since these 3 tools worked in the manner that I used them, I am going to leave them in that order and method in the guide. Now I am waiting to see what Windows Update does after March 2023 "patch Tuesday" arrives. This is my current lineup of updates and tools: The wuaueng.dll comment was directed towards frankielong who apparently is having an issue with its version. (post #700)
I don't use WU_DataStore_Fix , and can't find IE9 windows6.0-kb5022835 yesterday , patch it use xrononautis's script also I hide KB830890 , I catch a snapshot of update list & Installed update ~~~
I was a bit hesitant about using WU_DataStore_Fix, but it seems to have helped, so I'll continue using it for now. I discovered that Vista is supported by 3rd generation Intel and older, but it's not supported by 4th generation Intel and newer, so I don't know how much longer I'll be able to keep testing. My Dell Precision M6700 laptop which is used for testing is 3rd generation Intel, and I may be donating it in the near future to a family member. My other laptops are 4th generation Intel, and my desktops are 4th and 6th generation Intel, so they can't be used for testing.
You read my mind! I was about to write a thank you to @abbodi1406 for the WU DataStore Fix! That has solved all the issues I was having whenever I installed the ESU Licence Prep update. Now it's working as expected and WU always picks up the latest monthly updates. I install all the Vista updates first, then I Patch to Server 2008 using Vista_SHA2_WUC, then install the licence prep update, and then use the DataStore fix. Works every time!
My image in post #703 shows the sequence that I use to install updates and use tools. I may do another full testing over the weekend, just to re-confirm my most recent testing.
I just finished completing another clean install and update of Windows Vista Business SP2 64-bit. The exact same steps were used today that were used yesterday, and everything went fine. 203 Vista updates and 65 Server 2008 updates were installed. A few very minor edits were made to the guide. Now we wait until March 2023 "patch Tuesday" to see how Windows Update reacts, and if the DataStore and NET Bypass tools need to be re-deployed.
DataStore fix is only needed for first scan, but you should not remove it afterwards .NET Bypass is needed for every new .NE 4.6.2 update (within .NET Rollup)
I tested the most recently updated process on a VM and I'm able to get all the updates needed from Windows Update. However, I noticed the following issues: - When installing .NET 4.6.2, the .NET Runtime Optimization console showed a lot of errors. I don't remember the details, but it seems the process could not find some particular files. The installer still considered the installation of .NET 4.6.2 successful, though. I wonder if those error messages are normal for this part. - The IE9 update (KB5022835) doesn't appear to work, even after applying it using the batch script in the guide. The version numbers remain unchanged. IE9-related updates offered from Windows Update, however, installed fine and those updated IE9 to 9.0.167.
Did you restart the computer after applying the batch script with the KB5022835 IE9 update? If you did not restart, the version will not show 9.0.285.
I did restart as instructed. It doesn't appear to work. I restarted several times afterwards, and even re-attempted the batch script several times (restarted the system after applying)... still not working. IE9 updates offered by Windows Update after enabling Server 2008 updates, however, do work, and my IE9 is now on 9.0.167.
Does this work for you? mkdir .\tmp expand.exe -f:*Windows*.cab *kb5022835-x64*.msu . >nul expand.exe -f:* *kb5022835-x64*.cab .\tmp >nul start /w PkgMgr.exe /ip /m:"%cd%\tmp\package_2_for_kb5022835~31bf3856ad364e35~amd64~~6.0.1.1.mum" /quiet /norestart start /w PkgMgr.exe /ip /m:"%cd%\tmp\package_3_for_kb5022835~31bf3856ad364e35~amd64~~6.0.1.1.mum" /quiet /norestart del /f /q *kb5022835-x64*.cab rd /s /q tmp
LSS7777: Copy the 7 lines that Burdus77 provided into a Notepad text document window, then save that document. Type in a name for that saved text document, and change its extension name from .txt to .bat Ignore the warning message about the file being unusable if its extension name is changed. Place that .bat file and the KB5022835 update inside an empty folder. Right-click that .bat file, then select to run it as Administrator. A small window will appear and the integration process will begin. After about 30 - 60 seconds, the small window will disappear. Restart your computer, then wait for it to settle down from the restart. Load an Internet Explorer browser window, then click "Help - About Internet Explorer". Its version will appear in the small window, and it should be 9.0.285
the system can be installed in 4th gen or 6th gen Intel platform I have tested but the drivers suitable for Vista only in 3th or lower ~~~~
try this one from @xrononautis it runs well ~~ I suggested install it after all the updates finished mkdir "%~dp0\tmp" for /f "usebackq delims=|" %%f in (`dir /b "%~dp0" ^| findstr /i windows6.0-kb5022835-x64`) do copy %%f "%~dp0\tmp" CD "%~dp0\tmp" expand -f:*windows6.0-kb*.cab *.msu "%~dp0\tmp" expand -f:* *.cab "%~dp0\tmp" for /f "usebackq delims=|" %%f in (`dir /b "%~dp0\tmp" ^| findstr /i package_2 ^| findstr /i .mum`) do start /wait pkgmgr /ip /m:%%f /quiet /norestart for /f "usebackq delims=|" %%f in (`dir /b "%~dp0\tmp" ^| findstr /i package_3 ^| findstr /i .mum`) do start /wait pkgmgr /ip /m:%%f /quiet /norestart CD.. rmdir /s /q "%~dp0\tmp"
I eventually got it updated using this one. Many thanks for everyone's help. Guess the problem might be related to UAC. Back then with the batch script in the OP I simply double clicked the script and it showed a few extraction operations, then I got two PkgMgr UAC prompts which I permitted, but it doesn't appear to have run successfully, as the window disappeared very quickly. This time I opened a command prompt as administrator, CD'd to the path I put the files, and ran Burdus77's script. It properly installed the update and after reboot I'm now on 9.0.285. Note that you can't just right click on the batch script and choose Run as Administrator. That would not work, most likely because the admin console used to run the script uses a different working directory than the path where the script resides. It might also be the reason why the script previously failed when I double clicked it directly, as the elevated parts of the script also ran from the different working directory in question, which derailed the find operators so PkgMgr did not really find the files needed to be installed, even though they were present. So I think it's advised to disable UAC during step #20 to avoid the hassle of having to start a Command Prompt as Administrator and manually CD to the path where the files are.
LSS7777: I disable UAC right after Windows Vista SP2 64-bit is installed to avoid any risk of it causing any issues. I also hate its annoying pop-ups. frankielong: I've already tried to install Windows Vista SP2 64-bit in my 4th and 6th generation Intel computers, and it fails to do so. They'll boot from the disc and generate a "Press any key to boot from CD or DVD" message, but nothing happens afterwards. I have no problem with my 3rd generation Intel and older computers.