Bypass Windows 7 Extended Security Updates Eligibility

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

  1. adric

    adric MDL Expert

    Jul 30, 2009
    1,468
    1,686
    60
    #7041 adric, Feb 18, 2023
    Last edited: Feb 18, 2023
    What clickable link is being talked about without running the proxy? The link from WU doesn't work for me without the proxy running.
    WU.jpg
     
  2. Sunkist

    Sunkist MDL Novice

    Dec 29, 2009
    15
    4
    0
    hello abboddi1406,

    thank you for your fast answer.
    tried this first. but on my win7 32bit VM I get this error:
    WARNING: PopulateDataStore failed: 0x8007000e (ERROR_OUTOFMEMORY).
    Is RAM meant? Can't increase, it's already 4GB. Trying to increase Pagefile...
     
  3. Sunkist

    Sunkist MDL Novice

    Dec 29, 2009
    15
    4
    0
    hello abboddi1406,

    no more ERROR_OUTOFMEMORY now.
    But still: 0x80248014 in MSE Upgrade.
    Started from scratch, meaning: datastore reset and script Run_wsus-Both.
     
  4. Mivas

    Mivas MDL Novice

    Dec 14, 2019
    33
    3
    0
  5. BernieBildman

    BernieBildman MDL Junior Member

    Apr 19, 2019
    76
    10
    0
    So, in the notes on Page 1, it says::

    "Important Notice about the .NET 4 ESU Bypass

    it has incompatibility issue and may cause MSI or other programs to stop working
    therefore, it's recommended to install it only when new .NET 4 updates are available, then remove it after installing the updates"

    Does this mean to remove it after the .NET 4 updates are installed BEFORE rebooting, or to do the reboot so as the complete the install and THEN remove it??

    Thanks
     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    52,040
    114,325
    450
    Just remove it after the updates are installed or don't use it at all but use the separate .net esu updates installer.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,810
    94,905
    340
    Thanks for testing
    i will see what i can do
     
  8. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,810
    94,905
    340
    The one says: "Check online for updates from Windows Update" under "Managed by your system administrator"

    did you ran WSUS Proxy initial scan first?
     
  9. BernieBildman

    BernieBildman MDL Junior Member

    Apr 19, 2019
    76
    10
    0
    I appreciate your answer, but it is confusing. I have ALREADY "Installed" the update, but have not as yet rebooted. My question what constitutes "installed??" Does that word mean the "install" is complete after the reboot/restart, or before??
     
  10. adric

    adric MDL Expert

    Jul 30, 2009
    1,468
    1,686
    60
    #7051 adric, Feb 19, 2023
    Last edited: Feb 19, 2023
    Yes, built new datastore and then Installed the Feb updates.. The 4.8 .Net (5022509) via .msi first and then the 2 offered updates KB5022872 & KB5022731 via WU.
    WU1.jpg
    I just tried the link you mentioned and it did not give me an error. Neither does the other link now, but if I logoff and logon and launch WU, I get the screen below and then the error using the upper left search link. The only link that works each time so far is the one you mentioned.:confused:
    WU.jpg
     
  11. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,810
    94,905
    340
    Yes, that's exactly how the Alternative method woks:
    Check online for updates from Windows Update = WSUS Proxy not needed
    Check for updates = WSUS Proxy needed

    the second option is better, since updates are released once a month generally
     
  12. FuzzleSnuz

    FuzzleSnuz MDL Junior Member

    Nov 27, 2020
    66
    188
    0
    #7053 FuzzleSnuz, Feb 19, 2023
    Last edited: Feb 19, 2023
    Yep, the guy who replied to you earlier didn't actually read your question. I'll give you a better answer.

    From Feb 2022 through Jan 2023, I used the v11 bypass like this:
    - On Update Tuesday, boot up my PC
    - Run LiveOS-Setup.cmd and install the .NET 4 bypass
    - (Re)check for updates in Windows Update to ensure it finds everything, including the monthly .NET Framework rollup (if Microsoft released one for the month, which they sometimes skip)
    - Install all updates, including the .NET Framework rollup
    - Reboot PC
    - Run LiveOS-Setup.cmd and un-install the .NET 4 bypass. Leave PC running, no need to reboot a second time.
    - Continue to leave .NET 4 bypass uninstalled until the next Update Tuesday

    This procedure has worked for me without issue every single time. I have used the same procedure with the v12 bypass without issue as well. The effects of installing/uninstalling the .NET bypass seem to be immediate, which is backed up by the manner in which it works. Since Windows updates often require a reboot and may sit suspended in a queue until said reboot is performed, my intuition says to reboot first, then remove the .NET bypass. It has always worked for me.

    Edit: Fixed typo with two steps out of order
     
  13. RukiaPie

    RukiaPie MDL Novice

    Jan 28, 2020
    16
    6
    0
    Huh Simplix was pretty simple... don't think any windows update was that painless and straightforward. Thanks for pointing me in the right direction.
     
  14. RukiaPie

    RukiaPie MDL Novice

    Jan 28, 2020
    16
    6
    0
    Idk it's fun to use windows 7 vista and xp in 2023... we got the majority of modern features in these OSs and everything since has been incremental or regressive imo.
     
  15. Bill_Boquet

    Bill_Boquet MDL Junior Member

    Feb 5, 2012
    63
    57
    0
    #7057 Bill_Boquet, Feb 19, 2023
    Last edited: Feb 19, 2023
    Thanks @abbodi1406 for Windows 7 "return of the phoenix" ;-).
    One question : after having installed the latest fixes (BypassESU-v12 and WSUS Proxy for Windows 7), do I still need to manually install the latest Windows updates ?

    I have an x86 and x64 Windows 7 Enterprise OSes installed on a Oracle VM. I only use them when testing and struggling with very old softwares and games.
    Until mid February 2023, I routinely installed monthly Windows updates with the successive ESU bypass from abbodi1406, latest being BypassESU-v11.
    In order to install February updates, I installed the latest revisions of BypassESU-v11 and .NET 4 ESU Bypass and did the following :
    . Run Windows update : as expected, nothing pops up.
    . Change Windows Update settings to "Never check for updates".
    . Run add_wsus-and-reset_datastore.cmd only once : update history is indeed erased. Installed updates only displays .NET 4.8 and general Windows updates, and no longer cumulative .NET 3.5.1 ... and Windows updates.
    . Run_wsus.cmd + Windows Update : nothing pops up + "Check online for updates from Windows Update" : nothing pops up.
    . Without WSUS Proxy (i.e. without Run_wsus.cmd), again Windows Update : error message as expected + "Check online for updates from Windows Update" : nothing pops up.

    I tried again after reboot between the trials (but without disabling .NET 4 ESU Bypass, that I never did in the past) : nothing pops up.
    I read the last 4 pages of this thread and didn't find why it does not work. Windows 7 Enterprise ? Oracle VM ? Windows Defender ?
    Based on the past monthly releses, I know that "Monthly rollup" and "Rollup .NET all" should pop up.
    Did I miss something or did something wrong ? Or do I have to install these Windows 7 updates manually ?
     
  16. alzcoew397

    alzcoew397 MDL Senior Member

    Oct 6, 2018
    463
    215
    10
    can anyone make a video on how we install the 02/23 updates throughout dism???
     
  17. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,810
    94,905
    340
    you did not install 2023-02 updates manually yet?
    do you see activity or errors in Run_wsus.cmd window?

    .NET 3.5.1 update is named like general Windows update, it's not named like .NET 4.x updates