@ Pacman
Hello! 
Everything seems to be as usual pairwise compatible - SNB=IVB, HSW=BDW and SKL=KBL.
We are waiting for the GOP driver, it is likely to have 9.5.xxxx version and is compatible with SKL and KBL. 
Ah Kaby Lake, that probably explains the 11.5 fw as well. Anyway, I wanted to ask SoniX:
It is normal for the the VBT to say wrong version info? Maybe some OEM screw up or similar? I’m finding a lot of 9.0.1028 VBIOS for example that instead of saying 1028 PC they report 1070 from 2014 or something which makes no sense. The hex does categorize both of them as 1028 but I’m not sure about the VBT text.
That’s the signon message, should be ignored, as OEMs can and will put just about everything in there. The hex version from VBT structure should be trusted, not sure if it can be changed with BMP. For the VBT version, you can quickly check with “efivbt” or manually with <this guide>. For instance, VBIOS 9.0.1028 should report SKL_1028_VBT196, as in Platform - ROM Version - VBT Version.
Version VBT C8 = 2.00 in OROMs 1031-1037 .
Perhaps Intel will not change the version like HSW-BDW (5.0.xxxx -> 5.5.xxxx) and leave everything as it is 9.0.xxxx. But perhaps the changes. Everything is possible, wait and see everything in the next versions.
@ SoniX:
Found VBIOS 9.0.1036 which is SKL only. So the 9.0.1037 that Pacman found is the first SKL/KBL release apparently.
@ plutomaniac
Thank you. Let’s see what will happen in versions 1038 and above.
It looks like bios mod made by UBU UBU_v1_45_8 on Asrock Z170 mobo doesn’t remove the “capsule”.
I just received my new Z170M Extreme4 and tried to flash my modded bios before installing system but it gave me a “secure flash check fail” 
If you have any new direction to remove modded bios capsule…
Thanks but when I open the bios inside UEFITool there is no “capsule” it shows only “Intel”.
When there is no capsule, neither the UEFITool nor the UBU tool can remove it.
You should ask SoniX or CodeRush how to prepare a modded BIOS of your ASRock mainboard for a proper flashing.
I guess I won’t be the only one with this issue on Asrock Z170.
Maybe is there any change to be made to UBU and/or UEFITool?
I would be very pleased if SoniX or CodeRush could mod the bios for me, but i would prefer to do it “myself” since I won’t ask for a mod each time Asrock release a new bios 
Apparently in Asrock replaced protection from modified BIOS flash. Now, in the original BIOS file, there is no capsule header.
I think that the order of the modified flash file will be:
1) Flash the original BIOS file.
2) Using FPT (v11.0.0.xxxx) to copy the Region BIOS.
- fptw -d bios.bin -bios
3) Modify bios.bin.
4) Flash the modified file using FPT (v11.0.0.xxxx):
- fptw -f mod_bios.bin -bios
Edit:
FPT can be found >here<, section C2. Intel ME System Tools Full Packages
.
@SoniX :
Thank you very much for having written >this< guide about
a) how to modify an AMI AptioV UEFI BIOS of the latest ASRock mainboards with an Intel Chipset from X99 and 100-Series up and
b) how to get it properly flashed into the BIOS chip of the ASRock mainboard.
@all users with such ASRock mainboard:
Meanwhile I have inserted SoniX’s guide into the start post of >this< thread.
This will make it much easier for you to find it.
@ SoniX:
8086-0406 Intel Skylake-KabyLake VBIOS 9.0.9105
8086-0406 Intel Skylake-KabyLake VBIOS 9.0.1037
According to Lenovo, version 9105 was a test version only meant to fix a BSOD ("Intel test VBIOS 9105 for WIN7 BSOD 116 issue"). Version 1037 is the actual firmware.
SKL-KBL 9.5.rar (38.3 KB)
I did succeed folowing your instructions but after tweaking some settings in the bios I did realized that I was enable to disable CSM support.
If I dopp CSM support then I have a blank screen at boot and notning happen.
So I did flash back unmodded bios and have no issue with CSM disabled.
@ Fernando
@ propergol
Unfortunately, the method proved to be unsuccessful. 
Added:
@propergol
After flashing the modified BIOS and reboot, you did not try to Reset CMOS?
I think that it is version 9.0. The difference of 4 bytes at the offset 0x2CBE.
Ah, UEFI Strip does that. If it detects SKL/KBL then it names the file 9.5.xxxx whereas if it’s SKL it names it 9.0.xxxx. So the 1037 I uploaded is indeed the same as the one posted by Pacman. The other weird one is just so you guys know what it was about, a test version.
In the end, should I use 9.5.xxxx for SKL-KBL, or 9.0.xxxx? I thought they will use the same as HSW vs BDW. If no changelog is found, a KabyLake GOP will give us the full version.
9.0.xxxx. While there is no more accurate information.