...and here's yet another issue. Cos nowadays end-users are betatesters too, apparently ¬¬
I've two monitors connected to the NUC. And today I've nearly turned crazy because the HDMI ports worked seemingly at random: HDMI2 never worked, and HDMI1 sometimes it worked, sometimes didn't. After trying lots of combinations and different cables, I almost thought that my NUC was defective and that I'd have to RMA it. Fortunately, I noticed that the issue happens when HDMI detection is in Auto in the BIOS. If I manually put the Primary and Secondary HDMI, both monitors run fine.
Also, on an unrelated note, can you fix your cookies so the "Remember me" box would actually work? I'm tired of having to login every single time that I close all of the Intel forum tabs. It's the only website where that happens to me.
I understand that you are having HDMI recognition issues when auto HDMI detection is active
In order for me to assist you better, please provide me with the .txt file that the System Support Utility will generate. To attach a file, you must click the "Attach" option on the bottom right-hand corner of the response box.
As well, please provide us with the Report for Intel® Graphics Drivers; here are the steps to generate it:
Can you please provide us with you monitor's model and brand?
I hope to hear from you soon, please let us know the outcome.
Why of course. Betatester extraordinaire to the rescue!
You could at least send me an additional free NUC7PJYH in exchange for my services...
Ah, and monitor models: AOC U3277PWQU (4K resolution), Samsung S24D300H (1080p). And no, they've no new firmware avaliable.
Thank you for your patience.
I am elevating your case in order to perform research about the auto detection issues that you are experiencing.
We will try to replicate your issue based on the description of your issue and the information provided to us.
This may cause a delay between our answers, however we will reach you back as soon as possible.
I hope this helps.
OK, forget about this one. I reported this while I still didn't know that the drivers were the ones causing the issue. I put it in Auto again and it works just the same as putting it manually. Sorry for the inconvenience.
The driver issue still remains regardless.