Memtest86 image validation

[hunter86_bg]

Hello community,
I have searched for md5sum/sha1sum/sha256sum of the USB images provided on the website.I couldn't open the configuration page of the UEFI version (v7.2 free),which I suspect could be due to damaged image.

Thanks in advance for your responses.

P.S.: If this question has already been answered, feel free to add a link to the topic and close this thread.

[David (PassMark)]

The download is a Zip file. Zip files have 32bit checksums. So any corruption in the download will generally result in the Zip file throwing an error when you extract the files.

The Zip files contains an .img file (memtest86-usb.img) which gets copied to the USB drive.
Once on the USB drive, the executable files for V7 are,
C:\temp\MT\img\EFI\BOOT\BOOTX64.efi
and
C:\temp\MT\img\EFI\BOOT\BOOTIA32.efi (for 32bit)

These files are digitally signed (by MIcrosoft) to allow for them to work with secure boot, The signing process means that the signature will not be valid if the file is corrupted or has been tampered with. So you could check this if you wanted to.

But for the record,
memtest86-usb.img Version 7.2 (13/Dec/2016) is exactly 157,286,400 bytes in size
MD5: b8f1bf2b6372a205fe181ea165d6efed
SHA1: f0c840e53bab18c741774c33a421deaa3f4de26f
SHA256: b5c66339410ed1b3fd903e922333278ed0c9bb850bf5a2baaf 3845fb63555ce1

[hunter86_bg]

Thank's for the reply.
As i'm not using Windows (although I have tried the image there too) I can't benefit from the digital signature's.
It seems it's a UEFI based problem.

Also, I have managed to use the legacy (v4) with and without multicore support.Sadly it doesn't work in the UEFI (v7.2) build.

[David (PassMark)]

The checking of the digital signatures for secure boot is done at the BIOS level. So it effects, Windows, Linux, MemTest86 and any other bootable software.

If you have UEFI BIOS then this page might help you get it booting.