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

153 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-02-18T08:41:39+00:00

    UPDATE:

    Here are some files from the $WINDOWS BT folder. (today)

    1. https://www.dropbox.com/sh/8m1c6jnctp7qrxn/AAB5b0oxs6KEH-AJlHpDRvBXa?dl=0

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-18T07:25:52+00:00

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-18T07:12:57+00:00

    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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-18T05:46:10+00:00

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-02-18T05:34:02+00:00

    2018-02-18 10:19:49, Error                 DISM   DISM Package Manager: PID=14140 TID=11644 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

    2018-02-18 10:19:49, Info                  DISM   DISM Package Manager: PID=14140 TID=11644 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

    Try to find the CBS.log for that time and just before.  You may have to look at the archived bits to find one for that.  Otherwise, do it again and then you would be able to see the relevant logging in the current CBS.log

    HTH

    Robert

    Was this answer helpful?

    0 comments