Kali Linux is Installed but not showing in boot manager

62,524

The Problem is Finally Solved.

What I did is simply installed Ubuntu alongside windows and guess what in the grub of Ubuntu, Kali was already listed.

Now i am using triple boot.(Win10, Kali and Ubuntu)

Share:
62,524

Related videos on Youtube

Kavin Mayekar
Author by

Kavin Mayekar

Updated on September 18, 2022

Comments

  • Kavin Mayekar
    Kavin Mayekar over 1 year

    I recently bought a new Laptop:
    Lenovo IdeaPad 320e
    Intel i5 7200 2.5GHz processor
    8Gb RAM
    2Gb NVidia 940mx Graphics
    1TB HDD

    It came with freeDOS so i installed Windows 10 on it on EFI mode.
    A few days later i also installed Kali Linux in a new partition from a live USB on EFI.

    my partitions as seen on easyBCD

    Partitions on my HDD:
    Partition 1:Windows Boot(i guess) -450Mb
    Partition 2:Windows Recovery(i guess) -100Mb
    Partition 3:Windows reserved (i guess) -16Mb
    Partition 4:Windows C Directory -299Gb
    Partition 5:Local NTFS E Drive -200Gb
    Partition 6:Local NTFS F Drive -382Gb
    Partition 7:EFI Grub Boot Loader -477Mb
    Partition 8:Linux SWAP -9Gb
    Partition 9:Kali Linux -40Gb

    When I Installed Kali for the First time(i.e. Reboot after installation) i got the grub menu to start Kali Linux so i know that Kali is Properly installed.

    So the next time i selected Windows Boot Loader to Enter my Windows 10.

    The Problem is now that there is no record of Kali Linux in my boot Loader.
    When I enter the boot menu i can only see EFI on Network and Windows Boot Loader. There is no GRUB.

    I have already tried:

    1. Using bcdedit:
      bcdedit /set {bootmgr} path /EFI/Kali/grub64.efi

    Doesn't work show no such directory.

    1. Using live USB to reinstall GRUB:

      mount /dev/sda3 /mnt
      mount –bind /dev /mnt/dev
      mount –bind /dev/pts /mnt/dev/pts
      mount –bind /proc /mnt/proc
      mount –bind /sys /mnt/sys
      chroot /mnt
      grub-install /dev/sda
      update-grub
      exit
      umount /mnt/dev/pts
      umount /mnt/dev
      umount /mnt/proc
      umount /mnt/sys
      umount /mnt
      

    After reinstalling grub, the grub menu worked till i rebooted to windows boot loader; after which it again showed no signs of Kali Linux.

    1. Reinstall Kali.

    So my main problem is that when i install kali i see the GRUB menu but when i use Windows Boot Loader once the it always boots into my windows 10 and doesn't show Kali anywhere in my boot Section.

    Any help is appreciated.

    Update:
    I tried re downloading kali3 and then reinstalling.
    I did the Standard Installing process and now thankfully the kali entry is showing in the boot manager.
    Now the problem is the grub doesn't boot.
    I still haven't tried reinstalling grub which hopefully solves my problem.

    I will keep everyone updated if reinstalling grub works.

    P.S.: Looks like I accidentally installed GRUB on the same partition as the Windows Bootloader but Windows Bootloader still works so it didn't overwrite anything.

  • Kavin Mayekar
    Kavin Mayekar over 6 years
    I am not new to dual booting so i already turned those settings off.
  • Kavin Mayekar
    Kavin Mayekar over 6 years
    Kali doesn't seem to install on Legacy. Btw i updated the question.
  • Kavin Mayekar
    Kavin Mayekar over 6 years
    Except for the reinstalling part(which helped a bit) the process in the link didn't work. I have updated the question with the new problem. If you have the solution then please help
  • Fabby
    Fabby over 5 years
    Wow! Did not see that coming! Congratulations! Both Question and answer upvoted! Please take a system backup (all HDDs) using CloneZilla live Disk to image...
  • K7AAY
    K7AAY almost 5 years
    A separate swap partition is declassé ever since the 4.2 kernel. A swap file in /home runs just as fast, and gives you more flexibility in upsizing the swap file from the standard of 'make it the same size as your RAM to start and make it bigger if your apps use it'.