CIS 'Comodo Rescue Disk' creation fails; will not boot

In [i]Comodo Internet Security Premium[/i] I went to Tasks > Advanced Tasks > [b]Create Rescue Disk[/b] and burned an auto downloaded ISO to a newly formatted 32 GB FAT32 USB Flash Drive [according to the procedure described here:].  When booting from the Flash Drive, the process hangs in text mode at the point "Requesting events from the Kernel..."

I also downloaded the (stale) Comodo Rescue Disk vs. 2.0.275239.1 ISO and burned it to a USB flash drive with Rufus 2.18.  When booting this drive I get the error "vesamenu.c32: not a COM32R image" in a continuous scroll.

Then I burned the 2.0.275239.1 ISO using UNetbootin 661.  It would not boot, either.

So I'm stymied.  Configuring a bootable USB rescue drive in [i]Comodo Internet Security Premium[/i] is simply a matter of pressing a few buttons; there are no options, so how could I be doing something wrong?

[b]What is the secret to making a bootable Comodo USB Rescue Disk?[/b]

OS – Windows 10 Pro 64-bit version 1803 (Redstone 4 / “April 2018 Update”) build 17134.81 {aka Windows Version 10.0.17134.81}
OS HOST – 3.64 TiB Toshiba N300 P/N HDWQ140XZSTA HDD
MOBO – ASRock Z97 Extreme6
UEFI vs. 2.80 w. Haswell microcode 306C3_24 (latest as of 2018-05-29)
CPU – Pentium G3258 {Anniversary Edition} (Haswell Refresh, CPUID 306C3)
GPU – NVIDIA GeForce GTX 1060 6GB, DirectX 12
Driver (latest as of 2018-05-22)
RAM – 24 GB G.SKILL RipjawsX DDR3-1866
POWER SUPPLY – Antec ‘TruePower New’ TP-650 (~4 years old), 110V
ATX12V 2.3 / EPS12V 2.91, 80 PLUS Bronze Certified

Have I posted this question in the wrong place?

First the CRD version you get from CIS is actually an older version compared the the v 2.0 you get from the CRD release topic. I’m guessing CRD is so old that it won’t run on newer hardware such as yours. You can try burning the ISO of v2.0 to a blank CD or DVD and see if it works then, if not then yeah it won’t work on newer hardware.

Many thanks for the information, futuretech. I won’t bother burning from within CIS in future. Meanwhile, I may have determined why my rescue disks won’t boot.

I have discovered – of all the inscrutable things – that when my Blu-ray / DVD drive is plugged into the ASMedia ASM1061 SATA controller on my ASRock Z97 Extreme6 motherboard I am unable to boot Linux-based distros or utilities from either USB or DVD. But when the optical drive is connected to the Intel SATA controller, I can boot Linux-based distros and utilities from either USB or DVD.

This took me 7 weeks to figure out considering that Windows 10 installers and rescue disks boot normally on both USB & DVD when the optical drive is connected to the ASMedia controller.

[Several months ago I thought I had a hard drive failing because no utility would report its S.M.A.R.T. status or run drive self checks. At length I learned that if I switched the HDD from the ASM1061 controller to the Intel controller S.M.A.R.T. status was reported and drive self checks could be run.]

Looking forward to trying out CRD when I get some fresh media. The 2.0.0102154 User Guide indicates that the downloadable version can be USB-based [page 51 says, “Burn this new version of CRD ISO file to CD, DVD or USB for future use.”] … but I can not find instructions for burning to USB anywhere.

I typically use Rufus or YUMI or Unetbootin: hope those are acceptable.