Nothing new in Windows 10 build 18956.
I modded 9900k BIOS with:
906ED 1151v2\cpu906E9_plat2A_ver000000B4_2019-04-01_PRD_DACDA920.bin
906ED 1151v2\cpu906EA_plat22_ver000000B4_2019-04-01_PRD_B2B10713.bin
906EC 1151v2\cpu906EB_plat02_ver000000B4_2019-04-01_PRD_C9AD2768.bin
906EB 1151v2\cpu906EC_plat22_ver000000BE_2019-05-17_PRD_524214E5.bin
906EA 1151v2\cpu906ED_plat22_ver000000BE_2019-05-17_PRD_C24FCF05.bin
Is this 906ED 1151v2\cpu906E9_plat2A_ver000000B4_2019-04-01_PRD_DACDA920.bin just an older version of 906ED 1151v2\cpu906EA_plat22_ver000000B4_2019-04-01_PRD_B2B10713.bin or are they different microcodes?
@KedarWolf - is there some typos there, or misnamed directories/files ^^ ?
906ED 1151v2\cpu906E9_plat2A_ver000000B4_2019-04-01_PRD_DACDA920.bin << 906ED in "ID" column but this is 906E9 microcode here
906ED 1151v2\cpu906EA_plat22_ver000000B4_2019-04-01_PRD_B2B10713.bin << Same here, 906ED in ID column, but 906AE microcode here
906EC 1151v2\cpu906EB_plat02_ver000000B4_2019-04-01_PRD_C9AD2768.bin
906EB 1151v2\cpu906EC_plat22_ver000000BE_2019-05-17_PRD_524214E5.bin
906EA 1151v2\cpu906ED_plat22_ver000000BE_2019-05-17_PRD_C24FCF05.bin << Same here, 906EA in ID column, but this is the only actual 906ED microcode here
Yes, my bad, some were misnamed as I copied and pasted the microcode names into an existing UBU Tool .txt file.
Read the README at the github repo.
Quite a few new Intel MCs in Windows 10 build 18963:
!New_cpu306F4_plat80_ver00000016_2019-06-17_PRD_0FAB37D5.bin
!New_cpu40671_plat22_ver00000021_2019-06-13_PRD_B772C835.bin
!New_cpu406F1_platEF_ver0B000038_2019-06-18_PRD_E705E458.bin
!New_cpu50654_platB7_ver02000064_2019-07-31_PRD_8E7C22B2.bin
!New_cpu50662_plat10_ver0000001C_2019-06-17_PRD_6A540EAF.bin
!New_cpu50663_plat10_ver07000019_2019-06-17_PRD_C5E77EC6.bin
!New_cpu50664_plat10_ver0F000017_2019-06-17_PRD_43C2AD6B.bin
!New_cpu50665_plat10_ver0E00000F_2019-06-17_PRD_5E04DBCA.bin
!New_cpu806E9_plat10_ver000000BA_2019-04-30_PRD_D3A29416.bin
!New_cpu806E9_platC0_ver000000BA_2019-04-30_PRD_C93F17A1.bin
!New_cpu806EA_platC0_ver000000BA_2019-04-30_PRD_EF86C437.bin
!New_cpu906E9_plat2A_ver000000BA_2019-04-30_PRD_19E2FDAE.bin
!New_cpu906EA_plat22_ver000000BA_2019-04-30_PRD_4BEBC386.bin
!New_cpu906EB_plat02_ver000000BA_2019-04-30_PRD_D690DE6C.bin
Nothing new for AMD.
18963.zip (778 KB)
Intel cpu50656_platBF_ver04000029_2019-06-14_PRD_4C1C4DCE
Intel cpu50655_platB7_ver03000012_2019-04-12_PRD_50E6B5F2
mc.rar (94 KB)
Nothing new in 18965.
Does anyone know the latest microcode for coffeelake 8700k that does not have any spectre mitigations in it? Currently on 0xBA, and does OS microcode in updates override bios if the bios has an older one (on purpose downgrade)? Google doesnât help for this.
@Yuno - yes, OS can override and install itâs own (especially Win8-10), there is a way to stop it I think, but sorry not sure how itâs done
0x70
To force Windows to use BIOS Microcode, you will have to take ownership and remove/rename mcupdate_genuineintel.dll in \system32.
Then disable any and all Spectre/Meltdown mitigations with Inspectre or manually via the registry.
To stop Windows from updating the microcode, youâll need to rename or delete one of the following files (after taking ownership):
C:\Windows\System32\mcupdate_AuthenticAMD.dll -> for AMD CPUs
C:\Windows\System32\mcupdate_GenuineIntel.dll -> for Intel CPUs
This needs to be redone after every big update ( 1809 -> 1903 etc.).
Iâm using this method since a while and it works just fine (Windows 10).
Edit: Horstfuchs was faster.
To the poster above.
You neednât delete your whole user profile even if it was your first post - weâd love to have your input for the rest of the forum, too!
You did note that itâs important to check the dll after major updates, after all 
Intel cpu506CA_plat03_ver0000001A_2019-07-22_PRD_71479BDE
Intel cpu506C9_plat03_ver0000003C_2019-07-22_PRD_5BBF33D5
They didnât do that, I did. That account was created as a "shared login" for multiple people, which is not allowed in this community.
mc.rar (31.9 KB)
Intel cpu706E5_plat80_ver00000032_2019-07-05_PRD_61F1D47E
cpu706E5_plat80_ver00000032_2019-07-05_PRD_61F1D47E.rar (99.3 KB)
Thatâs an interesting note there that makes no sense:
Rolled back to microcode updates related to Spectre Variant 3a (CVE-2018-3640: âRogue System Register Read (RSRE)â), Spectre Variant 4 (CVE-2018-3639: âSpeculative Store Bypass (SSB)â), and L1TF (CVE-2018-3620, CVE-2018-3646: âL1 Terminal Faultâ)
Searching for "" we can see that 506C9 was rolled to 0x32 on all versions EXCEPT 1507 where according to documentation it is still 0x38 (canât extract the old msu file as I donât have 1507 windows 10 install anywhere). So that comment makes no sense - Iâm running on latest MC on my 506C9 and the newer versions did not âun-patch spectreâ that needs rolling back to 0x32 to âpatch spectreâ.
Nothing new in 18970.
@ post #272+274 - so sad to see! That is how I first started getting involved, and why I later eventually joined, after using such account.
I know we've discussed this already, but it still makes me sad to see accounts like this treated in that way, especially when they are normally used by good people providing useful info (I did for months, and you know how helpful I am)
Spammers and those up to no good don't waste time looking up an account login like that, they just make a new one every time they want to do their deeds
I know we've discussed this already, but it still makes me sad to see accounts like this treated in that way, especially when they are normally used by good people providing useful info (I did for months, and you know how helpful I am)
Spammers and those up to no good don't waste time looking up an account login like that, they just make a new one every time they want to do their deeds
Waiting for that Haswell 0x28, I see Broadwell 0x21 in that last Windows Insider Preview