Thank you @abbodi1406 I found the two versions of KB4538483, but had used KB4575903 instead. Everything went OK!!
KB5009719 keeps failing regardless of what I do. Standalone installer says it's already installed on an older KB. Not sure what to do as KB5009719 is only referenced once in another thread for the MS KB monthly repository. Edit: Alright, just to clarify when running the standalone x64 installer from the repository for KB5009719 I get the following message after a few minutes of searching: "Update for Windows (KB5008867) is already installed on this computer."
KB5009719 is just the Published Rollup number which bundle .NET updates, it's not a real update itself and doesn't have "installer"
Ah. Thank you so much, Abbodi1406. I went through and downloaded all the repository files and went through the installers on them all. Only one installed and that was that. Upon restart and running the search function again, it said the update didn't need to be installed. I figure I was good to go pending me being wrong, but I'm glad that was all. Again, thank you!
Hello, many thanks for your efforts. Is it strange that v7 still perfectly works in my W7 Home Edition - yesterday I received three updates: KB5009610, KB5009719 and KB890830?
Hello! I would like to install the ESU updates on my WES7 machine with the Windows 7 ESUs Standalone Installer and the Dotnet Standalone installer. But where can i find the supported updates for this? Or is there maybe an updated list which indicates which update is supported for WES7? Thank you very much!
It's the same ESU updates for Windows 7 latest SSU, latest Monthly Rollup, latest .NET 3.5 update, latest .NET 4.x update
Thank you abbodi1406! I check all the KB numbers and found out that i need these one: KB5006749 (Service Stack Update 12 October 2021) KB5008867 (Secure and Quality Rollup for .NET framework 3.5.1) KB5009610 (Montly Rollup WES7 x64 January 2022) NDP48-KB5008858 (Security and quality rollup for net framework 4.8 January 2022) Can you confirm this is right? Thank you very much for all your effort! Very nice!
Hello Everything working perfect, thanks to everyone involved on this amazing work! i just had a new update out of schedule KB5010798 and havent tried installing it yet.. only wanted to know if this is happening to everyone and is an out-of-time update or if its just me Edit: it was installed successful Thanks again for the amazing work
Can someone perhaps help me. I had to reset my PC complete new. Format all and installed windows. Installed thy Bypass and know i get error to update the November 2019 Security update KB4525235. Some Servicing Stack Updates before failed too. Did i miss something ?
There are two lines in `LiveOS-Setup.cmd` that test if the user is administrator. They don't work right if user elevated to admin rights because it tests the users ID. I propose to change the test to check if the current user has the right privilege, for example something like: whoami /PRIV | find /i "SeImpersonatePrivilege"
Hi All! This is my first post on My Digital Life. I joined because I am a long time Windows 7 user and I wanted to be able to access the ESU Bypass. While the bypass worked flawlessly, I am experiencing a strange problem with x64 version Adobe Photoshop CS5. All of the other programs in CS5 work without issue, including the x86 version of Photoshop, but each time I try to run the x64 version I get a popup that says "Could not find the file specified." After which the program does not run. I have attempted to run chkdsk on the C:\ drive and sfc /scannow in the directory where I have CS5 installed, but these troubleshooting methods have not helped. I revered the PC to a restore point I created before attempting the ESU Bypass and now the x64 version of Photoshop CS5 runs properly, but I still want access to the extended security updates. Any and all help would be much appreciated!
After updating using the ByPass, remove the .NET portion of t he bypass... see if that helps. Many users have applicatioon issues when the .NET ByPass is in place. What many of them do is remove the .NET portion once the update is complete and reinstall prior to the next update cycle.