Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Safe to put the BootMGR files on main drive?

17 Jan 2015   #11
Gandolf

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by Alejandro85 View Post
Quote   Quote: Originally Posted by Gandolf View Post
Quote   Quote: Originally Posted by Layback Bear View Post
Here is a tutorial by whs that should be helpful to you.

By whs:
Bootmgr - Move to C:\ with EasyBCD
Is it safe though? I mean, there must be a reason that Microsoft created a separate partition to house it.
There is a reason, actually. It's to support BitLocker full-disk encryption that's part of Windows. When it's active the normal system partition is encrypted, hence unreadable, so nothing can boot from it. That problem is solved with the"system reserved" partition, which is always left unencryptedl and holds the bootloader. It boots from there, initializes the encryption system and then decrypts and reads the rest of the system.
Even if BitLocker is not used, Windows will create, by default, that annoying partition. There it boot from there and just transfer control to the normal system.

By just copying bootmgr will not suffice for a sucesfull boot. You need to copy the whole contents of the system-reserved to the main drive. You also need to make the drive bootable with the Windows 6.x MBR code, that can be done with the "bootsect" utility included in the Windows installation disk.
I've never tried doing that but my supposition is that those things will make a partition bootable and Windows will start from there.
I only copied the BootMGR and I got a successful boot.


My System SpecsSystem Spec
.
17 Jan 2015   #12
dsperber

Windows 7 Pro x64 (1), Win7 Pro X64 (2)
 
 

Quote   Quote: Originally Posted by Gandolf View Post
I only copied the BootMGR and I got a successful boot.
You're holding back... surely you did more than that, although you never actually told us exactly what you did other than "I put the BootMGR on my C drive and transferred the C drive to my new SSD. Everything worked out perfectly, thanks guys!".

So, did you use EasyBCD to do that? Or not? If you did use EasyBCD then not only would ALL the components of Boot Manager (including its menu, with one or more bootable OS's on it) get copied from "system reserved" to C, but also the target C-partition would be marked "active". Then if you copied that C-partition to the SSD it, too, would be marked "active".

Or, if you didn't use EasyBCD, then what exact component(s) did you copy when you said "I put the Boot MGR on my C drive"? One file? Multiple files? What?

Finally, since the "system reserved" partition on the spinner is marked "active" and the C-partition is not, if you simply copied the original spinner-C over to become the SSD-C that by itself would not make the partition bootable. You had to do at least a bit more, in order to make the C-partition now residing on the SSD bootable. So did you use some other program to do that? Partition Wizard? Something else?

There is a possibility that the BIOS might default to the one-and-only partition on the one-and-only hard drive as the boot partition to find Boot Manager, even if it's not officially marked "active". I don't know this for sure, as I've never had an environment without a proper "active" partition in which Boot Manager officially lives, either Win98 C, or "system reserved" for Win7. But if this isn't true, and you haven't yourself marked the SSD C as "active", I don't know how you could be booting successfully. Unless you used some other program/utility to accomplish the copy from spinner to SSD which simultaneously marked it as "active".


Anyway, I'm sure your current SSD environment is successful as you say it is. But it would be great if you could just flesh out your story a bit, providing the actual details of how you "just copied BootMGR to C".

Did you use EasyBCD or some other program product or did you do something manual yourself?

And how did you get the C-partition on the SSD to be marked "active"?

Thanks if you would please finish the story, as it probably would be very helpful to someone else looking at this thread sometime down the road.
My System SpecsSystem Spec
17 Jan 2015   #13
Gandolf

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by dsperber View Post
Quote   Quote: Originally Posted by Gandolf View Post
I only copied the BootMGR and I got a successful boot.
You're holding back... surely you did more than that, although you never actually told us exactly what you did other than "I put the BootMGR on my C drive and transferred the C drive to my new SSD. Everything worked out perfectly, thanks guys!".

So, did you use EasyBCD to do that? Or not? If you did use EasyBCD then not only would ALL the components of Boot Manager (including its menu, with one or more bootable OS's on it) get copied from "system reserved" to C, but also the target C-partition would be marked "active". Then if you copied that C-partition to the SSD it, too, would be marked "active".

Or, if you didn't use EasyBCD, then what exact component(s) did you copy when you said "I put the Boot MGR on my C drive"? One file? Multiple files? What?

Finally, since the "system reserved" partition on the spinner is marked "active" and the C-partition is not, if you simply copied the original spinner-C over to become the SSD-C that by itself would not make the partition bootable. You had to do at least a bit more, in order to make the C-partition now residing on the SSD bootable. So did you use some other program to do that? Partition Wizard? Something else?

There is a possibility that the BIOS might default to the one-and-only partition on the one-and-only hard drive as the boot partition to find Boot Manager, even if it's not officially marked "active". I don't know this for sure, as I've never had an environment without a proper "active" partition in which Boot Manager officially lives, either Win98 C, or "system reserved" for Win7. But if this isn't true, and you haven't yourself marked the SSD C as "active", I don't know how you could be booting successfully. Unless you used some other program/utility to accomplish the copy from spinner to SSD which simultaneously marked it as "active".


Anyway, I'm sure your current SSD environment is successful as you say it is. But it would be great if you could just flesh out your story a bit, providing the actual details of how you "just copied BootMGR to C".

Did you use EasyBCD or some other program product or did you do something manual yourself?

And how did you get the C-partition on the SSD to be marked "active"?

Thanks if you would please finish the story, as it probably would be very helpful to someone else looking at this thread sometime down the road.
Sorry about that :P. I used EasyBCD to move everything and cloned my C drive (which had all the boot files on it) to the SSD.
My System SpecsSystem Spec
.

17 Jan 2015   #14
dsperber

Windows 7 Pro x64 (1), Win7 Pro X64 (2)
 
 

Quote   Quote: Originally Posted by Gandolf View Post
Sorry about that :P. I used EasyBCD to move everything and cloned my C drive (which had all the boot files on it) to the SSD.
AHA! Excellent. EasyBCD wins again.

Thank you.


Note... one more loose end.

People very often casually talk about "C drive", but technically speaking it's really "C partition", or maybe "the partition on your hard drive with a drive letter of C". It's easy to use these terms interchangeably and casually, but sometimes it's ambiguous and imprecise. If you only have one hard drive it's easy to think of it as your "C drive", although we realize it can have other partitions on it which may (or may not) have their own drive letters other than C.

Now I'm guessing that after using EasyBCD to migrate Boot Manager into your spinner C-partition, you perhaps neglected to physically delete the old (and now obsolete, unused and unnecessary) "system reserved" partition on the spinner. But maybe you did delete it. Anyway, it certainly has no purpose any longer, either on the spinner or on the new SSD, so you presumably didn't copy ("clone") it to the new SSD when you did copy ("clone") the now bootable C-partition.

When you say you "cloned your C drive", you can see why that's a bit vague. You don't have a "C drive". You actually have a [spinner] hard drive with a now bootable C-partition on it, and maybe (or maybe not) also a small "system reserved" partition on it. But it's only the bootable C-partition which deserves to now be on the SSD.

For sure, it's now no longer necessary to have the "system reserved" partition around at all, either residually on the old spinner or on the new SSD, since it now serves no purpose at all. But it does take a manual action on your part to delete it since EasyBCD consciously doesn't do that for you (since some unexpected problem might develop and you might want to reactivate it again for use). So if you plan to use the entire old SSD as a newly repurposed data drive (with one or more data partitions on it) I'm sure you've just now deleted all partitions (with Partition Wizard? something else?) and created one or more data partitions on it (lettered D or whatever you have changed it to), now that you're booting from the SSD.

Finally, when you say "cloned" you probably used some 3rd-party software product to do that: Macrium Reflect, Partition Wizard, even maybe the software utility which came with the Samsung SSD to do just that type of thing. Which was it? The Samsung software knows that the partition copied to the SSD must be marked "active" and will do that for you. The Macrium Reflect software also does that as part of its "clone" function, if the source partition itself is "active". I don't know if Partition Wizard's "copy partition" function will also set the resulting partition "active" if the source partition was, but certainly PW can be used to mark the partition "active" after the fact.
My System SpecsSystem Spec
Reply

 Safe to put the BootMGR files on main drive?




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Is 'virtual ubuntu' as safe as having it as the main OS?
Hi. I've just installed Virtualbox and now have a VM running Ubuntu. I intend using it solely for banking/Amazon etc. I've read that there are virtually no viruses directed at Linux but is the aforementioned setup as good as having Ubuntu as the main OS? My thinking is: What's powering your...
Virtualization
Can't move files from main HD to SATA
I got a second internal HDD for my computer as I keep a lot of movies/tv shows on my computer and my main hard drive was getting full. My new 3TB HDD was working great for months now, never really had any trouble until recently out of nowhere. When moving files to the second hd, it'd freeze up...
Hardware & Devices
Files that I can delete off of Main HD directory
I am terribly sorry if I posted this in the wrong place. I couln't really find a catagory that this could go under. This is the closest. I am cleaning out my HD, I am at the main directory and I know deleting certain files (such as C:\Windows) would screw up the system. There is tons of files in...
Performance & Maintenance
Installed files in main folder c: Drive I do not understand Pics
I have no idea what these files are or how they got on my c drive. but they have been here for a long time and im finally asking for help. I have a Raid 0 setup. I think? I bought this computer from a friend and installed windows 7 ultimate myself. I would be happy to give any info to anyone...
General Discussion
How to backup FROM external drive TO main drive
Windows backup is set up to not allow backups onto the C drive (or whatever drive windows is installed on), which generally makes sense. But I have a C drive with a lot of empty space, and an external hard drive that I need to back up. So... is there any way to get around the default behavior so...
Backup and Restore
Win 7 SP1 Leftover files on hard drive - Safe to remove?
since having to re-install comp after nasty virus i seem to have found files i don't recognise. Think they are SP1 files, and just wanted to know if they are safe to delete... The files are in a directory as below... C:\d603f9c34eb17f8b0961267e66081a inside this sub dir there are two ...
Windows Updates & Activation


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:53.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App