Obviously a false positive. You can always "build" it yourself if you don't trust it.

@ All:

I've made some visual changes at MCE, mainly to appear better at UBU. I'd like your opinion on whether horizontal lines are useful. Which one do you prefer (a or b)?

A



B

Zitat von plutomaniac im Beitrag #3476

---

The reason for the ASRock error is simple, folder Files > ASRockA5 is missing.

---

@Bugger Vance:
Your problem is caused by the mainboard manufacturer, who has put too many modules into the the DXE Driver Volume, and has nothing to do with the UBU tool.
Why don't you solve the problem yourself by removing unneeded DXE Driver modules?
After having done that, you can update the modules, which are important for you, by using the UBU tool.

Zitat von SoniX im Beitrag #3491

---

Important! We did not check how correctly patched MMTool works with Aptio 4 BIOSes.
That is, while there is still no opportunity to flash Aptio 4 BIOS, which was processed with the help of the patented MMTool.

---

@SoniX:
The patched MMTool v5.2 worked perfectly with my ASUS P8Z68-V system.
After having patched the MMTool, this is what I have done:

1. As first step I ran the UBU tool v1.69.11-fixed using the patched MMTool and loaded the latest original BIOS v3603.
2. Then I updated everything, what the UBU tool was offering.
   Here are the pictures:
   
   
   As you can see, everything went fine.
   Nevertheless I ran into a problem while trying to update the Intel LAN Option ROM: It didn't work at first try. The SetDevID tool gave me the message, that the DLL file named msvcr.dll is missing. This issue may have been caused by the fact, that I am currently running the Windows 10 Insider Preview Build 17083, which doesn't have such file within the Windows folder. After having downloaded and inserted the missing DLL file into the UBU folder, even this task has been completed successfully.
3. To verify, whether the patched MMTool is able to insert natively missing BIOS modules into an AMI Aptio IV BIOS, I tried to manually add the following EFI modules to the BIOS, which I had just modded by using the UBU tool:
   a) TRIM modded Intel SataDriver v12.9.0.1006
   b) Intel GopDriver v2.0.1024 for SandyBridge CPU
   c) NVMe EFI module named NvmExpressDxe_3.ffs
   Everything went fine.
4. Before flashing the finally modded BIOS, I opened it by using the the patched MMTool and the UBU tool (still using the patched MMTool).
   Here are the related pictures:
   
   Note: Obviously due to its strange structure the inserted NvmExpressDxe_3 module cannot be detected by the UBU tool. I already knew that from other UBU users.
5. As final step I flashed the previously modded BIOS into the BIOS chip of my ASUS P8Z68-V mainboard.
   Everything went flawlessly.
   To make sure, that the modded BIOS really had been successfully flashed, I checked the Intel RAID Utility version and it really was the v12.9.0.1006 (original version: v11.2.0.1527).