Dual boot problem - After installing Win7 on separate HD, CHKDSK ran and Windows Boot Manager got installed on my Win10 SSD and now it's not recognized as a bootable device.
Very long post, but lots of detail so you can hopefully help me.
I have Win 10 installed on SSD, with most of my files stored a separate 4TB HDD. I installed Win7 on a third 1TB HDD, and tried to create a Win10/7 dual boot. I failed, and ultimately did something to my Win10 SSD. It is no longer recognized as a bootable device.
I would like help doing three things, and any help is very much appreciated.
1) Recovering my Win10 SSD as a bootable drive.
2) Reinstalling a Win10/7 dual boot the correct way, and figuring out how to share my primary storage HDD between the two OS.
3) If there is no way to easily and safely share the Primary Storage HDD between both Win10 and Win 7 (and without screwing up the OS not in use), I would settle for just having a dual boot option where Win7 runs on its own and leaves the other drives alone.
Here are the steps I took, and what happened:
I already had Win 10 Education on a 500 GB SSD (GTP), and a 4TB HDD for storage (named Primary HDD) (GTP). Then, I installed Win 7 Ultimate on a third HDD, with no other drives connected. This turned out to be MBR partitioned. Then, I connected my storage drive, Primary HDD, and booted up the Win7 OS again. The new OS install didn’t like this and a black DOS screen came on with an error, and did some kind of CHKDSK scan. Then the Win7 OS loaded, and I could see all of the files in the Primary HDD.
Next, I turned the comp off, connected the Win10 SSD, and booted it up. So now all three drives are connected. I was expecting windows to ask me to choose an operating system, but it never did . The black DOS screen came on again, did the same error and filecheck again, then Win7 booted up, not Win10. In Win7 I was able to see the SSD where my Win10 was installed, and access the SSD folders. I restarted the comp and went into the BIOS to check boot orders, my SSD was listed differently.
The BIOS used to have an entry listed as Samsung SD 850 EVO. Now the listing showed: Windows Boot Manager (Samsung SD 850 EVO). What does that mean?
I tried to simply move this entry to Option #1, but it still loaded to Win7. Then, I went into “Hard Drive Boot Priorities” and saw the correct listing for Samsung SSD 850, and made it Boot Option #1.
Then tried to reboot with this listing as the first boot priority, and took the WD drive option out entirely.
[
It still loaded to Win 7.
I loaded up the Win7 OS again, and Disk Manager shows this:
When I connect only the Win10 SSD I get a black screen saying I don’t have a bootable device.
I assume the CHKDSK scan was because Win10 and 7 filesystems don’t like one another, and the new Win7 OS screwed up the boot record on the SSD, when it tried to “fix” the Win10 files it didn’t recognize…or something like that. Assuming this is true, how do you get a dual boot to work and not have the CHKDSK scan happen anytime both OS are recognized during the BOOT sequence. I read some posts about installing Win10 after Win7, but I don’t see the point in that. First, I installed both OS independent of the other, and then connected the drives. All the drives are connected to the mobo all the time, so there isn’t any “first” install anyway.
Any thoughts on how to recover my Win10 SSD as a bootable drive? Any thoughts on how to set up a dual boot that will work? Before I tried the dual boot I read several forums and posts, and I saw conflicting information. Some threads said you had to install 7 first, some said just install them separately, and it wouldn’t matter. I installed separate OS on separate drives, independently. Obviously something went wrong because it caused a CHKDSK scan each time I connected a new drive. I can keep reading posts on how to fix it, but I see conflicting opinions on dual boot processes and it seems wise to ask for help before I make this situation worse. Tell me I didn’t ruin my Win10 OS install.
All three of these drives will always be connected the mobo, so I need to make sure the acting OS is not doing something negative to affect the files in the HD with the other OS.
Very long post, but lots of detail so you can hopefully help me.
I have Win 10 installed on SSD, with most of my files stored a separate 4TB HDD. I installed Win7 on a third 1TB HDD, and tried to create a Win10/7 dual boot. I failed, and ultimately did something to my Win10 SSD. It is no longer recognized as a bootable device.
I would like help doing three things, and any help is very much appreciated.
1) Recovering my Win10 SSD as a bootable drive.
2) Reinstalling a Win10/7 dual boot the correct way, and figuring out how to share my primary storage HDD between the two OS.
3) If there is no way to easily and safely share the Primary Storage HDD between both Win10 and Win 7 (and without screwing up the OS not in use), I would settle for just having a dual boot option where Win7 runs on its own and leaves the other drives alone.
Here are the steps I took, and what happened:
I already had Win 10 Education on a 500 GB SSD (GTP), and a 4TB HDD for storage (named Primary HDD) (GTP). Then, I installed Win 7 Ultimate on a third HDD, with no other drives connected. This turned out to be MBR partitioned. Then, I connected my storage drive, Primary HDD, and booted up the Win7 OS again. The new OS install didn’t like this and a black DOS screen came on with an error, and did some kind of CHKDSK scan. Then the Win7 OS loaded, and I could see all of the files in the Primary HDD.
Next, I turned the comp off, connected the Win10 SSD, and booted it up. So now all three drives are connected. I was expecting windows to ask me to choose an operating system, but it never did . The black DOS screen came on again, did the same error and filecheck again, then Win7 booted up, not Win10. In Win7 I was able to see the SSD where my Win10 was installed, and access the SSD folders. I restarted the comp and went into the BIOS to check boot orders, my SSD was listed differently.
The BIOS used to have an entry listed as Samsung SD 850 EVO. Now the listing showed: Windows Boot Manager (Samsung SD 850 EVO). What does that mean?
I tried to simply move this entry to Option #1, but it still loaded to Win7. Then, I went into “Hard Drive Boot Priorities” and saw the correct listing for Samsung SSD 850, and made it Boot Option #1.
Then tried to reboot with this listing as the first boot priority, and took the WD drive option out entirely.
[
It still loaded to Win 7.
I loaded up the Win7 OS again, and Disk Manager shows this:
When I connect only the Win10 SSD I get a black screen saying I don’t have a bootable device.
I assume the CHKDSK scan was because Win10 and 7 filesystems don’t like one another, and the new Win7 OS screwed up the boot record on the SSD, when it tried to “fix” the Win10 files it didn’t recognize…or something like that. Assuming this is true, how do you get a dual boot to work and not have the CHKDSK scan happen anytime both OS are recognized during the BOOT sequence. I read some posts about installing Win10 after Win7, but I don’t see the point in that. First, I installed both OS independent of the other, and then connected the drives. All the drives are connected to the mobo all the time, so there isn’t any “first” install anyway.
Any thoughts on how to recover my Win10 SSD as a bootable drive? Any thoughts on how to set up a dual boot that will work? Before I tried the dual boot I read several forums and posts, and I saw conflicting information. Some threads said you had to install 7 first, some said just install them separately, and it wouldn’t matter. I installed separate OS on separate drives, independently. Obviously something went wrong because it caused a CHKDSK scan each time I connected a new drive. I can keep reading posts on how to fix it, but I see conflicting opinions on dual boot processes and it seems wise to ask for help before I make this situation worse. Tell me I didn’t ruin my Win10 OS install.
All three of these drives will always be connected the mobo, so I need to make sure the acting OS is not doing something negative to affect the files in the HD with the other OS.