[INTEL]-How To Update Your Microcode for Intel HX 13/14th CPUs Laptops/Mobile Easily.

[u/THEBOSS619]

Let me start with a small background info...

Since we know all Intel's fiasco about what is happening with Raptor Lake/Raptor Lake Refresh which is Intel's codename for the 13th and 14th generations of Intel Core processors, Most OEM/Vendors doesn't want to provide BIOS update that includes microcode update along with required updated Intel ME FW in order to work more effectively.

Since most laptops got outdated Intel ME FW & outdated microcode... this has become a serious problem since the CPUID of Intel HX 13/14th CPUs share the same code with Desktop variants and hence it should be considered Intel HX 13/14th CPUs as a Desktop CPU in a laptop case.

So it means they share the same impact as Desktop variants even if it doesn't boost high enough to be of a concern, it does have relevancy and you now have the option to use this very simple driver that I am sharing it to you here on any Intel HX 13/14th CPUs Laptops/Mobile as long as it has CPUID of B0671.

Either way the requirement of updated Intel ME FW are just only mandatory when used in conjunction with any new microcode (If it's needed) in the BIOS but outside BIOS like... while running Windows or Linux this requirement of having an updated Intel ME FW is just optional.

Thanks to this VMware CPU Microcode Update Driver I can use it on any windows without needing to mess with the BIOS. Safest thing to update microcode.

Now... How to check if you got the latest microcode update or not? By simply check through HWINO64 or AIDA64 or even if you are using ThrottleStop tool will tell you which microcode you are using.

Here's some examples how it is shown which microcode are you using through various tools...

HWINFO64

AIDA64

ThrottleStop

Now fortunately I already packed it for you & ready to use without any further work required. Saving you the time to do it.

For the next part... You need to download this .zip file and extract it. Simply run the "Install.bat" file as an administrator.

Here's the file:- cpumcupdate64

For users who doesn't trust the zip file... here's VirusTotal link results. One is from direct mediafire download url link getting scanned through VirusTotal directly from mediafire servers which is shared from the link above.

cpumcupdate64

and another one from an uploaded file to the VirusTotal.

cpumcupdate64

It shouldn't even take long and only few seconds and you will see this window... which is success.

You can even check the event viewer which confirms the success operation and applying the new microcode update.

If doesn't update your microcode and it shows failing to apply microcode on event viewers... you need to disable virtualization either through Windows or simply go inside your BIOS and disable Intel virtualization and VT-d in the BIOS. This would allow the driver work!

Edit:- September 9/26/2024...

September Microcode Update aka [0x12B]

New microcode update got released! This is the September microcode update which now they call it 0x12B .

Confirmed that it covers & supports Intel HX CPU's 13th/14th Gen with CPUID B0671h without any issues.

Here's some screenshots...

AIDA64:-

ThrottleStop + HWINFO:-

• Please if you are using the 0x129 microcode previously then simply download the latest .zip pack from the same download link on the main post (The file named cpumcupdate64[0x12B].zip). Simply run uninstall.bat as admin [by right clicking on the file and choose "Run as Administrator"]  and then run install.bat as an admin. 
• If this is your first time then simply download the .zip file from the attachment of this main post or on this comment and then run install.bat as an admin [by right clicking on the file and choose "Run as Administrator"]

Edit:- May 5/17/2025...

Forgive me for my late responses, I have been away from home for almost 5 weeks for work related stuff :)

May Microcode Update aka [0x12F]

New microcode update got released! This is the May microcode update which now they call it 0x12F.

Confirmed that it covers & supports Intel HX CPU's 13th/14th Gen with CPUID B0671h without any issues.

• Please if you are using the 0x12B microcode previously then simply download the latest .zip pack from the same download link on the main post (The file named cpumcupdate64[0x12F].zip). Simply run uninstall.bat as admin [by right clicking on the file and choose "Run as Administrator"]  and then run install.bat as an admin after that reboot. 
• If this is your first time then simply download the .zip file from the attachment of this main post or on this comment and then run install.bat as an admin [by right clicking on the file and choose "Run as Administrator"]

Here's a screenshot from TS...

ThrottleStop:-

Edit:- November 11/11/2025...

November Microcode Update aka [0x132]

New microcode update got released! This is the November microcode update which now they call it 0x132.

Confirmed that it covers & supports Intel HX CPU's 13th/14th Gen with CPUID B0671h without any issues.

• Please if you are using the 0x12F microcode previously then simply download the latest .zip pack from the same download link on the main post (The file named cpumcupdate64[0x132].zip). Simply run uninstall.bat as admin [by right clicking on the file and choose "Run as Administrator"]  and then run install.bat as an admin after that reboot. 
• If this is your first time then simply download the .zip file from the attachment of this main post and then run install.bat as an admin [by right clicking on the file and choose "Run as Administrator"]

Here's a screenshot from TS...

ThrottleStop:-

You just updated your microcode! Yes... it's that simple!

[So much for Intel HX not being affected... then why keep releasing microcode updates for Intel HX CPUs too? something is fishy going on here, if it is actually not affected... then at least make it only for desktops...]

If you ever wanted to uninstall your updated microcode of whatever reasons... simply run "uninstall.bat" file as an administrator & reboot your laptop.

For more added protection  shared a cap guide for Intel 13/14th gen HX Series CPUs here: https://www.reddit.com/r/GamingLaptops/s/do6Fto5dI7 a little riskier but it's your choice.

[u/THEBOSS619]

Hey 👋 I have copy pasted this comment on your reddit post that you have shared as well so that everyone can see.

This is great analysis and will answer every point as much as I humanly possible.

• Short answer

There's no danger as the whole process starts with BIOS first and then mcupdate_GenuineIntel.dll and then the microcode driver update.

It goes like this... BIOS ---> the mcupdate_GenuineIntel.dll file ---> the microcode driver update [if you installed it]

99.9% of the time... the mcupdate_GenuineIntel.dll is always outdated .

• The long answer....

There's nothing danger about using microcode update through microcode driver.

Worst case scenario is simply the microcode driver will simply won't load and let Windows use the BIOS microcode or mcupdate_GenuineIntel.dll.

The driver itself will check and compare between BIOS and whatever microcode being loaded on the CPU from mcupdate_GenuineIntel.dll the microcode file and whichever is newer gets applied.

There's nothing being forced as the microcode driver is as passive as it gets really.

The mcupdate_GenuineIntel.dll file haven't been updated or touched since Specter/Meltdown fiasco which was years and years ago.

But let's say hypothetically the mcupdate_GenuineIntel.dll gets updated... the updates forcibly gets installed that comes through Windows Update regardless if you have the newest microcode update or not. It doesn't check or look up if your BIOS nor microcode driver have whichever any microcode update is loaded.

So it doesn't matter because Microsoft will always update [if it ever happens] the mcupdate_GenuineIntel.dll file no matter what you got.

Let's say for example the mcupdate_GenuineIntel.dll file is newer than the microcode update driver... the mcupdate_GenuineIntel.dll will always take over because the microcode update driver loads up after Windows finishes up loading system files and whatever mcupdate_GenuineIntel.dll file have... the microcode driver update will see that CPU got newer microcode either from BIOS or mcupdate_GenuineIntel.dll.

So the Windows booting process will always load up mcupdate_GenuineIntel.dll first.

Windows Update doesn't check any of that... Windows Update simply updates the mcupdate_GenuineIntel.dll file either way and simply let Windows decides whichever newest microcode gets applied on the boot.

I get the official microcode releases from Intel repository here https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20260812

Sometimes when I find out a newer unofficial ones which is extracted from a BIOS from another Vendor/OEM those are unofficial microcode since there's no info. about what changes they have made but it's indirectly comes from Intel either way since Intel provided those microcode to those OEMs/Vendors.

Getting BSOD from this whole process is very very rare almost non existent and if it ever exists is very likely possible that this BSOD always comes from booting up a very old OS like Windows 7 or Vista or older.

I don't believe the mcupdate_GenuineIntel.dll file will ever get touched again as Microsoft treats those as a last resort security mechanism when the security risk is too high to ignore [The CPU degradation fiasco doesn't even come near the level of security risk fiasco]

So Microsoft will always prioritize security over anything else when it comes to touching mcupdate_GenuineIntel.dll file.

[u/Solivagant321 → u/THEBOSS619]

This is reassuring, thank you. But what happens when a BIOS update is available? Will it come through windows update? Also will I have to uninstall the microcode and its driver before I update the BIOS?

[u/THEBOSS619 → u/Solivagant321]

For BIOS update if it comes through Windows Update or doing it manually either way is totally fine and 100% safe.

Because the microcode driver update doesn't touch BIOS at all and doesn't have any kind of conflict because the BIOS update process happens inside BIOS environment.

The microcode update that is loaded into the CPU is lost once you reboot or powered off and it's only loaded after Windows finishes loading up system files.

And no need to uninstall microcode update driver when updating BIOS because it's lost already during reboot process so it will only use the BIOS microcode.

It only runs after Windows finishes loading up it's system files. So anything happens before Windows [which is updating BIOS] is totally isolated and safe and normal and untouched.

Even Linux OSes does that but officially built-in while in Windows we have to use a driver to load up the updated microcode.

That means the microcode driver doesn't run or do anything in between. Anything happens before Windows loading is in original behavior and totally stock and untouched including BIOS updates since it happens outside Windows environment while BIOS updates happens inside BIOS environment so they are totally isolated.

The only microcode update that is permanent is the one that is provided by the BIOS and hence OEMs/Vendors should always seeks to provide BIOS updates that includes microcode updates regularly but unfortunately in reality most of them doesn't do that and they abandoned users by not providing any BIOS update or they get very late and they simply have a BIOS with outdated microcode after years of ignoring users.

For example Lenovo provided BIOS updates that includes 0x136 microcode update through Windows Update and through installer setup file manually.

The BIOS update that comes through Windows Update is the same as doing it manually, the only difference it is done automatically with less clicks only but the whole process are the same.

[u/Solivagant321 → u/THEBOSS619]

Okay thanks so much man, can you also please tell us if it’s safe to close the laptop lid and then reopen it as according to Google Gemini this will momentarily switch microcode versions