My background = In the past, I have already modified a driver (FBWF. sys) from Winpe10 Version 1511 build 10586. I know a few things, like modify the checksum created by the linker, sign with SignTool. exe the file with a test certificate created by MakeCert. exe.
But, it's sure, I don't control all the settings.
The target: I want to modify the services. EXE program of Winpe10... for educational purposes only!
My modify: Replace the "M " of the string "Minit " with a "N ".
So I created a test certificate with MakeCert (an older version because it is no longer available in the "SDK... signing tools "). And I signed the program with SignTool. exe.
I checked with "SignTool Verify/pa" that the signature is correct.
I also checked that the BCD contains "testsigning = yes " (visible at the bottom right of the screen)
Then I copied this file into the VHD containing WinPE Flat mode.
My observation: When starting this WinPE, there is a blue-screen "Critical process died ".
My idea: The startup mechanism checks the signature of the file "services. exe " before launching it. This check fails.
Q = what is missing?
Should it put the certificate in WinPE? If so, how do I proceed?
Do I have to create the same "store " in WinPE to file the certificate?
Should it also copy the certificate in "root "?
PS : I created a NININT key in the System hive to make sure that the program's operation is not disturbed