Jani

Okay, I finally figure this out. Here's the reason why the updates were not installing: https://www.askwoody.com/2018/windows-10-enterprise-does-setting-telemetry-to-zero-disable-cumulative-updates/ So, my bad! The real correlation was early adopters of 1709 being more privacy minded instead of ESET being installed when FCU first came out.

And your updates are working I presume. Well, it probably is Microsoft's problem, but I still think ESET plays a role, because the only computers where I see this problem are the ones, which had ESET Endpoint AV installed when the Fall Creators Update (1709) came first out. All others are fine.

I think I found a hint why my Windows is not updating. It seems the key HKLM\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\PolicyState\BranchReadinessLevel is empty on the problematic computer whereas on my other Windows 10 computer, it contains a value "CB". If I try to set it to CB manually, Windows just overwrites it with an empty value. What values you guys have there?

So, on one computer I uninstalled EEA and ran the Windows Update Troubleshooter. The troubleshooter showed the following dialog, and yet I do not see any updates when I check for them:

For me the 1125 Anti-Stealth update added the WindowsCompatibilityLevel registry key, but I still do not see KB4074588. Clean installs of EEA 6.6 seem to work fine, but computers with incrementally updated EEA installations fail to detect the Windows' update.

I haven't received the .248 update yet, nor I have had the time to uninstall ESET to investigate this. I just checked and I do not have that WindowsCompatibilityLevel key. My registry looks sameish as @SieraZ's above. I'm on ESET Endpoint Antivirus 6.6.2072.4 and anti-stealth 1124. EDIT: I read this as the key should exist? I wonder why it does not currently exist for (and others).

Sadly I do not have one. The percentage sat at 0% when the bsod occurred and event log says: "Dump file creation failed due to error during dump creation."

So, with the anti-stealth update 1124, I got at least the Flash update and a bunch of Office updates (I'm not sure if these are patch Tuesday updates). Interestingly my computer BSOD'd when or right after installing the Office updates! Coincidence? It seems 16299.248 release notes (KB4074588) were just pushed, so let's see if I get that later. As said, it will be a forever mystery why I was stuck at 16299.19 in the first place. EDIT: My desktop and another laptop without ESET just updated to 16299.248. My laptop with ESET cannot see the update yet. Gonna wait till tomorrow and then try uninstalling ESET if it does not appear and see what happens then. (Is there some registry thing again?) EDIT2: The last event log entry before the BSOD is: This update is not offered to me anymore after the BSOD?

Patch Tuesday is coming up and I've installed the product again. Anything specific you guys want to try out?

Hey. So, my Windows installation was stuck at 16299.19 (notice no 2 at the end), which is almost half a year old! Noticed this issue when Windows started warning me that I should install my updates, although I thought I had been doing so for the past months. I manually installed 16299.192 and forgot about it, but now I noticed that I wasn't bumped to .214 either, although my desktop was. Also, I now noticed that uninstalling Eset makes other updates available as well, such as Adobe Flash. Office updates seem to have been installed properly though. EDIT: I'm on Eset Endpoint Antivirus 6.4.2014.0 and Windows Enterpise x64.