Hi, I can see the Windows 10 boot option when I startup, but when I try to boot, it shows the spinner several times and it starts Dell OS Recovery (I am using an XPS 15 laptop). After following the recovery procedure Windows still won’t boot. I’ve checked several posts in the forum but they’re not helpful.
I’ve tried that but it doesn’t help. Below is the output:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
Where does btrfs come into the picture?
How did you install?
Where is your boot device?
Do you share boot device with windows?
Did you erase the windows boot device and replace it with grub?
From what you have provided, it seems you have removed the windows boot partition and are now relying 100% on grub, at least I can’t see any on your system.
If windows is your main os I highly recomend you turning to a windows support forum.
If you do one more lsblk but without the -f and give the output maybe we can see if your windows data is still there at least (it looks like it but just to be sure).
Usually windows is pretty strict with creating backup points, you just need the tools to restore your boot drive so you probably don’t have to worry too much.
There is also something very strange going on with your manjaro install since your update-grub mentions btrfs.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 476.9G 0 disk
├─nvme0n1p1 259:1 0 500M 0 part /boot/efi
├─nvme0n1p2 259:2 0 128M 0 part
├─nvme0n1p3 259:3 0 236.4G 0 part
├─nvme0n1p4 259:4 0 837M 0 part
├─nvme0n1p5 259:5 0 128.7G 0 part /mnt/data
├─nvme0n1p6 259:6 0 460M 0 part
├─nvme0n1p7 259:7 0 11.2G 0 part
├─nvme0n1p8 259:8 0 1.1G 0 part
└─nvme0n1p9 259:9 0 97.7G 0 part /
For the installation process, first I shrink a new space in Windows, then I used the Manjaro image and used Rufus to get it on a USB. Then I boot from the USB and followed the installation guide. I chose replace partition with Manjaro and selected the allocated space. I thinks that’s pretty much it from what I remembered.
If this file starts DELL Recovery, then there must be some uncommon boot method which is not default. Probably secure boot was enabled in the UEFI and now Windows refuse to boot without it?
If someone with DELL can chime in it would be very nice. I can only give you the default ESP structure of Lenovo with Win 11, but Dell might be different.
systemd-boot not installed in ESP.
No default/fallback boot loader installed in ESP.
System:
Firmware: n/a (n/a)
Firmware Arch: x64
Secure Boot: disabled (disabled)
TPM2 Support: yes
Boot into FW: supported
Current Boot Loader:
Product: n/a
Features: ✗ Boot counting
✗ Menu timeout control
✗ One-shot menu timeout control
✗ Default entry control
✗ One-shot entry control
✗ Support for XBOOTLDR partition
✗ Support for passing random seed to OS
✗ Load drop-in drivers
✗ Support Type #1 sort-key field
✗ Support @saved pseudo-entry
✗ Support Type #1 devicetree field
✗ Boot loader sets ESP information
ESP: n/a
File: └─n/a
Random Seed:
System Token: not set
Exists: no
Available Boot Loaders on ESP:
ESP: /boot/efi (/dev/disk/by-partuuid/c8e8573e-d0fc-4cc4-a459-6199ab8dc8a8)
Boot Loaders Listed in EFI Variables:
Title: Manjaro
ID: 0x0002
Status: active, boot-order
Partition: /dev/disk/by-partuuid/c8e8573e-d0fc-4cc4-a459-6199ab8dc8a8
File: └─/EFI/Manjaro/grubx64.efi
Title: Windows Boot Manager
ID: 0x0000
Status: active, boot-order
Partition: /dev/disk/by-partuuid/c8e8573e-d0fc-4cc4-a459-6199ab8dc8a8
File: └─/EFI/Microsoft/Boot/bootmgfw.efi
Boot Loader Entries:
$BOOT: /boot/efi (/dev/disk/by-partuuid/c8e8573e-d0fc-4cc4-a459-6199ab8dc8a8)
token: manjaro
0 entries, no entry could be determined as default.
Except the somewhat dell customized Windows with 100 languages, looks pretty normal to me. Maybe you should look it the other way around and try to reinstall restore the win boot loader from windows (although it looks ok to me). That will most probably delete the manjaro entry, so be sure to have a manjaro live usb and see this guide
After that again update-grub and it should detect win. If it does not work again, than is something dell specific and you will have to chainload manjaro grub on the windows bootloader with bcdedit or similar tool.
Oh, and just one more thing, important: how exactly are you (not) booting into Windows (recovery)? Do you choose it from grub menu, or do you hit a key in the bios before you see grub? There might be a difference! Try both just to be sure.
Thanks! I just tried the other way (hit a key before grub), but its still the same. After Windows failed to boot it restarted and showed the Manjaro grub menu again.
Thanks for the advice tho.
Like I said yesterday, if windows is your MAIN os, go to a windows forum IMMEDIATELY and explain what you did and ask for support to restore your boot.
I suspect there is some kind of recovery media microsoft provides that can help.
I also suspect you might have disabled secure boot in bios, without first disabling it in windows so you now have to fix so your windows accepts the unsecure boot procedure from bios.
If I were you, I would remove Manjaro from the system, fix windows and then reinstall manjaro keeping the boot partitions separate from each other (so you can select what boot partition you want to use from bios instead).
Grub should still pick up and let you boot to windows from grub.
Well removing manjaro obviously won’t solve the problem that the uefi cannot boot the windows loader which is somehow broken.
What is actually a good idea to turn secureboot on and try booting with a key. Generally windows works without secure boot, but dell may have changed it as a requirement.
If that works there are some guides on the arch wiki how to sign manjaro/arch with oun key but it is a bit of uncharted territory. Or just toggle it every time. Or find how to disable it in Windows.
Nobody said that it would. But it would definitely make the windows fix easier when the question “can we wipe the whole boot partition to fix this” comes.
And it would also be way cleaner to reinstall with separate boot partitions for windows and linux.