I saw the WU Client lines several times in two of my machines (CBS.log), but as I was on one today Windows Update said that there was an update available, so whatever it was telling me, didn't affect getting the update.
So I only do updates every other month and now KB4586827 failed. Installed, rebooted, failed to configure, reboot, failed to configure. KB4586083 failed on install even before reboot. Saw the new v9, installed that now and will try again. EDIT: That seems to have worked now, though during install some form of popup came up, rebooted before I could read it, but update history does state it is installed.
There is no NDP stuff you have to install again. Maybe you mean the msiexec.exe problems that can occur when the .net 4 bypass is installed?
I remember there was a post saying that something NDP thing was released and it told you how to install it. Was it only important to install if you have .NET problems installing ESU?
Only that the .net 4 bypass can cause msiexec.exe and other related errors, then uninstalling the .net 4 bypass is needed.
Embedded Standard 7(not PosReady 7) is first month after EOS(2020/10/13) I tried BypassESU-V9 Live OS installation Result Direct ESU update (KB4586827) install - OK Direct .NET 4 update install - OK Windows Update - NG (not appear ESU updates) Since it works normally on Windows 7, I think that there is no mistake in the procedure. Please fix WU
Code: WmiQuery Namespace="root\cimv2" WqlQuery="Select * FROM SoftwareLicensingProduct WHERE (ID = 'B1703B31-8BD5-49F4-9011-811C4DDFD760' OR ID = '84153DED-345E-4871-AF77-19758B7DA9FB' OR ID = '6AAF1C7D-527F-4ED5-B908-9FC039DFC654') AND PartialProductKey IS NOT NULL" WU for WES7 check the installed ESU keys, not product policies like normal Win7 this will be hard or impossible to fool
----------------------------------------------------------------------------- As I reported in an earlier post regarding the November updates ... "The NET update available from the Windows Catalogue, as you might know, was an .exe file. I thought it would be easy to install, 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 a dll that the .NET 4 Bypass uses (sorry, I've forgotten the exact name), AND IT REMOVED IT ... AND PLACED IT IN QUARANTINE!!! Fortunately, I know enough about Norton to restore the file. I then ran the .NET update .exe again, and everything was fine, but I found it really weird. Nothing similar had ever happened before." ----------------------------------------------------------------------------- I assume my issue was related to what zyoops mentioned. What makes it sort of interesting is that, as I wrote, this only happened on two of the six machines on which I use the Bypass, although the basic software setup on all six is identical: OS, AV, email client, browsers, .NET version, updates, etc. The two problem machines are HP Elitebook laptops, an 840 G1 and an 820 G3. The other four are Lenovos. Does anyone have any idea how this could happen? Thank you.
@vonmir Try safer .NET Bypass https://forums.mydigitallife.net/th...dates-eligibility.80606/page-218#post-1618511
Sorry, could somebody explain this to me: I managed to download the security-only update for 11/2020. This means everything worked fine? Does it not include all prior security updates?? Thanks!
Did you install security-only update for 11/2020 ? If so, that means that you're fine. Security only updates contain all new security fixes for a month.
