Intel/AMD uCode fix for Spectre, HT bug fix and Meltdown.

This applies on all ROG Laptops & Non ROG Laptops too.. including PC too with broken Hyper-threading due to a bug on Microcode CPU + uCode fix for Spectre and Meltdown..
Updated Guide on [May 25 2019]​

Hello everyone... My name is Ehab H. aka THEBOSS619 or T.B.619 from Egypt.... anyway if you are not advanced or intermediate PC user... please save your self from trouble and forget it.

I would like to help for those who are using any kind of Microsoft Windows OS [example:- Win7,8,8.1,10] as this kind of microcode bug is not affecting linux only but to other OS as well so.... I would like to give a solution to SkyLake, Kaby Lake, Haswell, Broadwell, Ivybridge, Xeons and AMD cpu's.[AMD are immune to Meltdown]

First of all...


[Here-]
Go to this link ---> Click Here to get an idea or learn how to upgrade your CPU Microcode to the lastest version. It is detailed enough there.

[or-]
You can go an easy way by downloading from my attachment thanks to @Vasudev method

Extract the zip file and then you will find this file named [Install.bat] just simply click on it and you can stop here. You are done (^.^) Enjoy! .

Whenever you wanted to remove this update.. just simply click [Uninstall.bat] file


* I got my CPU Skylake 6700HQ on ASUS ROG GL552VX Laptop with this code 0x506E3 and Intel64 Family 6 Model 94 Stepping 3 and I successfully updated my CPU Microcode to the lastest version and it works like a charm! also this update fixes many cpu bugs including CPU flaws (especially ones dealing with sleep and hibernation) and as it fixes other processor issues as well (like heat issues and CPU locking at high frequencies, etc...).

Download Link:-
https://mega.nz/#!gZBzBIib!wNZwqhegXl1FME7h5HLhsfAT55Xk_EyTN6QNBo7l6Qo

SHA2:bd4e8e0280974be4cc914217c122e1ce48464c9c765812637f631678a7fe3e19
SHA1:11b71f406a474195d196a09ed0a469bf3e977440

Anyway... thumps up this post or make it stick on the top of the list so that everyone benefit from it

This post is made purely by me by my own effort [with the help from notebookreview.com link that I provided above].
The idea for this solution came to my mind after reading this ... Click Here
Credits to @Vasudev for an easy one click step .
Credits to Jacob Klein http://wp.xin.at/archives/4397#comment-154115 for providing easy way to convert .bin files to .dat files easily!
Converter can be found here https://1drv.ms/f/s!AgP0NBEuAPQRpdoWT_3G3XCdotPmWQ

Note:- If you want to use or install old microcodes I have made a google drive were I keep old microcode just in case

https://drive.google.com/open?id=1qUVS1G-T-vEKf8stXEGQ54lN_eRo8VhM

Up-to-date Microcode will always be on posted on mega.nz while older Microcode will be on my Google Drive link

Ryzen uCodes aren't tested so proceed with caution and make an image of your system using Macrium Reflect just in case, something bad occurs.

---------------------------------------------------------------For Advanced Users Only------------------------------------------------------------
Those new intel microcodes files on Intel-ucode folder are binary files so... I tried this python script to convert binary file to a text counterpart (.dat) and it works!

for those who is interested or like to be risky.. you can find the python script on this link:- http://www.codegists.com/snippet/python/bin2datpy_aikoncwd_python
Copy the python code to a txt file and then rename it whatever you like but be sure the extension will not be a .txt file but to be .py so that python script works

Find the file to which is related to your CPU [You must know which file on Intel-ucode folder is specific to your CPU] to convert binary files to .dat files

How to find your specific ucode file... is to know your CPU ID through RW-everything and then find your file.. for example..
I just find mine by knowing it through the file names.. for example:- My CPU ID was 506e3 so... I go to the Intel-ucode folder and started looking for it... so how would you know which file is made for your cpu? by looking to your CPU ID.. start searching which in my case it was 06-5e-03 file which is equal to my CPU ID=506e3... if you look carefully .. you will find there is similarity on numbers and letters so.. you can try

By the way.. the Python script have safe measurements because it reads your CPU ID on your current computer and then it asks you if this is your CPU ID and then it compares what you selected from the Intel-ucode.. if it doesn't match.. the python will terminate the process.. if it found a match.. it will convert your file to .dat file which you will be able to use it to upgrade your CPU Microcode


To save you sometime I converted the binary files to .dat files... and would like to share the current microcodes that Intel released on there official website 04/25/2018 ... I successfully converted all the binary file to .dat file in order to work on windows I found a way to convert it all at once through python script better than selecting file by file to convert it

Here is it for those people who like to test it but in order to find which microcode for your current CPU... As I mentioned on the previous paragraph how to find it anyway.. here is the link ---> https://drive.google.com/open?id=15v5hYB-hPD-sLd6CXPnfCrm6ouoQgfEm<---- this is only for Skylake CPUs microcode because to be able to have all the microcodes for all kind of CPU I must have the CPU physically which is impossible



Note:- All Microcodes are not tested

Only 1 microcode are tested which is [06-5e-03.dat] file because this microcode is related to 6700HQ according to CPU ID which is 506e3

 

Idk what was wrong with HT on older microcodes, but I see no difference between new one and old one (have sBIOS updates with both of them). Might be it's only applicable for super old BIOS versions.

 

Then I think you must read carefully here.... this fix is only for a specific skylake cpu it is not for all skylake CPU only those who got the code as I mentioned above will be fixed from HT bug.

Read here if you are not believing it https://lists.debian.org/debian-devel/2017/06/msg00308.html.

Also...I'm offering help for those who use only windows because officially windows doesn't have an option to update your Microcode CPU except through BIOS updates so..... what I am offering here is this is the only way to update it without needing a BIOS update nor waiting from OEM or vendor to provide a BIOS update (which we all know.. they are always late like 1 year delay or never provide any BIOS Update).

 

Changelog [7/7/2017]:-
- updated broken link + added mirror
- added @Vasudev method
- updated some info.

 

Add updated link contain kabylake uCodes in this post Skylake / Kaby Lake Hyper-threading bug

 

Thank you @Vasudev I updated my guide including your updated link .
I have tested it and works wonderfully

Changelog:-
- Included solution for KabyLake users
- Updated links
- Updated information + Credits
- Made guide more simpler and easier for users .

 

@THEBOSS619: This microcode simply fixed my sluggish performance on my older Lenovo PC having Pentium and my sis's PC having Broadwell.
This update can be applied by everyone regardless of PC's age. Haswell, Ivybridge and Xeons.

 

Thanks for testing & for your valuable info. I only got 1 laptop which is 6th gen 6700HQ so I couldn't confirm would it work with others generation of CPU's

Updating my guide ASAP

 

You could say, fixes for Haswell heat issues and CPU locking at high frequencies. I can say apply it on virtually any CPU made by intel. Also, you can update it on ASUS ROG forums too.
A little off-topic: Is there any method to dump BIOS from Aptio IV/V from ASUS, Mine simply returns an error stating it is only read only.
EDIT: See this link for more info. https://launchpad.net/ubuntu/+source/intel-microcode/+changelog

 

I will do it , but need more evidence for that... sorry if I was little late to answer

about the BIOS... I think you are entering the BIOS as a user .. not as a administrator

Do you see when entering the BIOS on the first page at Acess level : administrator ? or user? what does it says exactly?

for example this....



If you are administrator you should be able to take a dump BIOS other than that... I can't help , sorry

 

Sorry, I didn't update it. I was able to extract the rom and hdr file using command line switches from Dell EXE.
I edited the BIOS entries from default to USER.
MSI uses a different page for displaying info as per your screenie. Whereas Dell uses modified setup screen and menus as per AMIBCP. I enabled HWP and lot of things and I'm afraid of bricking it. Luckily, Dell issued a BIOS update to fix uCode issue and as an enhancement they updated GOP and IRST ROM. The performance is similar to VMWARE ucode patch, no difference at all.

 

No problem at all , Happy to know that thing got sorted out ! I guess Dell is showing some care to its consumer on major problems but not on minors things and I'm sure other like ASUS, MSI,etc... will follow the same thing

 

Updated Guide on [11/23/2017]

Changelog:-
- Updated Intel Microcode version to 20171117 according to Intel website ---> https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-Data-File?v=t
- Updated links
- Updated Information


Enjoy!

 

Did you get official update to fix HT bug for your skylake?
Any changes, there's something for skylake/kaby cpus?

 

My processor with this code 0x506E3 and Intel64 Family 6 Model 94 Stepping 3 is already fixed from long time ago officially this new update supports more processors with different Codes and Models and Steppings which fixes the HT bug and improve & fixes other issues but to note only--- only certain CPU's still... not all the Kabylakes & Skylakes gets the fix

For more Info:-

Click here http://metadata.ftp-master.debian.org/changelogs/non-free/i/intel-microcode/unstable_changelog
or

Here https://launchpad.net/ubuntu/+source/intel-microcode/+changelog

 

already saw that. First thing I did to check if they were able to fix intel MEI exploits on older PCs w/o vendor support.

 

@THEBOSS619 New uCode for intel is up and I'll update the VMware CPU patcher with new ucodes. Link will be up in 30 mins.
You can edit title uCode fix for Spectre, HT bug fix and Meltdown.

The link is up and I couldn't find latest AMD microcodes which I extracted through deb files from launchpad.net
Old ucode: BA 6700HQ

New uCode: C2

New CPU microcode for Intel is included to fix Spectre and Meltdown. SHA1 Hash of zip file is given after underscore.
SHA1:06A14BA0506D12B69ED78E226F22CE0F9EEA6E1A

@Papusan @THEBOSS619 @Prema @hmscott @Dr. AMK Phoenix @Mr. Fox
Sorry I forgot to include the link [WARNING] Intel Skylake/Kaby Lake processors: Broken HT on Laptops & PC [Fix is here]
First run of Cinebench R15 on high priority

After 2nd and 3rd run with Realtime priority:

I hope @Papusan likes this.

 

Never updated microcode unless via BIOS updates so far. This meltdown and Spectre semi fix is for all 6700HQ models right? So doesn't matter if it's clevo, MSI, Asus or AW right?

 

Yes, for now its semi-fix.
This is the only way to update when you're devices are on EOL list.

 

You don't happen to have some haswell microcode fix around now do you? I'd like some semi fix on me 4940mx if possible

EDIT: I realized your file contains all updates for all kinds of CPUs.

EDIT:
And there I was under the impression that microcode update + microsoft update would lessen my performance.

Spoiler

 

I ran that batch file and my CPU still shows as vulnerable according to Ashampoo Spectre Meltdown CPU Checker

Is this a software fix in the OS or does it really change the CPU Microcode so that even if you format the fix is still there?

 

According to my HWINFO it changed the microcode. Also you need to know that Specrte is not 100% fixable, hence I used the term "semi fix". Once you installed updates and the microcode you basicially fixed 2/3 volnurabilities, the 3rd one isn't fixable at this moment.

 

True

Updating my Post as we speak right now

Thread updated [01/10/2018]
The new uCode have been tested on my laptop and working as intended.. no noticeable any slowdowns.

Changelog:-
- Updated post
- Updated file to the latest version available
- Reported this post to be renamed to [uCode fix for Spectre, HT bug fix and Meltdown.] as I didn't have any option or ability to rename my post title

 

Yes, its a SW fix and Win 10 doesn't activate the bit to disable speculative branching or whatever they call it.
Daz(aka Daz loader fame) simply sent me a microcode fix and I applied it.

But Ashampoo tool shows I'm vulnerable to Spectre

I'll keep the post updated when I apply the patches using vmware on my lenovos.

 

So I applied the new updated microcode on my 4940MX and this happened:

Spoiler

Old score: 792
New score: well.. you see that...

Any idea what is going on because this seems kinda ridicolous.
The processor was always at 4ghz, after update still 4ghz. So idk what is going on.

 

Have you ever heard the term " margin of error"??

 

Sure why not, when before the score were consistently around 790s and now are consistently 825-835.

If you got more genius inputs go on.

BTW: I'll try to update another notebook with a 3920xm to see if that does anything as well.

 

I'll leave that to YOU Genius!

 

Dunno why, but expected more from you. What a letdown.

@others:
Anyone here knowing something why the microcode update improved on performance? Any known issue on haswell?

- Noticed that the system runs snappier than usual,
- Gained 5-10 more FPS on breath of the wild (emulated game)
- The CPU runs 6c on max temp cooler on a 20min stresstest run.
- XTU benchmark score also improved.

 

If the vendor didn't roll up microcode changes due that CPU while you were running it - before this latest microcode update that does catch you up to all the changes - there were likely 1 or more performance affecting changes.

Seems logical to me.

There have been other such reports of performance improvements, and that's the educated guess we make - we can't (aren't paid enough? don't care enough?) to unroll all the changes / updates included to figure out which microcode update did it.

Long ago I had a Haswell that had the same thing happen, but from an Asus BIOS update. My CB scores went up about the same. I wasn't concerned at the time about the lower scores, as other tests showed scores matching others. It was nice to know that was the fix at the time, a nice surprise.

 

Currently the method of updating microcode via the vmware driver, does not activate mitigations (no performance penalty is applied, no protection against Spectre variant 2 too) in Windows, check powershell Get-SpeculationControlSettings script.

https://support.microsoft.com/en-us...ive-execution-side-channel-vulnerabilities-in

https://social.technet.microsoft.co...s-108x-client-hyperv?forum=win10itprosecurity

 

Read this changelog:
intel-microcode (3.20170511.1) unstable; urgency=medium

* New upstream microcode datafile 20170511
+ Updated Microcodes:
sig 0x000306c3, pf_mask 0x32, 2017-01-27, rev 0x0022, size 22528
sig 0x000306d4, pf_mask 0xc0, 2017-01-27, rev 0x0025, size 17408
sig 0x000306f2, pf_mask 0x6f, 2017-01-30, rev 0x003a, size 32768
sig 0x000306f4, pf_mask 0x80, 2017-01-30, rev 0x000f, size 16384
sig 0x00040651, pf_mask 0x72, 2017-01-27, rev 0x0020, size 20480
sig 0x00040661, pf_mask 0x32, 2017-01-27, rev 0x0017, size 24576
sig 0x00040671, pf_mask 0x22, 2017-01-27, rev 0x0017, size 11264
sig 0x000406e3, pf_mask 0xc0, 2017-04-09, rev 0x00ba, size 98304
sig 0x000406f1, pf_mask 0xef, 2017-03-01, rev 0xb000021, size 26624
sig 0x000506e3, pf_mask 0x36, 2017-04-09, rev 0x00ba, size 98304
+ This release fixes undisclosed errata on the desktop, mobile and
server processor models from the Haswell, Broadwell, and Skylake
families, including even the high-end multi-socket server Xeons
+ Likely fix the TSC-Deadline LAPIC errata (BDF89, SKL142 and
similar) on several processor families
+ Fix erratum BDF90 on Xeon E7v4, E5v4(?) (closes: #862606)
+ Likely fix serious or critical Skylake errata: SKL138/144,
SKL137/145, SLK149
* Likely fix nightmare-level Skylake erratum SKL150. Fortunately,
either this erratum is very-low-hitting, or gcc/clang/icc/msvc
won't usually issue the affected opcode pattern and it ends up
being rare.
SKL150 - Short loops using both the AH/BH/CH/DH registers and
the corresponding wide register *may* result in unpredictable
system behavior. Requires both logical processors of the same
core (i.e. sibling hyperthreads) to be active to trigger, as
well as a "complex set of micro-architectural conditions"
* source: remove unneeded intel-ucode/ directory
Since release 20170511, upstream ships the microcodes both in .dat
format, and as Linux-style split /lib/firmware/intel-ucode files.
It is simpler to just use the .dat format file for now, so remove
the intel-ucode/ directory. Note: before removal, it was verified
that there were no discrepancies between the two microcode sets
(.dat and intel-ucode/)
* source: remove superseded upstream data file: 20161104
In OP, it says fixes for haswell fixes such as reduced temps, increased performance and get rid of strange bug on haswell 47xxxHQ that blocks clock rates anything over 3.1GHz on 4 active cores. @judal57 tested this and found his temps were reduced by 5-10C during extreme OC of CPU/GPU. It even pulls less power than usual that DC_IN cable from burning.
After Update the cb scores decreased by 10-20. I had to reboot and run several times to get the cb scores back to normal.

 

I used VMware tool to install driver with updated microcode.
For my system (laptop MSI GT72 2QE, i7 4710MQ, Haswell), only partly, windows is not activating mitigation measure since he detects that the hardware is not using proper microcode...

As per: https://www.win-raid.com/t3351f47-Microcodes-for-branch-target-injection.html#msg46070
"It depends on the CPU. My IB-E has no HW support for mitigation against BTI, but new microcode brings that HW support, and it happens that Windows kernel is loaded before VMware driver and it sees that there is no HW support and disables the mitigation. Only after I patched the BIOS file and flashed it Windows enabled the mitigation. So if your CPU has HW support for BTI mitigation (with current microcode) then you can use VMware driver."

My assumption: Vmware driver is loaded at boot after kernel and thus, is not a proper mitigation as is a real microcode update via Bios update, but it's better than nothing cause exploit needs to happen before this driver is loaded (at least that's my understanding but I'm probably wrong).

 

That's how its supposed to work. VMWare tool applies new microcode at boot similarly like Linux microcode is applied.
There's no other way to keep the uCode updated atleast at OS level.
W10 applies/sets Branch Target Injection to TRue if there's uCode present in BIOS/EFI.
These PC vendors simply refuse to fix the devices which are EOL. So, short answer from vendors to end user/clients is GFY.

 

Thank you

 

Put it here...


@Vasudev Have you a conclution?

 

About what?

 

Work the patch a expected? Read your own reply in pict

 

Phoenix: I'm attaching a screenie after I talked with Daz.

 

Microcode is patched thanks to Daz but like Microsoft said there is noticeable slowdowns. I will test on Linux too using Blender.

 

I talk about this... I know the fix is half baked and screw perfomance <because of new W10 patch and uCode the CPU is unresponsive on 100% load. So mouse cursor is stuck.>

 

What you guys need to know is this method of applying a microcode update is not low level. Windows will load the kernel before it loads this microcode so it technically is still susceptible to attack. the microcode needs to be applied at the low level/bios level so that it initializes before windows can load its kernel. This method, in essence, is useless to patch spectre. I'm trying to figure out how to extract and update the CPU microcodes from insyde BIOS, but for AMI BIOS it is fairly straightforward.

 

Well.. many OEM of laptops or desktops abandoned there products due to it is too old to get supported with BIOS updates or they become EOL so... by using this method will get those EOL products some performance + security + bugs fixes and can have a chance to still survive this attack

Biggest example is my laptop ASUS ROG GL552VX is being abandoned since 2016 so... so I gained alot from this method

by the way.. I got fully unlocked BIOS so.. updating the current BIOS to have an updated microcode is just wasting my time + little risk [to me it's fine] because I got the same benefits while using software method + it is safer and easy

 

Thank you for pointing this out... it is very important to know and for other users too

 

I'm sorry to inform that Ashampoo's spectre check tool is indeed correct since it was reporting vulnerabilities regarding Spectre Variant 2 which is not yet patched. Daz just told me via PM.
I should have waited a little longer before posting.

 

No problem at all still thanks for this valuable information

 

Haswell users, be careful when updating your microcode. My haswell based alienware just took a dump after applying the new microcode, was dead within 24 hours of application. Motherboard went kaput, and for the first time in my life, so did the processor (4940MX), so be careful. I'm not saying that this 100% caused this failure, just be wary.

 

I suspect you updated your cpu microcode through BIOS right? I mean by editing your BIOS file and flashing it so.... well if it is true then... I guess this is another reason to try software method then

and sorry to hear about your laptop

 

I'm so sorry this happened.

Intel seems to have acknowledged there is a problem with the Spectre BIOS fix on Haswell and Broadwell.

http://www.tomshardware.com/news/intel-spectre-bios-crash-broadwell-haswell,36324.html

https://newsroom.intel.com/news/intel-security-issue-update-addressing-reboot-issues/

 

I tried the VMware approach, then loaded the code into my modified BIOS, and died within 24 hours of both of these.