All legitimate kernel drivers are signed with certificates that ensure the file has not been modified. Obviously, for cheating, we can't all use the same certificate, or we'd all get banned very quickly. Thus, by default, the number of certificate fields and the certificate fields themselves are randomized for each person. However, much of the default text is just a bunch of random letters. You are encouraged, therefore, to sign your driver yourself and try to emulate a real certificate as much as possible. You only have to do this once.
Once you have signed your driver, you can re-sign any future versions of your driver with the "Re-Sign Driver" button. If your driver is already signed and you want to load it on a new computer, use the "Install Certificates" button on that computer. If you mess up your scripts so that they no longer work, you can download default ones from here.
Sign Driver (.ps1)
This method utilizes PowerShell scripts to sign your driver. It closely emulates how normal drivers are signed and allows for a lot of customization.
To begin, open Launcher and click the "Sign Driver (.ps1)" button. Click OK when it says it cannot find any .ps1 files. This will download four PowerShell scripts unique to you into the Launcher folder. They will be randomly named and will have the .ps1 file extension. Choose 2-4 of the scripts you'd like to use to sign your driver—it doesn't matter which—and open them in notepad or with the default PowerShell editor.
Pro-tip: You can rename the PowerShell scripts you want to use, like 1.ps1, 2.ps1, etc., so they are easier to keep track of.
Read the instructions at the top. Scroll down to "$pfxFileName." Change the file name. Change "$pfxPassword." Change the timestamp URL if you want (default is fine and regularly used for real drivers). Most importantly: change all the "CertName," "CertOrg," "CertOU," "CertCity," "CertState," "CertCountry," "CertSerial," and "ValidityMonths" to your own text/values for ALL the certificates, including "root," "intermediate" (if present), and "codeSign." You can leave fields blank! For example: $rootCertOU = "" or $codeSignCertState = "". I encourage you to leave 1 or 2 blank so everyone has different fields in their certificates. Do NOT delete anything.
When you are done editing the scripts you want to use, open Launcher and click the "Sign Driver (.ps1)" button again. Navigate to the first script you want to use. Open it, leave the edit field blank when Launcher asks you for the current signature number, and let Launcher sign your driver. If you want to sign the driver more than once (strongly recommended), click the "Sign Driver (.ps1)" button again. Navigate to the second script you want to use. Open it, write 2 into the edit field when Launcher asks you for the current signature number, and let Launcher sign your driver again. Your driver will now be signed twice and look just like a regular driver. You can continue signing it up to four times if you wish.
You may now delete your PowerShell scripts or store them in a safe location, preferably off your computer. Launcher automatically uploads the PowerShell scripts you use to sign your driver so that they can be reused later with the "Re-Sign Driver" button. Thus, all your changes will be saved, and the next time you click "Sign Driver (.ps1)," Launcher will download the changed scripts.
Pro-tip: Once you load your driver, right click it and go to properties. Click on "Digital Signatures." Ensure all the certificates match what you wrote in the PowerShell scripts.