When users want to try a build I make, they have to change Windows into "Test Mode". Which requires a reboot, and potential other issues a novice Windows users might not be aware of.
Have users to able to install a release I make without needing to reboot / change to "Test Mode".
If you are to use ZFS, you should probably use x64. So that is the main focus.
Latest Windows is 10 (at the time of this document) so it should support Win 10 x64 at least, since that is presumably the direction Microsoft is taking Windows, and any requirements here will be true for future versions of Windows. Support of older Windows builds would be nice - At least, Windows Server, 8, Vista.
- To avoid Test Mode, the Driver (kernel component) has to be codesigned.
(Is this the correct assumption? It is not entirely clear - I don't mind the Smartscreen warning, or having to click "trust this anyway" as long as it can be done with Test Mode and reboot.)
- To codesign Win10 x64 I must first get EV certificate, it can not be Standard.
- DigiCert had me show 2 IDs, 2 Skype video calls, fill in forms together, but I must also have a Registered Company. (Not non-profit, nor Org)
(Because of IDs and valid address, I then have to register in Japan.)
- To register a company costs about $13,000.
- Use EV to "Register for the Hardware Program".
- Obtain through Hardware Program a Cross-Certificate
- Sign compiled code
- Upload CAB file
- Pass $something - presumably some testing
- Download signed CAB file