Windows 10 Clean Install  

dst11 said:

The tutorial says to:

Is that safe to do? I read "right click on each partition and volume on the disk and click on Delete Volume" and my heart skipped a beat! I'm not criticizing. I'm just asking.

Hi,
Maybe this would be the easiest thing to do then delete the little partition and 10 has enough room to create a new 450mb one.

Bootmgr - Move to C:\ with EasyBCD - Windows 7 Help Forums

Hi,
Man looking at you win-7 disk looks like you missed the first step to make the disk gpt before doing the rest like the fat32 and the recovery partitions that is usually seen when it's a gpt disk not mbr.
You did some fancy footwork but forgot one step

ThrashZone said:

Hi,
I haven't done it personally win-7 as far as I know isn't compatible with gpt unless some kung fu is done before the install.

I don't think I know how W7 was installed. The computer came with W7 preinstalled. I have a UEFI BIOS but it is in LEGACY mode, not in UEFI mode.

As a storage devise gpt is nothing for 7 deal with.

'nothing for 7 deal with' as in 'nothing W7 can deal with'?

How was the mini tool instructions ?

do you mean the convert MBR to GP instructions? they were fine. I was scared a bit by the 'delete' step. see my post

Do you have a system image of 7 disk now ?

what? where did that came from? why do I need that?

- - - Updated - - -

ThrashZone said:

Hi,
Maybe this would be the easiest thing to do then delete the little partition and 10 has enough room to create a new 450mb one.

Bootmgr - Move to C:\ with EasyBCD - Windows 7 Help Forums

You mean now the boot sector is on the 39MB FAT partition in the beginning of Disk 2, and to use EasyBCD to move it to C: [that's the the W7 drive], and then delete the 49MB FAT partition so I have 1 more 'primary drive' designation available?

- - - Updated - - -

ThrashZone said:

Hi,
Man looking at you win-7 disk looks like you missed the first step to make the disk gpt before doing the rest like the fat32 and the recovery partitions that is usually seen when it's a gpt disk not mbr.
You did some fancy footwork but forgot one step

I didn't create those partitions! The computer came like that. I only shrunk C:OS(NTFS) and created E: DATA(NTFS) in the space that was left.

Hi,
System image the win-7 disk so if the below goes bad at the least you can return it back the way it was.

Afterwards use the free minitool conversion mbr to gpt.
See if win-7 still boots and works okay
If it does you're all set to install win-10 on the partition setup for it.

NavyLCDR said:

Using method 1, with the Windows 7 partition moved to the right, you are deleting the system and recovery partitions before Windows setup really starts working on the drive. Without the system partition there, Windows setup just sees the Windows 7 partition as a data partition, not an OS. Using method 2, you are leaving the system partition in place, that tells Windows setup that the Windows 7 partition is really an installed OS, so Windows 10 sets up dual booting with it.

Oh I see. It all depends on the installer being able to see W7 is there. Not in any left/right silliness I came up with.

My reply was mostly to @Matthew Wai's statement that you have to delete all partitions. You don't have to delete all partitions. In the OP's situation, disconnecting the Windows 7 HDD would be similar to method 1 in my post. There won't be a system partition to tell Windows 10 setup about any other installed OS.

If the HDD were left disconnect,

you mean connected, right?

that would be similar to method 2 in my post - there will be a system partition present on the HDD, and Windows 10 setup is likely to see that and set up dual booting with the system partition remaining on the HDD. Although that also depends on firmware settings. If the firmware settings prevent the computer from booting from the HDD, with an error such as "No OS present" or "No boot device", then the likely outcome of an install to the SSD would be method 1 - Windows 10 booting only with the system partition on the SSD.

Doesn't @dst11 want to install Windows 10 on disk 1, which is a completely blank unallocated SSD? Or am I missing something here?

Hi,
Could of been
With all the partition talk thought he wanted both os's on the ssd eventually
Heck 10 is only 35gb's

ThrashZone said:

Hi,
Could of been
With all the partition talk thought he wanted both os's on the ssd eventually
Heck 10 is only 35gb's

Well, good grief.... just boot from the Windows 10 installation USB flash drive, select the custom install option, then click on the drive 1 unallocated space and click next...

Another method for converting MBR to GPT without data loss:
How to convert MBR partition table to GPT without data loss
I used this method before clean-installing Windows 10 in 2017. See below:

Why all this talk about canverting MBR to GPT? It is 100% irrelevant to installing Windows 10 to a blank (unallocated) SSD.

It just isn't that complicated. Boot the computer from the Windows 10 USB flash drive. Select the custom install option, click on the unallocated space, then next.