Grub2Win Update March 26, 2026 Build 1803

[Ed P]

"Not that your Grub2Win EFI files will be upgraded to level 167."

??

[Drummer]

Hey again Ed,

"Not that your Grub2Win EFI files will be upgraded to level 167." ?

This was a typo, should have said "Note" instead of "Not".
Fixed this morning and the new level is 168.

Over the last couple of days, I have updated g2wisoboot in an attempt to detect these fragmentation errors.
g2wisoboot now provides the suggestion to defrag or move the .iso file.

Fragmentation errors are now much more common because users don't defrag SSD disks much anymore.

Note that even after I defragged the partition, I still had to move the .iso file to another directory within that partition to get it to work.

Hopefully GNU Grub will fix this fragmentation issue.

I have attached the gw2wisoboot code that works for me.
It also worked for the MX Linux user who originally posted this problem.

The $isopath variable must be set to reflect the location on your system.

Whew!,

Dave

[Ed P]

Hi Dave,

I suspected the "Not" was a typo. But it could have had a word missing: "Not included ".

Typos in comments or code ....

I don't agree $isopath variable must reflect the location on the system other than the directory. The root value should handle the drive. But if used in bootparms iso references may require the root and isopath variables.

[Drummer]

Hey again Ed,

The whole point of the $isopath variable is that the g2wisoboot function searches for the file in the $isopath variable and sets root automatically.

This greatly simplifies things for the user, since booting .iso files can be quite challenging.

They only need set the four variables, then the g2wisoboot function takes care of setting root, loopback and everything else.

Have you tried the MX Linux code I posted?

Please let me know.

Thanks,

Dave

[Ed P]

Dave,

I am aware of how g2win searches for the isopath and set root, but boot parms like from= and findiso= sometimes need the root drive in the parm's isoparm. ISO booting is complicated.

Ed

[Drummer]

Hey Ed,

Have you tried the MX Linux code I posted?

Please let me know.

Thanks,

Dave

[Ed P]

The MX code you posted is basically the same parms I always use. And even with a new fresh download the MX iso is classified as unfound.

In that I boot others isos from the same ISOs folder on the same drive I doubt the problem is a grub2 one. I suspect it's a MX bootparm ISO problem.