does this updated folder suffice?
https://www.dropbox.com/sh/k2zlwsbbpkvnuhk/AAAmcpf-StdF9V9\_EybbXcxNa?dl=0
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.
does this updated folder suffice?
https://www.dropbox.com/sh/k2zlwsbbpkvnuhk/AAAmcpf-StdF9V9\_EybbXcxNa?dl=0
does this updated folder suffice?
The new CBS.log shows there are bits missing
<extract>
2018-02-18 10:19:49, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2018-02-18 10:19:49, Info CBS Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2018-02-18 10:19:49, Info CBS Ensure WCP corruption flag is clear
2018-02-18 10:19:49, Info CBS
=================================
Checking System Update Readiness.
(p) CBS Catalog Missing Package_757_for_KB3206632~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_758_for_KB3206632~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_759_for_KB3206632~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_760_for_KB3206632~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_761_for_KB3206632~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_762_for_KB3206632~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_763_for_KB3206632~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS MUM Missing Package_764_for_KB3206632~31bf3856ad364e35~amd64~~10.0.1.8
Summary:
Operation: Detect and Repair
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption: 8
CBS Manifest Corruption: 8
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 0
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True
Total Operation Time: 615 seconds.
2018-02-18 10:19:49, Info CBS CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download Result: 0x800f0948 [CBS_E_SOURCE_MISSING_FROM_WU_CAB]
</extract>
December 13, 2016 — KB3206632 (OS Build 14393.576)
I wonder why that would matter? Maybe it is just to ensure that you could uninstall things if you wanted to.
If you can give me any hints on the timing of other things that could be associated with those other CBS logs I would be happy to have a look at them too. How about a ReportingEvents.log, SetupErr.log and a SetupAct.log too? ; )
HTH
Robert
Hope this helps Robert
https://www.dropbox.com/sh/8fljdcazeqfspm2/AACyhlqPeMDwdprmk9a243\_Ja?dl=0
https://www.dropbox.com/s/cmth94m7maakjlr/ReportingEvents.log?dl=0
UPDATE:
Here are some files from the $WINDOWS BT folder. (today)
1. https://www.dropbox.com/sh/8m1c6jnctp7qrxn/AAB5b0oxs6KEH-AJlHpDRvBXa?dl=0
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