Help me remember. Hasn't it been said a few times in this thread that the bybass bat file will now work with almost all versions of windows now?
Oh really? I have never updated Internet Explorer since Internet Explorer 10. Oops, so what should I do? What's the best course of action?
Separation of security, important, recommended, optional existed from the very beginning. If you never cared about this complex before you probably installed everything that was offered via auto updates, and you installed monthly rollups the last couple of years. Look into your update history.
Seems to correct to me as that's what I did it and everything worked as expected for me. That's my understanding as well. When I first downloaded the bypass and tried to install the ESU eligibility update it failed, but I remembered that I hadn't installed the Jan 2020 SSU yet so I downloaded and installed it. Once I had done that the bypass allowed me to install the eligibility update as expected which in turn allowed me to install KB4537813. I should also note that I did not need the bypass installed for the update to install successfully.
Problem...Windows 7 SP1, installed the ESU updates after installing the ESU bypass, all updates installed successfully including the KB4537829 one. However, the restart took over an hour to complete - perhaps because of interference of the 4537829 which I now understand should not be installed. So, my question is...should I uninstall 4537829, and if not am I going to have this interminably long boot into Windows after future updates? I did ESU updates on another laptop, WITHOUT the 4537829, and the restart took the normal amount of time after usual update installations. Any advice is appreciated
Your own post says it probably was something on the system that caused the long reboot, the SSU only causes the bypass to stop working, but recent development shows that when the old test ESU is installed, all ESU checks are suppressed, that's the reason MSFT removed it from catalog. The SSU doesn't cause any problems for windows itself.
Ah, Ok, I understand. Then the only patch that is killing the bypass is KB4537829?? That's the "malevolent" one?
On my system, Windows 7 Pro x64 SP1, it lists 3 .mum files mentioning KB4537829. Which do I need to edit to enable uninstall? Code: Package_2_for_KB4537829~31bf3856ad364e35~amd64~~6.1.1.2.mum Package_for_KB4537829_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum Package_for_KB4537829~31bf3856ad364e35~amd64~~6.1.1.2.mum