Page 3 of 3 First 123
  1. #41

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    SFCFix version 3.0.0.0 by niemiro.
    Start time: 2017-10-05 15:12:06.253
    Microsoft Windows 7 Service Pack 1 - amd64
    Using .txt script file at C:\Users\CiC24-40MFP\Desktop\SFCFixScript.txt [0]


    RegistryScript::
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8fde6f77ee68a252e5be4ffd5ee6a176d38c8ea18bf14d230a91c74f0cde3994.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8fde6f77ee68a252e5be4ffd5ee6a176d38c8ea18bf14d230a91c74f0cde3994.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9d25e0dc1b4..32d72ebc1f8_31bf3856ad364e35_11.2.9600.18738_364cd704f197a6d6.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_9d25e0dc1b4b9928532eb32d72ebc1f8_31bf3856ad364e35_11.2.9600.18738_none_364cd704f197a6d6.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8fde6f77ee68a252e5be4ffd5ee6a176d38c8ea18bf14d230a91c74f0cde3994.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\9d25e0dc1b4..32d72ebc1f8_31bf3856ad364e35_11.2.9600.18738_364cd704f197a6d6.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_9d25e0dc1b4b9928532eb32d72ebc1f8_31bf3856ad364e35_11.2.9600.18738_none_364cd704f197a6d6.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    RegistryScript:: directive completed successfully.


    Successfully processed all directives.
    SFCFix version 3.0.0.0 by niemiro has completed.
    Currently storing 42 datablocks.
    Finish time: 2017-10-05 15:12:08.213
    Script hash: FswWkIWoKnbYJKWjuYciH6C5o83xLrV5XeRYqI/rbkk=
    ----------------------EOF-----------------------
    SFC Scan 100% Good

    Windows Update Still Has Same Error


    CBS Logs Below

    Download CBS.zip from Sendspace.com - send big files the easy way


    • Ad Bot

      advertising
      Beep.

        
       

  2. #42

    Join Date
    Dec 2014
    Posts
    1,140

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    Follow the instructions below please.

    Step 1:
    WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.


    • Download the attachment SFCFixScript.txt and save it on your desktop.
    • Save any work you have open, and close all programs.
    • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
    • SFCFix will launch, let it complete.
    • Once done, a file will appear on your desktop, called SFCFix.txt.
    • Open the file, then copy and paste its content in your next reply.



    Step 2:
    Check Windows Update again and report the result.
    If it fails attach the cbs.log to your next reply.
    Attached Files Attached Files

  3. #43

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    SFCFix version 3.0.0.0 by niemiro.
    Start time: 2017-10-06 05:13:44.905
    Microsoft Windows 7 Service Pack 1 - amd64
    Using .txt script file at C:\Users\CiC24-40MFP\Desktop\SFCFixScript.txt [0]


    RegistryScript::
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8fde6f77ee68a252e5be4ffd5ee6a176d38c8ea18bf14d230a91c74f0cde3994.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8fde6f77ee68a252e5be4ffd5ee6a176d38c8ea18bf14d230a91c74f0cde3994.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3b01e568369..d49fa19ef6c_31bf3856ad364e35_11.2.9600.18738_40471265f2a54616.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_3b01e568369b6fc14863bd49fa19ef6c_31bf3856ad364e35_11.2.9600.18738_none_40471265f2a54616.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8fde6f77ee68a252e5be4ffd5ee6a176d38c8ea18bf14d230a91c74f0cde3994.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3b01e568369..d49fa19ef6c_31bf3856ad364e35_11.2.9600.18738_40471265f2a54616.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_3b01e568369b6fc14863bd49fa19ef6c_31bf3856ad364e35_11.2.9600.18738_none_40471265f2a54616.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    RegistryScript:: directive completed successfully.


    RegistryExport::
    Successfully exported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f.
    [HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f]
    "c!aed955ed866..cd6b212be7b_31bf3856ad364e35_11.2.9600.18738_cb4ccd530a52bd6f"=hex:
    "c!24278022660..45e1bf75a97_31bf3856ad364e35_11.2.9600.18738_dd0fd25736599742"=hex:
    "c!1600c7c2ab3..012ecdc1e22_31bf3856ad364e35_11.2.9600.18738_1393e72ccc8d8d74"=hex:
    "c!9d25e0dc1b4..32d72ebc1f8_31bf3856ad364e35_11.2.9600.18738_364cd704f197a6d6"=hex:
    "c!3b01e568369..d49fa19ef6c_31bf3856ad364e35_11.2.9600.18738_40471265f2a54616"=hex:
    Datablocks: O:BAD:AI(A;ID;KR;;;BU)(A;CIIOID;GR;;;BU)(A;ID;KA;;;BA)(A;CIIOID;GA;;;BA)(A;ID;KA;;;SY)(A;CIIOID;GA;;;SY)(A;CIIOID;GA;;;CO)
    RegistryExport:: directive completed successfully.


    Successfully processed all directives.
    SFCFix version 3.0.0.0 by niemiro has completed.
    Currently storing 44 datablocks.
    Finish time: 2017-10-06 05:13:47.051
    Script hash: B3Q9w8wMjdG+5ipiUcBHIDgqztyDuQjxDVpu9+Q60LM=
    ----------------------EOF-----------------------

    SFC Scan 100% Good

    Windows Update Still Has Same Error


    CBS Logs Below
    Download CBS_Logs.zip from Sendspace.com - send big files the easy way

  4. #44

    Join Date
    Dec 2014
    Posts
    1,140

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    Follow the instructions below please.

    Step 1:
    WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.


    • Download the attachment SFCFixScript.txt and save it on your desktop.
    • Save any work you have open, and close all programs.
    • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
    • SFCFix will launch, let it complete.
    • Once done, a file will appear on your desktop, called SFCFix.txt.
    • Open the file, then copy and paste its content in your next reply.



    Step 2:
    Check Windows Update again and report the result.
    If it fails attach the cbs.log to your next reply.
    Attached Files Attached Files

  5. #45

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    SFCFix version 3.0.0.0 by niemiro.
    Start time: 2017-10-06 15:10:19.732
    Microsoft Windows 7 Service Pack 1 - amd64
    Using .txt script file at C:\Users\CiC24-40MFP\Desktop\SFCFixScript.txt [0]


    RegistryScript::
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8fde6f77ee68a252e5be4ffd5ee6a176d38c8ea18bf14d230a91c74f0cde3994.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8fde6f77ee68a252e5be4ffd5ee6a176d38c8ea18bf14d230a91c74f0cde3994.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5cda374ce78..53c95a2224e_31bf3856ad364e35_11.2.9600.18738_8a8722d712656cbe.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\55b7ff229d5..c1e01ff7ce4_31bf3856ad364e35_11.2.9600.18738_60c8b2dd84fa7790.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\03520c2a65f..225e0334cec_31bf3856ad364e35_11.2.9600.18738_8b8feb1e6631930a.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1229f35d2d7..33d1ef6874a_31bf3856ad364e35_11.2.9600.18738_a42dbff4ed06be93.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\45495fb6664..93010fe55cc_31bf3856ad364e35_11.2.9600.18738_6c7132528795e59c.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\cca8e4d3e21..af55ee56668_31bf3856ad364e35_11.2.9600.18738_d0b1eed628a9d837.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed8a80a301c..31eac9e7605_31bf3856ad364e35_11.2.9600.18738_388c9a01a3ff1271.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed31f053c25..eee0bac0dff_31bf3856ad364e35_11.2.9600.18738_f9d9e91a858cdbd1.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5cda374ce78ec8aadc97e53c95a2224e_31bf3856ad364e35_11.2.9600.18738_none_8a8722d712656cbe.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_55b7ff229d540d553ed63c1e01ff7ce4_31bf3856ad364e35_11.2.9600.18738_none_60c8b2dd84fa7790.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_03520c2a65f9c11dcb25e225e0334cec_31bf3856ad364e35_11.2.9600.18738_none_8b8feb1e6631930a.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_1229f35d2d71b2cfede6e33d1ef6874a_31bf3856ad364e35_11.2.9600.18738_none_a42dbff4ed06be93.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_45495fb6664d248c4395f93010fe55cc_31bf3856ad364e35_11.2.9600.18738_none_6c7132528795e59c.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_cca8e4d3e21dd27ccaf50af55ee56668_31bf3856ad364e35_11.2.9600.18738_none_d0b1eed628a9d837.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_ed8a80a301cc68514e80331eac9e7605_31bf3856ad364e35_11.2.9600.18738_none_388c9a01a3ff1271.
    Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_ed31f053c250422435370eee0bac0dff_31bf3856ad364e35_11.2.9600.18738_none_f9d9e91a858cdbd1.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\8fde6f77ee68a252e5be4ffd5ee6a176d38c8ea18bf14d230a91c74f0cde3994.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\813b94a87cc695e9a59f6929aa6882f5f201cc3de1073711ae15aeaf2ac47e8f.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5cda374ce78..53c95a2224e_31bf3856ad364e35_11.2.9600.18738_8a8722d712656cbe.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\55b7ff229d5..c1e01ff7ce4_31bf3856ad364e35_11.2.9600.18738_60c8b2dd84fa7790.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\03520c2a65f..225e0334cec_31bf3856ad364e35_11.2.9600.18738_8b8feb1e6631930a.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1229f35d2d7..33d1ef6874a_31bf3856ad364e35_11.2.9600.18738_a42dbff4ed06be93.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\45495fb6664..93010fe55cc_31bf3856ad364e35_11.2.9600.18738_6c7132528795e59c.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\cca8e4d3e21..af55ee56668_31bf3856ad364e35_11.2.9600.18738_d0b1eed628a9d837.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed8a80a301c..31eac9e7605_31bf3856ad364e35_11.2.9600.18738_388c9a01a3ff1271.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ed31f053c25..eee0bac0dff_31bf3856ad364e35_11.2.9600.18738_f9d9e91a858cdbd1.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5cda374ce78ec8aadc97e53c95a2224e_31bf3856ad364e35_11.2.9600.18738_none_8a8722d712656cbe.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_55b7ff229d540d553ed63c1e01ff7ce4_31bf3856ad364e35_11.2.9600.18738_none_60c8b2dd84fa7790.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_03520c2a65f9c11dcb25e225e0334cec_31bf3856ad364e35_11.2.9600.18738_none_8b8feb1e6631930a.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_1229f35d2d71b2cfede6e33d1ef6874a_31bf3856ad364e35_11.2.9600.18738_none_a42dbff4ed06be93.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_45495fb6664d248c4395f93010fe55cc_31bf3856ad364e35_11.2.9600.18738_none_6c7132528795e59c.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_cca8e4d3e21dd27ccaf50af55ee56668_31bf3856ad364e35_11.2.9600.18738_none_d0b1eed628a9d837.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_ed8a80a301cc68514e80331eac9e7605_31bf3856ad364e35_11.2.9600.18738_none_388c9a01a3ff1271.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_ed31f053c250422435370eee0bac0dff_31bf3856ad364e35_11.2.9600.18738_none_f9d9e91a858cdbd1.
    Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
    RegistryScript:: directive completed successfully.


    Successfully processed all directives.
    SFCFix version 3.0.0.0 by niemiro has completed.
    Currently storing 60 datablocks.
    Finish time: 2017-10-06 15:10:23.262
    Script hash: 1ySLWB1iIz7MsZDHiADbFxrmBsk0wqtljxkA129WFDI=
    ----------------------EOF-----------------------

    SFC Scan 100% Good

    Windows Update Still Has Same Error


    CBS Logs Below
    Download CBS_Logs.zip from Sendspace.com - send big files the easy way

  6. #46

    Join Date
    Dec 2014
    Posts
    1,140

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    There are more failures then initially expected. Try to uninstall the failed update.

    Remove Update Manually
    1. Click on the Start button and in the search box, type Command Prompt
    2. When you see Command Prompt on the list, right-click on it and select Run as administrator
    3. When command prompt opens, copy and paste the following command into it, press enter
    wusa /uninstall /KB:4025341

    4. Let me know if it says it was successful or if there are any errors.

  7. #47

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    It said KB4025341 is not installed on this computer.

  8. #48

    Join Date
    Dec 2014
    Posts
    1,140

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    OK.

    Install Update with DISM

    1. Download the update MSU here: http://download.windowsupdate.com/d/...4249efbe9c.msu
    2. Copy the MSU file to a convenient location (such as C:\temp).
    3. Click on the Start button and in the search box, type Command Prompt
    4. When you see Command Prompt on the list, right-click on it and select Run as administrator
    5. When command prompt opens, copy and paste the following commands into it, press enter after each

      cd C:\temp
      replace C:\temp with your path if different

      expand windows6.1-kb4025341-x64_e2518cc83b86902d20302f114a7ebe4249efbe9c.msu -f:* C:\temp

      DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4025341-x64.cab
    6. You should receive the message:
      The operation completed successfully.
    7. Make sure to allow the computer to restart if prompted.

      If you receive any other message:
    8. Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
    9. Paste (Ctrl+V) it into your next post.
    10. Zip and attach C:\Windows\Logs\CBS\CBS.log

  9. #49

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    Install failed.

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    C:\Users\CiC24-40MFP>cd C:\temp
    C:\temp>expand windows6.1-kb4025341-x64_e2518cc83b86902d20302f114a7ebe4249efbe9c
    .msu -f:* C:\temp
    Microsoft (R) File Expansion Utility Version 6.1.7600.16385
    Copyright (c) Microsoft Corporation. All rights reserved.
    Adding C:\temp\WSUSSCAN.cab to Extraction Queue
    Adding C:\temp\Windows6.1-KB4025341-x64.cab to Extraction Queue
    Adding C:\temp\Windows6.1-KB4025341-x64-pkgProperties.txt to Extraction Queue
    Adding C:\temp\Windows6.1-KB4025341-x64.xml to Extraction Queue
    Expanding Files ....
    Progress: 2 out of 4 files
    Expanding Files Complete ...
    4 files total.
    C:\temp>DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4025341-
    x64.cab
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    Image Version: 6.1.7601.23403
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~
    ~7601.23862.1.6
    [===========================66.2%====== ]
    An error occurred - Package_for_RollupFix Error: 0x80073712
    Error: 14098
    The component store has been corrupted.
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    C:\temp>
    CBS Logs
    Download CBS_Logs.zip from Sendspace.com - send big files the easy way

    DISM Logs

    [2017-10-10 05:23:04, Info DISM PID=2952 Scratch directory set to 'C:\Users\CIC24-~1\AppData\Local\Temp\'. - CDISMManager:ut_ScratchDir
    2017-10-10 05:23:04, Info DISM PID=2952 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:04, Info DISM DISM Manager: PID=2952 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:04, Info DISM DISM.EXE:
    2017-10-10 05:23:04, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
    2017-10-10 05:23:04, Info DISM DISM.EXE:
    2017-10-10 05:23:04, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=2
    2017-10-10 05:23:04, Info DISM DISM.EXE: Executing command line: DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4025341-x64.cab
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Getting Provider FolderManager - CDISMProviderStore::GetProvider
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Getting Provider FolderManager - CDISMProviderStore::GetProvider
    2017-10-10 05:23:04, Info DISM DISM Provider Store: PID=2952 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info DISM DISM Manager: PID=2952 Successfully loaded the ImageSession at "C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9" - CDISMManager::LoadImageSession
    2017-10-10 05:23:06, Info DISM DISM Image Session: PID=2808 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Loading Provider from location C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Connecting to the provider located at C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:06, Info DISM DISM OS Provider: PID=2808 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
    2017-10-10 05:23:06, Info DISM DISM OS Provider: PID=2808 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Loading Provider from location C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Connecting to the provider located at C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Getting Provider OSServices - CDISMProviderStore::GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Loading Provider from location C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Warning DISM DISM Provider Store: PID=2808 Failed to Load the provider: C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info DISM DISM Manager: PID=2952 Image session successfully loaded from the temporary location: C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9 - CDISMManager::CreateImageSession
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Getting Provider OSServices - CDISMProviderStore::GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
    2017-10-10 05:23:06, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
    2017-10-10 05:23:06, Info DISM DISM.EXE: Target image information: OS Version=6.1.7601.23505, Image architecture=amd64
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Loading Provider from location C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Connecting to the provider located at C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:06, Info DISM DISM Provider Store: PID=2808 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:06, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
    2017-10-10 05:23:06, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
    2017-10-10 05:23:06, Info DISM DISM Package Manager: PID=2808 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
    2017-10-10 05:23:06, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
    2017-10-10 05:23:06, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
    2017-10-10 05:23:06, Info DISM DISM Package Manager: PID=2808 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
    2017-10-10 05:23:08, Info DISM DISM Package Manager: PID=2808 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Loading Provider from location C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Connecting to the provider located at C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Loading Provider from location C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Connecting to the provider located at C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Loading Provider from location C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Connecting to the provider located at C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
    2017-10-10 05:23:08, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
    2017-10-10 05:23:08, Info DISM DISM OS Provider: PID=2808 Successfully loaded the hive. - CDISMOSServiceManager:etermineBootDrive
    2017-10-10 05:23:08, Info DISM DISM Driver Manager: PID=2808 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Loading Provider from location C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Connecting to the provider located at C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Loading Provider from location C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Connecting to the provider located at C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Loading Provider from location C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Connecting to the provider located at C:\Users\CIC24-~1\AppData\Local\Temp\17B2ECB6-9B0F-404C-B237-850A57E5A2B9\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2017-10-10 05:23:08, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
    2017-10-10 05:23:08, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
    2017-10-10 05:23:08, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
    2017-10-10 05:23:08, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
    2017-10-10 05:23:08, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
    2017-10-10 05:23:08, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
    2017-10-10 05:23:08, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
    2017-10-10 05:23:08, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
    2017-10-10 05:23:08, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
    2017-10-10 05:23:08, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
    2017-10-10 05:23:08, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
    2017-10-10 05:23:08, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2017-10-10 05:23:08, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
    2017-10-10 05:23:08, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
    2017-10-10 05:23:08, Info DISM DISM Transmog Provider: PID=2808 Current image session is [ONLINE] - CTransmogManager::GetMode
    2017-10-10 05:23:08, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
    2017-10-10 05:23:08, Info DISM DISM Provider Store: PID=2808 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    2017-10-10 05:23:08, Info DISM DISM Package Manager: PID=2808 Processing the top level command token(add-package). - CPackageManagerCLIHandler::Private_ValidateCmdLine
    2017-10-10 05:23:08, Info DISM DISM Package Manager: PID=2808 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
    2017-10-10 05:23:08, Info DISM DISM Package Manager: PID=2808 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    2017-10-10 05:23:08, Info DISM DISM Package Manager: PID=2808 Encountered the option "packagepath" with value "C:\temp\windows6.1-kb4025341-x64.cab" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
    2017-10-10 05:23:13, Info DISM DISM Package Manager: PID=2808 Package Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23862.1.6 with CBS state -17(CbsInstallStateSuperseded) being mapped to dism state 7(Unknown) - CDISMPackage::LogInstallStateMapping
    2017-10-10 05:23:13, Info DISM DISM Package Manager: PID=2808 Initiating Changes on Package with values: 4, 7 - CDISMPackage::Internal_ChangePackageState
    2017-10-10 05:27:38, Info DISM DISM Package Manager: PID=2808 Error in operation: (null) (CBS HRESULT=0x80073712) - CCbsConUIHandler::Error
    2017-10-10 05:27:38, Error DISM DISM Package Manager: PID=2808 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80073712)
    2017-10-10 05:27:38, Error DISM DISM Package Manager: PID=2808 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x80073712)
    2017-10-10 05:27:38, Info DISM DISM Package Manager: PID=2808 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
    2017-10-10 05:27:38, Error DISM DISM Package Manager: PID=2808 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80073712)
    2017-10-10 05:27:38, Info DISM DISM Package Manager: PID=2808 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
    2017-10-10 05:27:38, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80073712
    2017-10-10 05:27:38, Info DISM DISM Image Session: PID=2808 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
    2017-10-10 05:27:38, Info DISM DISM Provider Store: PID=2808 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:27:38, Info DISM DISM Package Manager: PID=2808 Finalizing CBS core. - CDISMPackageManager::Finalize
    2017-10-10 05:27:38, Info DISM DISM Provider Store: PID=2808 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2808 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
    2017-10-10 05:28:03, Info DISM DISM.EXE:
    2017-10-10 05:28:03, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
    2017-10-10 05:28:03, Info DISM DISM.EXE:
    2017-10-10 05:28:03, Info DISM DISM Image Session: PID=2952 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2952 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2952 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2017-10-10 05:28:03, Info DISM DISM Provider Store: PID=2952 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

  10. #50

    Join Date
    Dec 2014
    Posts
    1,140

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    Please do following:

    FRST Registry Search
    1. Click your Start button and choose Control Panel.
    2. In the upper right corner ensure the View by: is set to Category.
    3. Select the Programs group.
    4. Click the Turn Windows features on or off link. This will bring up the Server Manager dialog.
    Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open.
    5. Please download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool

    6. Right-click on the file FRST64.exe and choose Run as administrator.
    7. Copy and paste KB4025341 into the Search box and click the Search Registry button.
    8. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
    9. You may close any remaining open windows now.

  11. #51

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    SearchReg.txt

    File attached. Thanks!

  12. #52

    Join Date
    Dec 2014
    Posts
    1,140

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    Step 1:
    Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

    1. Download the attachment fixlist.txt and save it to your desktop.
    2. Right-click on FRST64.exe and select "Run as administrator".
    3. Press the Fix button.
    4. The tool will now process fixlist.txt.
    5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
    6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
    7. Post the logfile Fixlog.txt as attachment in your next reply.

    Step 2:
    Perform the steps in message #50 again and attach the file SearchReg.txt to your next reply.
    Attached Files Attached Files

  13. #53

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    Zipped Logs Attached
    Attached Files Attached Files

  14. #54

    Join Date
    Dec 2014
    Posts
    1,140

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    Good. Check Windows Update again and report the result.

  15. #55

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    Quote Originally Posted by PeterJ View Post
    Good. Check Windows Update again and report the result.


    SUCCESS!! It updated!! Woohoo!! Thanks so much PeterJ.

    PS: Now I'm gonna have to start a new thread for my windows 10 machine that won't update.

  16. #56

    Join Date
    Dec 2014
    Posts
    1,140

    Re: [Win7SP1Pro x64] 2017-09 Security Monthly Quality Rollup Install Fails Code 80073

    Great.
    You may remove and the tools and logfiles created during this thread to clean up.

    All the best.

Page 3 of 3 First 123

Similar Threads

  1. Replies: 82
    Last Post: 09-01-2017, 08:57 AM
  2. Replies: 1
    Last Post: 07-17-2017, 04:18 PM
  3. Replies: 1
    Last Post: 06-16-2017, 03:48 AM
  4. [SOLVED] Security Monthly Quality Rollup for Windows 7 (KB3212646) fails
    By MattH in forum Windows Update
    Replies: 17
    Last Post: 02-02-2017, 03:57 PM

Log in

Log in