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

[Da-BOSS]

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 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.

The .zip file attached on this post look at the end of this post.

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.

Notice:- 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!

September Microcode Update aka [0x12B]

New microcode update got released! This is the September microcode update which now they call it 0x12B .Please if you are using the 0x129 microcode previously then simply download the latest .zip pack from the attachment of this main post. 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. 

No need to reboot, You just updated your microcode! Yes... it's that simple!

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

[Alpine_Alex]

I can only surmise you don't read what you link.

The user received a replacement laptop and the behavior was the same - how is that degradation? 

Also what's interesting is one of the people commenting in that thread is one of the only people to be making noise about it here.

Also, I think you may have shot yourself in the foot with this one below.

Can you explain why workstations would shift to these CPUs if they thought they were impacted by the Vmin shift?

They wouldn't.

They're based on the same die, they're not the same CPU. It's actually hilarious that you're still failing to comprehend that power is directly related to this issue and speaks volumes for the fact you shouldn't be parroting things that you do not understand.

[Da-BOSS]

I think you actually shot yourself a shotgun in the foot.. not just a simple gun. 🤣 what is this non sense that you are talking about? you still can't read? well.. let me show you another one since you can't comprehend at all and I will show a big arrow on it too just for your brain to process it 😂

I can only surmise you don't read at all. Please stop your misinformation and spreading lies. it's embarrassing as you are the only one making noise spreading false information when you are replying to me 😆 

Please stop replying to me unless you have something useful to say, thank you 🙂 Intel HX = Desktop CPU and will always will be.. period

It's really funny to see your comment as I kept laughing as you are trying so hard to discredit me.. don't worry.. it won't work... and speaks volumes for the fact you shouldn't open your mouth at all 😁

• Reference:-
  https://videocardz.com/newz/intel-introduces-13th-gen-core-mobile-hx-h-p-u-series-with-up-to-core-i... 

[Silent_Scone]

Alex Alphine is correct in his statement. Even though mobile HX and desktop CPUs may share the same die, they are not the same in performance or power behaviour. As frustrated as you seem to be throughout this thread, posturing on your part cannot change this fact. 

Unless users come forward looking for help updating, I suggest you take this to the Intel forum moving forward if you disagree with any statements Intel have made.

[Da-BOSS]

To people saying Intel HX CPU's isn't desktop CPU....

Will always be a desktop chips on a laptop case. I have been saying this since day 1. They have been doing this since the 1st Intel HX line series got to the public.

Intel HX=Desktop CPU... period.

I just wanted to share this since a user from discord pointed that out and I guess I wanted to share it here for countering misinformation that echoing on this forum.

Reference:-

• https://videocardz.com/newz/intel-core-ultra-200hx-series-leaked-core-ultra-9-285hx-with-24-cores-wi...  

[illusionth]

I have a 13980hx on the 329 bios. Updated microcode from 115 to 129 can confirm temp is lower and performance is the same. Thanks man.

[Da-BOSS]

Happy to help whenever I can. 🙂 thank you for your time reporting this.

Soon Intel will release another microcode September update and I will make sure to update the main post attachment with the new microcode once it's released.

[Da-BOSS]

Heads up... Intel will be calling the next microcode update as 0x12B update [AKA microcode September update]. Once it gets released I will update the main post with the 0x12B microcode update which will be used on Intel HX 13/14th CPUs normally.

Reference:-

https://community.intel.com/t5/Blogs/Tech-Innovation/Client/Intel-Core-13th-and-14th-Gen-Desktop-Ins... 

[AndyofGod]

from your link :

"Intel reaffirms that both Intel Core 13th and 14th Gen mobile processors and future client product families – including the codename Lunar Lake and Arrow Lake families - are unaffected by the Vmin Shift Instability issue. We appreciate our customers’ patience throughout the investigation, as well as our partners’ support in the analysis and relevant mitigations. "

Br

[Da-BOSS]

I'm available on those platforms.. feel free to ask or pm & I will respond whenever I get free time 🙂 can't talk outside the scope of microcode updates here due to mods.

https://www.reddit.com/user/THEBOSS619/

https://forums.guru3d.com/members/theboss619.271793/

https://www.techpowerup.com/forums/members/theboss619.184112/

and on Discord too. And many others I'm just the most active on those 🙂

[Da-BOSS · Accepted solution]

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 attachment of this main post or on this comment. 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"]

No need to reboot, but  a user from Guru3D mentioned that "microcode is not updated without reinitializing the operational mode, a reboot is required for it to take effect." so.. reboot for extra assurance 🙂

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