So now I'm part of this comedy sketch. I'm thinking that KB4537829 needs removed, but also see that a new installer may be coming. So, uninstall via the above hack or wait for new Bypass? I may wait until the following month to do anything next time, to see who's on first.
thank you my friend, i was able to uninstall KB4537829 using the given method. Very good job as always Just to be clear, you have to remove the mentionned line for all .mum files associated with the update.
Hey guys ... I just installed BypassESU-v4, and then the KB4528069 update, which was a success. My question is: Now, how do I get the ESU updates ? Is it done automatically by Windows 7 or do I have to get them manually from somewhere (and how do you know which ones you need) ? It is now february 11, so almost a month since the end of support ... Surely there are some security updates I need to get ?
Strange, .NET is part of the OS, but not supported by ESUs? Don't think I have seen any mention about this in Microsoft's docs. Hmm, maybe .NET updates are included in the Security Only and in the Cumulative Updates? EDIT: Just unpacked the updates, no they are not included. Maybe they will be released in a few days.
This method worked for me as opposed to the other method posted here before which suggested the PowerRun app. You should add it to the OP while an updated version of the bypass is on the works Thank you (both, actually).
Don't worry it is supported by ESU. Perfectly normal for extended support that is basically security only. Last one before January was September.
Hi. Thanks for this. According to what I've read above, is these all that is needed now for security? kb4537767 kb4537813 kb4537820 and not KB4537829 Again, Many thanks!
For now: skip the KB4537829 (Servicing stack update for Windows 7 SP1 and Server 2008 R2 SP1: February 11, 2020) update. If you already installed it, use system restore to remove it or wait for a new version of Bypass ESU which may hopefully fix this.
All you need is kb4537820. The other patches are contained within this update. Do not install KB4537829 yet.