Feature update to Windows 10, version 1709 fails to install

Anonymous
2017-12-15T05:07:39+00:00

Hi, I am trying to install the Creators Update on my computer, but it fails and has to recover every time I try. What system information should I post to help troubleshoot why the update continues to fail?

Thanks!

-Andrew

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

153 answers

Sort by: Oldest
  1. Anonymous
    2018-02-22T06:02:09+00:00

    It's one at a time, & hit "Enter" after each. You've done "BCDEdit" before. You know that goes on a line by itself & to hit "Enter" after typing it.

    "DIR  C:\BU  /a" will list the contents of the BU folder on C:. I want you to see "BCD_Backup" in there.  "/a" says to list the files no matter what the file attributes are - hidden, system, etc.

    If you get no listing, then try:  "DIR  D:\BU  /a". That D:drive of yours is a bug-a-boo in more ways than one. It may switch letters with the C:drive when in the Recovery Environment. We need to know. The command to recover your BCD (if necessary) may be either of these...

    BCDEdit  /Import  C:\BU\BCD_Backup

        ===== OR =====

    BCDEdit  /Import  D:\BU\BCD_Backup

    And you would hit Enter after it. Note: That's the new BCD backup - the one with the underline in its name. That way, you don't need to type quotes around it.

    I was told long ago by a venerable MVP (but I can't recall his name) that Windows doesn't like a clone to be attached at the same time as the drive it was cloned from. That could be the real root of the problem the computer has with doing the upgrade. It could be confusing the issue of BCD formation. Windows needs to adjust the BCD during the upgrade. We might have trouble regenerating it too.

    Why do you have both attached? As I said before, really, the D:drive should be wiped. And system image backups should be put there instead.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-22T06:11:41+00:00

    Thanks for the feedback

    I am surprised by this statement

    **"**I was told long ago by a venerable MVP (but I can't recall his name) that Windows doesn't like a clone to be attached at the same time as the drive it was cloned from. That could be the real root of the problem the computer has with doing the upgrade"    ....

    perhaps Paragon software in a way could be at fault.  anyway im also thinking of removing the HDD and try the upgrade. Il look for a pc shop first and ask for it to be removed temporarily. would that work? if not, il try your other method.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-22T06:24:47+00:00

    Yes, at the time, I was upgrading from Win 8.1 to the first Win 10. Not only did I make two system images first onto external media with two different apps, but I also made a clone out of extreme caution. Then, I thought, why not have both Win 8.1 & Win 10 attached? He not only said it was doubtfully legal - but that it wouldn't work. I can see now he might have been thinking of the BCD.

    Anyway, yes, by all means, have a shop detach the parent of the clone. On second thought, don't wipe it until you know the clone on the SSD is really working.

    OK. Good luck, & keep us informed.

    Edit: It's possible that BCD is bad enough that it still will prevent an upgrade even with the HDD detached now. Have the shop do both: detach the HDD first, & then regenerate the BCD. After that, try the upgrade.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-22T13:23:07+00:00
    1. remove HDD and kaspersky
    2. tried w10 ISO 1709 Clean install
    3. failed. same msg 

    0xC1900101 - 0x20017 Installation failed during safe OS phase with an error during boot operation

    i didnt read ur EDIT portion after that.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-02-22T16:07:42+00:00

    0xC1900101 - 0x20017 Installation failed during safe OS phase with an error during boot operation

    We could check if your setupact.log has changed at all.  E.g. it might be something else now.

    Was this answer helpful?

    0 comments No comments