New
#21
One thing I don't understand ...
Generally, when I partition a hard drive, I delete all partitions, format the whole thing, then partition it. I install Windows 10 on the first partition, which has always wound up being partition/volume 4. Once that's done, I install Windows 10 Insider on the second partition, which has always wound up being partition/volume 5.
What caused what has historically been partition/volume 5 to wind up as partition/volume 7?
Generally when you clean install windows 10, you delete all partitions and allow windows to create the 4 required partitions, which usually the OS partition is applied to Partition 4Generally, when I partition a hard drive, I delete all partitions,format the whole thing, then partition it.I install Windows 10on the first partition,which has always wound up being partition/volume 4.
Somehow you had several other EFI partitions created.. ( which is the unknown how )
I would assume you used a common method "here" to re-create the EFI partition by shrinking C:\
My guess is that most likely a batch file was run several times to re-create the EFI
Not exactly what I do. I first partition the drive into two partitions. Then, when I install the first OS, Windows tells me it will create additional partitions it needs. Then I install the second OS and Windows creates additional partitions it needs.
No, I didn't shrink anything. And, the first time I did anything with an existing partition was to expand C:\ to include the recovered 200 MB from what I did today.
What I think happened is that while Windows didn't see the second partition, it did create the other two EFI partitions each time I tried to install to the second partition.
Well, it seems I've heard the last from Samsung! Obviously there's something different with this drive than from others, but Samsung refuses to recognize it.
Their final response:
I think that says it all for Samsung support. I won't be buying another Samsung product any time soon!Wynona,
The drive does support dual booting, but we do not offer any kind of support in setting it up. You are correct you should be able to partition the drive to what you need and simply be able to install to it.
It's nothing wrong with Samsung. You had 2 EFI partitions ie. 5 and 6 so D drive is 7 even after you delete 5, 6. If D drive is still empty, delete it then re-create it, you'll get the partition number in sequence again ie. 1,2,3,4,5.I think that says it all for Samsung support. I won't be buying another Samsung product any time soon!
By the way, use the command James gave you in post #21 to install Windows in D drive, it's quicker and you can do it while Windows is running.
OK, thanks TopGun. Yes, D:\ is still empty, so I'll delete it and re-create it so it's in sequence.
I'll have to read his instructions a few times, but I should be able to do it. I'm always game to learning something new, as long as I don't mess things up.
I cannot believe I've been dual booting all these years and this is the very first time Windows didn't cooperate.
I'm also going to re-download the ISO from UUPDump, just in case what I have is messed up.
Good morning, Kyhi.
I tried to follow your instructions and use DISM to install to D:\, however, I got this:
It looks to me as if I'm right back where I started . . . For some reason, D:\ can't be found when I'm trying to install.Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell Installing PowerShell - PowerShell | Microsoft Docs
PS C:\Windows\system32> Dism /Apply-Image /ImageFile:"F:\Sources\Install.wim" /Index:2 /ApplyDir:\
Deployment Image Servicing and Management tool
Version: 10.0.18362.1
Error: 87
The parameter is incorrect.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
PS C:\Windows\system32>