Feature update to Windows 10, version 1709 fails to install

1. setupack log is that in Windows BT and windows old folder after a failed upgrade right?
2. if thats the case,i have deleted those. anyway il install it again under same circumstances

(1) Let me see a full:    BCDEdit -enum  all

(2) What is your progress in getting to a Command Prompt of external media?

     You must get there to delete the current BCD before "BootRec /RebuildBCD" will do a good job.

(3) But let's see what Robert will discover in your logs first.

Log files

1. https://www.dropbox.com/sh/7gjm6wdcakrhw0s/AACN-pI5GFWQoyjMzcmKqGFya?dl=0

EDITED:

2.(1) Let me see a full:    BCDEdit -enum  all

            darned, i just re attached my HDD. il try it again later

Darn, indeed. Anyway - when you said: "2. tried w10 ISO 1709 Clean install" - it can't be true.

(1) An ISO cannot do a clean install. It must be burnt to DVD & booted through the UEFI boot choices menu to do a clean install. (Or, an Installation USB drive can be booted.) Then, you must wipe the SSD to unallocated space, & install into that. In that case, everything would be new - beautiful new partitions & a brand new BCD. (Edit: However, I would unplug the HDD first. The clone parent doesn't belong, & its partitions may have an ill affect on the new BCD.) 

(2) If you don't wipe the existing partitions off the SSD, but only make a new area of unallocated space, & install into that - it is a dual boot. The v.1709 Windows partition would be clean & it would contain a folder that holds its own Recovery Environment. But the v.1511 EFI (system) partition would be kept, & its BCD would be shared with v.1709. The existing Recovery Partition still belongs to v.1511.

(3) If you open an ISO in File Explorer, click its Setup.exe, & directed it to install into the v.1511 Windows partition - that is an upgrade install. It is the same as if you took the upgrade through Windows Update. You end up with v.1709, & a new v.1709 Recovery Partition. The v.1511 Recovery Partition gets emptied but is not deleted. And the EFI (system) partition is taken over by v.1709, but the BCD is not fresh. It is altered but carries junk entries from v.1511 days.

Log files

Not the right ones.  The ones you had before were better, especially the setupact.log files you chose.  I was surprised not to find a single instance of 16299 (word) in the CBS.logs.   So whatever they show is all about your 1607 version (14393) doing I know not what.

HTH

Robert