

It is for the benefit of others reading the thread who not that familiar with BCD.

I hate to burst all the bubbles in here, but guess what?
I clean installed build 7068 by deleting all partitions from one of my Seagate 500 GB Barracudas, and then using the Win7 Setup program created a single 60 GB partition. I then told Windows to install into that partition, and the setup program informed me that it was going to create a small ~100 MB partition for recovery(?) purposes and would allocate the rest of the space to the Windows Partition.
And it did:
View attachment 6946
It may be because that is the first drive. In all my tests with an active partition present before the drive i install on, not once did it create the partition.
It should work
Don't know what you did but here is a copy of my current configuration
( I did format the C partition first however)
cheers
jimbo
It may be because that is the first drive. In all my tests with an active partition present before the drive i install on, not once did it create the partition.
Installed each version leaked at least 3 times the same way and I concur with YupYup, no "warnings" that it was going to create anything. It just did it. Maybe I never saw the warning because I wanted to let the installer partition the space I allowed it however it chose. I just pointed it at unpartitioned space and let 'er rip. That result was a partition ( C: ) a tad smaller than what I'd guessed and this itty bitty partition with no drive letter assigned. Didn't bother me in the least since other operating systems had been doing that as a best practice seemingly forever.
? I have not had that experience. over the years. Of the partition programs I have used - not many, but including Microsoft's built in manager, I always have to format the partition again. But, perhaps I have not understood what you are indicating by "recreating", or again, is this with SATA drives. I don't have that facility (yet).