Once again, thank you.
- i did read in asus rog forums that disabling smart might help. see this
what are your thoughts?
- Yes, time and settings is correct.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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
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.
Once again, thank you.
what are your thoughts?
Leave SMART ON. I think that is entirely within the HDD & has nothing to do with Windows installation, only with HDD diagnostics. I would leave Secure Boot ON too for now, although some recommend turning it OFF for problem solving purposes. It never was a problem for me. Let's see how it goes with it ON first, since Robert has confirmed the current problem to be a malformed BCD. It's possible Windows does something with that setting during the installation, & ON is better.
(1) Did you boot to the external recovery environment & check that the BCD backup you made is accessible there, that C:\ is still C:\ (hasn't switched to D:\ or another letter), & that BCDEdit will run there? I urge you to do so!
(2) I see in the extracts that Robert posted of your logs that your computer appears to be "Locale = en-US". Please confirm that at "START, Settings, Time & Language, Region & Language"...
(3) OK, I'll get to work on instructions to run BCDBoot. It will default to "US English". The URL I posted above...
Windows 10 Troubleshooting: Error upgrading to build 1607, 0x80070057-0x2000A
...suggests we put a letter on the system partition & rename the current BCD. It's a good idea to use the letter, since you've got two system partitions (the second being on the D: drive). It won't hurt to rename the current BCD, as that will provide a second backup.
But let me nose around a bit. I'll post full instructions later.
Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>bcdboot /?
Bcdboot - Bcd boot file creation and repair tool.
The bcdboot.exe command-line tool is used to copy critical boot files to the
system partition and to create a new system BCD store.
bcdboot <source> [/l <locale>] [/s <volume-letter> [/f <firmware>]] [/v]
[/m [{OS Loader ID}]] [/addlast] [/p] [/c]
source Specifies the location of the windows system root.
/l Specifies an optional locale parameter to use when
initializing the BCD store. The default is US English.
/s Specifies an optional volume letter parameter to designate
the target system partition where boot environment files are
copied. The default is the system partition identified by
the firmware.
/v Enables verbose mode.
/m If an OS loader GUID is provided, this option merges the
given loader object with the system template to produce a
bootable entry. Otherwise, only global objects are merged.
/d Specifies that the existing default windows boot entry
should be preserved.
/f Used with the /s command, specifies the firmware type of the
target system partition. Options for <firmware> are 'UEFI',
'BIOS', or 'ALL'.
/addlast Specifies that the windows boot manager firmware entry
should be added last. The default behavior is to add it
first.
/p Specifies that the windows boot manager firmware entry
position should be preserved. If entry does not exist,
new entry will be added in the first position.
/c Specifies that any existing objects described by the template
should not be migrated.
Examples: bcdboot c:\windows /l en-us
bcdboot c:\windows /s h:
bcdboot c:\windows /s h: /f UEFI
bcdboot c:\windows /m {d58d10c6-df53-11dc-878f-00064f4f4e08}
bcdboot c:\windows /d /addlast
bcdboot c:\windows /p
C:\WINDOWS\system32>
Thank you man. You and PCR might able to crack this thing.
I have down loaded the KB4057291 and installed first. And thereafter 4073290 and 4058258.I problem solved.
Here are some files from the $WINDOWS BT folder. (today)
Looks like PCR has you on the right tack. There is something wrong with your BCD so it can't be changed by the update.
Here is SetupAct.log saying what the state is and what's next
2018-02-18 16:31:37, Info SP Operation (completed): Save SAM and SECURITY hives
2018-02-18 16:31:37, Info SP Operation (remaining): Add boot entry for C:$WINDOWS.~BT\NewOS\WINDOWS. Locale = en-US
Then that (time) gives some context for these SetupErr.log items
2018-02-18 16:31:37, Error IBSLIB Failed to export alterations to firmware. Status: c000000d[gle=0x00000002]
2018-02-18 16:31:38, Error SP Failed to close the system store. Status = [c000000d]
2018-02-18 16:31:38, Error SP CAddBootEntry: Failure while adding the boot entry. Error: 0x80070057[gle=0x00000057]
2018-02-18 16:31:38, Error IBSLIB Failed to export alterations to firmware. Status: c000000d[gle=0x00000057]
2018-02-18 16:31:38, Error SP Operation failed: Add boot entry for C:$WINDOWS.~BT\NewOS\WINDOWS. Locale = en-US. Error: 0x80070057[gle=0x000000b7]
2018-02-18 16:31:38, Error SP Operation execution failed: 10. hr = 0x80070057[gle=0x000000b7]
2018-02-18 16:31:38, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x80070057[gle=0x000000b7]
and that's the end of that in both files. There are other Info and Warning messages in the SetupAct.log that add to the symptom description but these are sufficient to demonstrate there is a problem with your BCD. So, if we figure out a way to change these symptoms there will be a chance to change the whole result.
HTH
Robert