none
0x800F084F when installing CU or servicing stack patches on Windows 10 1809 RRS feed

  • Question

  • When trying to install OS CU or servicing stack patches on Windows 10 1809 LTSC I get:

    0x800F084F error in CBS log

    " Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F084F"

    The Updates will install though if I logout and back in as a different user?!

    I have tried the usual Windows update reset scripts .. no luck

    Would be really grateful for any help on this, its affecting multiple systems, here is a snip of the cbs.log errors:

    2019-10-03 14:19:20, Info                  CBS    Exec: Processing complete.  Session: 30767597_702352913, Package:
    Package_for_KB4465065~31bf3856ad364e35~amd64~~10.0.3.0, Identifier: KB4465065 [HRESULT = 0x800f084f -
    CBS_E_RESOLVE_FAILED]

    2019-10-03 14:19:21, Info                  DPX    Extraction of file: update.ses failed because it is not present in
    the container
    (\\?\C:\WINDOWS\SoftwareDistribution\Download\02e4d8ae9fe657cc3771f39c38cdce9a\windows10.0-kb4515843-x64.cab).

    2019-10-03 14:19:21, Info                  CBS    Not able to add file to extract: update.ses [HRESULT = 0x80070002 -
    ERROR_FILE_NOT_FOUND]

    2019-10-03 14:19:32, Error                 CSI    000000fc (F) STATUS_OBJECT_NAME_NOT_FOUND #264710# from
    Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key =
    {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY|ACCESS_SYSTEM_SECURITY), oa =
    @0x44595fe158->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[127]'\Registry\Machine\COMPONENTS\CanonicalData\Deployments\2206c0
    71843..581559db9d6_b03f5f7f11d50a3a_4.0.15744.246_8f1508555d52420a'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped
    dispositio[gle=0xd0000034]

    2019-10-03 14:19:32, Error                 CSI    n: 1499455288)[gle=0xd0000034]

    2019-10-03 14:19:32, Error                 CSI    000000fd@2019/10/3:13:19:32.437 (F)
    onecore\base\wcp\sil\ntsystem.cpp(5348): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function
    Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)

    2019-10-03 14:19:32, Error                 CSI    000000fe (F) STATUS_OBJECT_NAME_NOT_FOUND #264709# from
    Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name=
    ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY|ACCESS_SYSTEM_SECURITY), oa = @0x44595fe158->OBJECT_ATTRIBUTES {s:48;
    rd:NULL; on:[127]'\Registry\Machine\COMPONENTS\CanonicalData\Deployments\2206c071843..581559db9d6_b03f5f7f11d50a3a_4.0.
    15744.246_8f1508555d52420a'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped dis)[gle=0xd0000034]

    2019-10-03 14:19:32, Error                 CSI    000000ff@2019/10/3:13:19:32.437 (F)
    onecore\base\wcp\sil\ntsystem.cpp(5348): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function
    Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)

    2019-10-03 14:19:32, Error                 CSI    00000100 (F) STATUS_OBJECT_NAME_NOT_FOUND #264708# from
    Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::OpenRegistryKey(flags =
    (OpenForBackupIntent), da = (KEY_ALL_ACCESS|ACCESS_SYSTEM_SECURITY), kn = [l:127]'\Registry\Machine\COMPONENTS\Canonica
    lData\Deployments\2206c071843..581559db9d6_b03f5f7f11d50a3a_4.0.15744.246_8f1508555d52420a', key = NULL, disp =
    (null))[gle=0xd0000034]

    2019-10-03 14:19:32, Info                  CSI    00000101 Error STATUS_OBJECT_NAME_NOT_FOUND while executing
    operation SetKeyValue on [l:322]'\Registry\Machine\COMPONENTS\CanonicalData\Deployments\2206c071843..581559db9d6_b03f5f
    7f11d50a3a_4.0.15744.246_8f1508555d52420a, CatalogThumbprint, , OQBhAGUAOQAwAGYAMQBlAGIANgBkADIANwA1ADgAMQAzAGQANwBmADI
    AZABlAGUAYgBlAGQANwBjAGEAZAAzADcANQBjAGIAOABiAGIAYgA0ADQAOAAzADIANwAwADEAMgA0ADEAMAA0AGMAYQBlADMAMABhAGYANAA3ADkANAA='

    2019-10-03 14:19:32, Error                 CBS    Exec: Unexpected disposition from CSI transaction to resolve
    execution chain: 6 [HRESULT = 0x800f084f - CBS_E_RESOLVE_FAILED]

    2019-10-03 14:19:32, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x800f084f -
    CBS_E_RESOLVE_FAILED]

    2019-10-03 14:19:32, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800f084f -
    CBS_E_RESOLVE_FAILED]

    2019-10-03 14:19:32, Info                  CBS    WER: Generating failure report for package:
    Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3011, status: 0x800f084f, failure source: Resolve, start
    state: Absent, target state: Installed, client id: WindowsUpdateAgent


    • Edited by tigran_77 Friday, October 4, 2019 7:24 AM
    Friday, October 4, 2019 7:23 AM

All replies

  • Hi, 

    Are there any error codes recorded in the Event Viewer(Windows Logs\Applications, Setup, System)?

    How did you install update? through Windows update agent in Settings or download it from Windows update catalog.website manually. 

    If you tested one of the download measure, please check if the issue occur on another measure. 

    Extraction of file: update.ses failed because it is not present in the container (\\C:\WINDOWS\SoftwareDistribution\Download\02e4d8ae9fe657cc3771f39c38cdce9a\windows10.0-kb4515843-x64.cab).

    Delete SoftwareDistribution to check again.

    I noticed the update log show many update downloading and installing status, please try to check if the issue persists when just install one update rather than several update at a same time. 

    Run the command sfc /scannow with administrator right to check the health of system files. 

    Also please update in Clean Boot environment, and turn of firewall and antivirus software temporarily to check. 

    Changing another account will helpful to narrow down the issue. 

    Bests,


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, October 7, 2019 7:52 AM
    Moderator
  • Hi,

    Any update?

    Bests,


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 11, 2019 9:46 AM
    Moderator
  • Hi Joy-Qiao,

    We are still getting this problem, even if you install one update at a time, or if after running sfc scans. Has anyone else reported this error code?

    Wednesday, November 13, 2019 12:05 PM
  • Hi, 

    Thank you for your reply. 

    Would you feedback the other action result to us which I suggested in upper?  

    Bests, 


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 15, 2019 9:52 AM
    Moderator