First of all thx for all the hard work on this I followed the offline/WIM guide and installed the feb updates >> KB4538483 -- ESU Licensing Preparation Package KB4537813 -- 2020-02 Security Only Quality Update for Windows 7 for x86-based Systems KB4537767 -- 2020-02 Cumulative Security Update for Internet Explorer 11 for Windows 7 for x86-based systems KB4537829 -- 2020-02 Servicing Stack Update They all have been properly installed (IE version 11.0.9600.19626) After installation and checking Windows Update it gives me >> 2020-02 Security Monthly Quality Rollup for Windows 7 for x86-based Systems (KB4537820) Can i skip this one? since the others are already installed? Thx in advance.
@pegasus80 2020-01 Security Monthly Quality Rollup for Windows 7 for x86-based Systems (KB4534310) is installed on this system, should be ok then Thx for confirmation
Hello how are you? first congratulate them for the new version of bypass 5. I already tried it on a pc with windows 7 home basic and unfortunately it did not work, since I installed all the requirements that I was asked for except KB4474419 August 2019 that I did not let it install (I understand why I had several with the same number of kb and more current than August). The problem is that when I open Live OS Setup, I appeared with option 2, 4 and 5 and chose the 2 that was to install the wu esu patcher since option 4 was to uninstall ESU supressor. My question is what could I have failed? and try to restart then delete the SoftwareDistribution folder and throw me an error. I hope you can help me, thank you all
@abbodi1406 Yes, I miss this update error is not applicable to the equipment. Could it be that the problem is that I have to install the February update (I don't remember the kb number) that broke the bypass v4? What I did was: install that February update that broke bypass v4, then restart, then delete bypass v4, restart, install a January update that microsoft did not send me via WU and was necessary for the bypass V5. And restart and then install bypass 5 but I left options 2 4 and 5 and chose the 2 that was to install the wu esu patcher (the first recommended one did not appear to me) and from there I deleted the folder and everything and it did not work. Will it be that bad bypass v4 was uninstalled? I would really appreciate your help, thanks
v5 can work with January SSU KB4536952 or February SSU KB4537829 You mean WU did not offer 2020-02 Monthly Rollup after restart?
1.So if i want to intergrate the ESU KB Update inside a Windows 7 ISO You should Instal This ESU Suppressor? 2.How To Intergrate ESU Suppressor Inside Windows 7 ISO?(If That Possible) 3.Can Esu Suppressor be integrated in the modified Windows 7 Disc Image? (Example Windows 7 AIO Etc, Etc.) Can You Confirm? @abbodi1406 Thank You! ^_^ Best Regards NST_Adventure
I de- and reinstalled Bypass V5, cleared SoftwareDistribution again, and checked again against M$ WU (not the WSUS server). Same as above ;-(. This is an ancient 32 bit Win7 Enterprise, not 64 bit. Could this be the problem?
No, i have one too, and work in VM also can you verify that both sle.dll and wuaueng3.dll exist in C:\Windows\System32 after installing the patch?
Judging by the question, You have no idea what integration is; how it works .ISO and install.wim; and what is the Indexes. "*Offline Wim / Image integration " - Have you read? If the words are not familiar , You will not succeed.
Works like a charm. After everything is said and done, and rebooted the computer, It was able to discover Feb 2020 monthly rollup, and download/install it. Thanks!
@abbodi1406 nope I just throw a WU error that says something like Windows Update cannot find (or search I don't remember very well) updates for this computer. If I try to erase the entire bypass v5 with the live os setup and reinstall it I would have to take the bypass I think
i'm no longer being offered KB4537829, is this the same for anyone else? > ESU NOT activated it seems if you stop and start windows update service the system goes back into a ESU not active state.
Yes, both are there. I also compared wuaueng.dll to wuaueng3.dll using vbindiff and found wuaueng3.dll to be properly patched. However, when checking WindowsUpdate.log, I noticed some references to wuaueng3.dll on the WSUS server machine (the one which actually detected the ESU patches properly) while on the problematic machine I found only wuaueng.dll in the logfile. So I did something nasty and replaced wuaueng.dll by wuaueng3.dll in system32 and now it works. So apparently somehow wuaueng3.dll was not actually used on the problematic box... To be exact: This helped on two of two machines (on Win7 Enterprise x86 and one x64).