View Full Version : Problems Dual Booting Kali Linux with Windows 10 (No signs of GRUB bootloader)
Hi all!
I have been trying to dual boot any Kali Linux version with windows 10 which is my actual OS. The problem is that during the installation of Kali Linux, when installing GRUB it should detect that there is another OS and ask if I would like to install GRUB. This message does not appear. After this, I have tried booting into Kali-Live and re-installing GRUB from there but even if it does not report any error it still boots directly to Windows. I also checked going to the Boot Menu but only Windows 10 option appears.
Thank a lot in advance for the help!
Installer doesn't care if there is another OS installed. It automatically proceeds to install grub. Is there an option Boot From EFI in your Boot Menu Options?
You can follow this thread to reinstall grub: https://forums.kali.org/showthread.php?36601-UEFI-How-to-repair-kali-linux-grub-dual-boot-with-Windows-10
Hi again! Unfortunately, I do not have any Boot From EFI option in my Boot Menu. Also, the way I have re-installed GRUB was following those commands you posted. I have some kind of messages and some warnings. I will copy paste all the procedure below so you can see all the installation procedure
First, gave me this error
root@kali:~# mkdir /mnt/boot/efi
mkdir: cannot create directory ‘/mnt/boot/efi’: File exists
Then the same here
root@kali:~# mkdir /mnt/hostrun
mkdir: cannot create directory ‘/mnt/hostrun’: File exists
Same here
root@kali:/# mkdir /run/lvm
mkdir: cannot create directory ‘/run/lvm’: File exists
Then says this, which looks good
root@kali:/# grub-install /dev/sdb
Installing for x86_64-efi platform.
Installation finished. No error reported.
Then all these warnings
root@kali:/# update-grub
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.13.0-kali1-amd64
Found initrd image: /boot/initrd.img-4.13.0-kali1-amd64
WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb4 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb5 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb6 not initialized in udev database even after waiting 10000000 microseconds.
Adding boot menu entry for EFI firmware configuration
done
And that is
Thanks
Noo it didn't. I don't know what more I can do...
Your output says Adding boot menu entry for EFI firmware configuration so it was supposed to be added in your Boot Menu options. Have you retried the solution and checked the boot menu? Show the screenshot of your terminal when you run those commands.
I have checked the boot option menu and only the windows bootloader and the USB stick appears. I will execute the commands again and paste it all here and also some screeshots
-commands
root@kali:~# fdisk -l
Disk /dev/sda: 29.8 GiB, 32027705344 bytes, 62554112 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8312dfc0
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 5636095 5636032 2.7G 17 Hidden HPFS/NTFS
/dev/sda2 5636096 5637503 1408 704K 1 FAT12
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A2B0F795-2839-4321-BD52-AC1F60D42159
Device Start End Sectors Size Type
/dev/sdb1 2048 206847 204800 100M EFI System
/dev/sdb2 206848 239615 32768 16M Microsoft reserved
/dev/sdb3 239616 766033919 765794304 365.2G Microsoft basic data
/dev/sdb4 975749120 976773119 1024000 500M Windows recovery environment
/dev/sdb5 766033920 959148031 193114112 92.1G Linux filesystem
/dev/sdb6 959148032 975749119 16601088 7.9G Linux swap
Partition table entries are not in disk order.
Disk /dev/loop0: 2.5 GiB, 2646646784 bytes, 5169232 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
root@kali:~# mount /dev/sdb5 /mnt
root@kali:~# mount --bind /dev /mnt/dev
root@kali:~# mount --bind /proc /mnt/proc
root@kali:~# mount --bind /sys /mnt/sys
root@kali:~# mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
root@kali:~# mkdir /mnt/boot/efi
mkdir: cannot create directory ‘/mnt/boot/efi’: File exists
root@kali:~# mount /dev/sdb1 /mnt/boot/efi
root@kali:~# mount -o remount,rw /dev/sdb1 /mnt/boot/efi
root@kali:~# mkdir /mnt/hostrun
mkdir: cannot create directory ‘/mnt/hostrun’: File exists
root@kali:~# mount --bind /run /mnt/hostrun
root@kali:~# chroot /mnt
root@kali:/# mkdir /run/lvm
mkdir: cannot create directory ‘/run/lvm’: File exists
root@kali:/# mount --bind /hostrun/lvm /run/lvm
root@kali:/# grub-install /dev/sdb
Installing for x86_64-efi platform.
Installation finished. No error reported.
root@kali:/# update-grub
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.13.0-kali1-amd64
Found initrd image: /boot/initrd.img-4.13.0-kali1-amd64
WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb4 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb5 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb6 not initialized in udev database even after waiting 10000000 microseconds.
Adding boot menu entry for EFI firmware configuration
done
root@kali:/# exit
exit
root@kali:~# umount /mnt/dev
root@kali:~# umount /mnt/proc
root@kali:~# umount /mnt/sys/firmware/efi/efivars
root@kali:~# umount /mnt/sys
root@kali:~# umount /mnt/boot/efi
root@kali:~# umount /mnt/hostrun
root@kali:~# umount /mnt/run/lvm
root@kali:~# umount /mnt
I'm having problems inserting the screenshots...
The grub reinstallation looks fine and so do the other commands. You can manually add the entry of grub from your UEFI settings. Show me the screenshot of your UEFI settings. I'll help you find that option.
You also have the firmware developed by Insyde and so do I. The other user below your thread was reporting the same thing that the entry is not being saved in the NVRAM. He also has the Acer Aspire laptop.
In the Boot priority order, when you click on Windows Boot Manager, what options does it show you? Can you post a screenshot of that? Meanwhile I'm going to test this problem. It can be the problem with the firmware itself. You should update your firmware.
You also have the firmware developed by Insyde and so do I. The other user below your thread was reporting the same thing that the entry is not being saved in the NVRAM. He also has the Acer Aspire laptop.
In the Boot priority order, when you click on Windows Boot Manager, what options does it show you? Can you post a screenshot of that? Meanwhile I'm going to test this problem. It can be the problem with the firmware itself. You should update your firmware.
At the installer process you need to move the boot option from the Windows partition to the kali partition.
The partition disks screen should be the one
SCS|1 sda ect.
#1
#2
Ect.
The windows partition is labelled microsoft data look for a B for boot. Since you can only boot one os at a time you need to move the B to the Kali partition should be the main partition. Click on the partition and edit the boot option, if there isnt a boot option try a different partition to move the boot. The installer will reconize the windows partitions. Then you will three options from the main Kali boot screen. Kali - Kali advanced -Windows.
You also have the firmware developed by Insyde and so do I. The other user below your thread was reporting the same thing that the entry is not being saved in the NVRAM. He also has the Acer Aspire laptop.
In the Boot priority order, when you click on Windows Boot Manager, what options does it show you? Can you post a screenshot of that? Meanwhile I'm going to test this problem. It can be the problem with the firmware itself. You should update your firmware.
If with firmware you refer to the BIOS, I have the latest version. And for the options when clicking Windows Boot Manager, it does not show anything.
Thanks!
At the installer process you need to move the boot option from the Windows partition to the kali partition.
The partition disks screen should be the one
SCS|1 sda ect.
#1
#2
Ect.
The windows partition is labelled microsoft data look for a B for boot. Since you can only boot one os at a time you need to move the B to the Kali partition should be the main partition. Click on the partition and edit the boot option, if there isnt a boot option try a different partition to move the boot. The installer will reconize the windows partitions. Then you will three options from the main Kali boot screen. Kali - Kali advanced -Windows.
So, I don't really understand what you are trying explain me. Can you try to explain it again?
Thanks!
I tested the solution again and it is working: https://forums.kali.org/showthread.php?36601-UEFI-How-to-repair-kali-linux-grub-dual-boot-with-Windows-10
Try doing it again, I've slightly change the order of commands.
If it still doesn't work then that's your firmware refusing to add entry of grub. Then i would test it if it shows the same problem with ubuntu or debian.