Feature update to Windows 10, version 1709 fails to install

hey

sorry i havent been that active much. Im on a deadline at work so i have to use my laptop extensively. i havent given up yet. will post soon

We had begun work on your obit, but will put it aside a bit.

HI. Here is an update. I tried using a 1703 USB bootable drive and i choose a partition to install and windows cant be installed.

1. choose PRIMARY TYPE system  Drive ) partition 3 Samsung 850 . after i choose that one it says "we couldnt create a new partition or locate an existing one. see set up log files.

see pics

Hi Robert. i have made an update using 1703 iso. please see above. thank you

(1) At your UEFI boot options screen...

(a) It is correct to have the UEFI:Sandisk entry (Win 10 Installation media) below the Boot Manager.

(b) The top entry is the horrible {BootMgr} on page 5 of this thread. But it skips over the junk to boot "{current}" (Windows 10). Your Windows boot options screen (not the UEFI screen above) offers a choice for Windows 10 Home. But that wants to boot Windows.old. There is no Boot Loader entry in your BCD for any of the junk. I can't tell whether it is the Win 10 on the SSD (Disk 0) that boots.

(c) The third entry in your UEFI menu is this...

Windows Boot Manager

identifier            {08fe7334-d4d4-11e6-9155-d017c2263548}

device                unknown

path                   \EFI\Microsoft\Boot\bootmgfw.efi

description        Windows Boot Manager on Disk 0

That is dysfunctional. I wouldn't want to select it.

(d) The fourth entry is...

Windows Boot Manager

identifier            {1be2dc76-d4d8-11e6-9155-d017c2263548}

device                partition=\Device\HarddiskVolume1

path                   \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

description        Windows Boot Manager on Disk 0

locale                en-US

inherit               {globalsettings}

default              {current}

resumeobject    {5a601777-cc36-11e6-913f-d017c2263548}

displayorder     {current}                                                             << Windows 10

                         {5a60177b-cc36-11e6-913f-d017c2263548}     << Windows.old (Windows 10 Home)

toolsdisplayorder  {memdiag}

timeout              0

That is identical to {BootMGR} but without the junk. It doesn't reach from Disk 0 to Disk 1 or vice versa. It will boot Windows 10 or it will try to boot Windows.old. I think whichever disk holds the current BCD also holds the Windows that boots.

(2) I can guess that UEFI directs the boot to one disk or the other depending on which entry is selected. That could account for the difference in the parenthesized data. Then, looks like the top one (P3: HGST) goes to the HDD & the bottom one (P0: Samsung SSD) goes to the SSD. Could be worth a try to switch the two in the UEFI boot order. Then - if it works - I guess what happens is what Carmack wrote in here...

https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/clean-install-windows-10/1c426bdf-79b1-4d42-be93-17378d93e587

Clean Install Windows 10

" (Note:  If you did not rescue files stranded in C using the bootable media step earlier, you can save them here.  Instead of deleting partitions, just click on C and choose Next without deleting or formatting.  This will archive your files in C:\windows.old.  But it is not as clean of an install.)"

Sounds like you get a clean install (not an upgrade install) but end up with a Windows.old that holds the prior OS. I'm unsure what happens with the other partitions on the Disk - the system & recovery partitions. Hopefully they are wiped & replaced. Then, the system partition will have a fresh BCD & the prior recovery partition does not stay behind though empty (as it does in an upgrade install).

(3) But I still think the HDD should be unplugged or wiped. Windows isn't meant to have a clone & its parent plugged in at the same time. That isn't the way a dual boot should be.