Is it me or 2021-02 .NET Rollup KB4603004 is not requested by WU if 2021-07 Rollup KB5004231 is installed? although KB4603004 is not superseded by WU metadata
@abbodi1406, I lost interest in Win7 / Win 8.x since this flood of too many Windows editions. I did in depth research about Win 10 .NET Framework instead in relation to 2021-02 .NET update which is the latest security release and later .NET updates which are not security updates. I found that even if 2021-02 is not superseded directly, it is in fact superseded indirectly which is not observed unless all updates including preview releases are taken in consideration. So if superseding updates are missing from the chain, it appears that 2021-02 is standalone and not superseded. I thing this can be more clearly noticed if both 2021-02 and 2021-07 are installed and 2021-02 is uninstalled with dism /online /remove-package /packagename:<> The Setup Event Log with say if 2021-02 is superseded. Just to clarify even more, the issue which you noticed is obvious for Windows 10 current versions and while there are differences from Windows 8, Microsoft might have unified this behaviour accross the board.
@ch100 Windows 10 .NET CU are chained by CBS package name Package_for_DotNetRollup Windows 8.1 .NET updates are standalone CBS can still calculate supersedence of course
I am looking into this right now. .NET 3.5 and .NET 4.5.2 are common to 2021-02 and 2021-07. They are KB4578953 and KB4578956. So the issue is only for 4.6-4.7.2 and for 4.8 updates. Need to do further testing but I suspect you are right in what you noticed. Because there have not been security updates for .NET Framework since 2021-02, Microsoft likely decided to promote what used to be preview updates to full updates, similar to the security updates. There might be differences between too many versions of .NET Framework and combinations posible, i.e with/without 3.5, 4.5.1 vs 4.5.2 or any other 4.6, 4.7, 4.8 combination. The easiest way is to settle for the 3.5 & 4.8 combination but can be any other combination possible which is hard to track. I understand that you look behind the scenes much deeper than me. I am only trying to identify the behaviour from a (power) user perspective or even normal administrator.
@abbodi1406 I can confirm now that KB4601058 which is 2021-02 .NET Framework Security Update for Windows 8.1 is not superseded by KB5004118 which is .NET Framework 4.8 Non-Security Update for Windows 8.1. Even more, KB4601058 can be installed manually on top of the later update KB5004118. If the bundle 2021-07 KB5004231 is installed, then the bundle 2021-02 KB4601058 is not offered which I don't know if it is accurate in the technical sense. This has something to do with the bundle metadata and not with individual updates inside. So all your observations are correct for 4.8 but was not tested for other versions 4.6.x - 4.7.x. It is likely the same situation though. For the purpose of providing updates to alternative tools, I suggest keeping the latest security update which in this case is 2021-02 KB4603004 at least until the next Security Update superseding it officially is released and allow WU to sort out. Might miss an essential patch by those who do not install regularly or uninstall what is perceived as obsolete without actually being the case but there is not much which can be done about it.
@abbodi1406 For "windows 8" is there's a way to get the "Windows Embedded 8 Standard" update by windows update?
I think, he meant, to get updates for windows 8, but using windows 8 embbeded updates, just like to get updates for XP after 2014.
don't think it's possible to get 8 embedded updates onto client win8 os thru WU since WU detects OS edition & version
Probably, I did not check. I just say, how people think, you know, we have updates for XP after 2014, some Server 2008 updates for Vista, etc. And now, if there is some new update for Windows 8 Embedded, I suppose, someone think that we can somehow apply to consumer Windows 8.