Ok. Thanks for clarifying! I got that wrong and thought it easily worked for you by installing the old one over.
Agreed. I just now did the same. Finally got lucky enough to have Windows listen to me regarding file ownership authority. This will be a learning curve for all of us. Start taking notes.
Thanks all for testing and reporting - in the meantime, do not install SSU KB4537829 - to uninstall SSU KB4537829 , try this method https://forums.mydigitallife.net/posts/1154312/ - If test update KB4528069 is already installed sucessfully before, it will actually suppress ESU check in February updates so, it was not a useless update after all - alternative bypass is in the making
It's almost funny how confusing this has become. Kind of like an old time radio comedy show. The way I'm taking this, is that these updates don't need to be completed in the hour they become available. Relax, wait, see what's going on, then do it. All updates went fine on both Win7 Home Premium machines here. Thanks for this tool. OK, in the time it took me to write that, abbodi1406 posted to NOT install KB4537829, it was one that I did do. So, next month I wait longer.
abbodi1406 oops, thanks for a prompt. I didn't meal that a test KB4528069 has any other sense except ESU testing
please i would like to know where i can find and download 2020-02 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8??
Success! - Win 7 x64 Ultimate - what worked for me: After a few fails & reverts - applied the .mum edit(hack) to make Feb SSU KB4537829 "removable" instead of "permanent" - uninstalled it - and all worked out afterwards. Thanks to erpsterm35 for link. So definitely avoid that update!. Installed Bypass from root drive folder Installed KB4536952 - Jan 2020 SSU After that - installed Feb Updates - KB4537813 Sec. Only - KB4537820 Rollup - KB4537767 IE 11 Cum. Rollup No fails! Thanks to dev's for the work and progress with the ESU project!
REPORT: What people are saying now is accurate, however do remember to always make sure you have the newest version of the patch tool. Earlier I was using v3, and didn't understand there was an update, v4, until about my 5th restart. Save yourself some time and update before you update!