Results 1 to 8 of 8

Thread: Broken GRUB bootloader from Windows 10 Update? Here's what fixed it for me

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    2016-Aug
    Posts
    9

    Broken GRUB bootloader from Windows 10 Update? Here's what fixed it for me

    I just completed my Windows 10 update, only to realize that it broke my GRUB bootloader on the first restart. It would take me to a black screen, with a command prompt and a error message...

    rror: unknown filesystem
    Entering rescue mode...
    <grub rescue> _


    Yes, "error" is misspelled.

    I Googled online and found out it is a very common problem for anyone using dual-booting PCs (Mac + Windows, Linux + Windows, etc.), because apparently some Windows updates rewrite the partition tables or something. I am not a experienced Linux user but I hope that at least trying this bit could save all of you the wasted time and lost files from a reformat and reinstallation of both OSes. GRUB is apparently "lost", and needs help finding your Linux and Windows installs to continue on apparently. After following these steps, my Windows update proceeded normally.

    I took these instructions and adapted them to today's commands. Since it is not referred to as "grub2" anymore and I do not use Fedora. http://www.legendiary.at/2016/01/04/...d-breaks-grub/
    And this other one: https://www.linux.com/learn/how-resc...g-grub-2-linux

    1. Anyways, I started by typing "ls", and taking note of all of the partitions that it listed.
    2. Then I followed up by typing ls (hd#,gpt#), as how it was listed on my machine. Where "#" stands for the number. The goal is to find out where your operating systems are installed. For me, I discovered that "ls (hd0,gpt8)" returns the "ext2 filesystem".
    3. I typed the following commands without quotes "set prefix=(hd0,gpt8)/boot/grub" and then "set root=(hd0,gpt8)".
    4. Then I followed up with "insmod normal" and "normal", which automatically brought up our familiar bootloader. However, booting back into Kali normally is only temporary until the next reboot, where you have to once again help GRUB find your OS installs.
    5. In the terminal, I typed "update-grub" and then "grub-install /dev/sda", without a number pointing to any "sda". Just "sda". It completed in a few seconds, and after rebooting my GRUB is back and working again. Something about updating the GRUB configuration and then pointing it to the correct location of our operating system installs.



    Anyways, I got my Kali working again. But unfortunately, some Windows updates are more extreme, and would go as far as to delete your partitions. http://www.omgubuntu.co.uk/2016/08/w...lete-partition I don't know how to deal with THAT. I am sure, that means a forced reinstall of everything.
    Last edited by Lister; 2016-09-18 at 17:36.

Similar Threads

  1. GRUB taking over Windows Bootloader
    By dhanawade in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2020-11-01, 05:45
  2. Replies: 0
    Last Post: 2020-04-22, 01:58
  3. Kali linux Grub bootloader insted of windows
    By fojumdk in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2020-03-27, 21:16
  4. Dual Boot Lost WIndows 8 GRUB BOOTLOADER
    By N4 Nethunter in forum TroubleShooting Archive
    Replies: 5
    Last Post: 2015-03-28, 09:00
  5. GRUB Bootloader not recognizing windows 8, dualbooting with Kali
    By egregius in forum TroubleShooting Archive
    Replies: 1
    Last Post: 2013-09-20, 21:12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •