Bypass Windows 7 Extended Security Updates Eligibility

Discussion in 'Windows 7' started by abbodi1406, Nov 17, 2019.

  1. komm

    komm MDL Addicted

    Jun 16, 2011
    894
    3,069
    30
  2. unimbecil

    unimbecil MDL Novice

    Feb 12, 2020
    7
    1
    0
    I have a local WSUS server (Server 2008 R2) and clients (Win7 enterprise). All machines have the prerequisites of
    Bypass V5 installed. Bypass V5 is installed on all machines (WSUS server and clients) in mode 1 (Full Installation).
    SoftwareDistribution directory has been deleted and wuauserv run again.

    The WSUS server actually found the Feb ESU Updates (4537813, 4537829, 4537767 and 4537820) needed for
    itself and they can be approved. However, for the Win7 enterprise client none of the Feb ESU Updates are detected
    to be needed. But checking the Updates view on the WSUS server they appear to be known also for Win7 x86 and
    Win7 x64. So the catalogue on the WSUS server seems to be up to date.

    WindowsUpdate.log on the client doesn't reveal any errors.

    Simple question: Should this setup (Win7 enterprise being updated by local WSUS on 2008R2 with V5 Bypass
    installed) work at all? Or does it only work with M$ WU or manual install?
     
  3. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
    @unimbecil

    Did you approved and installed KB4538483 for Win7?

    the ESU Detectoids are the same between WU and WSUS, so it should work for both
     
  4. komm

    komm MDL Addicted

    Jun 16, 2011
    894
    3,069
    30
    Updates approved in WSUS does not mean they will appear on the client.
    You can see that with W10 clients, after eos, they will not find any new update even the updates are approved on the WSUS.
    Did you see the updates on the clients, if you search for them online?
    (Rename Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate to WindowsUpdate1
    restart wuauserv service
    check for updates,
    rename WindowsUpdate1 back to WindowsUpdate
    restart wuauserv service)
     
  5. unimbecil

    unimbecil MDL Novice

    Feb 12, 2020
    7
    1
    0
    > Did you approved and installed KB4538483 for Win7?
    Yep. Approved and installed (just checked again in the update history page) on both: WSUS and client...
     
  6. unimbecil

    unimbecil MDL Novice

    Feb 12, 2020
    7
    1
    0
    > For WSUS on 2008R2 KB4484071 is needed.
    Had been installed on the WSUS box and on the clients in June 2019

    > Did you see the updates on the clients, if you search for them online?
    Just tried. No, it finds only:
    - a very old Update for IE11 (2014)
    - Win Malicious Software removal tool Feb 2018
    - Win Malicious Software removal tool Feb 2020
    and a bunch of optional crap like language packs and drivers.

    But none of the ESUs of Feb 2020. Maybe I should de- and reinstall Bypass V5 again?
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    54,966
    125,941
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. haz367

    haz367 MDL Addicted

    Jan 11, 2020
    843
    1,541
    30
    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.
     
  9. pegasus80

    pegasus80 MDL Senior Member

    Nov 23, 2009
    259
    538
    10
    You can, provided that your system started using Security Monthly Quality Rollup from the beginning.
     
  10. haz367

    haz367 MDL Addicted

    Jan 11, 2020
    843
    1,541
    30
    @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 :)
     
  11. kevinmilana

    kevinmilana MDL Novice

    Jan 1, 2020
    20
    1
    0
    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 :)
     
  12. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
  13. kevinmilana

    kevinmilana MDL Novice

    Jan 1, 2020
    20
    1
    0
    @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 :)
     
  14. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
    v5 can work with January SSU KB4536952 or February SSU KB4537829

    You mean WU did not offer 2020-02 Monthly Rollup after restart?
     
  15. GreenMystic

    GreenMystic MDL Addicted

    Jun 1, 2019
    910
    207
    30
    #2116 GreenMystic, Mar 8, 2020
    Last edited: Mar 8, 2020
    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
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. GreenMystic

    GreenMystic MDL Addicted

    Jun 1, 2019
    910
    207
    30
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. unimbecil

    unimbecil MDL Novice

    Feb 12, 2020
    7
    1
    0
    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?
     
  18. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
    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?
     
  19. kamyshoviy

    kamyshoviy MDL Junior Member

    Nov 30, 2014
    53
    49
    0
    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.