Is this the correct site?
https://github.com/LongSoft/UEFITool
Yes.
All releases are here.
UEFIFind 0.10.8 does not work correctly, it will be fixed later.
Also all utilities are included in the UBU.
@SoniX
Hello 
Intel LAN PRO/1000 EFI Undi Version 7.5.11
Intel RSTe sSATA & SATA OROM & EFI Version 5.2.0.1023
Intel Lan UNDI 7.5.11.zip (132 KB)
RSTe_5.2.0.1023.zip (291 KB)
Hi,
Where can I find the removed MMTool for UBU_v1_69_5?
Search online, no links or attachments will be found here
Just to confirm my understanding of how UBU works: it mods the bios image that you provide and not the installed bios image (which may already be modded)? Is that correct? The reason that I ask is that I note that some steps seem to use admin privileges.
UBU with UEFIFind 0.10.9 doesn’t work correctly. I get “OptionROM not found” and missing rom is EFI GOP Driver SKL-KBL.
With original UBU_v1_69_5 works normal.
@SoniX - I see you changed the label of RSTE to E in UBU but neither cmd, nor poweshell (both on Win10) accept E as input for me (it keeps asking for input in a new line after I type E and hit enter).
Could it be a problem with my global keyboard / language / regional settings? (I use mixed settings: English GUI but Hungarian keyboard layout + Hungarian time/currency/etc regional settings which did cause some unexpected behavior in some “unique” software in the past). Or is it a bug (still) in UBU?
@janos666 :
Alternatively you can put the requested IRSTe RAID modules into the IRST\User subfolder of the UBU directory.
@SoniX :
According to my experiences with different Intel RAID systems I don’t see any need to generally offer Intel RAID modules, which belong to the IRST v11.6, v13.5 and v15.1 series. Users, who want to get any of these “exotic” Intel RAID modules inserted, can copy it/them into the Modules\IRST\User subfolder.
On the other hand I recommend to generally add the latest v15.2 and v15.5 series Intel RAID modules into the IRST folder. Especially the v15.5 series RAID modules seem to be the best choice for RAID users with an Intel 100-/200-Series Chipset system (look >here<).
At first, I tried deleting subdirs from the IRST dir (from 11 to 14) but figured that the UBU list is static (since nothing changed in the menu). Then I tried copying the 5_x folder to User (and also the files from 5_x to User *** which now I know is the right way) but the UBU list remained the same yet again (no U option popped up for the User dir files).
So, I took a look at the script itself and saw that some parts of the IRST list are really static but some options are dynamic (like IRST 15.7 only shows up for 100/200-series, etc) and it seems like an U (User) option should indeed pop up in the menu if I put module files (*** not dirs with files) into the User directory. However, for whatever reason, it did not seem to work for me.
From just a quick look and with lack of real understanding, I am not sure where the problem is and how to fix it properly. I supposed I could hack my way around but I think it’s better if the script gets a proper fix by someone who is already familiar with it.
Edit: A small update to this.
I changed 9 to T and E to 9 in the script and now the command line accepts an input of T (and tries to update the IRST OROM which fails with no space error) but 9 does nothing (it does not list the Enterprise options).
So, it’s not a problem of numerical vs. alphabet inputs but rather some problem with the whole Enterprise option (it does not execute when selected).
By the way, is it usual for stock images to contain both RST and RSTe ROMs?
@ janos666
Do you have problems with the letter E in the IRST/IRSTe section only? There are similar problems with letters for example in the section Updating microcodes?
@ Fernando
Now I’m working on version 1.70. In this version of the files EFI and OROM IRST(e) will no longer be.
Instead of them there will be 2 folders RST and RSTe. The user can add the versions of files that are necessary to him. (Analogy of the User folder).
No. See my later post (#3116, second paragraph): it’s definitely not a number/letter problem.
I am working on my nephews computer today,thought I would grab the bios for his mb and run it through the UBU tool.Can a Asus PRIME B250M-A which is a Intel® B250 chipset have the cpu microcode updated with the tool.The tool showed skylake and kabylake,it is Intel® Socket 1151 for 7th/6th Generation Core with a i5/Core processor.I was not sure if the microcode can be updated so I thought to ask here first…
Was wondering where the authors of Ubu find the cpu microcode files? Are they from the intel download center and extracted from the linux tar file? Reason I ask is that the date of latest release on intels site is 7/7/17 which is newer than ubus microcode dates. Maybe that doesnt matter…
Thanks
Edit: Played around with MCExtractor and extracted the 7/7/17 Intel Microcode linux tar file of microcodes and found them to be the same as last months Ubu. Apparently they have the inside track on new releases…
@SoniX ,
I think I found a bug with 1_69_5 in that if I choose option 7 to update cpu microcodes for Skylake (option 1) I am first presented with the Kaby Lake MC’s. Such that I am running a Skylake Cpu and thus with the list of Kaby Lake MCs I select 'Skip - 0 ’ and then the Skylake MC’s are presented. At that point I select the updated code and when I return to the main menu the Kaby Lake original MC that was there before has been deleted. Is this by design?
Thank you