Windows 10: linux grub bootloader failed after win 10 updates

My son (26) just returned a long term loan P8B67B Deluxe to me with Linux and Win 7 on it. I upgraded 7 successfully, but after updates installed last night the PC refuses to boot saying "error, no such partition, Entering rescue mode .. grub rescue>" Repeated boot attempts saw it fall into error 53 on the mobo lcd display. Removing one ram stick brought me back to booting to "error, no such partition, Entering rescue mode .. grub rescue>"

Trying to boot just one HDD either gives the above message, or "error, no such device : 521683dd-0417-4a66-b3fb-c6c67b9cc9fo grub rescue>"

I don't need the linux. That was my engineer son. What fixes are there to bring it to Win 10 alone? I don't know the new key or the old 7 key. Should have checked and written it down

:)

 

Win 10 won't boot after "update"

I was running on the RTM version of Win 10 (build 10240) and tried to update to the current version, both through the Windows automatic update and by downloading the latest ISO, burning it to a DVD, and running it from within Windows. Both times, the reinstall
ended when the computer restarted automatically and displayed the message:

error: unknown filesystem.

Entering rescue mode . . .

grub rescue>

(GRUB is the Linux bootloader. I'm dual booting with Linux Mint, 64 bit.) I tried using the tools on the Win 10 installation DVD, including automatic startup repair, CHKDSK (reported clean), SFC (ditto), BOOTREC, BOOTSECT, BCDEDIT, and System Restore; I
also tried the startup repair on Boot-Repair Disk (a Linux tool). My bootloader was apparently damaged by the update. What can I do to fix it?

I'm running Windows 10 Professional (32-bit) on a computer with a Gigabyte GA-EP45T-USB3P system board, an Intel Q9550 CPU, 8GB of memory, and two 500GB SATA drives. The bootloader was installed along with the Linux OS.

 

Dual Boot Linux Manjaro Issues in Windows 10

Thats weird. Usually the MBR should be overwritten by Linux Grub. But that is not an issue though.

I don't use Grub myself but Windows 10 Bootloader instead to boot into Linux, because that Grub Loader is so ugly.

(It looks like this but with Linux instead of Win7:
Windows Bootloader )

So I simply downloaded and installed "EasyBCD 2.2" (choose the Free version)

Just add a new startup entry with Grub 2 (or maybe GRUB) and choose the partition where you installed Manjaro and it should be fine.

 

I tried:

grub rescue>set boot=(hd0,msdos6)
grub rescue>set prefix=(hd0,msdos6)/boot/grub
grub rescue>insmod normal
error: no such partition.
grub rescue>

ls
(hd0) (hd0,msdos1)
grub rescue>set boot=(hd0,msdos1)
grub rescue>set prefix=(hd0,msdos1)/boot/grub
grub rescue>insmod normal
error: unknown filesystem.
grub rescue>

grub rescue>set boot=(hd0)
grub rescue>set prefix=(hd0)/boot/grub
grub rescue>insmod normal
error: no such partition.
grub rescue>

My limited linux knowledge got me nowhere there.

Now downloading a 64 bit Windows 10 N iso through media creation tool to try a boot repair for Windows.

Burnt a disk, went to repair/Advanced Options/Command Prompt
Tried:

• bootrec /RebuildBcd
• bootrec /fixMbr
• bootrec /fixboot
• Exit

At Rebuild Bcd it only found Windows.old

 

Code: bcdboot C:\Windows[/quote] Try running that at the command prompt to recreate the boot files. That's assuming your Windows installation is located on the C: drive. If another drive just change the letter.

 

Well, final workaround was installing Win 10 N intending to use the Win 7 N key. My son found the key. I installed an iso I got from the Media Creation tool earlier, and deferred putting in the key, wanting to wait till net connected. There were two key prompts during installation. When it finished I needed no other drivers, everything was up and running, and here's a kicker. Windows 10 N was activated and had a key already????

While I've kept the original hard drive, exploration showed that all the personal files that should have gone from windows.old default user to windows default user no longer existed. I think more than just the boot loader is damaged. 2:05AM here now. Sometime tomorrow I'll shift whatever useful files I can find over to the fresh instal. After that I may try your suggestion just to see.