Yes, you have dual-boot set up with both Windows and Linux installed.
Yes, you have dual-boot set up with both Windows and Linux installed.
It's odd why Manjaro keeps hiding Grub by default. Since Windows isn't available, I'm stuck using Manjaro. Need tips on making Grub recognize Windows? I've tried "sudo os-probe" and "sudo update-grub," but nothing works.
That's a whole other problem, and I don't know if there's any way around it in your situation. I don't use Windows on bare metal, but I did once install Windows on an extra partition temporarily to do a quick bit of debugging. After updating grub, it showed up in my grub menu. But the thing is, I had Windows efi files in my Arch EFI System Partition, which is why it showed up. I think it's because I installed Windows *after* Linux. To figure out what's going on, you'd need to give me the output of some commands (for the love of god use code tags for each one). I need the output of: sudo blkid cat /etc/fstab lsblk sudo find /boot/efi/ -print
Refers to existing operating systems already on the same disk. Adjusting grub.cfg manually works well compared to relying solely on automatic updates. This approach is superior because it avoids potential issues with system updates. Grub itself can be problematic, whereas systemd-boot or REFInd offer more reliable configurations.
It's interesting since I've managed multiple installations across various NVMe drives, one SATA SSD, and Grub consistently identifies all of them reliably each time. rEFind works well for me too, though it missed my Windows install while Grub succeeded, and systemd booting feels unreliable.
Interesting story about "works on my machine." But a quick search shows many exceptions. It's amusing since I've been using it for over five years across three different systems—from early EFI mobos lacking full UEFI support to the latest B550. Still, it functions perfectly with any .efi file I provide.
sudo blkd /dev/nvme0n1p1: UUID="652A-48EE" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="87db2a76-ce75-3a45-9d82-45254aa1683d" /dev/nvme0n1p2: UUID="ab979285-b46f-4939-96dc-b1c12213cd30" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f5b75c80-cd74-ba44-8c6a-2085effa3b69" /dev/sda1: LABEL="System Reserved" BLOCK_SIZE="512" UUID="DC68CB3968CB1166" TYPE="ntfs" PARTUUID="84556d8b-01" /dev/sda2: LABEL="Windows" BLOCK_SIZE="512" UUID="3E06CD4906CD033F" TYPE="ntfs" PARTUUID="84556d8b-02" /dev/sda3: BLOCK_SIZE="512" UUID="422042A420429EB3" TYPE="ntfs" PARTUUID="84556d8b-03" /dev/sdb1: LABEL="Data" BLOCK_SIZE="512" UUID="DC0A62110A61E94A" TYPE="ntfs" PARTUUID="37df4821-01" cat /etc/fstab
os-prober runs the command immediately and finishes in roughly three seconds on solid equipment.
Your Windows drive is connected to the /run/media/isxander/Windows directory.