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: Newest
  1. Anonymous
    2018-02-16T03:45:58+00:00

    I see no RAM defect in there. The whole thing (you didn't post all of it) looks fairly identical to mine. It's OK to have different GUIDs & partition/volume numbers.

    Microsoft Windows [Version 10.0.16299.248]

    (c) 2017 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>bcdedit -enum all

    Firmware Boot Manager


    identifier              {fwbootmgr}

    displayorder            {bootmgr}

                            {140ab3f9-3491-11e7-a4a0-952787f57a8e}

                            {140ab3fa-3491-11e7-a4a0-952787f57a8e}

    timeout                 1

    Windows Boot Manager


    identifier              {bootmgr}

    device                  partition=\Device\HarddiskVolume2

    path                    \EFI\Microsoft\Boot\bootmgfw.efi

    description             Windows Boot Manager

    locale                  en-US

    inherit                 {globalsettings}

    default                 {current}

    resumeobject            {140ab404-3491-11e7-a4a0-952787f57a8e}

    displayorder            {current}

    toolsdisplayorder       {memdiag}

    timeout                 30

    Firmware Application (101fffff)


    identifier              {140ab3f9-3491-11e7-a4a0-952787f57a8e}

    description             Onboard NIC(IPV4)

    Firmware Application (101fffff)


    identifier              {140ab3fa-3491-11e7-a4a0-952787f57a8e}

    description             Onboard NIC(IPV6)

    Windows Boot Loader


    identifier              {140ab3fe-3491-11e7-a4a0-952787f57a8e}

    device                  ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{140ab3ff-3491-11e7-a4a0-952787f57a8e}

    path                    \windows\system32\winload.efi

    description             Windows Recovery Environment

    locale                  en-us

    inherit                 {bootloadersettings}

    displaymessage          Recovery

    osdevice                ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{140ab3ff-3491-11e7-a4a0-952787f57a8e}

    systemroot              \windows

    nx                      OptIn

    bootmenupolicy          Standard

    winpe                   Yes

    Windows Boot Loader


    identifier              {current}

    device                  partition=C:

    path                    \WINDOWS\system32\winload.efi

    description             Windows 10

    locale                  en-US

    inherit                 {bootloadersettings}

    recoverysequence        {f122fa9e-b3ff-11e7-9217-d7700d4f6e45}

    displaymessageoverride  Recovery

    recoveryenabled         Yes

    isolatedcontext         Yes

    allowedinmemorysettings 0x15000075

    osdevice                partition=C:

    systemroot              \WINDOWS

    resumeobject            {140ab404-3491-11e7-a4a0-952787f57a8e}

    nx                      OptIn

    bootmenupolicy          Standard

    Windows Setup


    identifier              {7254a080-1510-4e85-ac0f-e7fb3d444736}

    device                  ramdisk=[C:]$WINDOWS.~BT\Sources\SafeOS\winre.wim,{140ab406-3491-11e7-a4a0-952787f57a8e}

    custom:11000043         partition=C:

    custom:11000083         partition=C:

    path                    \windows\system32\winload.efi

    description             Windows Rollback

    locale                  en-US

    custom:12000044         $WINDOWS.~BT\Sources\Panther\bootstat.dat

    inherit                 {bootloadersettings}

    osdevice                ramdisk=[C:]$WINDOWS.~BT\Sources\SafeOS\winre.wim,{140ab406-3491-11e7-a4a0-952787f57a8e}

    custom:21000152         partition=C:

    systemroot              \windows

    nx                      OptIn

    bootmenupolicy          Standard

    winpe                   Yes

    Windows Boot Loader


    identifier              {f122fa9e-b3ff-11e7-9217-d7700d4f6e45}

    device                  ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{f122fa9f-b3ff-11e7-9217-d7700d4f6e45}

    path                    \windows\system32\winload.efi

    description             Windows Recovery Environment

    locale                  en-US

    inherit                 {bootloadersettings}

    displaymessage          Recovery

    osdevice                ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{f122fa9f-b3ff-11e7-9217-d7700d4f6e45}

    systemroot              \windows

    nx                      OptIn

    bootmenupolicy          Standard

    winpe                   Yes

    Resume from Hibernate


    identifier              {140ab3fc-3491-11e7-a4a0-952787f57a8e}

    device                  partition=C:

    path                    \Windows\system32\winresume.efi

    description             Windows Resume Application

    locale                  en-US

    inherit                 {resumeloadersettings}

    recoverysequence        {140ab3fe-3491-11e7-a4a0-952787f57a8e}

    recoveryenabled         Yes

    isolatedcontext         Yes

    allowedinmemorysettings 0x15000075

    filedevice              partition=C:

    filepath                \hiberfil.sys

    bootmenupolicy          Standard

    debugoptionenabled      No

    Resume from Hibernate


    identifier              {140ab404-3491-11e7-a4a0-952787f57a8e}

    device                  partition=C:

    path                    \WINDOWS\system32\winresume.efi

    description             Windows Resume Application

    locale                  en-US

    inherit                 {resumeloadersettings}

    recoverysequence        {f122fa9e-b3ff-11e7-9217-d7700d4f6e45}

    recoveryenabled         Yes

    isolatedcontext         Yes

    allowedinmemorysettings 0x15000075

    filedevice              partition=C:

    filepath                \hiberfil.sys

    bootmenupolicy          Standard

    debugoptionenabled      No

    Windows Memory Tester


    identifier              {memdiag}

    device                  partition=\Device\HarddiskVolume2

    path                    \EFI\Microsoft\Boot\memtest.efi

    description             Windows Memory Diagnostic

    locale                  en-US

    inherit                 {globalsettings}

    badmemoryaccess         Yes

    EMS Settings


    identifier              {emssettings}

    bootems                 No

    Debugger Settings


    identifier              {dbgsettings}

    debugtype               Local

    RAM Defects


    identifier              {badmemory}

    Global Settings


    identifier              {globalsettings}

    inherit                 {dbgsettings}

                            {emssettings}

                            {badmemory}

    Boot Loader Settings


    identifier              {bootloadersettings}

    inherit                 {globalsettings}

                            {hypervisorsettings}

    Hypervisor Settings


    identifier              {hypervisorsettings}

    hypervisordebugtype     Serial

    hypervisordebugport     1

    hypervisorbaudrate      115200

    Resume Loader Settings


    identifier              {resumeloadersettings}

    inherit                 {globalsettings}

    Device options


    identifier              {140ab3ff-3491-11e7-a4a0-952787f57a8e}

    description             Windows Recovery

    ramdisksdidevice        partition=\Device\HarddiskVolume1

    ramdisksdipath          \Recovery\WindowsRE\boot.sdi

    Device options


    identifier              {140ab406-3491-11e7-a4a0-952787f57a8e}

    description             Windows Setup

    ramdisksdidevice        partition=C:

    ramdisksdipath          $WINDOWS.~BT\Sources\SafeOS\boot.sdi

    Device options


    identifier              {f122fa9f-b3ff-11e7-9217-d7700d4f6e45}

    description             Windows Recovery

    ramdisksdidevice        partition=\Device\HarddiskVolume5

    ramdisksdipath          \Recovery\WindowsRE\boot.sdi

    C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-16T03:14:41+00:00

    Heres the entry

    RAM Defects


    identifier              {badmemory}

    Global Settings


    identifier              {globalsettings}

    inherit                 {dbgsettings}

                            {emssettings}

                            {badmemory}

    Boot Loader Settings


    identifier              {bootloadersettings}

    inherit                 {globalsettings}

                            {hypervisorsettings}

    Hypervisor Settings


    identifier              {hypervisorsettings}

    hypervisordebugtype     Serial

    hypervisordebugport     1

    hypervisorbaudrate      115200

    Resume Loader Settings


    identifier              {resumeloadersettings}

    inherit                 {globalsettings}

    Device options


    identifier              {4ff9fd7f-0d0f-11e6-912a-d017c2263548}

    description             Windows Recovery

    ramdisksdidevice        partition=\Device\HarddiskVolume4

    ramdisksdipath          \Recovery\WindowsRE\boot.sdi

    Device options


    identifier              {5a601776-cc36-11e6-913f-d017c2263548}

    description             Windows Setup

    ramdisksdidevice        partition=C:

    ramdisksdipath          $WINDOWS.~BT\Sources\SafeOS\boot.sdi

    Device options


    identifier              {5a60177a-cc36-11e6-913f-d017c2263548}

    description             Windows Recovery

    ramdisksdidevice        partition=\Device\HarddiskVolume4

    ramdisksdipath          \Recovery\WindowsRE\boot.sdi

    The parameter is incorrect.

    PS C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-16T03:06:15+00:00

    Scroll up the page to where I said:  BCDEdit  -enum  all

    And read the rest of what I posted up there, especially to backup the BCD.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-16T03:02:21+00:00

    [the parameter is incorrect]

    I get

    PS>bcdedit --% /enum {badmemory}

    RAM Defects


    identifier              {badmemory}

    badmemoryaccess         Yes

    badmemorylist           0x199105

    So maybe you need to have badmemoryaccess set too?

    Here's a way (apparently) to find out if you are using that value anywhere

    PS>bcdedit --% /enum INHERIT

    Strangely that does not show badmemorylist being inherited.

    Was this answer helpful?

    0 comments No comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more