How to make the system partition both boot and system (Windows 7 x64)

#1
Well,first of all I d like to congratulate the people who startd this forum.
It trully is a wealthy source of information on many many subjects! :smile:

My situation is as follows.
Windows 7 Ultimate x64 installed on a new drive I bought recently.Run setup from scratch.Re installed OS ( C: ).
Everything working ok till I noticed that I cannot format the partition that Windows 7 were originally installed ( W: ).
In Disk Management to my surprise I found out that W: is assigned as Boot and C: is System,both Active partitions.
Upon further investigation I followed this guide and when using the bcdedit /enum all /v command I get this:


Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device boot
path \bootmgr
description Windows Boot Manager
locale en-us
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {39db824c-0044-11e2-ae42-fb7e07222570}
resumeobject {39db824b-0044-11e2-ae42-fb7e07222570}
displayorder {39db824c-0044-11e2-ae42-fb7e07222570}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 0
Windows Boot Loader
-------------------
identifier {39db8249-0044-11e2-ae42-fb7e07222570}
device ramdisk=[C:]\Recovery\39db8249-0044-11e2-ae42-fb7e072225
70\Winre.wim,{39db824a-0044-11e2-ae42-fb7e07222570}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice ramdisk=[C:]\Recovery\39db8249-0044-11e2-ae42-fb7e072225
70\Winre.wim,{39db824a-0044-11e2-ae42-fb7e07222570}
systemroot \windows
nx OptIn
winpe Yes
custom:46000010 Yes
Windows Boot Loader
-------------------
identifier {39db824c-0044-11e2-ae42-fb7e07222570}
device partition=C:
path \windows\system32\winload.exe
description Windows 7
locale en-us
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=C:
systemroot \windows
resumeobject {39db824b-0044-11e2-ae42-fb7e07222570}
nx OptIn
detecthal Yes
Windows Boot Loader
-------------------
identifier {3f53f540-64cc-11e0-b9ab-9ad00bd2edc5}
device partition=C:
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice ramdisk=[W:]\Recovery\3f53f540-64cc-11e0-b9ab-9ad00bd2ed
c5\Winre.wim,{3f53f541-64cc-11e0-b9ab-9ad00bd2edc5}
systemroot \windows
nx OptIn
winpe Yes
custom:46000010 Yes
Windows Boot Loader
-------------------
identifier {3f53f548-64cc-11e0-b9ab-9ad00bd2edc5}
device ramdisk=[W:]\Recovery\3f53f548-64cc-11e0-b9ab-9ad00bd2ed
c5\Winre.wim,{3f53f549-64cc-11e0-b9ab-9ad00bd2edc5}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
custom:15000065 3
custom:15000066 3
osdevice ramdisk=[W:]\Recovery\3f53f548-64cc-11e0-b9ab-9ad00bd2ed
c5\Winre.wim,{3f53f549-64cc-11e0-b9ab-9ad00bd2edc5}
systemroot \windows
nx OptIn
custom:250000c2 1
winpe Yes
custom:46000010 Yes
Resume from Hibernate
---------------------
identifier {39db824b-0044-11e2-ae42-fb7e07222570}
device partition=C:
path \windows\system32\winresume.exe
description Windows Resume Application
locale en-us
inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {4be53114-6ae5-11e1-bacb-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Microsoft Windows 7
locale en-US
inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
filedevice partition=W:
filepath \hiberfil.sys
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {b2721d73-1db4-4c62-bf78-c548a880142d}
device boot
path \Boot\memtest.exe
description Windows Memory Diagnostic
locale en-us
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
badmemoryaccess Yes
EMS Settings
------------
identifier {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
bootems Yes
Debugger Settings
-----------------
identifier {4636856e-540f-4170-a130-a84776f4c654}
debugtype Serial
debugport 1
baudrate 115200
RAM Defects
-----------
identifier {5189b25c-5558-4bf2-bca4-289b11bd29e2}
Global Settings
---------------
identifier {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
inherit {4636856e-540f-4170-a130-a84776f4c654}
{0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Boot Loader Settings
--------------------
identifier {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
{7ff607e0-4395-11db-b0de-0800200c9a66}
Hypervisor Settings
-------------------
identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Resume Loader Settings
----------------------
identifier {1afa9c49-16ab-4a5c-901b-212802da9460}
device partition=C:
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
Device options
--------------
identifier {39db824a-0044-11e2-ae42-fb7e07222570}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\39db8249-0044-11e2-ae42-fb7e07222570\boot.sdi
Device options
--------------
identifier {3f53f541-64cc-11e0-b9ab-9ad00bd2edc5}
device partition=C:
description Ramdisk Options
ramdisksdidevice partition=W:
ramdisksdipath \Recovery\3f53f540-64cc-11e0-b9ab-9ad00bd2edc5\boot.sdi
Device options
--------------
identifier {3f53f549-64cc-11e0-b9ab-9ad00bd2edc5}
device partition=C:
description Windows Recovery
ramdisksdidevice partition=W:
ramdisksdipath \Recovery\3f53f548-64cc-11e0-b9ab-9ad00bd2edc5\boot.sdi

I tried moving things to my C: drive succesfully,also run this command
Windows7DVD:\BOOT\BOOTSECT /NT60 C: /FORCE
and made sure the C: partition was active before rebooting.

I did reboot using the C: drive as boot drive in the BIOS menu but got an error message.

Disk Read Error Occurred on boot
Press CTRL+ALT+DEL to reboot.
Ok,I changed back to the initial settings and the PC loaded Windows normally.

After trying to use EasyBCD to "Change boot drive" and rebooted,the same happened again.

So,my question is: What do I do to end this mess?!?
I d like to format the W: drive and use the drive space for something else.
Can you help me please?
Thank you in advance.
N.

PS.I m running a PRimo RAMDISK software but I dont think this has anything to do with this.
 
Last edited:
#5
Well,just like that?
Do I need to move all identifiers again before entering this command or just do it after changing boot drive with EasyBCD?
Btw,I tried using the DISKPART command in recovery and all drive letters assigned to my HDDs are different than those in Windows.
I mean that W: was E: and that confused me more.
Also SCANOS cannot find a Windows installation.I mean what the hell is going on? Obviously I m missing something.
N.

PS.This is my situation right now.
Capture.PNG
 
Last edited:

Terry60

Knows where his towel is.
Staff member
#6
Boot letters are not "real". They are virtual labels given to devices/partitions by a particular OS (i.e. they are just entries in its registry).
It follows that any/every OS will see them uniquely/differently unless the end user uses the "change disk letter" capability of the Disk Management snap-in.
The repair disk is an OS in its own right, so it will label the partitions differently. That doesn't mean that they will have changed when you get back into your normal environment.
It causes great confusion and sometimes damage when users who have not taken the trouble to label their partitions physically, apply changes in the wrong place, but you have used volume labels, so you are not in any doubt about which partition is which, regardless of what letter the current OS might be using. (The volume label is physically associated with the partition (in the MBR partition table), so all OSs (even Linux which doesn't assign any letter) will see that label the same way.).
There is also scope for confusion in the words boot and system.
EasyBCD (and the rest of the galaxy) uses "boot drive" in the sense that that's where the boot files are.
Unfortunately MS has a topsy-turvy view of the use of those words

Disk Management flags have the following meanings
"boot" = "this is the system you're running"
"system" = "this is where I found the boot files for the currently running system"
"active" (on the first HDD in the BIOS boot sequence) = "this is where I started the search for the boot files"
"active" (on subsequent HDDs in the BIOS boot sequence) ="this is where I will look if I don't find something in the MBR on the first HDD"

I hope that helps to sort out any confusion you may be suffering
 
#7
Thank you for the clarification! :smile:
As far as the problem of moving the boot part to the system partition is concerned,how should I proceed?
Any tips or solution?

bootsect.exe /nt60 all /force
This didnt work either!

N.
 
Last edited:

Terry60

Knows where his towel is.
Staff member
#8
Last edited:
#9
Ι did do that,but I just read this:

EasyBCD will not delete or remove boot files from the current boot partition. As a result, you may revert to it without difficulty or dataloss but you will also need to remove them yourself at a later time.
Does this mean that PCDEDIT will still pick up the Boot files in W: ?

Also,no matter what I ve tried I still cannot boot from my Hybrid SSD.
At some point I lost my Windows Activation too.
When I try to boot from the HSSD I still get the message:

Disk Read Error Occurred on boot
Press CTRL+ALT+DEL to reboot.
I m beginning to think that this is indeed a BIOS settings problem.

My BIOS picks up both disks during POST.
Sata configuration is as follows:
SATA Channel : Enabled.
Sata 1-4 : AHCI.
Sata 5-6 : IDE.
(The ASUS manual states that setting the last on to IDE instead of AHCI allows the
system to recognise the optical drives connected to SATA ports 5/6 when installing OS)

If I change all to AHCI there s no boot at all.
BIOS doesn't even pick up my Primary IDE drive (W) anymore.

Also with my current configuration when I enter the BIOS menu,
under the DISKS Tab (called something like that anyway) I can only
"see" the Primary IDE and one of my SATAs but NOT the Hybrid SSD.
All the disks show up afterwards though.in a separate page, just
before the system loads Windows Welcome screen.

So,maybe it all has to do with changing the SATA port I have the HybridSSD
connected to in order to make the BIOS pick it up first? Maybe Port 5/6?
Will changing the port affect my Windows drive letters or anything it shouldn't?
I cant seem to think of another solution right now.
N.
 
Last edited:

Terry60

Knows where his towel is.
Staff member
#10
The fact that your W is still "system" shows that the PC is still using that as the boot device.
The problem, if you've copied the boot files to C, must be with your BIOS boot sequence.
You are changing the sequence in the HDD sub-menu of the "Boot" section in the BIOS setup menu ?
The SATA channel sequence in the general menu is of no consequence for booting.
 
#11
Yes,of course.I did change the boot priority to make the system boot from the HSSD (C) but every time I get the "Disk Read Error".
I m lost at this point.I have no idea what to try next.Thing is that now I can delete the 29GB my old OS installation was using.
If I try to format it I wont be able to boot.BOOT folder and hidden files must be there in order to log into my current Windows OS.
N.
 

Terry60

Knows where his towel is.
Staff member
#12
I think it's going to require some research into your BIOS settings to discover why it won't let you boot from the SSD.
That's the key. If you can't make it stop going to the W disk, you can't do what you want with it.
I don't have any SSDs so it's not a problem I've encountered.
 
#13
I know.Here are some info about my motherboard.


My motherboard is an ASUS M4A88T-V EVO/USB3.
It has a separate controller for SATA ports 5/6 in order to give you the option to make
them IDE under SATA config menu and let you install an OS via an optical SATA drive.
Thats all I know as far as this is concerned.

Well,to tell you the truth I just rearranged the HDDs using my motherboards SATA ports
and still nothing.In fact,I can boot from every other HDD (In my pursuit of solving this mystery
I've used a prompt command to copy BOOT files to them.I just do not remember the exact command right now),
but not from this Hybrid SSD drive which oddly enough has the Windows 7 system files still on it.

Take a look at these BIOS screens I took.

Here you can see how there are different prefixes the BIOS uses for the HDDs.
I ve since,moved them around so that the SSD (ST9500) got the prefix HDD and then SATA.
Both times the system returned with a DISK READ ERROR.

(See first attachment!)

This photo shows the only IDE drive I have installed plus the SATA CDROM
and whichever HDD is on SATA6 (same channel).
Even when mounting the SSD as SATA6 I couldn't get anything more than the same
DISK READ ERROR during POST.

DSC_0115.jpg

Well,for my sanity,I ll leave the whole problem as it is.
It s really only a problem of not formatting the infamous W partition.
I still can delete my old Windows 7 system files and use the partition as storage.
Anyway,Terry I really thank you for your replies!
N.
 

Attachments

Terry60

Knows where his towel is.
Staff member
#14
It's worth persevering to boot from the SSD because it should make the boot appreciably faster.
Is that 2nd screenshot the HDD sub-menu of the boot menu ?
Have you used the "+" key to shuffle your SSD to "1st Drive" ?
 
#15
Yes,of course.I dont think I ll bother more with this problem.
I m about to install Windows 8 anyway.
I m just gonna do it with only the SSD attached to the system this time.
I m not taking any chances this time around.
N.
 

Terry60

Knows where his towel is.
Staff member
#16
Sorry, don't wish to be patronizing, but we get a huge variation of expertise and experience amongst our new posters, and it's not apparent till we get to know them better which end of the scale they're at.
I've spent days before now trying to help users who are elbow deep in the advanced and esoteric detail, only to discover that they never actually bothered with the "bleedin' obvious" !
 
#17
Oh,no dont get me wrong! I absolutely agree with you and I would have asked the same question if I was you!
Its just that what's happening to my PC is such a weird case.Also I ve tried anything on my part up to re arranging
all the HDDs around my motherboard's SATA slots and also spent 4-5 afternoons trying software modifications.
I m almost certain I did what I could.Anyway,I m into PCs since I was 10 years old with an 80286 and all this time
I could troubleshoot a wide variety of software and hardware problems by myself or with the aid of forums.
This one though is something I can t figure out...
Anyway,I really thank you for your efforts! :smile:
N.
 

mqudsi

Mostly Harmless
Staff member
#18
The usual final solution is to set up your system the way you want it, even if it doesn't boot, then use a repair CD to fix the bootloader.