KB4090007 Intel Microcode Updates for Windows 10 v1709 - January 8

Anibor said:

There is an explanation here: Intel processor design flaw forces Linux, Windows redesign | Page 41 | Wilders Security Forums, post #1013.

Thanks for the link, quote:

At boot up the appropriate microcode data is copied to the CPU at boot time, but only if the revision stored in this file is later than the revision that was copied to the CPU by the bios prior to boot. So anyone who gets a bios update with the new microcode from their OEM/supplier, won't see any affect of this update.

Some correction for this quote from the link...

The OS will copy the newer microcode code to the CPU during boot time. Once the system is shutdown, the copied microcode stays in the OS partition, but not in the CPU in itself. If the system only has Windows OS, loosing the copied microcode in the CPU does not matter. Windows just copies the microcode again at the next time the system is booted.

If the system is dual booted and neither the BIOS nor the second OS have the latest microcode, the second OS is vulnerable to the Meltdown/Spectre exploits.

There's some disadvantage for manually applying the KB4090007. If the backup image restored does not have this patch installed, it will be vulnerable until it is installed, provided the BIOS had not been updated with the latest microcode. The same goes for reinstalling Windows, since the KB4090007 is not pushed to Windows by MS.

If the motherboard has been updated with the latest microcode, it does not matter if the KB4090007 had been installed manually, or not. Windows, for that matter Linux, will not overwrite the microcode, if and when the BIOS has the same or later version of the microcode.

Intel Newsroom problem today:

Access Denied
You don't have permission to access "http://newsroom.intel.com/wp-content/uploads/sites/11/2018/02/microcode-update-guidance.pdf" on this server.
Reference #18.403b3717.1521311110.1d943441

The most recent guidance is from the 6th of March. That's a link to guidance from last month.

https://newsroom.intel.com/wp-conten...e-guidance.pdf

Ground Sloth said:

The most recent guidance is from the 6th of March. That's a link to guidance from last month.

https://newsroom.intel.com/wp-conten...e-guidance.pdf

Did you check your own link?

Access Denied
You don't have permission to access "http://newsroom.intel.com/" on this server.
Reference #18.6b9a7a5c.1521316346.4def20fb

Access Denied
You don't have permission to access "http://newsroom.intel.com/wp-content/uploads/sites/11/2018/03/microcode-update-guidance.pdf" on this server.
Reference #18.6b9a7a5c.1521316368.4defd9bd

Hi,

Did you check your own link?

Clicking that link automatically starts downloading the pdf file for me. It has always done so.

Cheers,

fdegrove said:

Hi,



Clicking that link automatically starts downloading the pdf file for me. It has always done so.

Cheers,

Empty your caches and you will see that the Newsroom site is down. What was always is not always.

Hi,

Nope, it is not down at all. Can you change the tone as well ? Thank you.....

Cheers,

fdegrove said:

Hi,

Nope, it is not down at all. Can you change the tone as well ? Thank you.....

Cheers,

It is down for me and others! newsroom.intel.com resolving to e11.b.akamaiedge.net [23.56.184.207]

Where does your DNS point to?

indianacarnie said:

Link works just fine for me............................

Link works fine here too...