abbodi1406: I already have Windows 7 Professional SP1 64-bit configured as Windows Server 2008 R2 64-bit with BypassESU_v13. I used the gitlab.com and box.com links to download BypassESU_v13f. I noticed the file size for the old v13 and the new v13f are both 366 KB. When I deployed v13f, the window showed it as v13. This is the first window that appeared: When I selected option #3, this is the window that appeared: Am I doing something wrong?
After switching from BypassESU-v13 to BypassESU-v13f and rebooting, I re-installed the KB5046687 SMQR update for Windows Server 2008 R2 64-bit to see what would happen. After installing it and rebooting, I quickly discovered that my Mozilla Firefox ESR 115.17.0 browser was broken again. Uninstalling KB5046687 and rebooting again resolved the issue.
1. well, i guess that after this micro-fix applied everything works just fine but i have no idea why Win7 WU now as WinServer2008R2 can't find z Nov2024 NET3.5.1+4.8 update(s) while it easily popups a Nov2024Rollup that has been skipped to be installed due to z reported uncertain issues. 2. i don't see any clear issues related to NET4-Bypass as a part of BypassESU-v13 as kindly prompted by you. Anyhow z pre-downloaded NET4.8 update Nov2024 has been installed smoothly. Appreciate always!
Moin CaptainSpeleo! Once again for better understanding: The issues that occur after installing KB5046705 & KB5046687 with the vintage browsers (Chrome 109, Edge 109, Firefox ESR 115, Opera 95) have absolutely nothing to do with the abbodi1406 ESU Bypass Tool. It has to do with the fact that Microsoft, knowingly or unknowingly, added a bug to these two updates. Solution approaches in a clear form, which also have nothing to do with the ESU Bypass Tool, can be found here: Link The bypass ESU validation for .NET 4 updates & the patch of WU engine in the BypassESU-v13f version working well for me.
Interesting because only cumulative security update from November kill browser's functions. Net work normally. You should don't let's that concrete to install. And interesting is that, when we try that Esus, VMware put only bsods but on Virtualbox work that modifications on windows 7.
Thank you, but unfortunatley not for me in my win7 pro. I had to use dotNetFx4_ESU_Installer_v4 to install KB5046258 , while BypassESU-v13f worked well only for the other WU. I would like to know the reason... Thank you so much in advance for the answer.
For some reason i just can't get ESU to work on a OEM install of Windows 7 Pro. It has all original supported updates installed. I then followed all the usual steps of setting up ESU, inclduing the preperation package and the ESU patcher itself. It detects all the new updates just fine but i can only download and install some recent .NET Framework updates. All of the monthly update rollups do not work. I then tried to do a recovery reset and do it all over again, but still, it doesn't work. All of them fail with: 8024200D, weird.
Moin sXpTv! Error code 8024200D = It indicates that the Windows Update handler can’t install the update because the update downloaded is invalid and damaged. It`s have nothing to do with the ESU Bypass Tool but it can have the following reasons, for example: Lack of disk space on the system partition, third-party applications such as antivirus programs or tuning tools, system files required for the update function are corrupt, connected usb-devices, missing servicing stack update, Windows Update Store function faulty...
If the update is for Windows Server 2008 R2 Premium Assurance, it's for this only. These are enterprise customers paying highly expensive fees for these updates, and also being a Server edition, they almost certainly don't use it for watching videos or opening a browser. They will care about Server things only. I suspect they updated a security component. I think W7 is over now. Please save your October 2024 updated ISO on your archives. For W8.1 I think there aren't problems, since updates from 2023 are Server 2012 R2 only, and these things work fine. Also, I have the January 2020 W7 ISO created by myself from Simplix.
microsoft have confirmed it will be fixed in the dec update type in kb5046687 problems on google, and it in the top result (micorosft community) last post. hope this helps
Excuse my ignorance, will there be a way to enable the "Windows Server 2008 R2" category for x86 system in the future?