Windows 7 BOOTMGR

Genesius

New member
Hi, windows keeps saving BOOTMGR to another disk.

I install to my SSD and I can boot and everything is fine, I connect a second drive and it move BOOTMGR to that drive
After reboot everything works but if I remove the other drive and just leave my windows SSD it won't boot because the boot partition is on the disk I took out!

It's not a problem with SSD's, my other system has 2 SSD's 1 sata, pulled an SSD out and had the same issue, windows was installed on c drive but put the boot on another drive.

I have no idea why it's doing this but I just did 2 new clean installs and I'm going to use easybcd to move it around, but i don't know if it will move it back again.

Any ideas why this is happening?
 
when installing a fresh OS, you should only have one drive in operation. including
any RAID or suplemental drives should be disconnectedf rom the system until the
OS is completely installed. then enable the supplemental drives.
 
Yep, did that, always do. But if I connect a new drive, next time I shutdown and reboot windows will have moved my boot partition off of its original drive and onto anywhere it pleases.

I have found a few things on google about this happening but not much, I just can't understand why. I'm installing windows 7 pro, maybe it's something to do with that. I'm just doing all updates now and a little later I'll add a new drive, format it and get it showing up and after a reboot home that my boot stays where I put it!

I'll post back
 
That should definatley not happen, are you using any apps like acronis disk director ?

Make sure your booting from the correct disk in the bios !
 
No apps, I honestly get the mono and my destination drive and use an external DVD drive to install. I do it all and I still end up with the same issues. I format first then do a clean install.
 
it happens after install. I only have one drive in at the moment, but once im done overclocking ill do a fresh install and take a picture. The second drive becomes 'active' and dissappears from 'my computer' and in disck management, it shows the disk as being a 'boot' disk. if i then associate a drive letter i get use of the unpartitioned part back.

its very strange


ok, so incase anyones interested this is an issue with my Crucial M4's. my samsung ssd does not do this. if i install windows to my M4 and then put a HDD in, the boot will just jump off of that disc to another. if i add another M4 SSD and then a HDD and rebooot, the BOOTMGR will now be on the other M$. its very strange. using EasyBSD i can move it back and it will stay where i put it. it must just be an odd glitch, and i would have never of noticed it it i hadnt pulled the Hdd out.

my new Samsung SSd doesnt do it. it must be a glitch with my board and the latest firmware i have on both discs. i know that certain Crucial M4 firmware has issues with UEFI BIOS's. Is BIOS's even a word?
lol
well thats what ive found, no reason why, just odd!
 
Last edited:
Back
Top