Solved Lap top won't boot up error 15 GRUB4DOS red screen

[gregrocker]

Grub writes boot code which is only cleared by wiping the hard drive with Diskpart Clean Command - formatting or merely deleting partitions is not enough.

In GRUB1 just the mere presence of this could ruin Win7 boot until it was wiped, something we dealt with here almost daily for years. Then suddenly GRUB2 was released and problems that severe have become rare - about as often as problems with Windows boot code interering in such a way they require wiping the HD.

 

[lehnerus2000]

My issue was due to me swapping HDDs in and out of my system without adjusting the boot order in the BIOS.

The old hdd that used to have my operating systems on it, kept being detected first and that would trigger GRUB-Rescue.

I would never have found out about this if I hadn't been playing around.

 

[Slartybart]

I've seen something similar myself (during the past week).

I rebuilt my system last month and I re-purposed the old OS drive for data (i.e. deleted all partitions and then Quick Formatted the entire drive as NTFS).
Whilst I was playing around with another HDD, I discovered that the old OS drive still contained GRUB-Rescue, which kept popping up at inconvenient times.

This and the other posts re Grub rescue disk location, is very good information - thanks, now I know.

 

[Hueristic]

wedaolu file deleted

Necro additional info.

I had this issue when I deleted file "wedaolu" from System reserve partition on windows 7.

I had completely forgot I had previously installed grub on this laptop years ago and was taken aback when the grub menu appeared.

Repair was a rebuild of the MBR.

Drop to command line and run these commands
bootrec /FixMbr
bootrec /FixBoot

That should do it. but you can continue to these next commands if it didn't upon reboot.

bootrec /ScanOs This returned "0 windows operating systems found" on my system.

I ran the next command anyway

bootrec /RebuildBcd

Since no instances were found when I ran "ScanOs " and I believe "RebuildBcd " just appends to the boot menu whatever "ScanOs" portion can find it was a moot point. I just didn't feel like doing a few extra reboots

Upon reboot System found bootloader just fine and grub should be out of the picture now.

So IOW I believe running the first two commands should repair the MBR and point it to the correct BCD file.



GL all, M$ sux.