Feature update to Windows 10, version 1709 fails to install

Regarding the boot options.

I did changed the bootsequence. i tried using the HDD as boot drive. thinking it has something to do with Samsung EVO M2 SSD. anyway the boot options are

BOOT 1 

           2

           3

i hve returned the boot options on its original set up.

BOOT 1    0

           2    SAMSUNG

           3    HGST HDD

Thanks for your feedback.

Im a bit confused on

(1) UEFI must be set to boot the Windows Boot Manager during an upgrade.

              are you saying my laptop is not set on UEFI on boot? If not, how do i enable it?

(2) C:\Windows.old should not pre-exist the upgrade.

             this folder has been deleted some time ago.

(1) No, I think you are in UEFI mode. But, as you confirmed, it looked like you had moved - I guess SAMSUNG - to be above the Windows Boot Manager in UEFI (that's the real name for BIOS these days).

So - you say you moved it back down? Then, show me:   BCDEdit -enum {FWBootMGR}

Yours should look different now & will be one less thing we must do to your BCD.

(2) That is very good, that Windows.old does not exist on C:.

(a) Does it exist on the other drive - the D:\drive? If so, I'd delete/rename it there too. Windows may be nosey.

(b) I don't know how references to Windows.old got into your BCD, but I'll add it to the stuff we will delete. Windows is nosey, & may take it as a sign that the folder exists & refuse to do the upgrade.

(3) Have you made a "BCD Backup" & "BCD Copy"? Upload one, so I can get it to play with.

(4) Can you easily disconnect HGST HDD? It would be best to do so during the upgrade. Reconnect it afterward, if you must.

(5) Go back & re-read my posts for any items you may have missed.

I don't know about booting a .vhd or using Hyper-V.

That's what I thought, you never did a clean install on that computer. I did it twice on this Dell Inspiron 3542, once into a dual boot fearful a Dell wouldn't like it. But all my Dell/Intel/Realtek drivers came in nicely on their own during the process. (OK, the Realtek drivers had to be updated, so did the Dell Ethernet driver. They had installed & functioned - but kept asking for a "reboot to complete".) A couple of Dell partitions & an extraneous Win 10, v.1511 recovery partition were wiped the second time. (But now I've got an extraneous v.1703 recovery partition after the upgrade to v.1709). Anyway, the process was 24 minutes/so each time, & Cortana was speaking after 17. I did lose a powerful Dell WiFi toggle keyboard key, but don't miss it. The installation is half the size it was, at least. I don't miss Dell Support Assist, Dell Update or any of the rest - not that I hated Dell. Also, it got rid of every last bit of McAfee.

But yours being a Microsoft computer may not gain so much in cleanliness.

hi ROBERT.

thank you for your time in looking at this. Here are the rest of CBS files

https://www.dropbox.com/sh/k2zlwsbbpkvnuhk/AAAmcpf-StdF9V9\_EybbXcxNa?dl=0

Now, I can't quite recall whether I had a "badmemorylist", though. Maybe run a RAM test, & delete the entry, if you pass. (I do recall running a RAM test once/twice, but not having the list.)

Good idea.  I wasn't aware of this at all.  So far this Surface 2 Pro has just been updated progressively from W8.1 to W10 FCU -- all naturally.  Occasionally I wonder about doing a clean install but then find better things to do.   E.g. I still want to native boot my .VHD for a preview instead of using Hyper-V.   ; )

Thanks for your feedback.

Im a bit confused on

(1) UEFI must be set to boot the Windows Boot Manager during an upgrade.

              are you saying my laptop is not set on UEFI on boot? If not, how do i enable it?

(2) C:\Windows.old should not pre-exist the upgrade.

             this folder has been deleted some time ago.