I can't find my last email to reply, solved. I have built bleeding edge computers since the early 90's. Never have I ever had to deal with secureboot. What a pain in the **bleep**. I cannot find any technical information on the mechanics of its use. On my first MFM hard drive, I had to manually enter all of the bad sector locations manually. Yes, I have been doing this for a while.
I just had to vent a little. The BIOS information available is cryptic, incomplete, and anything but intuitive. Making changes to it for the sake of a game is just stupid. I had secureboot enabled in the BIOS but not indicating enabled in Win 10 using the Admin Powershell. A status request using Confirm-SecureBootUEFI returned False despite being turned on in the BIOS. I returned to the BIOS because of a tip to enable default keys. I could not get the BIOS to enable the default keys. Here is your tip, turn off Secureboot first, then enable default keys (which only works when secureboot is disabled). Reboot, reenter BIOS and enable Secureboot again. Save changes, start windows, check Admin Powershell with Confirm-SecureBootUEFI and the response was True. It now works with 2042.
In my decades of computer building I learned pretty quickly that YOU DO NOT CHANGE THE BOOT METHOD. It ALWAYS leads to data loss and weeks of lost time trying to uncover the culprit. This was a rare case of it working and not deleting some delicate invisible set of Hex values that differentiates the way that the computer boots. Your mileage may vary.
