You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Signed OpenCore.efi fails version auto-detection due to MD5 hash mismatch #214
When using the "Clean Snapshot" tool using the latest version of ProperTree and OpenCore 1.0.7, ProperTree will append a "HideVerbose" boolean to OC drivers. While OC will complain about not having schema for this at boot, it doesn't seem to cause any problems.
Thanks for the reply and apologies for the delay. I'm sure I did, but I did double check and grab the latest version of ProperTree, OpenCore.efi, and BOOTx64.efi from your and Acidanthera's repos respectively. The issue persists even after updating everything, I get 1 "No schema" error per driver entry after using OC Clean Snapshot. The issue goes away after removing each HideVerbose boolean. The plist validation tool confirms this.
I downloaded the latest OpenCore (1.0.7 - both the Release and Debug builds from Acidanthera's GitHub repo) and performed an OC Clean Snapshot with the latest ProperTree in a blank document and it does not create HideVerbose values under UEFI -> Drivers:
Do you have ProperTree's OC Snapshot Target Version setting set to Auto-detect as follows?:
Do note that (assuming you've verified and compared to my settings and findings) ProperTree's OC version detection relies on generating an MD5 hash of the OpenCore.efi file - and comparing that to a known list of releases from Acidanthera. If you've gotten OpenCore from Dortania's build repo - or any other build (even locally built), the hash will not be the same, and PT will fall back to assuming it's the newest version it has Snapshot info for.
Thank you for the explanation, I see what happened. My OpenCore binaries are signed by me so I can enable secure boot, thus changing the MD5.
Can I change this to a feature request to use pefile to skip over any EFI signatures and hash the file itself? If you are preoccupied I can also make a pull request later for it that you can look over.
I realized that adding a dependency would make the tool much less user friendly, so I found a way around it with built in libraries and have submitted a request :)
changed the title [-]HideVerbose flag appened to drivers incompatible with OpenCore[/-][+]Signed OpenCore.efi fails version auto-detection due to MD5 hash mismatch[/+]on Sep 5, 2026
Activity
corpnewt commentedon Sep 2, 2026
Hey there - did you get OpenCore from the official Acidanthera releases? Or from somewhere else?
GybiBite commentedon Sep 4, 2026
Thanks for the reply and apologies for the delay. I'm sure I did, but I did double check and grab the latest version of ProperTree, OpenCore.efi, and BOOTx64.efi from your and Acidanthera's repos respectively. The issue persists even after updating everything, I get 1 "No schema" error per driver entry after using OC Clean Snapshot. The issue goes away after removing each HideVerbose boolean. The plist validation tool confirms this.
corpnewt commentedon Sep 4, 2026
I downloaded the latest OpenCore (1.0.7 - both the Release and Debug builds from Acidanthera's GitHub repo) and performed an OC Clean Snapshot with the latest ProperTree in a blank document and it does not create
HideVerbosevalues under UEFI -> Drivers:Do you have ProperTree's OC Snapshot Target Version setting set to
Auto-detectas follows?:Do note that (assuming you've verified and compared to my settings and findings) ProperTree's OC version detection relies on generating an MD5 hash of the OpenCore.efi file - and comparing that to a known list of releases from Acidanthera. If you've gotten OpenCore from Dortania's build repo - or any other build (even locally built), the hash will not be the same, and PT will fall back to assuming it's the newest version it has Snapshot info for.
-CorpNewt
GybiBite commentedon Sep 4, 2026
Thank you for the explanation, I see what happened. My OpenCore binaries are signed by me so I can enable secure boot, thus changing the MD5.
Can I change this to a feature request to use
pefileto skip over any EFI signatures and hash the file itself? If you are preoccupied I can also make a pull request later for it that you can look over.corpnewt commentedon Sep 4, 2026
For the time being, you can specify the version under that drop-down list:
Regarding
pefile- I'm not familiar with it, is there a way to do that purely in the standard library of python (in a cross-platform way)?-CorpNewt
GybiBite commentedon Sep 5, 2026
I realized that adding a dependency would make the tool much less user friendly, so I found a way around it with built in libraries and have submitted a request :)
[-]HideVerbose flag appened to drivers incompatible with OpenCore[/-][+]Signed OpenCore.efi fails version auto-detection due to MD5 hash mismatch[/+]