Skip to main content
The 2024 Developer Survey results are live! See the results
10 events
when toggle format what by license comment
Dec 24, 2021 at 22:34 comment added Валерий Заподовников grubx64.efi will not work anyway on any normal code for UEFI, since that is not correct name for the bootloader. Rename for bootx64.efi
Jun 12, 2020 at 13:48 history edited CommunityBot
Commonmark migration
Aug 12, 2019 at 10:21 comment added norbjd @Biswapriyo thanks for your help. I've just deleted the p8 (and other Arch-only partitions) and can successfully boot into Windows.
Aug 12, 2019 at 9:41 comment added Biswapriyo Becasue generally ESP (fat32) is generally different partition from Arch's root partition (ext4). You can install GRUB later to make it dualboot/chainload with Windows bootloader.
Aug 12, 2019 at 9:22 comment added norbjd @Biswapriyo Thanks. I think I understand for Windows, because there is still the ESP in p1, but what about Arch? Why deleting ESP in p8 may not affect Arch? If I delete p8, grubx64.efi will disappear. Could you elaborate please? I'd like to understand why deleting ESP in p8 may not affect Arch :)
Aug 12, 2019 at 9:15 comment added Biswapriyo From the folder structure, I think you can go without GRUB. Deleting, ESP in p8 may not affect Arch nor Windows.
Aug 12, 2019 at 8:16 comment added norbjd @Biswapriyo thanks for your comment. After deleting the partition nvme0n1p8 (and if I don't install Grub for now), should I always be able to boot into Windows? Actually, I would like to restore my system as it was when I booted it for the first time (only Windows) to be able to reinstall Arch cleanly after that.
Aug 11, 2019 at 20:11 comment added Biswapriyo My choice: I would delete the EFI in nvme0n1p8 > install GRUB in nvme0n1p1 > mount it as /boot > grub-install and grub-mkconfig can automatically detect WIndows bootloader.
Aug 11, 2019 at 20:00 review First posts
Aug 12, 2019 at 5:34
Aug 11, 2019 at 19:59 history asked norbjd CC BY-SA 4.0