Cannot Install Windows 10 to Second Partition on Samsung 860 EVO SSD

Page 3 of 8 FirstFirst 12345 ... LastLast

  1. Posts : 29,075
    Windows 10 21H1 Build 19043.1023
    Thread Starter
       #21

    Kyhi said:
    as seen by your command window pic > remove partition 5 & 6

    thus the two Fat32 EFI partitions between > C=partition 4 and D=partition 7

    then mount the 19002 ISO and use dism to apply the image to D:
    it is assumed the Mounted ISO will be driveletter F and the UPP Dump Pro index of 2
    Code:
    Dism /Apply-Image /ImageFile:"F:\Sources\Install.wim" /Index:2 /ApplyDir:D:\
    then
    Code:
    bcdboot D:\Windows
    reboot to continue
    Duhhhhhhhhhhhh! How did I mess that one up so much! Now you know why I asked for advice!
      My Computer


  2. Posts : 29,075
    Windows 10 21H1 Build 19043.1023
    Thread Starter
       #22

    Here's New Disk Managment

    Cannot Install Windows 10 to Second Partition on Samsung 860 EVO SSD-new-disk-management.png

    And here's New Mini Tool

    Cannot Install Windows 10 to Second Partition on Samsung 860 EVO SSD-new-mini-tool.png

    I think I did it right!
      My Computer


  3. Posts : 29,075
    Windows 10 21H1 Build 19043.1023
    Thread Starter
       #23

    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?
      My Computer


  4. Posts : 3,840
    Windows 3.1 to Windows 10
       #24

    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.
    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 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
      My Computer


  5. Posts : 29,075
    Windows 10 21H1 Build 19043.1023
    Thread Starter
       #25

    Kyhi said:
    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 4
    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.

    Kyhi said:
    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
    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.
      My Computer


  6. Posts : 29,075
    Windows 10 21H1 Build 19043.1023
    Thread Starter
       #26

    So, here is what DiskPart shows me now:

    Cannot Install Windows 10 to Second Partition on Samsung 860 EVO SSD-new-diskpart.png

    What I think I should be seeing is:

    Partition 1
    Partition 2
    Partition 3
    Partition 4
    Partition 5

    Could the fact that I'm seeing Partition 7 instead of Partition 5 possibly be key to why I haven't been able to install my Insider Preview?
      My Computer


  7. Posts : 29,075
    Windows 10 21H1 Build 19043.1023
    Thread Starter
       #27

    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:

    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.
    I think that says it all for Samsung support. I won't be buying another Samsung product any time soon!
      My Computer


  8. Posts : 2,790
    Linux Mint 20.1 Win10Prox64
       #28

    I think that says it all for Samsung support. I won't be buying another Samsung product any time soon!
    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.

    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.
      My Computer


  9. Posts : 29,075
    Windows 10 21H1 Build 19043.1023
    Thread Starter
       #29

    topgundcp said:
    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.

    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.
      My Computer


  10. Posts : 29,075
    Windows 10 21H1 Build 19043.1023
    Thread Starter
       #30

    Kyhi said:
    as seen by your command window pic > remove partition 5 & 6

    thus the two Fat32 EFI partitions between > C=partition 4 and D=partition 7

    then mount the 19002 ISO and use dism to apply the image to D:
    it is assumed the Mounted ISO will be driveletter F and the UPP Dump Pro index of 2
    Code:
    Dism /Apply-Image /ImageFile:"F:\Sources\Install.wim" /Index:2 /ApplyDir:D:\
    then
    Code:
    bcdboot D:\Windows
    reboot to continue
    Good morning, Kyhi.

    I tried to follow your instructions and use DISM to install to D:\, however, I got this:

    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>
    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.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:19.
Find Us




Windows 10 Forums