I tried creating a simple example of a custom refind.iso with custom refind.conf as follows, but it doesn't seem to make any difference: Copy refind-cd-0.13.3.1.iso to refind-test.iso. Edit refind-test.iso using UltraISO as follows: Change its labels to REFIND_TEST. Rename /EFI/boot/refind.conf to refind.conf.NOT. Extract a copy of /EFI/boot/refind.conf-sample and rename to refind.conf. Edit refind.conf: Set timeout = 100. Add refind.conf into /EFI/boot/. Save refind-test.iso, which creates a modified...
Sorry it's not something that can be fixed. Do you know which parts of the API are affected, so that Explorer++'s developer can try to avoid them?
At startup Explorer++ always looks for a config.xml file in the folder it is in (described here). If it finds one then its "Run in portable mode" option is automatically ticked and its settings are saved there instead of the registry. If there's no config file then ticking the portable mode option creates one. This works OK when it's in a drive that's a partition of a physical device, or the partition (NTFS) of a virtual disk (MBR) created by attaching a VHD file using Windows' Disk Management panel,...