Windows 10: Win 10 keeps losing dual boot info

Hi there. I had been dual-booting between win 7 and win 10. That part was working fine, but I was unhappy wth my win 10 installation. So I erased the partition and reinstalled it. First sign of trouble: It didn't detect my win 7 installation. But it was there (I already got files from it). I installed EasyBCD, added the entry for win 7, saved the set up, then wrote the MBR with the new entry. Went to MSConfig to doublecheck. Both entries were there.
I restarted, and it booted straight into Win 10. EasyBCD no longer had the win 7 entry. Neither did MSConfig. Went through the whole process again. Same problem at restart. And it wasn't fastboot, I could see the BIOS entry, etc.
What went wrong? Thanks in advance for your help.
P.S. By Windows 10 I mean Build 10049.

:)

 

Dual boot Windows 10 and Windows 7 by cloning Windows 7 to new HDD

Old title: Dual boot Win 10 and Win 7

Have Win 10 on SSD C:\ and a failing HDD with Win 7 and some programs I don't want to lose. I have a new HDD to use to create a dual boot. Media for Win 7 is no longer available. How do I clone the failing disk into a bootable partition on the new HDD?

 

Win 10 upgrade

I have a dual boot pewter. XP on one partition, win 7 on the other. If I let micropuke upgrade me to win 10, will I lose my XP partition?

 

When you wiped out Win 10, did you check if Win 7 boots up? You have to make sure that the host OS is booting up as normal before installing the second OS.

 

Thanks, badrobot. No, I did not make sure. After doing stuff like that many times with no problem, I never thought of it.

 

It's probably still there, press and hold Shift while clicking Restart to see if you get 'Chose another operating system' option.

 

Win 10 always sets itself as a default but you can always change it in msconfig. The problem is if 7 has boot problem before installing 10, you will not get dual boot options and will go straight to 10.

 

Have you tried to repair windows7 with Startup repair by booting from 7 install media. You must have deleted your active partition when you installed 10.
http://www.sevenforums.com/tutorials...air.html?ltr=S

 

Thanks, Edwin. Holding Shift with Restart got me into Startup Repair. But no, it didn't give me the option of Windows 7.

Thanks, Charlie, for the tip of repairing Windows 7. I will try that today and post back.

 

Code: bcdboot C:\Windows[/quote] Type that in an elevated command prompt and it should take care of your boot files. Do the same with your drive letter for the other installation.

 

Thanks, cyberrufus. Didn't need that.
I did what Charlie suggested, and repaired the win 7 installation. Everything is ok now.

Thank you all guys, for your tips.

 

You can also use: Download EasyBCD - MajorGeeks to resolve boot issues and boot order.

 

Thanks, CountMike. If you read my original post, I had been working with EasyBCD, and it didn't solve my problem either. Even when I entered my setup in EasyBCD, it didn't help. It lost it there, too. Probably because Windows only saw one entry in the Bootloader when it started. So this wasn't fixed until I did a repair of Windows 7. From then on, EasyBCD worked with my setup.

 

EasyBCD v2.2, older one that worked on W7 doesn't work on 8/8.1 or W10 properly.
My situation yesterday:
Win8.1 on primary boot disk SSD
Win10TP on secondary HDD, both bootable by themselves.
Updated W10 and boot was screwed up royally. 5 entries at boot and only W10 would boot.
EasyBcd was installed on primary disk too. I installed EasyBcd on W10 and set boot order and menu, it was down to two W8.1 and one W10 on the boot menu. I found executable EasyBcd file on SSD with W8.1 and run it while still in W10, set the boot order and everything came out right. Now I can BOOT thru BIOS to either of disks and get exactly same BOOT menu.

 

This is why I got those screwless removable trays and hard drive power switch installed on my PC. We need to discnonnect all the other working OSes on the same machine before updating Win 10. Or else, boot managers will get screwed up. But you can also manually disconnect them by opening up your case. *Smile But if it is a minor update (KB updates), no need to disconnect.