-
Notifications
You must be signed in to change notification settings - Fork 242
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
Problems with manual installation inside VMWare #173
Comments
"Image" means executable in EFI error message. The first error is caused by some extra data which Assuming that you copied the provided shim and MokManager, the second error would mean that VMWare doesn't trust the same Secure Boot certificates as physical machines commonly do, or has specifically blocked these tools from loading. I can't provide any specific support for VMWare, but at least make sure you have the most recent version. There are guides for adding keys or hashes manually into VMWare Secure Boot, so you could also try those. |
What happens?
I'm doing some experimentations with this tool, after first boot in VMWare with secure boot enabled it says:
I've not modified the config.txt file, the image I'm using is the default splash.bmp.
After some time time it finally shows Verification failed: (0x1A) Security Violation with an OK at the bottom. I can only hit enter here, there's nothing to see. However, after hitting enter it immediately continues, the last 2 lines from the error above flash on screen and it then shows the default Windows boot logo and boots without HackBGRT, it doesn't give me a chance to add the certificate or hash from the grub EFI, and MokManager is never launched.
Disabling secure boot helps somewhat but it still shows the 3 error lines and then shows HackBGRT's splash.bmp, however this doesn't fix the above error.
What am I doing wrong?
How this happens?
Log file
setup.log is NULL
The text was updated successfully, but these errors were encountered: