Going nuts over repeated KB4055532 Update Fails

Update 2018-01 Security & Quality Rollup for.NET Framework (KB405532) has failed to install umpteen times since it first popped up in Windows Updates on January 27. Error code 800B0100 is reported every time and is of course meaningless: when I seek "get help with this error" I'm merely told to "Please check your spelling".

I've now read and tried (but failed) to understand the relevant Microsoft KB405532 article, part of which states:

"A default installation of Windows 7 SP1 or Windows Server 2008 R2 SP1 will not have an antivirus application installed. In these situations we recommend installing a compatible and supported antivirus application such as Microsoft Security essentials or a third-party antivirus application. The antivirus software must set a registry key as described in the "Setting the registry key" section for you to receive the January 2018 security updates. . .

" You will not receive the January 2018 security updates or any successive security updates and will not be protected from security vulnerabilities unless your antivirus software sets the following key: HKEY_LOCAL_MACHINE Subkey=SOFTWARE\microsoft\Windows\Current Version\QualityCompat Value= cadca5fe-87d3-4b96-b7fb-a231484277cc Type=REG_DWORD Date=oxoooooooo."

My desktop PC is running Windows 7 Home Premium SP1. Avast antivirus is installed and is fully up to date. I do NOT allow Microsoft to install updates automatically, but merely to alert me to their existence.

Unfortunately, I am a novice where computers are concerned so am having a hard time of it, trying to fathom all this. There's also the fact that these repeated KB4055532 failed installs have coincided with two failed boot ups: just coincidence? No idea, but I've never had these problems before. And then, finally, to add to all this, NVIDIA Display 23.21.13.8813 is equally, and repeatedly, a failed install. Again: coincidence??

Bearing in mind that I'm anything but well-versed in computing, is there nevertheless something a simpleton such as I can do to comply with Microsoft's specific warning about there being no future security updates for me "unless your antivirus software sets the following registry key". Er yes, well, OK . . . but HOW??

Help appreciated. Thanks.

PS: My graphics card is an NVIDIA GeForce GTX570. According to my GeForce Experience dashboard, an update is available: Game Ready Driver, version 381.65, released 4/6/2017. The driver update is to fix gameplay on "Quake Champions Closed beta" (oh really?) but I don't play any games, anyway. The current driver version 344.48 ain't broke so I haven't fixed it. What I can't work out is if this is what the NVIDIA Windows Update is referring to, because if it is, then I need no longer bother worrying about it. . .

H Phil.

Cutting to the chase
Its all about the Meltdown & Spectre debacle.
There are conflicting reports flying around - Update Dont update - wait for this etc

The Kb your referencing was the 1st issued, to TRY and fix it, and was dependent on the AV running on your system having that registry key
There are reports, just like yours, regarding Boot failures because of MS Driver updates
Please turn OFF MS driver updating, see screenshot


Open Regedit, then navigate to
HKEY_LOCAL_MACHINE Subkey=SOFTWARE\microsoft\Windows\Current Version\QualityCompat Value= cadca5fe-87d3-4b96-b7fb-a231484277cc Type=REG_DWORD Date=oxoooooooo."

note i belive Avast included the fix in late January

However thats not the only fix required or being issued
Your manaufacturer for CPU, GPU and OEM's Bios (depends on your Motherboard)

Back to the MS update - it also included a hardening patch for IE and NetframeWork.
As you stated you only View MS, i would suggest that you install any that relate to IE and Netframework, as this update may be dependant on earlier patches.


If you have a restore point or Image dated LATE December roll back to it.>> then update

Roy

Roy: many, many thanks for that really helpful (and quick!) response, as constructive as it's comprehensive.
I was unaware of anything to do with Meltdowns and Spectres (doh!) so should maybe take a bit more interest in the computing world around me. That said:

(1) The screenshot was great. I've changed my settings to match those shown -- so: BIG thanks;

(2) I've "hidden" the pesky NVIDIA update. I honestly don't see why I need it;

(3) I've opened regedit and found the key. . . but, but (and here we go, me being stoopid again):

I'm not sure what I'm supposed to do about adding the REG DWORD Date= . All that's showing on my regedit screen is 2 lilnes of information:

Line 1: a standard icon with (Default) next to it;

Line 2: a different icon for the cadca5fe etc etc etc key.

And that's all there is.

I guess both of those entries can be modified via right clicking but, er, which one? Or do I not modify anything at all but instead attempt to add in the DWORD data separately?

Sorry to be so thick.

Regards:

Phil

PS: meant to say, no, I unfortunately don't have any restore point or image for late December. Iyiyiyiyiyi.

Roy: sorry to be a nuisance, but it's just dawned on me, what this spectre and meltdown stuff is all about. I now remember hearing about it on the news. However . . .

Not being overly blessed with intelligence when it comes to matters computing, I didn't take much interest in what was being said after hearing a commentator say "The problem relates to computers with Intel chips and dates back xxxxxx years."

Yes, but . . . My PC is NOT Intel. It's AMD. Specifically: AMD FX-45100 (Zambezi) dating from 2014.

Thanks to you awakening my interest, I've found this revelation on Microsoft's website:

'Microsoft has now resumed updating all AMD-based devices with the Windows operating system security update to help protect against the chipset vulnerabilities known as Spectre and Meltdown.

'Microsoft worked with AMD to resolve update blocks on a small subset of older AMD processors (that were previously blocked to avoid users getting into an unbootable state after installation of recent Windows operating system security updates).'

I'm beginning to wonder if somehow, in some way, the mess I've gotten into here with failed boot-ups (and all the panic that triggered) signals that whatever the "previous blocking" might've been, it certainly was never enough to prevent "users getting into an unbootable state". And specifically: AMD users.

Really, this kind of thing is just so-oooo. . . frustrating, and especially when it's not self-inflicted: I haven't, and I don't, mess with my computer, because I'm really not bright enough to know what I'm doing. If it stops working, then I'll ask. (And ask here . . . hence why I'm being such a nuisance now: apologies!)

Hi Phil,

as i said a total DEBACLE
a prime example of the left hand not knowing what the right ones doing

Spectre & Meltdown, as you have discovered, 2 different problems revealed at the same time
AMD was only affected by 1 of them, unfortunately the updates issued by MS didnt take this into account and they had to pull-it, as they said the source code they had in thier library was different to that shipped in computers - hence the boot issue.

We all have our own expertise niches, mines just computers suspect you have your own.
Absolutely NO need to apologise, and your not a nuisance
Thats why were here

As for the registry value as long as its Present your up to date in this regard, it can only be set by the AV not MS. see mine in screenshot.

As for updating, can you view your hidden ones see if any relate to IE or Netramework, if so install them and then kb4055532.
If it fails then we'll need to dig a bit further.

MS now issue monthly updates, next ones tomorrow, unless a major flaw is found
Might be worthwhile waiting for them.


Roy

Hi Roy: Back again . . . I really can't thank you enough for your patience, and your help. You've clarified so much for me that it's a real weight off my mind. That said:

A further apology is needed -- I know, I did say I was a computer numpty, but no-one gets numptier than me in opening regedit but failing, entirely, to upsize the window . . . DOH!!! Now that I've seen the screenshot you so kindly took for me, I realise the error of my ways, because, um, yes: with the column headers 'Type' and 'Data' at last (at last!) in view, I can also see that my regedit screen is exactly the same as yours, and crucially, the REG DWORD data. So that's all right then.

As to the rest: I'll go through my record of updates (failed and successful) and re-check that I haven't inadvertently hidden stuff that I need.

Meantime -- and I know this sounds like the confessions of the suicidal -- I'm sitting here remembering what happened before with Windows Blasted Updates, back when my then-new computer was running Vista. All was well for three or four months, and then Windows Updates ceased altogether. The problem was eventually traced -- and God knows, it took an age to do so -- to some kind of issue over the actual Windows OS certificate. The computer was a Dell, bought from Dell. The Windows cert was genuine. But could Microsoft Support even begin to figure out what had happened from the Event Log of that period, and why? Nope. Not a chance. So-oo . . .

Despite all advice to the contrary, but because I was sick, weary and tired of Microsoft, I ran my computer from then until I junked it three years and six months later . . without a single Windows Update.

It was protected by Malwarebytes Pro (the paid-for full version, nowadays called Malwarebytes Premium), as well as Avira (paid), and, last but not least, WinPatrol Pro. Flash and Java and Firefox were always but always updated as required. All three main protectors played nicely together; I never experienced a single security issue -- nor any computer hiccoughs, either. Vista just ran and ran . . . without the updates that some folks were telling me I couldn't afford not to have.

Since replacing that much loved Dell with this specially built desktop, I've been meticulous in studying Windows Updates alerts and updating where such seems important. (I've also been scrupulous about avoiding Microsoft's shameful Windows 10 upgrade: Windows 7 suits me just fine.)

So. There we are. From 2012 to now, 2018, the only problems I have had with my computers have arisen from . . . Windows Updates.

On which basis, I'm going to leave off any further updates for the time being. I still have the triple protection in situ (though Malwarebytes Premium reckons a stand alone AV isn't needed now to run alongside it) and Scotty the dog still woofs at anything suspicious. I'm not saying, ah, who needs Windows Updates, but I am thinking that until I can be a damn sight more certain of their accuracy and their relevance to me and my computer, then I'm better off without all the time-wasting hassle Microsoft causes me.

Sincere thanks again, Roy; your help has been invaluable! And no more pestering from me. . . until, er, the next time. :)

Hi Phil,

No worries:).

Were allways around.

Hope NOT to see you soon


Roy