OK, so, I just went through and uninstalled the bypass (I even ran the .bat remover 3 times to make sure the bypass was uninstalled), then downloaded & installed the Feb SSU. As far as I can tell, the install of the Feb SSU was successful. After installing the Feb SSU, is it necessary to restart the computer? And, if a restart isn't necessary, do I now simply wait for the March 2020 ESUs?
I notice you can install the 2020-02 rollup WITHOUT installing v4 fix, but of course it only breaks after a reboot when applying system modification. Ha! So it seems the final check for valid ESU may be at very last stage of install process of .msu file. I was expecting it would break as soon as you try to install, but no, at bootup stage. Interesting! Seems to me, in future slipstream may be possible which will be good.
So i guess that is because of missing updates. Make sure that these 3 prerequisites updates are installed on your machine before installing the bypass : KB4490628 -> KB4474419 -> reboot -> kb4536952 if one of them is missing, download them from MS server.
I hate to add to the confusion, but I successfully installed the Rollup update for Windows 7 x64 (KB4537820) directly after installing ESU bypass and without installing KB4528069. The only thing installed on the computer is KB4537820. I've since removed the bypass.
Okay so that worked, i was missing KB4490628. I installed the kb4528069 and installed february 2020 updates. Now i'm just waiting for this tool to allow windows update to download automatically these updates
Does it still make any sense to install the test update KB4528069 now ? The february updates were successful without this test update, I have this file on my hard disk though. No, or ?
Hello. Just want to confirm that you can Code: run installer.bat > install KB4528069 > run remover.bat > install Servicing Stack Update and Security Monthly Quality Rollup all without rebooting in between? I know you have to reboot after, just making sure whether you need to in the middle of it.
Hi, I tested on a fully updated till 2020-01 group A virtual machine, switching to group B, and installing KB4537767 and KB4537813. Then, after running cleanmgr.exe, nothing appears for windows updates to be cleaned. Is this normal?
@agony111 it will not hurt to keep the test update @liam2 security only updates do not supersede monthly rollup
OK, so from what I'm gathering by the posts made after my most recent one... With the successful install of the Feb SSU (thanks to the test update) after the successful uninstall of the bypass, it's waiting time for March's ESUs & then see if anyone is able to install them without the bypass. If so, that means all the bypass was ever needed for was to install the test update. If not, then that means a new version of the bypass would have to be developed & distributed to the users here.
Hello everybody. Thanks for providing a tool to keep Windows 7 alive! I've been reading the 68 pages long forum, and found a lot of useful and misleading information. What I've gathered so far, is that the bypass needs to be updated to allow the installation of the February SSU KB4537829 which might be necessary for the March ESU updates. The recommended steps here to get the February ESU updates are: 1. Install BypassESU v4 2. Install Test update KB4528069 (can be installed using older (January) SSU) 3. Remove BypassESU 4. Install KB4537820 (Security Monthly Quality Rollup) or KB4537813 (Security Only Quality Update) + KB4537767 ( Cumulative Security Update for IE) 5 Forget about February SSU KB4537829 for the time being Without Test update KB4528069, it seems we can't install ESU updates. I found on another site, the following steps which enabled the installation of all the updates including February SSU KB4537829 1 Install the bypass. 2 Install the ESU Test update. 3 Remove the bypass. 4 Install the SSU KB4537829. (Installed before any security updates) 5 Install the KB4537820 update. Has anyone tried that? Does it work? Thank you for reading me.
Where can i find the latest updates released for software? Like that Cumulative Security Update for IE, which cant be found on windows server 2008 r2 update history.