How to sign a driver and most importantly what?

Question

Windows

Good afternoon, there is a home-made device in production, in the amount of one piece. To communicate with this device, at one time a driver was written from the time of windows 2003.
Due to lack of memory and the specifics of the software, we decided to switch to 2012r2.
The driver was written, everything works great, but there is one small nuance - the driver is unsigned and therefore works only when the signature verification is explicitly disabled.
I read "In these boarding schools of yours" that you can only use a purchased certificate.
From here I want to give a list:

• We bought server 2012R2
  
• Bought a dozen RDP Call
  
• Bought about a dozen Server Call
  
• Bought a hardware server
  
• Designed a device (for personal use)
  
• Wrote a driver (for personal use)
  
• Wrote software to work with the driver (for personal use)
  

And now we also have to pay an annual “Tribute” so that we can use our device with our own driver ??
Emotional outburst.
Well, actually the question is this, is there any way to still sign at least with a "left" certificate, or add your own root certificate?

Answer 1

And now we also have to pay an annual “Tribute” so that we can use our device with our own driver ??

Who is forcing you?

bcdedit.exe /set TESTSIGNING ON
certmgr.exe /add "ваш_самодельный_сертификат.cer" /s /r localMachine root

Creating a certificate yourself is also not difficult, write something like -
The makecert.exe utility can be downloaded from the Microsoft website.
And everything will work great.