ok ..fully removed bypass v11 removed the "c:/upgrade" folder i did previous while trying the .NET fix some people did ( the "NDP48-KB4600944") reboot (re) installed bypass v11 (including .NET bypass) reboot Managed to FINNALY install both .NET updates (KB4603002) and the new March .NET update (KB4579977) reboot now having the same issue as other people, the KB4579977 keeps coming and coming after reboots
I manually installed KB5000841 and NET Framework 4.8 updates (KB4578977 and KB4600944). Do I need anything else ? Maybe KB4578952 ? Thanks.
I, too, had a problem with the .Net updates. However, the details are too complex and boring, so I'll restrict myself to a question. I now have KB4578977 and KB4578977v2. Do I need both of them? Thank you.
Both seem to fail, v2 should have fixed it but msft f**ked up again (only the latest revision will be needed afaik).
What do you mean "both seem to fail", please? Just out of interest, I have KB4578977 (installed 13 Oct 2020) and KB4578977v2 (installed tonight) on both of my Lenovo S20 machines (which have almost identical hardware). However, on one of them, tonight's updates worked "automagically" from WU. On the other, I had to download them manually and then use the bypass to install them. I was offered both of them several times on the machine that installed them via WU, but I finally just hid them, and this has ended the problem - at least so far. On the machine on which I installed them manually, I've haven't been offered them again. Finally, I've just emptied the "Updates" folder that I created to run the Bypass, except for the two .msp files. Now I'm going to restart my machine. I'm not sure if this will screw up the updated NET process, but we'll see. I'll let you know if it does.
Looks like the March 2021 .NET updates for Win 7 may have been pulled by MS. They have gone from the Catalog and no longer offered on a fresh search on WU.
I was offered to install an update for .NET from September 2020 and two updates .NET for this month (on two computers, x86 and x64). After installation, I have not yet started the update search again. I confirm this.
Apparently solved: 1) uninstall KB4578977v2; 2) uninstall KB4600944v2; 3) uninstall KB4578977; 4) uninstall KB4600944; 5) reboot; 6) WU offers KB46003002 again, please install it. The final result is that no more updates are offered by WU. Maybe I made a mistake, but it works. Please, don't laugh...
I've had some really odd behavior from NET Framework updates in the last few days on a fresh install of Win7Pro. All prerequisites and the v11 bypass installed. A whole bunch of .NET 4.5.x security updates (back to 2019) being offered and failing with 800b0101 error from Windows update. Read a whole load of posts on that which didn't help much until in a random fit of curiosity (madness) I set the computers clock to the day after patch Tuesday on that month and year. And the damn thing installs, did this for several versions of the security updates up until last month having to set the clock back, and this months installed fine as is. One of the weirdest things Windows has ever done to me! I don't know if it's related to the bypass or not. This install USB has been used before on other machines and they don't show this issue. Confusing to say the least.
Weird, it worked for me without any problems with bypass v11, everything installed without errors, but I don't know what's different with me. It's an old System Q9650 with 8GB RAM if that's any help
I've done a bit of digging into this issue of 4579977 and 4603002 being pulled and re-released and some of what I have seen matches what you have experienced... 4579977 has been re-released as a v2 update for the 2020-10 .NET update. This fixes an expired certificate error that appears if you try to install the 2020-10 .NET update in March 2021. For the vast majority of Win 7 users this re-release is not relevant as it is probably already installed on those with current Win 7 ESU updates. However I suspect it has to do with the fact that the 2020-10 updates are the final updates applicable to Windows Embedded Standard 7 without ESU. By pure coincidence I was testing a fresh install of WES7 earlier today (before todays patch release) and it failed on this update with a certificate error. Setting the clock back a month allowed it to install prior to this new update coming out. I later found this mentioned on the KB4579977 article notes as the reason for a v2 release. So it appears that this newly issued 4579977-v2 update is probably only of use to those doing a fresh install of WES7 without ESU and wanting to bring it up to 2020-10 patch level. I suspect MS made a mistake and released 4579977-v2 named as 2021-03 by mistake, before pulling and re-issuing named as 2020-10. The files are binary identical, just the name/date has changed. 4603002 has been re-released as 2021-02, it was released as 2021-03 earlier today but then pulled. I can't see an obvious reason for this other than the files for the .NET 4.5.2 update are binary different (dated Oct 2020 in the pulled 2021-03 release and dated March 2021 in the updated 2021-02 release). All other files are binary identical, so I suspect this one just went out with an older file by mistake before being pulled. Again unlikely to affect many people as this update is only used by those with .NET 4.5.2 - I suspect most Win 7 ESU users either have 4.8 or no .NET 4.x installed at all, in which case this part of the update doesn't apply.
I had this problem with one machine running Windows 7 Pro. The other machine (on Windows Home Premium) just installed everything and didn't present any updates a second time. The solution described above solved the problem.
i don't think you fixed it by doing this... what happens is that .NET updates aren't being offered now, MS probably removed it, the KB4579977 was installed fine, but it kept always being offered by rebooting the machine (like many users had reported here, myself included) now it no longer happens ( MS pulled it out)