New
#80
I ran updates on all four of the AV packages I have installed (MBAM,Spybot S&D, NIS, and MSERT). NIS is the only one active. After the MSERT update, WU automatically ran a search for updates and found none. System is still at .309. I looked at the reg key listed above and the data value was 0. I ran PhoneMan's reg key and the above listed reg key still shows a data value of 0, but WU is downloading the update. Be afraid, be very afraid. Thank goodness I have a System Image from right after .309. 15 minutes later, the system is at bld. 16299.334. Now I have just enough time to do another system image save before next week's cumulative update is released.
Last edited by jamis; 24 Mar 2018 at 17:33. Reason: added text
How did you try to open it. If your right click under Open With it should default to Registry Editor. On my system I use a double left click and Registry Editor will open. I am getting a unsigned warning. I downloaded the reg file from Bleeping Computer from this article. Scroll down and it is right above the RED Warning banner.
https://www.bleepingcomputer.com/new...tre-cpu-flaws/
Jim
Yea, this quality compatibility by Microsoft on this issue appears a bit confused in implementation on their part. You are at 334 without the key being present. I did not have the key and the KB update would not install or even be seen by Windows Update. All is well now with this machine but many will not get things right, especially if they don't seek help like that found in this thread. We'll see going forward if this continues to plague folks with Windows Update and as you say, "do we need this key or we don't?"
Last edited by wordsworth; 24 Mar 2018 at 18:21.
The machine didn't like it at all. CPU Fan went crazy, lost internet and the network switch after reboot. Shutdown to stop the fan from running at high speed after deleting the key.
Is that key usually there (QualityCompat)?
Got it from the catalog and no issues. Same as usual for a 700+MB file, about 10 minutes. QualityCompat still not there
I haven't been offered this update yet on any of my 3 PCs running v1709 Build 16299.309. I wonder why not?
I had the same issue and found the QualityCompat reg key mentioned in earlier posts which I definitely had before had been deleted. I'm not sure whether it was a previous Windows update or Malwarebytes update which did this.
I added the reg key back and KB4089848 started downloading immediately when I checked for updated in Windows Update.
Judging by the number of people reporting the same issue I think Microsoft screwed up big time when they released KB4089848. Windows Update is clearly still checking for the existence of the QualityCompat reg key which they now say is no longer required.
I think all of March's updates have been hosed up by MS in some fashion or another. Wondering what maladies SCU will foist on us next month.