I see, so you might need the UEFI info from the host or something similar I don't know if this exists, I have to admit I'm not using Windows in production myself.

You are welcome

I second @olivierlambert saying that you should consider EPYC, they are fantastic to work with, have moved my entire org to almost 100% EPYC systems and they have been nothing but rock solid reliable, fast, and efficient. You get more power for the money too and more expansion options. And both Intel and AMD run just fine, there aren't really any issues or differences that matter for most workloads. EPYC is mature at this point though, the "teething" issues from years ago are long gone, I have some first gen EPYC stuff running, some that have had uptime in the realm of a year without a single hiccup.

@olivierlambert I made a system update (yum update) and rebooted the server without interfering on grub menu... So it persisted on the same error... I nad to choose the second option again to do a good boot. I tried to find where those faulty grub log lines where saved, but journalctl just stored healthy boot.

Not sure to get it, so giving the question for @fohdeesha