Am I missing something? Microsoft pulled the .NET updates for this month, right? Why is the last 4 pages full of people still trying to install them? Doesn't the fact that Microsoft pulled them indicate that maybe we should NOT install them? Or is there more going on here than I'm seeing?
They did not pull them completely at first, they created totally new version of .NET Rollups that contain v2 of .NET 4.x updates Code: 2021-03 Security and Quality Rollup for .NET Framework for Windows 7 (KB4579977) 2021-03 Security and Quality Rollup for .NET Framework for Windows 7 (KB4603002) you get both new rollups offered even if you have v1 installed but this caused some detection confliction (for KB4579977), so they pulled them then, they added v2 of .NET 4.x updates to the old .NET Rollups Code: 2020-10 Security and Quality Rollup for .NET Framework for Windows 7 (KB4579977) 2021-02 Security and Quality Rollup for .NET Framework for Windows 7 (KB4603002) you get KB4603002 rollup offered only if you do not have v1 installed
Can somebody help, why the installation of march rollup(KB5000841) after restart fail. I have Bypass11 and the last rollup(KB4601347) was without problem. Thanks
Thanks for the very detailed explanation. I was not aware that there were the 2021-03 versions released initially. This must have been for extremely short time, maybe 1 hour. In addition to what was said, KB4603002-v2 installs fine on top of KB4603002-v1 although apparently is not offered by WU if v1 is already installed. I am actually referring here to KB4600944-v2 update for .NET Framework 4.8, included in KB4603002-v2. In a manual installation, it is possible to have only KB4600944-v2 and uninstall all the other updates for .NET Framework 4.8. The other update for .NET Framework is old and there is nothing new in the current package. Is this configuration without KB4579977 (v1 or v2) complete from a patching perspective? WU seems to think so.
KB4578977-v2 also contain some newer files, but you might not be able to install it after KB4600944-v2
Hello abbodi1406 If one has neither v1 nor v2 installed, would it be convenient to download and install them manually? Thanks
is there any reason to install KB4578977-v2 after KB4600944-v2? EDIT: I was under the impression that there is a supersedence relationship between KB4600944-v2 and KB4578977-v2. Another check of the catalog doesn't show any supersedence. EDIT 2: Sorry, they are the individual packages for 4.8, normally there is no supersedence. What a mess with the .NET Framework updates.
Thanks for the explanation. I was initially offered the first 2 you mentioned but decided to hold off on installing them until things sorted out. I did install the monthly security rollup (KB500041). However, since then WU is not offering me any .NET updates. This would be the first time that I've had to do an update not offered by WU. The last one installed was KB4603002 (February Rollup). Is that normal? Should I wait for WU to offer them or should I install them on my own?
Yes, Microsoft indicate that you don't need v2 if v1 is already installed v2 don't contain any new security fixes, they just re-signed the files with new certificate
Okay. NOW I understand (I think). Let me rephrase it a bit differently as it might help others: If we had previously installed the October, 2020 .NET Rollup (KB4579977) then it is NOT necessary to install ANY of the March, 2021 .NET Rolllups Is that right, then?
LOL... Okay. If we had previously installed the October, 2020 .NET Rollup (KB4579977) AND the February 2021 .NET Rollup (KB4603002), then we are up-to-date and it is NOT necessary to install ANY of the March, 2021 .NET Rolllup
It's always been this way Code: windows6.1-kb4578952-x64_30ac0df8554c2647017f3b36cc02e833a3187364.msu <--- dotnetfx35 ndp47-kb4600945-v2-x64_974660a8bbb596162e9b65710cee274bc509e1c9.exe <--- for people on dotnetfx472 windows6.1-kb4019990-x64_35cc310e81ef23439ba0ec1f11d7b71dd34adfe5.msu msipatchregfix-amd64_5011cb29b096fb674a4795ee8fc2f7fdad33863a.exe <--- no manual usage ndp45-kb4578955-v2-x64_bf17567bb3a895fe08a07a75323776a49266bfad.exe <--- for people on dotnetfx45 ndp48-kb4600944-v2-x64_46e4157f2e3793c230ff8fad706130142769c2ff.exe <--- for people on dotnetfx48 WU assesses which of the updates is needed and will install the appropriate ones.
Yes, you're right. My only point was that, although being a "2021-02" update, KB4603002 now has a 09/03/2021 modification.
NOTE -> This post is about an update for M$ .NET Framework 5, not the versions under discussion so far. A program I recently installed requires NET Framework 5. I have the program installed on two Win 7 Pro x64 machines. I've been using the Bypass to keep things up to date since the beginning. As I've written many times, my most sincere thanks to the Bypass team! Anyway, on one of the machines, I have the .NET Bypass active; on the other it's inactive (uninstalled). This evening, I decided to run WU again, just to see what's going on. I was very surprised to see that WU provided and installed the update to the latest version of NET 5 (it's 5.0.4) on both machines! Of course you can't just get rid of NET Framework v. 4+; some programs need it to run. However, as time goes on, it appears that the use of NET 5 will grow, so I thought I'd bring this to the Bypass users' attention. Have a nice weekend.
Interesting, I thought this was only updated manually still. COU has some .NET Core stuff for V3 but not V5. I wonder if it will start showing up there?
There is no Microsoft .NET Framework 5.0 The very last version was 4.8 I'm assuming you're referring to Microsoft .NET 5.0 Runtime
To be fully patched and up to date with all .NET Framework versions, you only need KB4603002-v2 which is the current one, v1 being expired and no longer available. Anything else is redundant but not harmful if left alone in the system because it is superseded by this latest update which contains updates for various versions. The update for .NET 3.5 is from September 2020 and has not been updated since, but the updates for all other versions have been revised recently and should be installed. As @abbodi1406 says in an earlier post, the v2 versions only have resigned files and strictly speaking are not required, but moving forward, to have the cleanest possible updates and avoid future issues as much as possible, you should have KB4603002-v2 installed as this is the version which Microsoft currently has as reference/baseline. Hopefully next month this will all be cleaned up with a superseding package. EDIT: If this is all too complicated, it is OK to let Microsoft Update to do its own thing, assuming that you are entitled to receive the updates and have them installed in one way or another.