KB4497165 Intel microcode updates for Windows 10 1903 and 1909 Sept. 1 Win Update

Ground Sloth said:

When it comes to releasing BIOS updates that address security issues, HP seems to give priority to business PCs and workstations, followed by OMEN gaming computers.

Even if you have a home PC that is relatively new, you might have to wait quite a while.

OK, that explains it then, as I run a (Good) OMEN Notebook! Thanks.
- But the 306C3 is clearly now in HP's release 'pipeline' anyway.

Ground Sloth said:

When it comes to releasing BIOS updates that address security issues, HP seems to give priority to business PCs and workstations, followed by OMEN gaming computers.

Even if you have a home PC that is relatively new, you might have to wait quite a while.

Good to know. In any case, I am not in a hurry since my main machine (HP Envy) still on 1809 is running super smooth just the way I like it. Nowadays, one never knows what kind of headache a new update can bestow upon us. LOL!

My HP laptop got a bios update on May 14th. Dose this mean I do not need the microcode updates
from Microsoft?

rezpower said:

My HP laptop got a bios update on May 14th. Dose this mean I do not need the microcode updates
from Microsoft?

You don't need it.

Under Fixes it says

- Enhancement to address security vulnerabilities CVE-2018-12126, CVE-2018-12127, CVE-2018-12130.

Those are the MDS vulnerabilities that the latest Intel microcode update mitigates. So that's just another way of saying that the BIOS update contains the latest CPU microcode update.

Ground Sloth said:

You don't need it.

Under Fixes it says




Those are the MDS vulnerabilities that the latest Intel microcode update mitigates. So that's just another way of saying that the BIOS update contains the latest CPU microcode update.

Thank you very much for the information. I didn't know and installed the microcode which broke my windows Sandbox! So good to know that I don't need it :)

rezpower said:

Thank you very much for the information. I didn't know and installed the microcode which broke my windows Sandbox! So good to know that I don't need it :)

If you want to be absolutely certain that the MDS mitigations are enabled, there is a PowerShell script from Microsoft that will tell you.

https://support.microsoft.com/en-us/...ngs-powershell

IronZorg89 said:

Nowadays, one never knows what kind of headache a new update can bestow upon us. LOL!

No kidding. Bios updates scare me a bit but decided to take the plunge and did mine (from Dell) a few minutes ago, all looks well after rebooting but I am keeping my fingers crossed for a while.

Bo

bo elam said:

No kidding. Bios updates scare me a bit but decided to take the plunge and did mine (from Dell) a few minutes ago, all looks well after rebooting but I am keeping my fingers crossed for a while.

Bo

The whole point about BIOS/UEFI update is to really make sure you are doing it the right way — if you know what I mean, talking about bricking your machine — otherwise, everything should be OK. I am a bit like you when confronted with that experience.

bo elam said:

No kidding. Bios updates scare me a bit but decided to take the plunge and did mine (from Dell) a few minutes ago, all looks well after rebooting but I am keeping my fingers crossed for a while.

Bo

I almost borked one of my computers last year doing a BIOS update. After flashing the BIOS. the computer wouldn't POST. I tried, unsuccessfully, to revert to the previous BIOS revision. But somehow after about 30 minutes I got the updated BIOS to POST. I still have no idea what I did that got it to work.