KB4100347 Intel microcode updates for Windows 10 v1803 - January 8 Win Update

Intel refreshed the 20180807 uCode release with 20180807a ostensibly for CVE2018-3639 & CVE2018-3640, no idea when, as the document carries no revision to the date.

Yet MS re-emit KB4100347 again (possibly as a result of the above) and no extension of scope to KB4346084 (new processors only).

"But hey, get your patches for Spectre variants 1 and 2!"

ddelo said:

I would partly agree with my fellow Greek and namesake...it is hidden (with the tool he described) until the Microsoft geniuses change the prefix of its name, i.e. from "2018-09 Update for Windows 10 Version 1803 for x64-based Systems (KB4100347)" to "2018-10 Update for Windows 10 Version 1803 for x64-based Systems (KB4100347)", in which case it will be offered again!!!

Indeed my friend, the 1809 update apparently includes the microcode update. I just updated and the overclocking is gone for good this time!
Let's hope that either MS or Intel provide a solution.

winactive said:

artins90 said:

I have a PC dedicated to rendering only, basically I connect it to the internet only for driver updates.
I run it will all the mitigation disabled, to circumvent mcupdate_GenuineIntel.dll I just renamed it to "mcupdate_GenuineIntel.dll.disabled" and it looks like it gets disabled correctly according to the get-speculationcontrolsettings powershell module.

If you run a sfc/ scannow, the file gets marked as corrupted and you need to rename it again.
It's also protected so you need to get ownership of the file in order to rename it.

Brilliant! I don’t often have the need to run SFC often, if at all. Thank you!

From another thread.

winactive said:

From another thread.

Thank you! I took ownership of mcupdate_GenuineIntel.dll, renamed it and after the reboot the overclocking was back!

dimitris123 said:

Thank you! I took ownership of mcupdate_GenuineIntel.dll, renamed it and after the reboot the overclocking was back!

No problem the other user takes all the credit! 👍

I'm not really following what you are doing with GenuineIntel.dll but should I run sfc/scannow after updating to 1809 to get rid of this corrupted file/files?

andyouf said:

I'm not really following what you are doing with GenuineIntel.dll but should I run sfc/scannow after updating to 1809 to get rid of this corrupted file/files?

No, it's not corrupted. We are disabling it ON PURPOSE to AVOID forced uCode updates through the OS (v1809).

I see. Thank you. And just to confirm the MS ucode updates won't mess with my OEM's BIOS update even though the MS updates went first, then I did the BIOS update, now apparently more ucode updates? Is my BIOS update still taking precedence?

andyouf said:

I see. Thank you. And just to confirm the MS ucode updates won't mess with my OEM's BIOS update even though the MS updates went first, then I did the BIOS update, now apparently more ucode updates? Is my BIOS update still taking precedence?

*speechless*