I am trying to install Win7_WU_ESU_Patcher but i receive an error (Patch wuaueng.dll error)! Any help?
N But when I am running windows update I received an error (Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer.)!!!! Any help!!!
did you configure any settings for windows update in group policy? If so set everything back to not configured
One of the major achievements of Microsoft is backwards compatibility. However sometimes we come across things that manage to not work on newer OS.... in this case 32-bit Windows Server 2008 SP2 was the latest OS that could run it. I would only need this for less than a year but I'd really really want to have the OS updated during that time...... So x86 2k8SP2 (not R2) was installed, fully updated until ESU started including all listed requirements for ESU bypass. I hoped to get it updated beyond that with the 2008/Vista bypass. .NET bypass was not enabled. Hoorays echoed around the house and fists were pumped when WSUS listed 17 new updates needed by the ancient machine. Thanks to the team for such a great script! After ESU bypass, on the 2k8SP2 side several updates were installed: KB4537767 (2020-02 IE 9), KB4537810 (2020-02 monthly), KB4537822 (2020-02 monthly), KB5016129 (2022-07 servicing stack). Plus four .NET updates failed... Everything looked good. Except after the reboot, searching for new updates fails with 0x8007000E. In windowsupdate.log: WARNING: File open failed. Error 2 WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab are not trusted: Error 0x80070002 Whoops. Running the setup script again, there is only option 4 to uninstall esu patcher, option 5 to uninstall esu suppressor is missing completely..... It seems this error starts after installing the 2022-07 servicing stack update KB5016129. Strangely I could not find anyone having this same error or maybe nobody just had shared this error from the log file publicly? Anyone have ideas what to do without reinstalling everything - it is a *major* process to get everything installed for this. It looks like something after KB5016129 invokes WU selfupdate and that fails? As a test installed 2k8 SP2 on a VM because it takes hours and hours of work to get everything re-installed on the real machine and I need to involve other people for that as well. This time .NET updates were not even attempted but I installed manually the four .NET updates that had failed on the real machine. The WSUS error 0x8007000E didn't go away. Tried to remove + reinstall all 3 functions of Bypass ESU and 0x8007000E still. Probably the wsus3setup.cab error is totally unrelated to the .NET update and now I am stumped.
One possible cause of this might be that the relevant certificate is either missing or expired. The puzzle is to figure out which one, and where to find it and get it properly installed. Usually the 6.x variants of windows will automatically fetch some of the needed certs but if this system did not have internet at the time it was needed, the fetch would not happen.
The service does not run in safe mode. So follow instructions, reboot to normal mode, and that should restart the service.
The service does not run in normal mode. The safe mode was used to to install Win7_WU_ESU_Patcher. So when i try to run windows update I received an error (Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer.). In addition I discovered that in windows services (services.msc) there is not the windows update service!!!
BypassESU-v12 is working since I installed kb5022509 but Win7_WU_ESU_Patcher is not working. I tried sfc /scannow which found that Windows Resource Protection did not find any integrity violations. I did exactly what is described in ReadMe.txt for windows 7 x64!!!
I've been out of the loop but I thought Server 2008 R2 support ended on January of 2023. When was it extended to 2024 or was this always the case? I have this applied on an old Home Server 2011 Box (built on 08 R2) and logged in today to see it was still receiving updates just last week.
Usually, this error is corrected in the registry - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost (see details on the Internet) , for example, add the value to the netsvcs key: the name of your service (for example, wuauserv) and restart the computer. ... but: "there is not the windows update service!!!"... where did it go? until 2023-01 was, and then disappeared? ... miracles.