Fatal1ty Z170 Gaming-ITX/ac BIOS settings backup

Dear ASRock support,

After updating it, does the 2.00 Bios - on an ASRock Fatal1ty Z170 gaming-ITX/ac - support the "backup.BIN" file which I've made with an 1.80 bios? The reason I did ask about it that I simply can not load it from HDD, after the update.

It took me a day to optimize my profiles (overclock, FAN tune curves etc.) with the 1.80 bios and now I lost them all.

Thank You and Have a nice day.

ps.: sorry for my english...

Edited by Alucard - 23 Mar 2016 at 9:22pm

Alucard wrote: Dear ASRock support, After updating it, does the 2.00 Bios - on an ASRock Fatal1ty Z170 gaming-ITX/ac - support the "backup.BIN" file which I've made with an 1.80 bios? The reason I did ask about it that I simply can not load it from HDD, after the update. It took me a day to optimize my profiles (overclock, FAN tune curves etc.) with the 1.80 bios and now I lost them all. Thank You and Have a nice day. ps.: sorry for my english...

I'm checking with ASRock about this, and will have an official answer as soon as possible.

But I can tell you now that saved profiles from an earlier UEFI/BIOS version should not be applied or used with a new UEFI/BIOS version.

I understand that it is frustrating to have all your UEFI settings and UEFI profiles lost after a UEFI/BIOS update. I've been living with that for a long time.

I don't know of any mother board manufacture that allows profiles from a different UEFI/BIOS version to be used with a new or different version.

One big problem with this is, we cannot control or know how old or different the saved profile a user has, and might try to use with a newer UEFI/BIOS version. The saved profile might be two, three, or more versions older than the UEFI/BIOS version that they are using now.

While it might be possible to use a saved profile with a new UEFI/BIOS version sometimes, if an old profile cannot be used with even one new UEFI/BIOS version, then we have no choice in not allowing all old profiles to not be used with new UEFI/BIOS versions. We must make that choice if a user could ruin their UEFI/BIOS with an older profile.

If a UEFI/BIOS image is not perfect, it will not work correctly. If there is anything that might corrupt a UEFI/BIOS image, that cannot be allowed. I'm sure you can understand this.