I fixed aller the error in the checkSUR (I follow the instructions ) All is ok now with it. But I always have the '80073701' error when I install the KB4561643 I just look to the WindowsUpdate.log, but I don't know if this will be very helpful
Fixed ! Thanks to secured2k who give me some clues to find the problem ! I'll detail later for those who had the problem one day !
Hey, I have a question regarding the bypass and the ESU updates, since the problem started occuring after installing them. So you know how you have to restart your PC to configure Windows after the installation of the updates, right? Welp, after I restart it, when Windows boots up, my Aero theme is replaced with a Windows Classic one, and in the taskbar a padlock icon shows up saying that "Windows couldn't connect to Windows Event Notification Services. Please consult your administrator.". When I click on it, nothing happens. Usually, this gets fixed by restarting the PC again, but it takes a lot more time than the "usual" 30 secs to 1 min restart. Since this service doesn't work and Windows Aero is broken, the PC just terminates explorer.exe, leaving my wallpaper only, and then I have to wait for approx. 3 to 5 mins before it actually proceeds to restart. I am asking this, because this never happened while installing normal updates (these before February 2020). Thanks in advance!
@abbodi1406 does the Server 2008 (and Vista) bypass need an update to install this month's updates? The last time the tool was modified was in March, and I don't know if the latest Servicing Stack invalidates the bypass.
You would use System Restore to the most recent point your system was working. In your case, restore to the point before the most recent update that caused the problem. The description you provided indicate some files or registry values were not completed successfully and rather than spend a lot of time trying to fix it (and possibly making it worse) it would be easier to go back to the recent Restore point, ensure the system is healthy at that point, and then retry the update.
I haven't tested this personally, but if there was a problem where the recent SSU broke something, we normally would hear a lot more complaining on the forums. So far no one else has complained so I would assume that it works and there has been no need to update the tool.
It is working... I said a restart is how I fix the problem, try to read my message again, more carefully this time.
Hello Abbodi, Does the above imply there is a possibility the ESU Bypass you've developed has it's end of days ? Saw nobody replied to your message and to me it seems that M'soft has taken action and using this method to get everyone registered in some way, or at least have control back in the ESU matter.
Hi, I re-read your original message as quoted in my first reply and I think we may have had a language usage misunderstanding. When I read "Usually, this gets fixed by restarting the PC again,...", I thought that you have restarted the PC in the past to fix the problem but this time it didn't work. My assumption was that you posted because you were still having a problem. Based on your recent reply, my interpretation is that you meant, "I fixed the problem with a restart. Has this happened to anyone else or know why it happened?" To answer that question - Yes it has happened on various systems due to hardware failure (even if intermittent) or corrupt files/missing updates, or third party programs interfering. It is not a normal thing to happen and indicates there is a problem with your hardware and/or software configuration.
There is always a possibility of a cat and mouse game where Microsoft makes a change that causes an old process to fail. However, in this case, it seems the poster was just informing us that there is yet another method to enable ESU updates (KMS Activation). Originally, you need a license key and install it on a system. KMS would allow the keys to be managed and distributed from a KMS server. What this means is there may be a way to perform a KMS activation of Windows that includes the ESU license. However, since the one discovered is only for the first year (Until Feb 2021), it doesn't seem worth the time and effort; especially when a working method is already in place.
I restarted it and the failed update came back up. WU installed it. I did install bypass ESU validation for .NET 4 updates (4.5.2 up to 4.8) Thanks. I have a Clean 7 Ill have to catch up now.
Win7 version is still working (the same concept) since late February if they didn't invalidate that yet, i doubt they will care more for Server 2008 the only ways (in my mind) that they could invalidate the bypass, is to bump ExtendedSecurityUpdatesAI manifest version above 6.1.7602.20587 (KB4528069 version), or to explicitly blacklist this version in new SSU
probably not .. you can create your own manifest with the version above ... There is an opinion that they (M$) need us to "fix holes" in new versions of Windows. And they will collect the necessary amount of money from corporate clients anyway.