SieraZ

Looks like AS module version 1125 has resolved this issue - the updates are now coming through to all our PCs. Thanks for sorting this out @Marcos

@Marcos Thank you. Will the new version of AS write this value for existing installations after being updated to?

OK, so here are my findings: when upgrading directly from 6.4 to 6.6 the aforementioned registry key is not populated with the required value. As a result some Windows patches are not being offered when checking for updates. Then after uninstalling 6.6 and reinstalling it again the value gets populated and the patches become available. @Marcos Here's the link to the bootlog created on a PC with 6.6 after the upgrade. Anti-stealth module version is 1124. https://www.dropbox.com/s/s7mldq7p09x7z7w/Bootlog.zip?dl=0

No, i meant i just didn't wait long enough for the program to be fully installed. Once fully installed the value was there, but also yes, it took a full uninstall/reinstall cycle for it to appear. I will find another affected PC and try and get you the required logs.

I have reinstalled ESET and the value still does not exist. I am also unable to manually add it even if running regedit as the inbuilt Administrator account. EDIT: The value has appeared after a refresh! Does this mean I will have to fully uninstall and reinstall all the endpoints (around 150) for this to work properly? Before this the endpoints were upgraded from 6.4.2014.0 without uninstalling it first.

@Marcos My apologies, I've just said myself that I had uninstalled it duh! I've just checked another PC that is affected and the value is not present

@Marcos Yes, the Anti-Stealth module version is 1124 but I don't seem to have this registry key at all

I can confirm that the latest and up-to-date version of ESET Smart Security (6.6.2072.4) is blocking the latest Windows 10 updates including the newest KB4074588. As soon as it is uninstalled the patches become available in Windows Update.