I'm using dual boot Windows 11 and Fyde OS. On my bootloader screen there are 3 other boot options which are not any OS, they are EFI and recovery partition. I want only Windows and Fyde OS boot logo on my bootloader screen. The boot manager is rEFInd boot manager which got installed automatically with Fyde OS. I also have Linux environment installed on Fyde OS.

I don't necessarily need it to be GRUB, I just want *a* bootloader. I've done a lot of troubleshooting already, but here's what I found. The last thing before the installer dies on me, it says:

mint grub-installer: error: Running 'grub-install --force --target x86_64-efi "/dev/sda"' failed.
mint rtkit-daemon: Supervising 11 threads of 8 processes of 1 users.
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:20: Warning: Source ID 6749 was not found when attempting to remove it.
    GLib.source_remove(self.timeout_id)
Unable to install GRUB in /dev/sda/
Executing 'grub-install /dev/sda' failed. This is a fatal error.

Now keep in mind, all three partitions of Linux are on sdb6, sdb5, and sdb7 (extended sdb3) respectively. At no point did I ever specify the system to touch sda whatsoever, so I don't know why it's trying to install GRUB or anything there. So I tried a couple of things. Mounting my EFI partition and attempting to chroot it yields this error:

chroot: failed to run command ‘/bin/bash’: No such file or directory

Initially, GRUB rescue gave me this back:

grub rescue> set prefix=(hd0,msdos8)/boot/grub
grub rescue> insmod normal
error: file '/boot/grub/i386-pc/normal.mod' not found.
grub rescue> normal
Unknown command 'normal'.

After performing cp -r on the directory from lib, it gives me a different, equally unhelpful error:

grub rescue> set boot=(hd0,msdos7)
grub rescue> set prefix=(hd0,msdos7)/boot/grub)
grub rescue> insmod normal
error: unknown filesystem.

A buddy of mine suggested to just unplug what is currently sda, and see what it tries to do then (since, again, I never asked it to install anything to that drive). No clue if it'll work or not, but I'm trying everything, and I appreciate any further ideas.

I'm booting from EFI using the awesome rEFInd bootloader. I've so far had to configure boot myself by manually copying over my EFI-compatible linux boot image to my EFI partition and writing a configuration file to define a rEFInd menu entry and link to the specific kernel image on the EFI volume. GRUB, on the other hand, adds new kernel versions as they're installed and I always boot into the new kernel on next boot. It accomplishes this via the update-grub script, I believe. Is there another script I can call into to automatically deploy new kernel images to my EFI partition and ensure they're available on next boot? I'd like to automate this process as much as possible so I'm always getting the latest kernel security updates.

I am trying to get my acs-patched Antergos kernel to boot from rEFInd. It was detected automatically by rEFInd but it did not boot properly. I kept on getting ERROR: device 'UUID=...' not found. Skipping fsck., so to bypass this, and have the kernel parameters, I tried a custom menuentry, which fails. No information at all, only a black screen. Additionally, I would like to get the rEFInd-minimal theme working. Normal Antergos boots perfectly fine, after I manually select it from rEFInd submenu and XUbuntu still works fine. A note about the theme, the custom Antergos icon works, but the banner does not, nor overriding icons for XUbuntu or normal Antergos. rEFInd is setup on a separate partition like so: **/dev/sda**: | EFI BOOT | Empty Partition | SWAP | XUbuntu | Antergos | Free Space | | 1.0 GB | 1.0 GB | 8.6 GB | 21 GB | 40 GB | 185 GB | **EFI BOOT**: . └── EFI ├── BOOT │   ├── bootx64.efi │   ├── drivers_x64 │   ├── icons │   ├── keys │   └── refind.conf ├── refind │   ├── rEFInd-minimal │   └── refind-theme-regular └── tools **refind.conf**: timeout 20 menuentry "Antergos IOMMU" { icon EFI/refind/rEFInd-minimal/icons/os_antergos.png volume Antergos loader /boot/vmlinuz-linux-vfio initrd /boot/initramfs-linux-vfio.img options "root=/dev/sda5 rw quiet iommu=pt amd_iommu=on" } hideui singleuser,hints,arrows,badges icons_dir EFI/refind/rEFInd-minimal/icons banner EFI/refind/rEFInd-minimal/background.png banner_scale fillscreen selection_big EFI/refind/rEFInd-minimal/selection_big.png selection_small EFI/refind/rEFInd-minimal/selection_small.png showtools shutdown ***/dev/sda5*/boot/**: . ├── grub │   ├── fonts │   ├── grub.cfg │   ├── grub.cfg.example │   ├── grubenv │   ├── i386-pc │   ├── locale │   └── themes ├── initramfs-linux-fallback.img ├── initramfs-linux.img ├── initramfs-linux-vfio-fallback.img ├── initramfs-linux-vfio.img ├── intel-ucode.img ├── vmlinuz-linux └── vmlinuz-linux-vfio

Okay so a little backstory: I've been trying to install Linux as a dual boot (with Windows) since yesterday, here's how it went down : - installed Debian, worked well but I had to boot in nomodeset for some reason and it hardblocked me in 4:3 resolution - a friend told me Debian was a weird distro choice so I mehed and tried to install MX instead : I still had the nomodeset problem, but it also killed my grub (weird normal error preventing grub from launching) - since the distro had the same problem, I tried with a third one (EndeavourOS) which (yay) didn't have the nomodeset problem. However, the Grub was still broken, so impossible to launch on-disk. I tried fixing the Grub for a few hours, gave up and decided to instead switch to rEFInd. I installed it with pacman, ran the refind-install (got an warning saying I wasn't in EFI mod, which was normal I guess since I was working from my USB boot) and I also had to rename a file to match my AMD gear. BUT when I restarted, I still fell on the grub error page. So I relaunched from the USB, removed Grub with pacman, and deleted everything with "grub" in the name on my EFI partition (there was a grub folder I wiped from /boot/, and also some grubx64 files in /efi/). I thought that would force switch to rEFInd but instead it just broke the launch totally, and now the only option I have in the BIOS is Windows. I'm still rather new with Linux so please detail your solution a little. What I know how to do is : - Launch Endeavour from my USB and mount the installed one there - Use pacman to install packages - basic file management -------------- EDIT: Just completely wiped my hard drive and reinstalled Windows then Linux. I still get the exact same grub error : error: verification requested but nobody cares: (hd0, gpt5) /boot/grub/x86_64-efi/normal.mod

In GRUB2, you can use [grub-reboot](https://wiki.debian.org/GrubReboot) to temporarily set the default boot option to another OS for a single boot, allowing you to switch OSes without having to stand by the computer, wait for POST, and press keys. Is there an equivalent operation for rEFInd so I can remotely reboot my PC into Windows without locking that as the default until I get home?

I've just installed Arch Linux alongside Windows, using the rEFInd boot manager to choose between them. Everything is working perfectly, except for the *tools menu located below the main OS icons*. I would like the tools menu to only display the "shutdown" option, and to do that I added showtools shutdown to rEFInd's configuration file (/efi/EFI/refind/refind.conf). Doing that resulted in this . Not what I wanted. After some more investigation, I've found that when showtools is specified with no options, this happens; it appears as if **four extra tools** are being appended after whatever I want. When I commented out showtools completely, I got this . This output is the default which is described in refind.conf. It's the only time I've gotten what I've "asked for" I've tried all sorts of combinations of showtools, hideui, and including an external theme's config. Everything is working as expected other than these **four tools** that just won't go away. Thanks in advance for all the help!

Upon booting and choosing rEFInd, I get a blank screen as shown in [this post](https://sourceforge.net/p/refind/discussion/general/thread/bcf53133ab/) . My filesystem is like so: $ mount /dev/mapper/luks-71740d10-cf57-4b82-9311-aa584acaa81e on / type btrfs (rw,relatime,compress=lzo,ssd,space_cache,subvolid=256,subvol=/arch) /dev/nvme1n1p2 on /boot type ext4 (rw,relatime) /dev/nvme1n1p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro) The contents of my boot partition is (omitting refind icons directory for brevity): $ ls -lR /boot/ /boot/: total 159116 drwxr-xr-x 3 root root 4096 Dec 31 1969 efi -rw-r--r-- 1 root root 85725131 Nov 7 13:32 initramfs-linux-fallback.img -rw-r--r-- 1 root root 62696900 Nov 7 13:32 initramfs-linux.img -rw-r--r-- 1 root root 4769792 Jun 8 13:31 intel-ucode.img -rw-r--r-- 1 root root 9735104 Nov 5 13:39 vmlinuz-linux /boot/efi: total 4 drwxr-xr-x 4 root root 4096 Nov 7 14:38 EFI /boot/efi/EFI: total 8 drwxr-xr-x 6 root root 4096 Nov 7 14:38 refind drwxr-xr-x 2 root root 4096 Apr 19 2021 tools /boot/efi/EFI/refind: total 412 drwxr-xr-x 2 root root 4096 Apr 19 2021 drivers_x64 drwxr-xr-x 3 root root 8192 Nov 7 13:25 icons drwxr-xr-x 2 root root 4096 Apr 19 2021 keys drwxr-xr-x 2 root root 4096 Nov 7 14:38 vars -rwxr-xr-x 1 root root 140 Nov 7 13:25 BOOT.CSV -rwxr-xr-x 1 root root 37839 Nov 7 14:39 refind.conf -rwxr-xr-x 1 root root 34513 Nov 7 13:25 refind.conf-sample -rwxr-xr-x 1 root root 317712 Nov 7 13:25 refind_x64.efi /boot/efi/EFI/refind/drivers_x64: total 72 -rwxr-xr-x 1 root root 69776 Nov 7 13:27 ext4_x64.efi My configuration is as follows: menuentry "arch" { icon /EFI/refind/icons/os_arch.png volume 3c3b698a-8212-324b-9b63-4dc3a7a98aee loader /vmlinuz-linux initrd /initramfs-linux.img options "luks.uuid=71740d10-cf57-4b82-9311-aa584acaa81e root=UUID=15773c68-a4e5-49b5-8071-f390750b7162 rootflags=compress=lzo,ssd,subvol=arch ipv6.disable_ipv6=1 add_efi_memmap rw" } menuentry "windows" { icon /EFI/refind/icons/os_win.png volume 13aa9955-4538-40ac-b674-006c334b5088 loader \EFI\Microsoft\Boot\bootmgfw.efi } My devices are as follow: $ sudo blkid /dev/nvme0n1p5: LABEL="Windows RE Tools" BLOCK_SIZE="512" UUID="08C4E6C5C4E6B45A" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="4eced110-9723-4dde-955c-b0ab8576869b" /dev/nvme0n1p3: TYPE="BitLocker" PARTLABEL="Basic data partition" PARTUUID="a358833d-f07c-45f8-9119-3592577bfd23" /dev/nvme0n1p1: LABEL="SYSTEM" UUID="4CE7-C215" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="13aa9955-4538-40ac-b674-006c334b5088" /dev/nvme0n1p4: BLOCK_SIZE="512" UUID="D2063641063626BF" TYPE="ntfs" PARTUUID="32a62eef-7764-4de9-b230-e582a2fba9ef" /dev/mapper/luks-71740d10-cf57-4b82-9311-aa584acaa81e: UUID="15773c68-a4e5-49b5-8071-f390750b7162" UUID_SUB="b79765d9-5a84-4327-b8e0-b4a7c27107a8" BLOCK_SIZE="4096" TYPE="btrfs" /dev/nvme1n1p2: UUID="db6871f3-f5d5-4d46-965e-7bbd9d335d34" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="3c3b698a-8212-324b-9b63-4dc3a7a98aee" /dev/nvme1n1p3: UUID="71740d10-cf57-4b82-9311-aa584acaa81e" TYPE="crypto_LUKS" PARTUUID="004162c0-d9e6-5043-8427-630a0efce107" /dev/nvme1n1p1: UUID="0298-8CEA" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="82f72318-1bba-2d4b-936d-41142e979d9f" /dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="2d6499be-a167-4920-93d6-7a15a8a82ee6" There are no actual errors reported, rEFInd just boots to this blanks screen and stays there indefinitely. Pressing enter (in case this is a graphical problem and behind the scenes everything is as it should be) does nothing. Using refind-install from a live Arch USB disc also does not fix this, creating an improper refind_linux.conf. I know my refind.conf to be correct as it has previously worked.

Moving right along with rEFInd, one issue left: When I boot two of the three automatically created choices, the boot hangs for two minutes as the kernel looks for a resume device. BTW, to add to the mystery, one of the automatic boot options has no issue with 'resume' -- it seems to find the resume/swap partition by itself.

Please **do not move** this question to SuperUser. My question relates to EFI partition manipulation, which is not inherent to Windows. ## Background ## I ran into an issue with UEFI and OS Versions, and I would like some help. By no means is this an advertisement for my OEM, or a preference for OS'es, but I'm using them to give a thorough description of the issue. Recently, I found Xidax , an OEM builder for gaming systems. I also use the system they built for Linux and OS experimentation, besides the gaming. I used to build my own, but age and disability have severely hampered my hand strength and my patience, which is where this issue starts. ## Issue ## My System is built with a MSI motherboard supporting UEFI, SecureBoot, etc. (fairly recently built). I've replaced the stock MS Windows UEFI loader with rEFInd . This EFI boot manager allows me to boot the following OS'es, all on Different Drives: 1. Windows 11 M2 - 1TB (also where the EFI partition is) 2. Gentoo Linux 3. FreeBSD 12 or 13 (which I removed because I hadn't touched or updated it in ages) Having removed #3, I now have an empty drive (8TB in size), and decided to try something I'd never done. I have installed Windows 11 on the empty 8TB in hopes of "converting it" into the current AtlasOS . The Windows Installer correctly found the EFI Partition on my M2 Drive and added the Entry to the Windows Loader(WinLoad.efi). I now have a boot menu based on winloader(the white and blue screen) with 2 choices for Widows 11. ## Side By Side versions of Linux ## Forgetting for a moment that this is Windows and remembering I cannot disconnect the First Install to trick the second install into building an EFI partition (due to disability) on the second drive, and using the following scenario: 1. Replace the Word Windows above with a Linux Distribution - For the sake of this example I'll choose Ubuntu 2. Install Ubuntu grub version X copy 1 into the only EFI partition 3. Install Ubuntu grub version X copy 2 into the only EFI partition Now realizing that I've clobbered the First Installs grub with the second because there is only one ubuntu folder in the EFI partition, I'm stuck as I would like to access both copies independently of each other. For an example of the type of fix I need to implement in a different way, see In rEFInd, need 2 different OS icons for 2 instances of same OS (Ubuntu-MATE) . To do this for Windows/rEFInd, I started with: Booting Multiple Windows Installations from a Third-Party Boot Manager . If you look at the "7 Getting into Windows Went..." steps that is exactly what I have to do to get to either version until I get this fixed. I'm trying to do this with only 1 EFI Partition, before I use the second answer in Installing rEFInd on Dual Boot Windows 10 Machine (See why I don't want it moved now?). I'd rather not have EFI partitions all over my drives if I can help it. ## Attempted Fix ## 1. From a Windows Command Prompt, issued mountvol b: /s. - That worked, I did that the first time I installed rEFInd without access to my Gentoo Install 2. mkdir b:\EFI\Win10 and mkdir b:\EFI\AtlasOS. - Worked again, but darn their empty and I sure don't want to screw up my EFI partition. 3. First xcopy /s b:\EFI\Microsoft\Boot b:\EFI\win10 - Well *shoot*, that failed with Sharing Violation. What?!?! Wait, didn't I run the prompt as Administrator, and isn't my account in the Administrators Group... checking... yes Oh wait Microsoft thinks I'm stupid for wanting to alter the EFI manually on a machine that I OWN. But wait, I can edit it in my Gentoo install so: 4. Rebooted into Gentoo 5. Mounted boot 6. Opened gparted because I never can remember the /dev name for the EFI partition 7. Mounted the EFI partition to /boot/efi 8. Cded to /boot/efi/EFI/Microsoft/Boot 9. Issued cp -xa . /boot/EFI/Win10 and the same for AtlasOS 10. Reinstalled grub as I had to boot the kernel directly from rEFInd. Now I'm finally to the step to alter the BCD, whew back to Windows. By that time it was 12:30AM last night, and I need sleep, so I decided to come here and ask for advice/help. ## Questions ## As I said, I'd rather have 1 EFI partition so I'd like to modify that Fix a bit by asking the following: 1. What are the barebones essentials that need to be in /boot/efi/EFI/{Win10,AltlasOS} in order for the boot to occur cleanly? - cp -xa did in fact replicate xcopy but when I rebooted to start on the BCD I noticed all kinds of files etc. listed on rEFInd's menu. I don't want to have to hide them all when there are possibly hundreds. 2. Is there an easier way to split the entries up than the approach I've chosen? 3. How do I treat an update to the EFI partition in the Future, i.e., will the manual adds need to be readded if Windows Update decides to push an update to the EFI/BCD?

I have a 2008 iMac that has MacOS and Linux Mint installed. When searching for a solution to a problem I have seen it stated that I need to boot in 'legacy' mode. What does this mean? Does it refer to old PC BIOS? Such a BIOS never existed on this iMac, it was always EFI. I installed using the Mint installer as far as I remember and I think it is using EFI. If I run efibootmgr I get the following: $ efibootmgr -v BootCurrent: 0000 Timeout: 5 seconds BootOrder: 0000 Boot0000* ubuntu HD(1,GPT,04202405-8589-4b15-b2c7-f72a95053a68,0x28,0x64000)/File(\EFI\ubuntu\shimx64.efi) Boot0081* Mac OS X PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(2,GPT,5f1185c2-ae3c-4590-99ba-c57db72f5442,0x64028,0xcbee240) BootFFFF* PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(2,GPT,5f1185c2-ae3c-4590-99ba-c57db72f5442,0x64028,0x79fc5c8)/File(\System\Library\CoreServices\boot.efi) I've seen references to rEFInd being used. This package is not installed. Can I just install that on the running system or do I need a clean installation? I'd prefer to keep the ability to run MacOS, though I don't normally need it. The problem I'm trying to resolve is waking the iMac/Mint from suspend, as described here: https://forums.linuxmint.com/viewtopic.php?t=335072

So, I'm getting this error when using rEFInd and trying to load Android. Here is a picture of the error as displayed. The Android entry in /boot/efi/EFI/refind/refind.conf is as follows: menuentry Android { volume cc24a13b-a535-4e82-b250-ed69614c6b86 icon os_android.png loader cm-x86-14.1-r5/kernel initrd cm-x86-14.1-r5/initrd.img options "BOOT_IMAGE=/cm-x86-14.1-r5/kernel root=/dev/ram0 androidboot.selinux=permissive" } Things to note: 1. Android is installed into a folder on the root of the Linux partition, which is formatted as BTRFS. 2. The distro Linux is installed on is Pop! OS by System76. 3. Android was installed using Alien following the RPM instructions here . 4. The laptop in question is from Razer and has an Nvidia GeForce RTX 2080 Max-Q, so some settings may be required to allow it to boot with Nvidia Graphics. 5. When installing using Alien, there was an error related to not being able to add it to GRUB's custom.conf file, since I don't have GRUB installed.

I'm trying to install Linux Mint on my 2010 21.5" iMac. I managed to install it after booting from the usb drive with the nomodeset option, but I haven't been able to boot from the actual install so far. The typical recommendation I found from googling is: on the boot selector screen (I'm using rEFInd) hold Shift and select grub options, then press e to edit the boot options and add nomodeset after where it says quiet splash. However, this does not work for me - I still get a black screen when it tries to boot up.

I recently dual booted Arch and Windows and I've been playing around with Plymouth to try to make the boot up process more aesthetic and I found a really nice theme but rEFInd's boot up text ruins it by appearing before the theme loads and then after it before loading my lightdm login. I already took a look at this question and I followed the answer and it works. The text no longer appears. However, instead there's a weird blackish screen that replaces it and my theme is still ruined. Is there anyway to remove this and just show my theme? The plymouth theme is dark-arch if that makes a difference. I can post any needed config files or anything else too, don't know what's needed though. Thanks for any help!

If someone has any information about Windows update actions, please share. I'm currently running Pop!_OS 22.04 (and other several temporary distros) and booting to it through rEFInd. So, I heard a lot of comments about Windows breaking GRUB, but I don't know what that means exactly. Does it wipe EFI partition? Does it remove non-Windows stuff from EFI partition? Maybe something else? I know for a fact that rEFInd basically have its own folder in EFI partition, and it automatically detects installed OSes and you can create custom boot entries in the same folder. This means that rEFInd is more clear than GRUB (I remember GRUB also stores some files in /boot/ directory of a distro). But I think it doesn't solve the "Windows update broke my GRUB (rEFInd)" problem. Or does it? As rEFInd is a standalone folder (in practice), it will be probably impossible to boot into Pop with Windows (if I had one) removing the folder of the bootloader (without recreating rEFInd via live CD). P.S. I'm just curious about this, and I don't have any issues (because I no longer have Windows installed — and that's a huge relief).

I formatted an old MacBook and installed: 1. MacOS El Capitan 2. rEFInd boot manager 3. Linux Mint 17.2 Rafaela MATE with codecs (64-bit) At first both OSs installed. When rebooting it still loads to rEFInd boot manager, but after that, restarting again, it will either go straight to Linux Mint or I have to press the Option (Alt) key to show macOS and Recovery disk 2 drives only. How do I turn on rEFInd boot manager again?

I have installed PopOS on a number of laptops but this one is just giving me fits. Current patient: Toshiba E45t-B4106 Intel Core I5-5200U 8GB Ram, 1TB HDD Windows 10 now adding Pop_OS 22.04 LTS I have come across the new 1GB requirement for a /boot partition and just made a new partition in free space and it just works. Generally I add REFIND to handle the dual boot. So this one - REFIND is complaining that: The ESP doesn't seem to be mounted"... Must be VFAT - Aborting... I notice now that the new installer is making the new boot partition EXT4... Is that part of the problem? There is no way to convince it to make that partition FAT32. Grub OS prober is not locating Windows. So even keeping GRUB doesn't really solve my problem. Inside Bios settings - there is no setting to set which partition I want the boot from - so now stuck not able to get into Windows... I think this has to do with the current patient being MBR setup vs GPT? But now I am typing way over my head... Really not sure what to search for or try at this point too. Any thoughts, tips or solutions are appreciated.

I’ve installed Debian using a bootable usb 3 times now trying to make this work. The issue is that instead of booting into Debian the computer boots into a grub command line. When I use the command boot it says to load a kernel first. I have no idea how to do that. After 2 days of no luck with grub, I installed rEFInd, which I hoped would give me the option to boot into Debian. Not the case. There are 2 options that look promising, one with the Debian icon, and one with the Linux icon, but they both point towards a file called grubx64.efi which boots into the command line. I’m extremely confused because every time the installer said it was successful but it also boots into grub still. That didn’t happen in any tutorials I watched. I’ve looked for any and every fix online and tried at least 20 thing but they didn’t help. I feel like I missed a step between the finished installation and when I expected Debian to boot but there isn’t a step between those in anything I’ve seen. rEFInd:

I am new to Linux and very confused. I need to change the i915.enable_psr and i915.enable_guc parameters or modules or whatever they are called to prevent my laptop from being in a constant state of agony, but I only recently found out that pop!_os instead of grub uses systemd or refind to boot or something and I genuinely can't find the alternative to the GRUB_CMDLINE_LINUX_DEFAULT from grub, can anyone help me? And could anyone be kind enough to tell me what the difference between systemd or refind is? Or one better, what do they even mean? P.S. In case it matters this whole ordeal started because of this: i915 Atomic update failure on pipe A And no, moving to a different os didn't solve the problem. Sincerely, One hell of a confused Linux noob.

Few weeks ago installed my first Linux distro, Mint and managed to set-up rEFInd with it. Then I decided to switch to Pop_OS. I formatted the partition that I had both Mint and rEFInd on and installed Pop instead. Since rEFInd got unistalled, I installed it back using

apt install refind

, the same way I did when I was on Mint. But then I got this problem. After a successful install, **I rebooted to rEFInd to find that it is showing rEFind_x64.efi as a possible boot option.**  **Once I hit enter, it booted into my old, customized rEFInd that was stored in the deleted partition along with mint.**  When I tried to take a screenshot in rEFInd suing F10 I got this error.  I can boot Windows from both, but Pop only works in the second (the old one that should not exist). I already tried unistalling and reinstalling, didn't help. **Does anyone know where that rEFind_x64.efi is stored? Any help is really appreciated :)!**