Bug 195294 - FreeBSD overwrote Windows boot partition
Summary: FreeBSD overwrote Windows boot partition
Status: Closed Not A Bug
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 8.4-RELEASE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-22 23:03 UTC by Michael Starr
Modified: 2019-01-10 03:19 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Starr 2014-11-22 23:03:06 UTC
I installed FreeBSD on my Toshiba laptop and now I can't access Windows on the laptop. How do I undo this mistake?
Comment 1 lgfbsd 2014-11-24 18:58:04 UTC
The BIOS is not involved here; the bootloader is where the problem is coming from (if someone with the appropriate powers could change the subject, that would be helpful). This would have been easier to take care of on the technical support mailing list, because there isn't enough information in the report to figure out what has gone wrong here.

The first step in looking at the problem will be to determine whether the disk is using an old-style "MBR" partitioning or a newer "GPT" partitioning. This can be determined from the gpart(8) command, "gpart show /dev/<whatever device your disk is>". 

The second step is to make sure that the Windows partition is still present. That should also be present in the output from "gpart show". 

Assuming that you have an MBR-partitioned disk, the third step is to reinstall the bootloader and configure it to show all partitions. See the FreeBSD Handbook section on bootloaders to be sure, but I think the command would be "boot0cfg -B -m 0xf".
Comment 2 Pedro F. Giffuni freebsd_committer 2019-01-10 03:19:48 UTC
I've seen this in my system as well. It's not the BIOS (we can't simply overwrite that) but your boot partition.

If ypu were careful during the partition phase it is also possible that your Windows boot partition is still there but inactive. I have had luck rescuing such systems with the Windows repair disk and even FreeBSD.

Another helpful tool for dual booting is EasyBCD.

I will be closing this PR, hopefully you found a solution since 2014.