none
.NET Framework 4.7.2 update replaces issue in Windows Update

    Question

  • Update, May 2nd Later:

    I find that things have changed now and that the changes have been marked with strikethrough or deleted.

     

    Now consider the following three scenarios:

    1: Install netfx472 directly on the new w8.1.

    2: w8.1 has netfx452 installed, netfx472 installed later.

    3: w8.1 first installed the netfx452, then installed one or more versions of netfx46-471 (I test with netfx461 and netfx471, the issue appare, I disn't test netfx46/462/470, but I think those will couse the same issue), and now has netfx472 installed.

    4:  w8.1 has one or more versions of netfx46-471 installed, netfx472 installed later.

    Note: In the above case w8.1 refers to any Nov 2014 updated version of NT63 client/server/embedded

     

    In scenarios 1 and 2, any 2018-01/2018-02 .NET Rollups/Preview Rollups will not be pushed by Windows Update. For more information, see the "Repo, scenarios 1 and 2" section below

    In scenario 3 and 4, you can see 2018-01/2018-02 .NET Rollups/Preview Rollups pushed by Windows Update. For more information, see the "Repo, scenario 3 and 4" section below

    There is an awkward problem on Windows 8.1, I guess this problem may also happen on the server version: Windows Server 2012 R2.

    Update, May 2nd:

    7th and 8th in repo.

     

    After I installed the .NET Framework 4.7.2 (netfx472), Windows Update will still pushes the following NETFX updates for me:
    2018-01 Security and Quality Rollup (KB4055266),
    2018-02 Security and Quality Rollup (KB4076494),
    2018-02 Preview of the Quality Rollups (KB4074807).

    netfx3 feature is turned off, the AV compatibility registry setting (KB4072699) is enabled(by install latest Windows Defender definition)

    Those old NetFx updates don't seem to work on the netfx472, they just lie quietly in the WinSxS folder, and those updates only take up download bandwidth and you need to manually hide the updates.

    So what I can do now is to wait until Windows Update and WSUS officially push netfx472?

     

    (I just installed the netfx472...)

     

     

    (netfx472 should replace the security and quality updates that apply to previous versions of NetFx, but those old updates are still being pushed...)

     

     

    How to repo:

    1: Install Windows 8.1 Nov 2014 Refreshed image on a Virtual Machine (set the
    VM not connect to the Internet now).

    2: Install netfx472 on Windows 8.1.

    3: Go to Windows Update setting, select "Check for updates but let me choose whether to download and install them" and save setting.

    4: Connect the VM to Internet.

    5: Check for update in Windows Update, when the updates are listed, install only the Latest Windows Defender definition (If only manually set the AV compatibility registry value, the Jan and Feb .NET Framework updates may not be listed in next step).

    6: Check for update in Windows Update again, you can see the Jan and Feb NET Framework are listed in Windows Update list.

    7: Hide 2018-01 & 2018-02 .NET Security and Quality Rollup and check for updates again, you will find 2018-01 Preview of the Quality Rollups in WU optional updates list, hide the 2018-01 Preview of the Quality Rollups and check for updates again, you won't see any 2017 .NET Security and Quality Rollup or Preview in the WU list.

    8: Install 2018-02 Security and Quality Rollup (KB4076494) , you will only find KB4054980 (for netfx46-netfx471) listed in "Install Updates".(Note: To do this step, you should Restore All Updates Hidden in 7th step)

      

    Some facts in repo step:

    Since the NetFx update mode has been converted to "rollups", each rollup is actually divided into three packages, one for netfx3, one for netfx452, one for netfx46 to netfx471 (up to 2017-02 updates), in Windows 7, except NETFX3 package is MSU format other packages are MSI format, on Windows 8x, these packages are all MSU format. In general, Wu will push updates based on the currently installed NETFX version.

    For example, in 2018-02 Security and Quality Rollup (KB4076494), 3 updates is included: KB4054999 is for netfx3, KB4054990 is for netfx452, and KB4054980 is for netfx46-netfx471.

     

    Repo, scenarios 1 and 2:

    1: Install Windows 8.1 Nov 2014 Refreshed image on a Virtual Machine (set the
    VM not connect to the Internet now).

    2: Install netfx472 on Windows 8.1 for scenario 1, or nstall netfx452 first and then install netfx472 for scenarios 2.

    3: Go to Windows Update setting, select "Check for updates but let me choose whether to download and install them" and save setting.

    4: Connect the VM to Internet.

    5: Check for update in Windows Update, when the updates are listed, install only the Latest Windows Defender definition (If only manually set the AV compatibility registry value, the Jan and Feb .NET Framework updates may not be listed in next step).

    6: Check for update in Windows Update again, you will not see the 2018-01 and 2018-02 .NET Framework Rollup/Preview Rollup are listed in Windows Update list.

     

    Repo, scenarios 3 and 4:

    1: Install Windows 8.1 Nov 2014 Refreshed image on a Virtual Machine (set the
    VM not connect to the Internet now).

    2: Install netfx452 first(optional for scenario 4), then install one of netfx46-471 (e.g. netfx471) on Windows 8.1.

    3: Go to Windows Update setting, select "Check for updates but let me choose whether to download and install them" and save setting.

    4: Connect the VM to Internet.

    5: Check for update in Windows Update, when the updates are listed, install only the Latest Windows Defender definition (If only manually set the AV compatibility registry value, the Jan and Feb .NET Framework updates may not be listed in next step).

    6: Check for update in Windows Update again, you will see the 2018-01 and 2018-02 .NET Framework Rollup/Preview Rollup are listed in Windows Update list.

    7: Uninstall the netfx46-471 version just installed in “Installed Updates” (No changes are required for netfx452 and netfx472),then check for update in Windows Update again, you will not see the 2018-01 and 2018-02 .NET Framework Rollup/Preview Rollup are listed in Windows Update list. (Compare this step with the 6th step in Scenario 1 and 2 and step 6th in scenario 3, which I think can illustrate some of the issues)

     

     

    My view:

    Through steps 7th and 8th in repo, I think Windows Update may not recognize the netfx472 version correctly, but recognize it as a lower version of netfx46-471. Alternatively, the applicable version specified for any published 2018-01/2018-02 NetFx Rollups/preview rollups is incorrect, so that Windows Update believes that these updates also apply to netfx472

     





     


    • Edited by Erica Asa Wednesday, May 2, 2018 5:54 PM add info
    Tuesday, May 1, 2018 4:33 PM

All replies

  • Hi Erica Asa,

    Welcome to MSDN forum.

    >>netfx472 should replace the security and quality updates that apply to previous versions of NetFx, but those old updates are still being pushed...)

    The Microsoft .NET Framework 4.7.2 is a highly compatible, in-place update to Microsoft .NET Framework 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1, but they are independent of each other. 2018-01 Security and Quality Rollup (KB4055266), 2018-02 Security and Quality Rollup (KB4076494) and 2018-02 Preview of the Quality Rollups (KB4074807) are the update for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, and 4.7.1 instead of .net framework 4.7.2, installing .net framework 4.7.2 have no effect on the previous version of .net framework.

    Best regards,

    Joyce


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, May 2, 2018 6:36 AM
  • Thank you for your report, we have identified that there was an issue in our offering detection. The issue has been resolved and made available this morning, 5/3/18.  All affected KBs will now be offering correctly.

    Susan Lester - MSFT

    • Proposed as answer by Slownomad Thursday, May 3, 2018 10:32 PM
    Thursday, May 3, 2018 10:32 PM