Feature update to Windows 10, version 1709 fails to install

I entrust the study of his CBS.log to you, Robert. I saw your work in another thread. Good going to see a wrong drive was getting accessed. My current thoughts...

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

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

(3) Could be problematic to have a clone attached during an upgrade. Windows may seek to pull it into a dual-boot & may have trouble with its system & recovery partitions.

Regarding your RAM Defects...

PS>bcdedit --% /enum {badmemory}

RAM Defects

identifier              {badmemory}

badmemoryaccess         Yes

badmemorylist           0x199105

IIRC, that's a Win 8.1 phenomenon. An upgrade to Win 10 doesn't wipe it. It was my clean install of v.1703 that made that go away, & it hasn't returned after an upgrade to v.1709. See...

https://social.technet.microsoft.com/Forums/en-US/49abeeb2-f2c3-44c1-b9ee-d4faf0c7de91/why-badmemoryaccess-yes?forum=WinServerPreview

Why "badmemoryaccess yes"?

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.)

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

(1) Your CBS.log is "too big to preview".

In fact, I downloaded it and was going to say it is not current enough; all it has is rollback info.  We probably need either the PersistCBS or even the PersistCBS... cab file.   Or something more relevant that I don't know to suggest--which is why I suggest using my PowerShell script to find out what else is available.   ; )

The .nfo file is interesting though.  E.g. the WER file makes me think that there is an interferer active but I'm not finished yet with my analysis.  I intend to respond in the poster's other thread.

FYI

Robert

For the meantime

1.THE CBS log is actually Feb 16. All of them. The download option 10mb is at the right side once you opened the link. 

--i change the cbs log into cbs.old   restart and attempted the ISO updated which resulted in error of 1ST PHASE BOOT. thus the new cbs log which is 10mb--

(1) Your CBS.log is "too big to preview". Please delete everything in it except the date of the run, which I guess was 2/16/18. Then I'll try again.

(2) Please answer the other questions in my last post - you answered item (7) only. Give me an answer or a comment on items (1) through (6). For item (1), the question is: Did you go into BIOS Setup & move something above the Windows Boot manager? But go answer them all.

(3) I'm not sure I like seeing the clone HDD plugged in at the same time as the original (or visa versa). That's a third candidate for the inability to upgrade. The upgrade may not like that.

(4) Do you have a Recovery USB Drive (ask Cortana for "Recovery" to make one) or Win 10 Installation media? This may be needed in case of catastrophe. Let us test it this way...

Edit: The BU folder will not auto-create. So, first:  MD  C:\BU

(a) At a DOS Prompt:   BCDEdit  /Export  "C:\BU\BCD Backup"

                          Also:   BCDEdit  /Export  "C:\BU\BCD Copy"

Now you have a backup BCD that can be recovered. Also, you have a copy that we can play with.

(b) Boot to the Recovery USB drive or to the Installation media.

      If to the Installation media, choose "Repair this computer" (instead of to install).

(c) At the "Choose an option" screen, click "Troubleshoot > Advanced Options > Command Prompt".

(d) At the Command Prompt:   DIR  C:\BU  /a

                                       Also:   BCDEdit

Do you see the files listed? If not, I guess try letter D:, in case they have switched. Which letter gave you the files? Did you get output for BCDEdit, (just to prove it is there should it become necessary)?

(e) Close the Command Prompt, & click "Continue" to return.