Zitat von Feyd1364 im Beitrag #1650

---

Skylake GOP Driver 9.0.1111 in new UBU 1.79.15 doesn't work. "File can't be opened." So force replace is unavailable and only GOP Driver 9.0.1080 can be used.

---

link dead again, seriously what clown is flagging it

@Net7

Checked it out. The link from March 20 is still working.

Zitat von SoniX im Beitrag #1653

---

@Net7
Checked it out. The link from March 20 is still working.

---

GOP v9.0.1111 is the issue with Z390 boards I think.

Tried it with the stock VBT, 221, and 228, you can enable it in BIOS but the onboard video is not working. :(

230+ bricks the BIOS.

to SoniX how to update the vbt gop.i have three raw gop vbt skl but i need update to the kbl ja need peavad olema ver.221.i have understood this by researching other lenovo oem bios and i want my m900 tiny to get i7 7700 without a programmer making biost.i have got to change officially fw me. here in the forum with instructions for microcode, vbiose and gop but it seems there is no vbt yet.here is proof that klenovo can insert kbl support without writing to a 16mb chip.https://support.lenovo.com/us/en/downloa...-v520-and-v520s
as they only offer 8mb or half.the thing is that there is no way software can do oem lenovo bios dump that by changing it back to flash as there is protection on top of which you don't want to go into it and it doesn't make sense since a programmer is coming to ensure pc hardening tests. however, I am gathering the blade of wisdom to make this device with kbl support without a programmer.

Zitat von SoniX im Beitrag #1643

---

@ScorpionX
I cannot say what is the reason for this problem.
I can advise the following. Replace not all modules at once, but one at a time, followed by flashing and testing

---

@KedarWolf

Need only clean VBT + BSF 23x for customization for a specific motherboard model.
If you use already configured VBT 23x from other motherboards, then nothing will work.

I`m trying to update the microcodes from a HP Envy Phoenix 860, that uses a Pegatron IPM17-TP motherboard, with the Z170 Chipset. The BIOS Platform is AMI Aptio 5.
When I try to start the microcode replacement, I get the following error from MMTool_a5
"ERROR 3000: The VTF size or alignment specified in the FFS file header is invalid.
VTF Location: 0x124e3970. VTF Data Location: 0x124e3988. Required VTF Data Alignment(based of FFS file attributes"
Anyone knows if there is anything that I can do to fix this? Maybe do the procedure manually?

I just downloaded UBU 1.79.15, installed Python with the two dependencies of UBU, copied mmtool_a4.exe and mmtool_a5.exe from my older UBU folder, and finally loaded BIOS P1.90 from an Asrock J3455M board: http://asrock.com/mb/Intel/J3455M/#BIOS
When I select "5" to update the microcode, there is no option for replacing it:
https://imgur.com/a/LeE4Mqb
What am I doing wrong?

@BlackArchon You aren't doing anything wrong, UBU does not support Apollo Lake systems and does not provide microcodes for socket 1296 BGA CPU's.

Well, that's sad. Is there a list of supported CPUs?

@BlackArchon Any Intel CPU using these LGA sockets 1150, 1151, 1151v2, 1155, 1200, 2011, 2011v3, 2066, 3647.

Thank you! Is there maybe a guide for manually updating the microcode on unsupported platforms, like my Apollo Lake one?

@BlackArchon Yes, there is this guide for example --> AMI INTEL CPU Microcode Update Guide