The 2 root certificates shown in step #2 of the current guide allow KB4575904 ESU LPP to work without breaking Windows Update and generating an error code message. This may be a coincidence, but as most of us already know, KB4575904 ESU LPP did not previously work with Windows Update when the former root certificate was used. As long as the current ones allow Windows Update to display and automatically install post-EOL updates and not generate an error code message, I will use them.
I am working on some scripts that will walk through the updating process automatically with restarts in between and everything. One of the obstacles is IE9 Cumulative Update the one that needs to be installed through pkgmgr.exe. When I run the script from the GUI runs just fine but when I run it in the pre gui environment I get the message that the pkgmgr.exe was not found. Any ideas? Should I just copy pkgmgr.exe in the folder with the script or should I CD to the system32 folder and run it from there? Shouldn't it be able to run the same way it run through the GUI? An other problem is that I am trying to call the dotnetfxbypass installer.cmd and remover and install .net 2022-01 Cumulative in between but running the .cmd file is the last thing happening. It runs it properly but doesn't nothing else after that. Any ideas?
The next "patch Tuesday" is only 2 days away, so I'm looking forward to seeing if Windows Update automatically displays February 2022 updates. I'm guessing there will be a security monthly quality rollup, but will there also be a .NET Framework cumulative update or IE9 cumulative update or servicing stack update? 2 separate installs of Windows Vista SP2 64-bit are in my laptop which were done per the steps in the current guide, so I'll be checking each one.
Run "C:\Windows\System32\pkgmgr.exe" not just pkgmgr.exe .NET ESU bypass script needs edit to be able to work, I can help on that, but...why? I can install .NET ESUs just fine without it
Same here I have been storing the VMs after updating them instead of deleting them and I will be able to check all versions of vista this patch Tuesday. Thank you I will try the full path and come back with the results. Regarding .Net the only one that I can install without .netfxesubypass is the 3.5 cumulative. 4.5.2 and 4.6.1 will fail if I don't have the bypass. Also I still cannot detect updates for 4.6.1. Only using the option 1 detects something but it is from 2016.. ancient even for Vista's own EOL. I did an installation where I followed the guide to the letter even the restarts... Still same results. What leads you to believe this? Although definitely we have seen huge difference in the way that windows update works now. Still the latest SSU came after almost a full year after the one before it.
I have tried literally all of them when it comes to 64bit and Ultimate when it comes to 32bit. Business is the one that I did the most test runs in the past since it was the only one to be able to detect the cumulative. Since the last month I am testing mainly Ultimate x64 but I did all of them at least once.
abbodi1406: Thanks for the link to that tidbit of information. I entered KB5010452 at the Microsoft Update Catalog site to see if it has been posted in advance, but it has not. This is the list of updates that I currently use after doing a clean install of Windows Vista Business SP2 64-bit - which was last done on January 22th and 24th. According to the the article in your link, it appears that KB5010452 will take over KB5006750 in #14. I wonder if there will be a new IE9 cumulative update to take over KB5006671 in #15? If there is, the script from xrononautis will need to be modified to reflect the new KB number.
It appears some members here are not yet aware that M$ lifted NT 6.0 sanctions on .NET Framework 4.6.2 and made that the LAST Server 2008 (ergo Vista) SP2 compatible/installable version... msfn.org/board/topic/175262-last-versions-of-software-for-windows-vista-and-windows-server-2008/?do=findComment&comment=1207652 msfn.org/board/topic/181612-wip-windows-vista-extended-kernel/?do=findComment&comment=1207413 ... Using option 2 (and the bypass?) should now detect available updates, if any... 4.6.1 was never officially supported by MU on Vista SP2 and was not supported on WS2k8, either... support.microsoft.com/en-us/topic/-net-framework-4-5-2-4-6-4-6-1-end-of-support-faq-72b7d8ca-3057-4f0c-8404-67305d40cc04 (Forum software won't let me post proper links... )
I didn't know that! Thank you so much for your information. Now I can delete the 4.6.1 installer and keep only 4.6.2 since it is the latest version for Windows 6.2 as well. I will have a look on how it behaves with the different options of WUC patch. Edit: It installed fine and detected updates just fine as well (I checked with option 3)!! The only update that this needs is the latest ESU Cumulative for 4.6.x and 4.7.x (kb5010458 for 2022-02). As a result of this kb2763674 (SHA256 app signing related) and kb4474419 (SHA2 Support) update needs to be installed in the system before you can install .net 4.6.2 and therefore it cannot be so early in the update process (who cares ). Edit: Updated KB numbers
What about .NET 4.7+? Does it get updates via MU? Does it even allow installing updates manually from win7 or something like that?
Windows Update just updated itselt to wua 7.6.7600.256. That is funny... I hope we don't have complications with the patch that has the 7.7 ported from WS2008. Edit: It worked wua7.6 was able to detect things.
kb5008859 is being part of KB5009722 in vista and part of KB5009719 in Seven. It applies to .Net4.6.x and .Net4.7.x but it is the exact same update with save hash. Exactly as abbodi says above. Edit: Upon reading again abbodi's comment I see that he meant something else. The latest cumulative update for .net4.6.x updates the .net version to 4.7 and they are the same for both 4.6.x and 4.7.x so maybe we already have 4.7.x in a way.
I had this problem too, it seemed to have been caused by me installing a language pack from WU. After installing the new WU client from control panel I got some early 2009 WUC..