Everything checks out for me in all 4 of my Dell desktops - just as it does for nicholaasjan. Same partial product key Same SSU and LPP updates installed Same 4 DLL files Same registry entry Windows Update did not detect the March 2023 KB5023769 SMQR update, so I had to manually install it. It is frustrating, but it can still be manually installed without being rejected, which is the important thing.
Windows 7 Ultimate x64 was all up to date, including February 2023, Installed BypassESU-v12,I then installed Win7_WU_ESU_Patcher with option 1, Rebooted the PC and checked for updates, didn't find any, so I repeated those steps again but checked option 2, rebooted then checked for updates, after a few minutes, 4 showed up. So I installed them. Works well for me.
Not sure if anyone else did this for Win7_WU_ESU_Patcher, but I turned of my Avast Antivirus pgm for the install of the patcher.
abbodi1406 If I understand correctly Bypass modifies or installs its own version of the system files to update Windows, therefore I would like to clarify if you remove ByPass components completely will the native system files come back or after modification the process will not change?
Hi Thank you so much to the people behind this project for keeping Windows 7 alive! I have been using BypassESU to install updates for Windows Professional 64-bit SP1 until 10 January 2023. I have just installed the standalone WU ESU Patcher for Window 7 client to continue receiving updates as posted by abbodi1406 on March 3. The following three important updates were subsequently successfully installed on my computer: 1. Security Update for Windows (KB4575903) 2. 2023-03 Security Monthly Quality Rollup for Windows Embedded Standard 7 for x64-based Systems (KB5023769) 3. 2023-02 Security and Quality Rollup for .NET Framework 3.5.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Embedded Standard 7 for x64 (KB5022731) My question is, are these all the important updates I should expect to be installed on my system at this point or is anything missing? Just wanted to make double sure everything is working fine. Thank you for your help.
@Avalon2020 None of system files are changed, only a copy of the file is patched + some registry modifications uninstallation will remove the patched files and restore registry @AutumnBreeze yes since 2016-10, Windows 7 only gets Monthly Rollup + .NET Rollup
abbodi1406 Got it. Fine. Another question: should I start by installing Bypass v9 or can I start with v11?
install official windows 7 update required for bypass ( after install bypass v12 + net v4 bypass from v12 ) install all update after full update to january 2023 stop windows update service open cmd promp with admin and write net stop wuauservc delete softwaredistribution folder present on c:/windows reboot not search for update ! patch as windows 7 embedded with latest abbodi fix
When I go to the local WSUS instance IP address stated when running Run_wsus.cmd, I get this: To connect to this service you need to enter the following address to the WSUS configuration in the group policy: (cannot post IP) Please note that the ? has to be appended at the end of the URL because of limitations this implementation of WSUS server. How do I do this?
abbodi1406 I need your explanations. Why, after applying the actions I described above, I have lost the hidden updates: regional languages, video and audio drivers, Logitech utilities? I get it all back, I'm specifically interested in Logitech and Realtek drivers.
First, I want to say what a great job was done by abbodi1406 and anyone else working on this project. Thank you! My system is Windows 7 Ultimate x64 and I only show .Net 4.8 installed. Before installing standalone WU ESU Patcher, I had used BypassESU v12 to manually install all updates through March from the catalog. This included kb5022509 and kb5023823 for .Net 4.8. Once I had WU ESU Patcher configured and searched for updates it found kb5022731, but actually installed kb5022523 which is for .Net 3.5.1. I assume this is because .Net 3.5.1 is part of Windows 7 "out of the box" configuration. I was not sure I needed to install it, so this was another benefit of WU ESU Patcher! I want to add that I use Bitdefender and no matter what exceptions I added or what I turned off, it kept interfering with execution of WU_ESU_Patcher.cmd. I had to uninstall Bitdefender to properly run WU_ESU_Patcher.cmd, then after installing kb5022523 I reinstalled Bitdefender. When Bitdefender messed up the execution of WU_ESU_Patcher.cmd, it got things messed up with the wuauserv service where it would not start. I had to use regedit on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost, edit netsvcs to add wuauserv back to the list of services. I recommend anyone else using Bitdefender to uninstall before running WU_ESU_Patcher.cmd.
If whitelisting does not work with bitdefender did you try restarting with bitdefender turned off? I turn off my Kaspersky AV & Malwarebytes ransomware protection & restart with just WinDefender working. Win7 Home Premium on Acer Aspire Laptop. Don't forget to turn them back on & restart when done. Norton use to really mess systems up because it dug so deep inside the system internals it could not be removed normally.
Maybe we should ask for a recommended list of files to exclude from antivirus software and have that included in the first post. From what I found if you select to patch using Server 2008 R2 option: C:\Windows\WuEsu C:\Windows\System32\sle.dll C:\Windows\System32\kerneles.dll If you are patching as Windows Embedded you need to exclude these additional files: C:\Windows\System32\wbem\sppwmi.dll C:\Windows\System32\wbem\slw.dll And you also should exclude the folder where you extracted the downloaded ZIP file. Perhaps wuaueng3.dll in System32 should be excluded too.
Lost it where? WU? WU_ESU_Patcher is to allow installing updates after 2023-01 you are supposed to install prior updates and whatever WU drivers offer normally before applying the standalone patch