Wow, nice to know.
So how does debugging work?
I go to the hardware dashboard, submit my sys file, instantly get it signed, and then debug?
Also, any thoughts on my second error, ServiceBinary path?
You use bcdedit to turn test signing on, sign your driver using either your ev cert or a self signed cert (visual studio driver builds can generate one for you) and install your driver.
I used bcdedit and turned on test signing. After restarting my Win10 VM, I saw the test logo in the lower right corner.
Installation proceeded without comment. Log file shows:
dvs: {DrvSetupInstallDriver - exit(00000000)}
<<< Section end 2025/05/02 20:02:35.637
<<< [Exit status: SUCCESS]
I did not see anything in Computer Management, sadly. I restarted the Win10 VM and saw a BSOD "Inaccessible Boot Device".
I would say the problem is with something in the driver, but I purposely am using just the unmodified default VS22 Create Project sample, so it does nothing, like really nothing.
Thoughts?
For whatever it is worth, the reason that I got into this project of creating a Win10 driver from the Win7 driver is that after some point, Windows threw that exact same error message. I was told that Microsoft introduced a third partition and maybe that is why. I want to start off clean with a Win10 driver and then build up from there.
Here I am. A clean VS22 driver throws that Inaccessible Boot Device BSOD.