Intel AMT self signed certificates – Points with USBFile.exe

Hello All,


I’ve been organising Intel AMT / vPro in my testing setting at work, and I’ve efficiently put in EMA Server efficiently and operating in CCM.

I’m needing to make use of ACM – have tried utilizing our pre-existing DigiCert account nonetheless we do not have the function so as to add vPro prolonged properties on our account.

Regardless I’m going through an points the place I can’t use the USBFile.exe instrument to create a setup.bin file for our personal CA’s SHA256 hash.

Can anybody lend some help on the best way to get the USBFile.exe instrument working?

I’ve adopted a few guides, and I am caught with:

Did not load libcrypto.dll – Cannot compute hash algorithm SHA256 for file: certificates.cer.

Did not course of command line parameters.”

I’ve tried on a number of pc’s and have put in VC_redist.x64 + OpenSSL Mild and moved the libcrypto.dll file into the folder nonetheless it isn’t recognizing it even after renaming the file?

My command line is : “USBFile.exe -create setup.bin password password -hash certificates.crt “Customized AMT Root CA” sha256″ (the password has been modified for this objective



For reference :

LibCrypto from OpenSSL V3.3.1 Mild is getting used.

Newest AMT SDK.

Newest Model of EMA Server

Have tried on Home windows 11 & Home windows 10 similar error with each.




I’ve exported the .cer from our Root CA which is our native area controller, and nonetheless going through the problem. Is it an issue with the libcrypto.dll, or with the .cer file itself.


Additionally going ahead, if this does work may somebody present clear steps on what to do subsequent to get the gadget to recognise the SHA256 hash?

E.g do I load the machine into the MEBx UI, and have the usb flash drive plugged in and it’ll decide up the setup.bin file?


Am I doing this fallacious or is that this nonetheless the one option to allow a SHA256 hash into the MEBx?


Any assist shall be a lot appreciated!



Leave a Reply

Your email address will not be published. Required fields are marked *