Bypass Windows 7 Extended Security Updates Eligibility

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

  1. Nazzy

    Nazzy MDL Junior Member

    Nov 19, 2016
    90
    38
    0
    Since ESU_FLAG/LOCK procedure has been removed, does July .NET updates still require .NET bypass? Can Bypass-v5 by itself install July .NET updates?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream
    Staff Member

    Dec 21, 2012
    8,076
    10,298
    270
    The override flags have been removed, they cannot be used to manually install the .NET packages, anymore. You now need to enable the DotNET option in BypassESU v7 temporarily while installing DotNET updates. Bypass v5/v6 together with the separate DotNET Bypass tool should also work.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. adric

    adric MDL Expert

    Jul 30, 2009
    1,527
    1,720
    60
    #3763 adric, Jul 17, 2020
    Last edited: Jul 17, 2020
    I followed your instructions for creating the slim. I used dotNetFx.cmd and it
    created
    Code:
    netfx_Full.mzz                                227621516
    netfx_Full_x64.msi                              2134016
    netfx_Full_x86.msi                              1355776
    
    I then ran 7zSFX.cmd which created
    Code:
     ndp48-Slim-x86-x64-ENU.exe
    Your command is launching an individual msi. Running the Slim which includes 4565636 at SetupComplete won't work will it? Do I just need to add the reg entry?
    I'm confused :confused:
     
  4. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,610
    100,025
    340
    Either will work at SetupComplete.cmd (ndp48-Slim-x86-x64-ENU.exe /ai or start /w netfx_Full_x64.msi /qn /norestart)

    Setup_NDP48.cmd is mainly to install the updated .NET 4.8 pack on already installed OS with older .NET 4.8 installed
    because it need to uninstall the old pack (msiexec.exe /X) before installing the new one (start /wait netfx_Full_%arch%.msi)

    the two reg keys commands are cosmetic, not needed at all
     
  5. noodlechicken

    noodlechicken MDL Novice

    Jan 11, 2020
    4
    0
    0
  6. stubornjedi

    stubornjedi MDL Novice

    Feb 12, 2020
    5
    1
    0
  7. adric

    adric MDL Expert

    Jul 30, 2009
    1,527
    1,720
    60
    #3769 adric, Jul 17, 2020
    Last edited: Jul 17, 2020
    I did a small test on an active ESU system where I had a .NET offer from WU that showed somewhat over 68MB. I assume the size was for both the 3.5.1 and 4.8 updates. I manually installed windows6.1-kb4565612-v2-x64.msu. Searching WU again it still offerred me KB4566517 except the size was now 38.7MB which I'm thinking is now only the 4.8 update. I ran your Setup_NDP48.cmd with the newly created .msi without errors and WU is satisfied and no more .NET offered. Great, I can continue using the slim installer as you said. So, there's no ESU checking when using an .msi - is that correct?
     
  8. pegasus80

    pegasus80 MDL Senior Member

    Nov 23, 2009
    259
    538
    10
    By using Setup_NDP48.cmd, It makes it easier to update w/out manually uninstalling the old .net 4.8 update pack. Just run the Setup_NDP48.cmd along w/ the current Net4.8 slimmer pack. It also eliminate .net esu checking.
     
  9. adric

    adric MDL Expert

    Jul 30, 2009
    1,527
    1,720
    60
    I only use the slimmer pack with the latest update on fresh installs during SetipComplete where there is no old .NET48 to uninstall. For anything new online, I could use the cmd with msi or .NET Bypass with WU
     
  10. pegasus80

    pegasus80 MDL Senior Member

    Nov 23, 2009
    259
    538
    10
    I can't use .Net Bypass due to msiexec.exe crashing.
     
  11. Jamizon

    Jamizon MDL Novice

    Nov 14, 2017
    11
    27
    0
  12. 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...
  13. AutumnBreeze

    AutumnBreeze MDL Novice

    Dec 22, 2019
    34
    4
    0
    #3775 AutumnBreeze, Jul 17, 2020
    Last edited: Jul 17, 2020
    July Security Monthly Quality Rollup for Windows has installed successfully. However, 2020-07 Security and Quality Rollup for .NET Framework has failed with Error code 80073712.

    I am running Windows 7 Professional x64., don't use an anti-virus, and have BypassESU v7 AIO installed.

    Any idea what went wrong?

    Reading through the posts, I can see some people also have problems with .NET update but with a different error.

    TIA
     
  14. AndyMutz

    AndyMutz MDL Senior Member

    Jun 30, 2011
    369
    688
    10
    so it seems that MS somehow f**ked the .net update up, when even people with legal ESU licenses are encountering errors trying to install it..

    -andy-
     
  15. lunalala

    lunalala MDL Novice

    Feb 7, 2020
    14
    15
    0
    Try sfc /scannow
     
  16. AutumnBreeze

    AutumnBreeze MDL Novice

    Dec 22, 2019
    34
    4
    0
    And yet, some people have installed it successfully.
     
  17. AutumnBreeze

    AutumnBreeze MDL Novice

    Dec 22, 2019
    34
    4
    0
    It requires administrator rights. Funny though, I AM an administrator.
     
  18. ThomasMann

    ThomasMann MDL Expert

    Dec 31, 2015
    1,939
    362
    60
    ONLY for those that paid M$. :rolleyes: Its a nice irony