You don't have to remove the HDD while installing Windows on SSD!

Liby195

Distinguished
Jul 29, 2011
31
0
18,530
The consensus is that you should remove any secondary HDDs you might have before installing Windows on a SSD for two main reasons:

1) avoid formatting the wrong drive and losing backup data.
2) avoid Windows putting installation file on the secondary drives.

However, I think this only applies if you are worried about the first reason.
If you are starting out fresh for all your drives, or don't mind losing data on the secondary drives,
then you don't have to worry about the second reason. There is a work around to stop Windows from putting installation files on secondary drives without removing any HDDs.

I asked in a thread below about what's better between:
allocating unallocated drive space while installing Windows
and
allocating in Windows using Computer Management

The answer was they're both the same. So if this is the case, during Windows you can simply delete your secondary drives into unallocated state, and proceed to installing Windows on your drive of choice. Since the drive is unallocated Windows will not be able to find any secondary drives to put files on. And once the installation is finished, you can safely allocate and format the other drives.

I apologize if this is a "DUH, everyone knew that already" thing, but it was a revelation to me just now, and thought it was good to share so that people can avoid the hassle of opening up their chassis and unplugging the HDD and whatnot.

But if I got this all wrong, please correct me, as this is only my assumption based on shallow knowledge.
 
Solution
And whether it's the 'installation file' or the 'system reserverd boot information', wouldn't it stay away from the second drive if we didn't allocate it while installing Windows?

Not necessarily. Windows may create that partition anyway. After all...it's creating a brand new partition on the primary drive. What would prevent it from doing the same on a secondary drive with the System Reserved partition?

I'd say it is easier to have only the designated target drive connected, and know that things are how I want it. Rather than to have multiple drives connected, and come back around and fix if Windows does what it wants, rather than what I want.

Your method might work. I've never tried it. But that seems like more...

USAFRet

Titan
Moderator
Why bother with a workaround if you don't have to? Simply have only the target drive (HDD or SSD) connected when you do the OS install.

And it's not the 'installation file' that gets put on the 'other' drive, but rather the System Reserved boot information. 6 months from now, when you want to use that other drive in a different system and remove it....no boot for you.

Reconnecting the second drive after takes maybe 10 seconds.
 

Liby195

Distinguished
Jul 29, 2011
31
0
18,530


I see your point, and I know I don't HAVE TO have a workaround, but I just thought it was easier to just allocate later.
I mean, I know reconnecting a drive doesn't take much time or effort, but wouldn't you agree allocating is much simpler? Just wondering.

And whether it's the 'installation file' or the 'system reserverd boot information', the point was wouldn't it stay away from the second drive if we didn't allocate it while installing Windows?

I'm arguing with really shallow knowledge, so I'm pretty sure I'll come out wrong, but I'm only arguing for curiousity sake.
 

USAFRet

Titan
Moderator
And whether it's the 'installation file' or the 'system reserverd boot information', wouldn't it stay away from the second drive if we didn't allocate it while installing Windows?

Not necessarily. Windows may create that partition anyway. After all...it's creating a brand new partition on the primary drive. What would prevent it from doing the same on a secondary drive with the System Reserved partition?

I'd say it is easier to have only the designated target drive connected, and know that things are how I want it. Rather than to have multiple drives connected, and come back around and fix if Windows does what it wants, rather than what I want.

Your method might work. I've never tried it. But that seems like more work than simply disconnecting a SATA cable.
 
Solution

Liby195

Distinguished
Jul 29, 2011
31
0
18,530


Well, now you have a point I can't disagree to. Though I still think using the mouse to click a few times is easier than shutting down, opening the computer and unplugging the drive, the possibility that Windows might still create partitions on the second drives voids my argument. I guess it's better to unplug afterall.

Well, thx for clearing this up for me. Though I'd like to hear more opinions on this, I guess I'll also go the unplugging route for now :)