-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved CKS Enablement Scheme. #10
Comments
I tested this project and the driver was loaded successfully, but some drivers that were supposed to be loaded could not be loaded (not all), such as the leaked signature, and even many regular drivers. When loading the driver, it prompted "Your organization uses device guard to block this app". I decided not to use this item anymore, and finally deleted the SiPolicy.pb7 file in the EFI partition. These abnormal drivers can be loaded again. Why? Is it my fault? |
Strange things happened again. After I regenerated the binary file of the Enterprise Edition, the driver can be loaded normally. Is it because it was generated in the Professional Edition before? After using ssde_enable.exe once, why can the self-signed driver be loaded normally every time the computer is started? I don't even use ssde.sys. Shouldn't this be restored after restarting? |
Did you generate your own SiPolicy xml with powershell or did you use a pre made one by some one else? If you have sppsvc service stopped I think the license data are not restored anymore. |
I regenerated the xml myself and there was no problem. Thanks for your reply! |
I had a lot of headache with ssde_enable.exe and I came up with a much more convenient solution.
0. Setup everything, Own PK & Co, Policy, etc...
Voila nothing but the driver needed and very reliable.
The text was updated successfully, but these errors were encountered: