Mint19.1- USB Boot error — vesamenu.c32: not a com32R image [closed]
I downloaded the latest Torrent version of Linux mint cinnamon 19.1 ,from its official website here , (a 1.8gb file) on my Windows10(64bit )machine. I tried creating a bootable usb via Rufus but it gave the following error —
ISO image is an obsolete image of vesamenu32
Rufus offered for a solution and on clicking on «yes» it gave the following error-
[0x00000002] cannot find the specified file
However,I did manage to create a bootable usb inspite of the errors thrown above by just clicking «OK» and «Start» options wherever appropriate. But,now on booting a new error was thrown —
vesamenu.c32: not a com32R image
The system goes into a bootloop throwing this error.Note that a similar error was thrown during creation of the boot usb.How could this be resovled?
asked Jan 12, 2019 at 7:30
129 1 1 silver badge 5 5 bronze badges
where did you download the torrent from?
Jan 12, 2019 at 7:58
We need to know the exact messages Rufus gave you, and what steps you then took. You say it «offered [. ] a solution» and you clicked «yes». What solution was that?
Jan 13, 2019 at 9:41
«I tried creating a bootable usb via Rufus but it gave the following error«. Is that «it» referring to a message from Rufus when trying to build the bootable USB, or at some point when you attempted to boot the USB?
Jan 13, 2019 at 14:38
Did you verify the ISO as instructed on the torrent download page?
Jan 13, 2019 at 14:40
1 Answer 1
[Solution]-Installing Linux_mint 19.1
Linux_mint 19.1 comes with it’s fair share of challenges during installation.This post attempts to provide a guide to navigate through these and successfully install Mint.
1.On downloading Mint from the official website here,the downloaded file might turnout to be a zip file rather than an ISO file.This is because the preinstalled compression software like Winzip treats it as a part of Zip package.To avoid this,firstly uncheck ISO as a part of winzip integration in winzip settings before downloading Mint and after download, confirm the(.iso) extension type of the downloaded file under it’s properties.
2.While creating a bootable USB via Rufus , following error’s would be thrown,just click on the options provided below and move ahead to create the bootable usb-
ISO image is an obsolete image of vesamenu32 [Click -«Yes»]
[0x00000002]System cannot find the specified file [Click -«OK»]
Once the options are accepted the bootable usb will be created. 
3.On booting into the system with the new bootable usb,you will be provided with a boot option
vesamenu.c32 :not a COM32R image
boot:[type-> «live «]
This will create a live session and then you would be able to install Mint from the Operating system. 
Ошибка, которая появляется при попытке установить Linux mint 18.1: «vesamenu.c32 not a com32r image linux mint».
Я сделал запись жесткого диска на флешку iso файла установщика Linux mint 18.1, который скачал с официального сайта https://www.linuxmint.com/download.php. Настроил автозагрузку флешки в BIOS и перезапустил ноут. После этого я, ничего не делая, смотрю процесс: через считанные секунды постоянно добавляется новая строка, которая читается так: «vesamenu.c32 not a com32r image linux mint», как показано на добавленном мною изображении. Не знаю что делать. Кстати, к примеру, linux mint 17.2 я успешно устанавливал без этих ошибок.
Голосование за лучший ответ
либо граб битый, либо не соответствие разрядности между грабом и его плагинами
* нажмите кнопку Tab
* введите с клавиатуры “live”
* нажмите кнопку Enter.
Рецепт старый, но должен помочь
Cannot boot from USB disk with «not a COM32R image» error
After installing 11.10 on my Dell Studo 15 (Model 1557) laptop, it started to overheat. Recently it even shutdown twice saying that critical temperature has reached even when I was just idling (not even a single program was open except for Firefox). After learning that it is a problem with 3.0.0 kernel I decided to roll back to 10.04 LTS. I have downloaded the most recent 10.04 iso from ubuntu.com and created a live USB using startup disk creator in 11.10. But when I am trying to boot from USB I am getting the following error
vesamenu.c32: not a COM32R image I have installed ubuntu from usb stick a couple of dozen times before this and I think it is not a problem with my hardware. Please tell me what to do.
58.2k 44 44 gold badges 147 147 silver badges 201 201 bronze badges
asked Dec 5, 2011 at 6:00
430 1 1 gold badge 6 6 silver badges 14 14 bronze badges
Corrupted ISO image, check that the MD5 matches with the one in Ubuntu.com or download it again, did you use Unetbootin to make the LiveUSB?
Dec 17, 2011 at 16:55
There was a long time bug in usb-creator regarding making 10.04 live usb, so looks like maybe it’s still around.. Try typing live or boot, or even just press return when you get the error. (I forget which one works)
Dec 17, 2011 at 17:27
@duffydack Yes, this error is still present. I’m usually typing help and . magically LiveCD is «waking up». But in this problem I would also consider corrupted ISO image.
Porteus
rick619 White ninja
Posts: 7 Joined: 07 Mar 2022, 17:11 Distribution: 5.0rc3
vesamenu.c32 not a com32r image
Post #1 by rick619 » 05 Apr 2022, 15:59
I setup the latest rc3 on a USB drive. When it boots, I get the error: ‘vesamenu.c32 not a com32r image’.
I’m able to type ‘GRAPHICAL’ and it boots and works well. Is there a way to fix this so it will boot without any errors? I have tried copying the VESAMENU.C32 file so the two versions on the USB drive match in size and version. This didn’t help.
Other than that error, rc3 with Cinnamon seems to work well, saves my changes, etc.
rick619
Ed_P Contributor
Posts: 8376 Joined: 06 Feb 2013, 22:12 Distribution: Cinnamon 5.01 ISO Location: Western NY, USA
vesamenu.c32 not a com32r image
Post #2 by Ed_P » 05 Apr 2022, 16:25
An interesting problem rick619. Maybe the file on the USB drive is fragmented. Rebuilding the drive or using a different USB drive might resolve the problem.
Ed_P
rick619 White ninja
Posts: 7 Joined: 07 Mar 2022, 17:11 Distribution: 5.0rc3
vesamenu.c32 not a com32r image
Post #3 by rick619 » 05 Apr 2022, 16:28
05 Apr 2022, 16:25
An interesting problem rick619. Maybe the file on the USB drive is fragmented. Rebuilding the drive or using a different USB drive might resolve the problem.
I did try that, no difference. Is there a line I can add to startup to use the GRAPHICAL option so I don’t have to type it every time? I tried adding this in the default startup area, but it still prompts with the message.
rick619
Ed_P Contributor
Posts: 8376 Joined: 06 Feb 2013, 22:12 Distribution: Cinnamon 5.01 ISO Location: Western NY, USA
vesamenu.c32 not a com32r image
Post #4 by Ed_P » 05 Apr 2022, 16:55
So you are saying when you boot you’re ending up at a terminal screen and not getting to the boot menu? And your entering GRAPHICAL without signing on? What does a ls -l command show for the file? This is what I have.
/boot/syslinux$ ls -l vesa* -rw-r--r-- 1 root root 26684 May 9 2020 vesamenu.c32Ed_P
rick619 White ninja
Posts: 7 Joined: 07 Mar 2022, 17:11 Distribution: 5.0rc3
vesamenu.c32 not a com32r image
Post #5 by rick619 » 05 Apr 2022, 17:13
05 Apr 2022, 16:55
So you are saying when you boot you’re ending up at a terminal screen and not getting to the boot menu? And your entering GRAPHICAL without signing on? What does a ls -l command show for the file? This is what I have.
/boot/syslinux$ ls -l vesa* -rw-r--r-- 1 root root 26684 May 9 2020 vesamenu.c32Correct, I’ve never seen a boot menu. Just the prompt where you can enter cheat codes. I am typing GRAPHICAL before sign in. I’ve tried the copy2ram option, but then it doesn’t save my changes.
I’ll try the above and post results.
rick619
rick619 White ninja
Posts: 7 Joined: 07 Mar 2022, 17:11 Distribution: 5.0rc3
vesamenu.c32 not a com32r image
Post #6 by rick619 » 06 Apr 2022, 14:52
So here’s a picture of what it’s doing. It’s stops at the boot prompt and displays this message every few seconds. I can then type GRAPHICAL and it will start.
I did try it on one laptop and it would just get a ‘kernel not found’ error.
Tried another laptop:
If I boot to UEFI and select the drive, I just get a black screen.
If I do the legacy boot, the photo is what happens.
EDIT: Looks like I can’t attach pictures.
It will show
line 1: boot:
line2: vesamenu.c32: not a COM32R image
This will repeat until you type GRAPHICAL
rick619
Ed_P Contributor
Posts: 8376 Joined: 06 Feb 2013, 22:12 Distribution: Cinnamon 5.01 ISO Location: Western NY, USA
vesamenu.c32 not a com32r image
Post #7 by Ed_P » 06 Apr 2022, 17:23
To post pictures upload them to a free image server then post a link to the images. I prefer postimage.org but there are others.
It sounds like your boot problems are more than just the vesamenu problem. What is the size and format of your USB drive and how did you install Porteus to it? Did you follow the steps in the ISO’s USB_INSTALLATION.txt file? How are you booting the drive in the various laptops, machine ESP/BIOS selection or Grub2 menus? Did you do an ls -l on the vesamenu.c32 file? And can you do one of the USB drive?
Ed_P
rick619 White ninja
Posts: 7 Joined: 07 Mar 2022, 17:11 Distribution: 5.0rc3
vesamenu.c32 not a com32r image
Post #8 by rick619 » 06 Apr 2022, 18:43
The USB drive is 32GB and is currently formatted with NTFS.
I extracted the ISO to it and ran \boot\Porteus-installer-for-Windows.exe
Looking at the USB installation file, looks like I will need to re-do the USB drive and follow the EFI instructions, make sure the first partition is FAT32 first. I’ll give that a shot and try it again.
rick619
Ed_P Contributor
Posts: 8376 Joined: 06 Feb 2013, 22:12 Distribution: Cinnamon 5.01 ISO Location: Western NY, USA
vesamenu.c32 not a com32r image
Post #9 by Ed_P » 06 Apr 2022, 19:53
06 Apr 2022, 18:43
The USB drive is 32GB and is currently formatted with NTFS.
Not a good choice for a USB drive. Journeling adds overhead and wear.
06 Apr 2022, 18:43
make sure the first partition is FAT32 first.
Make the whole drive FAT32, that’s what I do for mine.
Ed_P
rick619 White ninja
Posts: 7 Joined: 07 Mar 2022, 17:11 Distribution: 5.0rc3
vesamenu.c32 not a com32r image
Post #10 by rick619 » 06 Apr 2022, 20:12
Ok, I just formatted the drive as FAT32 and it did get the boot menu and booted right up! Appears to be working well. I’ll mess with it more later.
Thanks for your help!
rick619
Rava Contributor
Posts: 5419 Joined: 11 Jan 2011, 02:46 Distribution: XFCE 5.01 x86_64 + 4.0 i586 Location: Forests of Germany
vesamenu.c32 not a com32r image
Post #11 by Rava » 07 Apr 2022, 22:34
06 Apr 2022, 19:53
Make the whole drive FAT32, that’s what I do for mine.
Or create a FAT32 as 1st partition and a small 2nd partition as ext2 (without journaling!) as 2nd, then you can use the UUID cheatcodes and have a rootcopy folder.
Or just use that partition for Linux files, because Windóws is unable to see any partitions on a USB thumbdrive that is not the 1st partition. (That is only valid for USB thumbdrives, Windoze can see all partitions on USB harddrives)
Since I have a 2GB SD card and no real use for such a small SD card, I formatted it as ext2 and use it as my USB boot drive (using a quality USB-cardreader, booting directly using the notebook’s own SD card slot not works)
root@porteus:~# fdisk -l /dev/sdc Disk /dev/sdc: 1.84 GiB, 1977614336 bytes, 3862528 sectors Disk model: STORAGE DEVICE Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x009000b0 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 135 3862527 3862393 1.8G 83 Linux Cheers!
Yours Rava
Rava
rick619 White ninja
Posts: 7 Joined: 07 Mar 2022, 17:11 Distribution: 5.0rc3
vesamenu.c32 not a com32r image
Post #12 by rick619 » 08 Apr 2022, 15:04
07 Apr 2022, 22:34
06 Apr 2022, 19:53
Make the whole drive FAT32, that’s what I do for mine.
Or create a FAT32 as 1st partition and a small 2nd partition as ext2 (without journaling!) as 2nd, then you can use the UUID cheatcodes and have a rootcopy folder.
Or just use that partition for Linux files, because Windóws is unable to see any partitions on a USB thumbdrive that is not the 1st partition. (That is only valid for USB thumbdrives, Windoze can see all partitions on USB harddrives)
Since I have a 2GB SD card and no real use for such a small SD card, I formatted it as ext2 and use it as my USB boot drive (using a quality USB-cardreader, booting directly using the notebook’s own SD card slot not works)
root@porteus:~# fdisk -l /dev/sdc Disk /dev/sdc: 1.84 GiB, 1977614336 bytes, 3862528 sectors Disk model: STORAGE DEVICE Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x009000b0 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 135 3862527 3862393 1.8G 83 Linux Probably going to keep it simple and have one fat32 partition. That way I can still use all the space as a thumb drive.