The KB5037917 update in post #57 of Abbodi1406's NET Framework repack thread is what I used. https://forums.mydigitallife.net/th...r-windows-vista-server-2008-2024-05-14.85546/
The .NET 3.5 SP1 and 4.6.2 won't install without the Bypass as I have posted screenshots of both. Both the 3.5 SP1 and 4.6.2 files are .exe files. Only the 2.0-3.0 is a .MSU file. I have no issue using the Repacks, that's what I plan to use for any fresh (not VM) installs I do later. But for others who don't want to use the repacks the Bypass will be needed. If Captain doesn't want to include the Bypass then I suggest links to the repacks should be included in the OP. Saves people posting questions like "Why won't the 3.5 or 4.6.2 updates install?" later, but I'll leave that up to Captain to decide.
From what I can determine, there doesn't appear to be any update for June 2024 "patch Tuesday" for Microsoft .NET Framework. Someone else can correct me if I'm wrong. There's a new Servicing Stack Update (KB5039341), so a change has been made to step #16 of the guide.
Windows Server 2008 running on Hyper-V cannot boot after installed 2024-06 cumulate updates or 2024-03, 2024-04, 2024-05 cumulate updates, but Windows Server 2008 on VMWare can boot successfully, I don't know why. Is this caused by the Update's or other issue?
When I do a clean install of Windows Vista SP2 64-bit, I do it in the normal manner. I don't install it in virtual machine(VM) mode, as most here appear to do. It's my guess that's why I don't experience some of the issues they do, and vice versa. It would be impossible for me to make changes to the guide that everyone would agree on, so it'll stay with its current steps for now. These are the updates that Windows Update detected and installed in my Dell Precision M6700 laptop today which was already up-to-date to May 2024:
I always wondered why the official installer was so large! Could never work out why it was so bloated compared to all the other installers. These are the installers I have used in the past and on VMs with a batch script I made to install them all in one go. But I'll definitely use the repacks going forward,
The guide in the original post has been updated to reflect changes to step #18. The changes made: Added KB5040426 cumulative security update for IE9 - which updates it to 9.0.320. Edited the .bat file with the new KB number so the IE9 update can be installed. Windows Update detected these 2 updates: KB5040499 security monthly quality rollup KB5041024 security and quality rollup for .NET Framework 2.0, 3.0, 3.5.1 SP1, 4.6.2 KB5040499 installed fine, but KB5041024 failed multiple times to install. After a restart was done, I obtained and installed KB5039882 for 4.6.2 and KB5040673 for 3.5.1 SP1. After another restart was done, Windows Update detected KB5041024 again. It installed successfully this time. There was no servicing stack update.
You need to pay attention to steps #20 and #21 and #22 and #26 of the guide and follow them correctly. Make sure to do a restart after completing each step. If you do, Windows Update should work fine, and you should be able to install the Vista updates and Server 2008 updates.
It doesn't work even with Vista_SHA2_WUC because they are removing (and readding) the compatible cipher suite https://forums.mydigitallife.net/threads/restore-windows-update-for-vista.82336/page-16#post-1836843
I successfully tested the guide in its entirety on May 17th, so I won't be doing it again any time soon. If the Vista_SHA2_WUC WU_Fix_For_Vista_WS2008 tools are no longer allowing Windows Update to work, my guide will become useless.
This guide should continue to work as long as the WU_Fix_For_Vista is applied. I'm still able to receive updates on Vista. I will do another test tonight. LegacyUpdate doesn't have the same restrictions that MS has implemented. This is the reason why Windows 2000 and XP can continue to receive updates from LegacyUpdate. Windows 2000 and XP have long since been abandoned by MS. LegacyUpdate fixes that. So it will continue to work on Vista as long as it continues to be developed. How long that will be? Only the Dev of LU knows that.