Hello, as mentioned in the title of this post, I need the ‘Windows 10 WHQL’ setting option in the latest BIOS of the Z490 Vision D motherboard. There are only ‘Other OS’ and ‘Windows 10’ available in the latest version (F22). Unfortunately, in these settings, the post-screen and the BIOS logo is only displayed in low resolution. Until now, this problem could only be solved with the now missing setting ‘Windows 10 WHQL’. Would someone perhaps be so kind as to unlock or add the missing option if possible?
You cant unlock whats NOT present in the code, you cant add it a new string but it can be edited “cosmetically”… then what for, if the function itself can be added as real to the code of the bios, that you cant re-compile or have the source and your not a bios engineer with access to the right tools and skills from AMI…or other.
Not taking out your “hopes”…but the mod community has its own limitations of knowledge and leaked tools to work with… still im not the only forum user, wait for other users povs.
1 Like
The original WHQL string isn’t gone, so there’s a chance that the code too.
Install with Q-Flash.
2 Likes
Hello and sorry for my late feedback and thank you first of all for your efforts. Unfortunately the problem could not be fixed. With @Sweet_Kitten’s BIOS, I do have ‘Windows 10 WHQL’ to choose from in addition to ‘Other OS’ (now ‘Windows 10’ is missing), but it does not solve the problem with the low resolution of the post screen and BIOS logo. I also contacted GIGABYTE support who wrote me that the ‘Windows 10 WHQL’ setting would not affect the display at all. However, I have had completely different experiences with this setting and not only with GIGABYTE boards, but also with e.g. MSI. I am now waiting for the next answer after I contradicted the last statement of the support.
@Forsiko Could you please give us a little more info?
Are you using a discrete GPU? If so which video card model?
Do you have CSM disabled?
If you are using the Intel iGPU what CPU model do you have?
Are you using HDMI or DP?
What is your PC connected to - a monitor or TV?
What is the native resolution of the monitor/TV and what resolution does the post-screen and the BIOS logo appear to be displaying at? (upload a photo if you can)
Did any previous BIOS version display correctly? If so, which BIOS?
Video Card is Sapphire Pulse 5500 XT 8GB
Display is a LG 4K monitor - DP connected
3860x2160 is the native resolution
CSM is disabled (everything I boot is in UEFI mode)
Every previous BIOS version worked correctly - the problem first appeared with the first beta version of F22 ( F22b -Address blank display while system powers up with RTX3060 series graphics cards 14/03/23)
So since GIGABYTE solved a problem with RTX3060 cards my problem exists.
I hoped, that everything will be fine with the final F22 version, but it isn‘t.
In the previous versions, the post screen and bios logo had been displayed correctly with CSM disabled and the ‚Windows 10 WHQL‘ setting.
1 Like
@Forsiko As the change occurred on the latest BIOS I think you only have 2 options;
-
Leave everything as is and put up with the issue.
-
Attempt to flash back to previous BIOS.
Downgrading back to previous BIOS does not come without risk, you would need to use the correct version of Intel FPT (Flash Programming Tool) for your chipset as the newer capsule BIOS cannot be downgraded with either of Gigabyte’s flash tools (Q-flash or EFIflash).
As you have 2 x Intel ethernet adapters there is the risk that the MAC address(es) could be overwritten by FPT if you don’t use the -savemac command.
Before attempting a BIOS downgrade it is highly recommended to make a complete BIOS backup using FPT and to write your MAC addresses down somewhere so that you can recover from a failed BIOS flash - note that in this case you would need a hardware programmer to recover the BIOS.
The F22 BIOS has an updated version of ME Firmware 14.1.67.2046 (compared to 14.1.53.1617 in F21) and they both share the same PCHC firmware (14.0.0.7002) PMC firmware (140.2.01.1018) which is good.
1 Like
@chinobino How should I use the -savemac parameter?
EDIT:
This is right:
fpt.efi -f bios.bin -savemac
1 Like