Failed to load crypto64.efi - Error booting ESXi via Auto deploy

Products

• VMware vCenter Server 8.0

Issue/Introduction

During ESXi host boot via Auto Deploy using UEFI, the following error occurs:

Failed to load crypto64.efi: Not Found
Falling back to internal crypto suite
Fatal error: 15 (Not Found)

/var/log/vmware/rbd/httpd_request_log

YYYY-MM-DDTHH:MM:SS.000 127.0.0.1 - - "-" "iPXE/1.21.1-vmw (g188e)" "GET /vmw/cache/vital/174bd154157d193bc344787cb7a3ef73/crypto64.efi HTTP/1.1" 404 275

/var/log/vmware/rbd/rbd-syslog.log

YYYY-MM-DDTHH:MM:SS.347010 err rbd  [2644282]director:ERROR:no handler for -- /vmw/rbd/host/5a0aa2b07b30462d1c00593966902496/efi/boot/crypto64.efi
YYYY-MM-DDTHH:MM:SS.579746 err rbd  [2644282]director:ERROR:no handler for -- /vmw/rbd/host/5a0aa2b07b30462d1c00593966902496/crypto64.efi

Environment

vCenter 8.0U3

Cause

This issue is caused by a known bug related to the snponly64.efi.vmw-hardwired file required for boot during ESXi installation via Auto Deploy. The engineering team is aware of this issue and it will be resolved in a future vCenter Server release.

Resolution

Workaround:

Obtain the snponly64.efi.vmw-hardwired file:

• Deploy a vCenter Server 8.0U2 instance and enable Auto Deploy.
• Navigate to "Home -> Auto Deploy -> Configure -> Download TFTP Zip file."
• Extract the contents of the downloaded ZIP file.
• Locate the snponly64.efi.vmw-hardwired file within the extracted directory.

Copy to TFTP server:

• Copy the snponly64.efi.vmw-hardwired file to the TFTP server used by your Auto Deploy configuration.
• Replace the existing snponly64.efi.vmw-hardwired file on the TFTP server with this new file.