@Fernando Sorry to spam this thread. I want to fix the ACPI tables, make the BIOS…UEFI options visible always, research that MSIHiddenFun EFI variable (it seems to show some fun when changing the value, I copied all efivars in Linux so I’ll put it here too), see if there’s a way to jump over “Pessimus” (Nvidia Optimus), some way to enable vGPU, able to put 32gb RAM instead the official 16gb max and make this laptop suck less in Linux and other systems 
Thanks for your tools.It is very useful for old computers that vendor won’t update its uefi.Hope you get well soon.
I have found that the Updated Microcode for haswell:
sig 0x000306c3, pf_mask 0x32, 2017-11-20, rev 0x0023, size 23552 version 23 has the partially fix for spectre. (partially because the other part of fix is implemented by the OS update)
UBU provides the version 22 it is posible to be update with microcode 23?
For those of us with older (uefi) motherboards that have long since fallen out of manufacturer support - will the microcode updates meant to address the Meltdown/Spectre vulnerabilities be made available through UBU?
Sorry for the stupid question. But does anybody know if there will be a microcode update for Sandy Bridge and Ivy Bridge? Z67 and Z77?
PS: Thank you for all the hard work.
@boombastik :
@killkernel :
I have moved your posts into this UBU Discussion thread, because the other thread has been designed just for the UBU Guide and SonX’s announcements of the UBU Updates.
What do you think about creating a new thread within the “BIOS Modding” Subforum with a title like “[Meltdown/Spectre] First Aid by CPU Microcode Update”?
cpu000906EA_plat22_ver0000007C_date03-12-2017 (Coffee Lake)
@jjxaker and everyone else:
New CPU Microcodes should be reported at the Intel, AMD & VIA CPU: Microcode Repositories thread from now on, whether they are included in UBU or not. I can see that the attached microcode is already there. You can use MC Extractor to check.
I have a question, if someone wants to answer. I have updated the microcodes of my i7 4790k on z97-p motherboard. The operation was successful, but I manually updated the microcode by selecting it from the desktop and updating it on the bios. Before the change, on the original bios there were also microcodes for broadwell (I have a haswell). I have manually updated only the microcodes by haswell (and I think that after the change there are only those for haswell). Is it a problem? Should I update those for broadwell too? My pc works perfectly. Thanks to those who want to answer.
@Raziel :
Welcome to the Win-RAID Forum!
Your BIOS just needs the Microcode for the CPU, which is currently in use. So if your mainboard has a Haswell CPU, your system neither needs nor can use the CPU Microcode for Broadwell CPUs.
Regards
Dieter (alias Fernando)
Thanks for the quick reply, and congratulations for the forum and the guides.
So is there a way to use bin-files from Intel, AMD & VIA CPU: Microcode Repositories with UBU?
Yes there is i’ve Updated UBU to use it, you need to edit the bat files in Modules/mcode folder which matches your cpu.
My CPU is Haswell so i edited Sel1150.bat to add the bin file name to to the menu.
for example i added these lines for the latest haswell 23 mcode:
@Fernando
Antimalware security application EMSISOFT does detect a problem with "high risk" with UBU v1.69.6 and does an immediate quarantine of the file UEFIExtract.exe.
With previous UBU v1.69.5 I had never got this problem.
@100PIER :
Thanks for your info. My Antivirus program Defender didn’t show any warning after having unzipped the latest UBU package.
So I suspect, that the EMSISOFT “high risk” message was false.
Anyway you should address such messages to SoniX, the maker of the UBU Tool.
@Fernando ,
@Sonix,
Thanks for your comments. I have reported to EMSISOFT the potential false detection.
Some anti-virus programs can find a potential threat in OROM or EFI files.
I can assure that utilities downloaded by official links do not contain potential threats, except for BIOSes. :))
So can UBU work with Intel bios that have been dumped from a flash programmer (I’m not talking about a .BIO file)? The UBU batch file looks for a hex string to detect an Intel bios and then exits the script…
uefifind body count 49006E00740065006C00…4400650073006B0074006F007000200042006F00610072006400 bios.bin>nul) && echo File Intel Desktop Board BIOS is not supported! && goto exit1
…but is there a particular reason for this?
If UBU is not setup to do this is it at least possible to manually merge/replace the TRIM-modified IRST 11.2 OROM into an Intel bios (specifically a DX58SO board that currently has IRST 11.1 OROM) using the same tools UBU uses (UEFITool/MMTool/etc) or some other tool (Phoenixtool)?