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.
This is correct. KB4603002-v2 does it all. If I look at the "installed updates", they are now all shown as being installed in March 2021. (including the older ones that were already there) All is shown as being a recent install. So it looks like the new KB4603002-v2 cleans out earlier updates and than puts everything back in place that is needed for your system. At least that's how it went in my case....
When I downloaded the program I use (it's called Vidcoder), its installer called M$, which installed NET 5.0.1. (Vidcoder 6.67 beta requires NET 5+.) Then, when I ran WU, it automagically updated to NET 5.0.4. As I wrote above, this happened on both the machine on which the NET Bypass was active and on the one from which I had uninstalled it.
Sorry if I am also asking the same question that others have already asked. I have not had any problems with updating until now. After following the link - Tutorial: Using BypassESU AIO + ESU Updates Overview. I receive a popup window "There was a problem sending the command to the program" when I try to access the Windows Update program. What am I doing wrong, or what did I miss?
I believe there's a big difference between updating FRAMEWORKS and RUNTIMES. RUNTIME updating should not be restricted by ESU/non-ESU support. Runtimes are needed by any program using them and are most likely updated just like OFFICE modules. FRAMEWORKS are a whole nuther thing. They are development environments and, as we can see, are ESU update restricted accordingly. If the v5 FRAMEWORK eventually becomes available, I'm sure it will be ESU restricted as well.