• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Intel Microcode Bootloader

D

Dexter1983

New Member
Joined
Apr 23, 2019
Messages
5 (0.00/day)
Hi someone could help me to configure Intel Microcode Boot loader in windows 10 build 1809 so that it is loaded not by pendrive but by a dedicated mini fat32 partition? Can you help me?
 
Fill your specs.

90% you can mod the bios using UBU and quit joking around. Also mitigations are currently baked in the kernel, you can feed any microcodes you wish.
 
Ferrum Master said:
Fill your specs.

90% you can mod the bios using UBU and quit joking around. Also mitigations are currently baked in the kernel, you can feed any microcodes you wish.
Click to expand...

Yup, much less painful to just load those patches into the BIOS.
 
What do you need the updated microcode for?

Windows by itself also updates the microcode. You can check the versions before and after update in registry mentioned here.
 
Ferrum Master said:
Fill your specs.

90% you can mod the bios using UBU and quit joking around. Also mitigations are currently baked in the kernel, you can feed any microcodes you wish.
Click to expand...

What specs do you need? Cpu? Ram?
Or the partition/disk/volumes in my configuration?

Flaky said:
What do you need the updated microcode for?

Windows by itself also updates the microcode. You can check the versions before and after update in registry mentioned here.
Click to expand...
Just for study, IMB is a very good workaround and i'd want to learn how it works

I can do it on windows 7 but not on windows 10....why? The xcopy command fails with "access denied" error and my account is an administrator!
 
Access denied is related to NTFS permissions. You need to login to recovery console with administrative account with full RW permissions for both source and destination.
 
@Regeneration

I did some tests with little success:
I state that for my processor (Core i7 2820-qm 206A7) the microcode version that corrects spectre v2 is 2D (Distributed also by Microsoft in a Windows 10 environment) later Intel released version 2E, with other fixes. Intel Microcode Boot Loader has the latest 2E as standard, the experiment consists in flashing a bios with microcode version equal to or lower than 2D (distributed by microsoft) to see if Intel Microcode Boot Loader microcode actually upgrades to version 2E, the result is that even if everything works in appearance (the software is loaded at startup and the operating system is launched) however aida 64 detects a 2D microcode version, did I miss anything?

Wrong platform ID.......should be 12.....why?
 

Attachments

  • Screenshot.jpg
    Screenshot.jpg
    168.7 KB · Views: 472
Dexter1983 said:
@Regeneration

I did some tests with little success:
I state that for my processor (Core i7 2820-qm 206A7) the microcode version that corrects spectre v2 is 2D (Distributed also by Microsoft in a Windows 10 environment) later Intel released version 2E, with other fixes. Intel Microcode Boot Loader has the latest 2E as standard, the experiment consists in flashing a bios with microcode version equal to or lower than 2D (distributed by microsoft) to see if Intel Microcode Boot Loader microcode actually upgrades to version 2E, the result is that even if everything works in appearance (the software is loaded at startup and the operating system is launched) however aida 64 detects a 2D microcode version, did I miss anything?

Wrong platform ID.......should be 12.....why?
Click to expand...

Sounds like an issue with Intel Microcode Boot Loader, not sure you can do anything about it.
 
Dexter1983 said:
@Regeneration

I did some tests with little success:
I state that for my processor (Core i7 2820-qm 206A7) the microcode version that corrects spectre v2 is 2D (Distributed also by Microsoft in a Windows 10 environment) later Intel released version 2E, with other fixes. Intel Microcode Boot Loader has the latest 2E as standard, the experiment consists in flashing a bios with microcode version equal to or lower than 2D (distributed by microsoft) to see if Intel Microcode Boot Loader microcode actually upgrades to version 2E, the result is that even if everything works in appearance (the software is loaded at startup and the operating system is launched) however aida 64 detects a 2D microcode version, did I miss anything?

Wrong platform ID.......should be 12.....why?
Click to expand...

According to your screenshot, the microcode wasn't updated.

Make sure the correct microcode file is placed in the /mcu folder.

PlatformID is reported by the BIOS. The false value came from the manufacturer.
 
Is there anything I can do to induce a correct detection of the platform ID? I've already put the correct microcodes in both the MCU folder and the MCUDB folder
 
@Dexter1983 :

Hi Dexter, one question: How did you get the screenshot? On my machine this bootloader is running through very fast and then loading OS.
 
On most PCs, the PAUSE key will pause the screen output during POST.

You can slow it down by placing a lot of ucode files in the \mcu folder.
 
Thanks @Regeneration, now I got it. It's not easy to catch the right moment, so I had to try several times.

Maybe you could add a small logfile on the stick that is replaced at each system start? This would be easier than PAUSE...

Regards, Ludwig.
 
Regeneration said:
You can slow it down by placing a lot of ucode files in the \mcu folder.
Click to expand...
That trick didn't really help: Error messages for the wrong CPU files before and after the matching one were not displayed, so again it was a very short moment to hit PAUSE... But of course it's not necessary to check the message at each system start, maybe when a new versions is tested.
 
Ludwig von Ay said:
That trick didn't really help: Error messages for the wrong CPU files before and after the matching one were not displayed, so again it was a very short moment to hit PAUSE... But of course it's not necessary to check the message at each system start, maybe when a new versions is tested.
Click to expand...

edit grub.cfg, find "mcu_load /boot/mcu" and replace with:

py 'import sys; sys.path = ["/boot/python", "/boot/python/lib.zip"]; del sys'
py 'import init; init.early_init()'
mcu_load /boot/mcu
py 'from bits import pause ; pause.pause()'
 
Great! It works. :toast:

Now I have two cfg files - one for 'normal life', the modified one for testing purposes.

Regards, Ludwig
 
Dexter1983 said:
@Regeneration

I did some tests with little success:
I state that for my processor (Core i7 2820-qm 206A7) the microcode version that corrects spectre v2 is 2D (Distributed also by Microsoft in a Windows 10 environment) later Intel released version 2E, with other fixes. Intel Microcode Boot Loader has the latest 2E as standard, the experiment consists in flashing a bios with microcode version equal to or lower than 2D (distributed by microsoft) to see if Intel Microcode Boot Loader microcode actually upgrades to version 2E, the result is that even if everything works in appearance (the software is loaded at startup and the operating system is launched) however aida 64 detects a 2D microcode version, did I miss anything?
Click to expand...

the i7-2820QM seems to be an laptop/mobile based Intel Sandy Bridge CPU.
 
@Regeneration: any chance of the Intel Microcode Bootloader software being updated to have the recent fixes mentioned in Intel security advisory INTEL-SA-00233?
www.intel.com

INTEL-SA-00233

INTEL-SA-00233
www.intel.com www.intel.com
 
might need to be updated again. MS revised the intel microcode patches for Win10 near the end of August, reverting the Intel microcode fixes for apollo lake & gemini lake series
 
You must log in or register to reply here.
Back
Top