The entire problem here, I suspect, is related to fundamental changes made to Windows technology starting in 2015 through 2018. The three interrelated technologies are:
Device Guard
Credential Guard
Hyper-V/VBS
To support the, fundamentally, security related changes, Microsoft forced fundamental changes to Windows Kernel Mode drivers. Changes are outlined in the following article:
Driver compatibility with Device Guard in Windows 10 - Microsoft Tech Community - 364865
There are probably a bunch of additional issues and articles available, but take a look and you'll see that simply editing the executable won't take you very far...
The sad part is, it works just fine.
What works just fine?
Editing the exe to skip the check. See TOM_RUS on Twitter: "Like this in version 2.1.0.1424… "
Although the MS AHCI driver shows a 2006 date, it is in reality more recent. The AMD AHCI driver though is actually from 2005 and is not advised to be used...
Damn. I totally missed that.
I cant get that screenshot to match the .exe i got. So no luck here
Did you succeed in modifying the exe?
This thread is marked as "Presumed Answered". Many people gave answers, but the issue is not solved unfortunately.
I'll be surprised if its ever resolved.