I confirm, it does work with IE6. Although you do need Windows to be activated, otherwise you'll get an genuine windows activation error. Luckily, all you need to do is activate Windows online, which only takes 30 seconds. I wonder if this method also works on Windows 2000.
Does this also work with Server 2003 ,XP x64, and XP RTM, SP1, and SP2? Those versions of Windows do not support SHA-2 which also means they would require SHA-1 signing.
As @Burdus77 found out here, if you install the LPP before the WUC patch there won't be any problem. That was before the February patch Tuesday and I had done test installs on every version of x64 vista and x86 ultimate. In all my tests the cumulative updates detected just fine. As I found out exploring further and based on what Burdus77 had said, the key point isn't to install the LPP exactly before the WUC patch but before you do the initial scan. In my tests I was able to fix this error by completely removing the Software Distribution folder and scanning again. To my understanding neither the root certificate plays any roll to this neither the Servicing Stuck. Although the new servicing stuck might made it possible without resetting the software distribution folder (haven't test it).
So, here's my findings on x86. 1 (Vista Only) and 2 (Server2008 only) work flawlessly. However when using 3 (Vista and Server2008) I get the dreaded C8000266 error. As I reported earlier this does not happen with x64. This was tested with Business and Home Premium editions. I guess that means I need to run two scans with x86. Thoughts? M2GD
The problems in x86 versions are related to RAM being limited mostly. Vista during the scan is picking on 4.6GB of RAM. Good luck with that if you are on x86 obviously
xrononautis: When you have time, can you go to post #148 and edit your code so it reflects the new IE9 cumulative security update (KB5011486)? I plan to do a new test clean install of Windows Vista SP2 64-bit in the next few days and will need to update my guide afterwards. Besides the new IE9 cumulative security update for step #18, I will be adding the new servicing stack update (KB5011942) for step #17. Thanks!
Hello Captain I have updated the post 148 with the new code. what you missed is that the mum files have also changed version from 6.0.1.0 to 6.0.1.1. I added two echo lines so that we can see some of the progress If I am allowed to joke a bit in times like these.. the new cumulative update is 199.9MB and the new MRT version is 5.99. Is this the end of the world? Nostradamus? is it you? xD
I get error 643 whenever i try to install the May 2020 update "Security and Quality Rollup for .NET Framework 2.0, 3.0, 4.5.2, 4.6 for Windows Server 2008 SP2 (KB4556402)" or any later one. The last update that installed was 2020-01. I hid all Update offers that failed with 643 until it offered me 2019-12 which installed just fine, then I unhid the 2020-01 which then installed just fine too (gave me 643 error before 2019-12 update), now there is no -02, -03, -04 update in between (crosschecked with update catalog), and the 2020-05 still fails with error code 643. A generic error code. Any idea?
Has anyone tried Windows Update for Server Only or Vista and Server Updates? It appears that the dreaded C8000266 error is back and this time it's for x64 also. Just wondering?
My2GirlsDad: A clean install of Windows Vista Business SP2 64-bit using the current steps in the guide: https://forums.mydigitallife.net/th...s-vista-sp2-64-bit-beyond-its-eol-date.83461/ was done by me 8 days ago in a Dell Precision M6700 laptop that I acquired. Everything went fine and the C8000266 error code never appeared in Windows Update.
Thank you for the clarification. The last time I did a test WU worked with the ESU LLP installed. I now know that is not the case and have removed the offending update.
You're welcome. I've tried various methods with KB4575904 ESU LPP, but can't get it to work properly, so it no longer appears in the guide.
The situation with this update is very weird. I have many VMs which originally had their first scan back in January when every version would detect the esu updates. All of them still work on every patch Tuesday. Only fresh installs are impacted as far as I can tell. Anyway it doesn't matter much at this point.