can not boot into 3.2 ISO image from the VM-based

[Amen]

trying to  migrate our ISE nodes to 3.2 version in a VM-based infrastructure, I am trying to boot VMs into the ise-3.2.0.542a.SPA.x86_64.iso image as obtained from Cisco's software download center but I keep getting the attached error. It is worth noting that I can boot without any issues into 2.6 and 3.1 iso images with the exact same settings in VSphere so I am not sure why there is this issue with the 3.2 image specifically

[marce1000]

         - Verify the md5sum (checksum) of the ISO  file used  , 

 M.

[Arne Bier]

Marce1000 has a good point - the file could be garbled.

Did you set the VM to be Redhat 8 (64bit) ?  You can also set the Boot to use UEFI (but in that case you must disable Secure Boot) - the older mode also works. 

[P.e.k.k.a.]

Hi! I know this is 3 month old question but any how. At my own lab, I was to test ISE 3.4 and its installation workflow. For some reason I got my ESXi set to run bios in "BIOS" not "UEFI" mode. Thus the default choise on this ISE VMhost was to use UEFI boot sequence, hence failing the boot. Swapped the setting from ESXi virtual host settings to BIOS and all honkidory now. Thanks Arne Bier for pointing this out. 

[Arne Bier]

While there is certainly nothing wrong with BIOS mode, you can install ISE when the VM hardware is set to UEFI. VMWare defaults to UEFI with Secure Boot when you choose the newer Redhat OS. ISE does not boot in Secure Boot mode (sadly). All you needed to do was to untick Secure Boot and leave UEFI enabled. But once ISE has been installed in BIOS mode you can flip back to UEFI. Maybe try that on your next install.
I noticed that Aruba Clearpass supports Secure Boot. Not sure why Cisco has done the same.