Dear Maintainer @idrassi, The details are on this Github issue: https://github.com/chenall/grub4dos/issues/441 The Veracrypt Rescue Disk ISO can boot from G4D. However the password entered is always incorrect and fails to decrypt the system. I think for some reasons, despite G4D remapping disk order, the Veracrypt Rescue Disk wouldn't read the disk order changes and will still try to decrypt the first disk that the BIOS did boot in which would be the disk holding the G4D partition hence never decrypting...
Dear Maintainer @idrassi, The details are on this Github issue: https://github.com/chenall/grub4dos/issues/441 The Veracrypt Rescue Disk ISO can boot from G4D. However the password entered is always incorrect and fails to decrypt the system. I think for some reasons, despite G4D remapping disk order, the Veracrypt Rescue Disk wouldn't read the disk order changes and will still try to decrypt the first disk that the BIOS did boot in which would be the disk holding the G4D partition hence never decrypting...
Dear Maintainer @idrassi, The details are on this Github issue: https://github.com/chenall/grub4dos/issues/441 The Veracrypt Rescue Disk ISO can boot from G4D. However the password entered is always incorrect and fails to decrypt the system. I think for some reasons, despite G4D remapping disk order, the Veracrypt Rescue Disk wouldn't read the disk order changes and will still try to decrypt the first disk that the BIOS did boot in which would be the disk holding the G4D partition hence never decrypting...