I did some more testing yesterday and what I found is that kb3078601 applies on a fresh install but doesn't apply any more after I install kb4012583 kb4015380 kb4019204. Those are related to the long scan issue hence they were always the very first that I would install. What is even more interesting is that all 3 of them have to be installed for the kb3078601 to stop being applicable. Today I managed to resolve a problem that was bugging me for quite some time. Basically ie9 would crash no matter what I did after the installation of ANY cumulative (be it for vista be it for WS2008 be it ESU didn't matter... just crash). Apparently the cumulative enables by default gpu rendering while my desktop was on Vista basic colors.... go figure... I guess that this happens to me on the VMs because my host has dual gpu which wasn't common in the vista era. Hence it kind of applies only on VMs and not on real hardware. Anyway it is funny how we often go for complicated solutions when the solution is very simple and in front of our eyes... After I solved this I was able to focus on the script for the cumulative installation and I found another very simple solution when I was looking for a complicated one. So read beneath @CaptainSpeleo I have a new script for the installation of the ie9 cumulative. It is ExtremeGrief's script I just slightly refined the "find string" line to include the whole kb and architecture instead of just kb. That way we need to change only the kb number at the top every time we have a new ie9 cumulative instead of kb number in 3 places places along with the mum versions while the same time it won't try to install everything in the current folder. Enjoy!! Code: 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 updated the script with a CD.. instead of homedrive.
I see that's actualy understandable KB4012583 replace all components of KB3078601, except Win32k & GDI KB4019204 replace Win32k KB4015380 replace GDI
Thanks! I will try it out during my next clean install and update. Is the word exit at the very bottom, is it part of the script?
Hi Captain , you can ignore that word ~~~ and I couldn't understand why it need to go to the system drive before delete \tmp CD %HOMEDRIVE%\ %HOMEDRIVE%
OKIC，Thanks , I missed this line CD "%~dp0\tmp" BTW , which edition you guys used normally I found that Ultimate edition would get more updates than enterprise edition except Ultimate Extras
Could anyone do me a favor for a test when you're free ? install any 64-bit edition you like as normal reboot , then go to the Sysprep (CTRL+Shift+F3) fully follow CaptainSpeleo's instruction till #24 to #27 (all runs well) then reboot and continue to #28 Winload.exe Status 0xc000428 occurs after Windows Server 2008 64-bit important updates be detected and installed (Windows cannot verify the digital signature for this file) I changed two laptops three 64-bit editions and all got the same error ~~ does it meant something modified the file or missed ? Live system never get this problem ~~~
I am in the process of doing a new clean install and update in my 3rd generation Dell Precision M6700 laptop. I will be eliminating steps #2 and #3. The device drivers that do not install will be done after step #22. The entire process will take a few hours, so I will post the results later today.
#2 Is still needed in my opinion. Although personally I do it after the first restart together with IE9 and .net 4.6.2 The script is now updated with cd.. instead of homedrive as Abbodi1406 suggested. I wonder if the whole for /f could be rewritten in a way that it never does cd %~tmp0\tmp in first place. My focus is elsewhere though at the moment. What drivers are you having problem with? you could maybe extract the inf files. It seems to me that the dotnet requirement has to do with the bloodware accompanying the drivers and not the actual drives themselves. If you can upload the particular driver I could have a look.
xrononautis: I used this previously suggested 10-line script file, and it worked fine with getting IE9 updated to version 11.0.285. Since it does, I am going to use it in the next updated copy of the guide. 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 %HOMEDRIVE%\ %HOMEDRIVE% RMDIR /S /Q "%~dp0\tmp" Without installing NET Framework 3.5 SP1 and 4.0 immediately after installing Windows Vista SP2 64-bit, all of the drivers did not install in the normal manner. I easily resolved that issue by extracting their contents and then installing them in that manner. Once that was done, I established an internet connection and installed all the necessary KB updates and NET Framework 4.6.2. Vista_SHA2_WUC (options #1 and #2) were used, which allowed Windows Update to detect and install a total of 266 Vista/Server 2008 updates. Everything proceeded fine up until that point and updated Vista/Server 2008 to January 2023. Unfortunately, things went downhill after that. The February 2023 KB5022734 NET Framework update that was detected by Windows Update kept failing to install, even after deploying dotNetFx4_ESU_Bypass_Vista. The February 2023 KB5022890 Security Monthly Quality Rollup was not detected by Windows Update, so I tried to manually install it, but it displayed "This update does not apply to your system". If there is a way to get these post-ESU updates to install, please let me know.
For my installed yesterday with Ultimate Edition The February 2023 KB5022734 NET Framework update install by BypassESU-v7-WS2008 #5 The February 2023 KB5022890 Security Monthly Quality Rollup installed automatically Vista_SHA2_WUC options #2
I am not familiar with BypassESU-v7-WS2008 and have never used it. Where within the steps of the guide is that tool supposed to be deployed? Okay, I just found it in the Windows 7 section. https://forums.mydigitallife.net/th...urity-updates-eligibility.80606/#post-1560451 I deployed the option to install the NET Bypass, and it allowed KB5022734 to install. I then deployed the option to install the ESU Suppressor, but KB5022890 still displayed the "This update does not apply to your system" message. I am obviously doing something wrong.
That's it ~~~ shake hands with @abbodi1406 you would get two or three updates failed install that meant almost finish with Vista_SHA2_WUC options #2 BypassESU-v7-WS2008 #7 help to do remains
I finally gave up and formatted the SSD that Vista/Server 2008 was installed in. As soon as someone shows me what I need to do to get to the point of getting the February updates to be detected and installed, I will start over from the beginning. It has been a long day, so I am going to take a break until tomorrow.
I forgot about deploying Vista_SHA2_WUC (option #2) first, then deploying WU_DataStore_Fix immediately afterwards, then doing a Windows Update scan for Server 2008 updates. Leaving WU_DataStore_Fix out of the equation is what probably messed things up. I will find out tomorrow after getting some rest and starting again with a clear head.
I always do as following Vista_SHA2_WUC option #1 、#2 finished one by one BypassESU-v7-WS2008 #7 just for .NET Bypass
@CaptainSpeleo and now I succeed ~~~Cheering revised script BypassESU-v7-WS2008 #7 (no #5 , bad memory ) today I write the ISO as Bootable USB & intsall till now it finished all updates Vista + 2008 and I need to patch Update Agent (wuaueng.dll) from 7.0.6002.18005 to 7.7.6003.20555. Three times I think some updates would rollback the DLL file (not sure which one , no more Winload.exe 0xc000428 ) Aloha Heja He~~~