Not really needed, afaik, but best to go with the latest, if all already runs fine, no real need to install it.
o.k., (Server 2008 R2 Standard) installed KB4586827*.msu in cmd.exe now successfully (successful/Erfolgreich). What i have done: cleared all files in C:\Windows\SoftwareDistribution\Download\*.* before.
@Enthousiast ,Hello to you, How is it going ? Would you have updated your tutorial? who is here : https://forums.mydigitallife.net/th...pdates-eligibility.80606/page-70#post-1578167 Thank you very much .
@Enthousiast , Thank you very much , By chance is it possible to find an updated Windows 7 iso on the forum and compatible with Esu?
No, use https://forums.mydigitallife.net/th...-aio-iso-with-install-wim-esd-creation.79421/ to create one.
I would like to post the following question, what is the difference between following your tutorial and install a Windows 7 make all possible updates there then install the: - UpdatePack7R2 20.11.11 Thank you very much .
Supporting the subject of this thread Separate project, supported in the Simplix Updatepack and SiMPLiX Tool threads.
@Enthousiast I wouldn't want to be clumsy but it's Chinese for me could you tell me this by proceeding like this: 1. I install Windows 7 2. I make all the updates possible via Windows Update 3. I install: the UpdatePack7R2 20.11.11 will Windows 7 be Esu compatible or not?
I have a little home network with two Lenovo S20s (which have similar CPUs, GPUs, SSDs, and RAM), two Lenovo Thinkpad laptops (an x200s and an x220), and two HP Elitebooks (an 840G1 and an 820G3). All the laptops have 8gb RAM. On the software side, all the machines have Win7Pro x64 (US English), the latest version of MalwareBytes and Norton Security, a super-old version of Thunderbird (2.0.0.25pre(!), the latest version of the PaleMoon browser, and the latest Sumatra PDF beta. Also, all except the Thinkpad x200s have, believe it or not, MS Office 2003; the x200s has Office 2010. I've been using the Bypass since the very beginning, so I think I have a fair idea of what to do and how to do it. I won't go into the details, but I have a little routine I follow, and - generally speaking - it ultimately has worked fine so far (with varying degrees of fooling around). Thanks to the Bypass team, I've been able to update every machine every month since this all started! Update Tuesday is one of the highlights of my month, and I generally have all the machines updated within 2-3 hours. However, it's fascinating to me that every month something different happens! What follows is only about the latest updates (November). As I mentioned here on the forum a couple of days ago, one of the S20s updated perfectly using WU; the other one had to be updated manually. Much more interesting, though, were the laptops: Both Lenovos worked perfectly with WU (even the x200s with the Office 2010 updates), but the HPs ... WU found all three updates for the HPs, but the only thing that installed successfully was the Windows Malicious Software Removal Tool. After the machines had rebooted, both said installation of the Monthly Quality and Security Rollup was "Pending", and the Security and Quality Rollup for .NET Framework 4.8 for Windows 7 had failed. I then downloaded both files from the Windows Catalogue, and after I installed Monthly Quality and Security Rollup .msu file manually, both machines changed the installation from "Pending" to "Successful". The NET update available from the Windows Catalogue, as you might know, was an .exe file. I thought it would be easy, but I got a surprise from somewhere I never expected: The installation failed, and all of a sudden, I got a notice from NORTON SECURITY that it had found a problem with the .dll that the .NET 4 Bypass uses (sorry, I've forgotten the exact name), AND IT REMOVED IT FROM BOTH COMPUTER AND PLACED IT IN QUARANTINE!!! Fortunately, I know enough about Norton to restore the file. I then ran the .exe again on both machines, and everything was fine, but I found it really weird. Nothing similar had ever happened before. Installing the IE update worked fine on all the machines. Let's see what happens next month. As always, my most sincere thanks to everyone responsible for the Bypass. You people are GREAT!