[SOLVED] Unable to apply KB3185278 after HD corruption

optikal

Member
Joined
Sep 23, 2016
Posts
9
Hello,

Recently my HD had some file corruption due to a faulty SATA cable. After replacing the cable I was able to get Windows bootable and right now everything is running normally, just not able to install KB3185278. Windows update installed the System Update Readiness Tool a few times when doing updates, that has now stopped and now I'm left with this one last update. The update fails with Error Code 80073712. I tried many things including SFCFix which fixed a few things but now I'm at an impasse.

Any help is appreciated.

Logs are to follow.
 

Attachments

Last edited:
Hi optikal,

Do you still need assistance with this issue?
 
SFCFix shows that SURT reports corruption. Let's grab its log.

IGJdB0T.png
System Update Readiness Tool (SURT) - Scan
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log;
  • Download the right version of SURT for your system;
    • Your version of Windows is: Windows 7 x64
  • Once downloaded, execute the installer, and go throught the installation (this process can take around 15-20 minutes);
  • On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log;
  • Attach this log in your next reply;
Alternatively, if these instructions are unclear for you, you can follow the tutorial below.

System Update Readiness Tool (SURT)
 
Alright, follow the instructions below please.

myjIXnC.png
SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.
  • Download SFCFix and move the executable on your Desktop;
  • On your Desktop, right-click and select New, then Text Document. Give it the name SFCFixScript (it should be a .txt) extension;
  • Open the SFCFixScript.txt file you just created, and copy/paste the following in it;
    Code:
    Trace::
    amd64_f1ac3c38cd05aa1d6f33d5a2f5281973_31bf3856ad364e35_6.1.7601.23539_none_a7bb3d6fd73ea3fc
    amd64_4a0d0a605c9b19f8b6caef959e9893cd_31bf3856ad364e35_6.1.7601.23529_none_7ed809bff59147ed
    wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.23512_none_336791e21127bbc8
    amd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.23512_none_2912e78fdcc6f9cd
    amd64_006f1bee347aa0a86984388c82ccb379_31bf3856ad364e35_6.1.7601.23529_none_4683d079b6ce11b3
    amd64_microsoft-windows-peauth_31bf3856ad364e35_6.1.7601.23471_none_668ad6dcb996dbd7
    x86_microsoft-windows-crypt32-dll.resources_31bf3856ad364e35_6.1.7601.23471_en-us_d073d28331d9c209
    amd64_907cf4d1d0cc728778468171e48b478c_31bf3856ad364e35_6.1.7601.23539_none_ad2ddac781c26559
    x86_microsoft-windows-enhancedvideorenderer_31bf3856ad364e35_6.1.7601.23471_none_91ef72a04419cc7e
    amd64_microsoft-windows-enhancedvideorenderer_31bf3856ad364e35_6.1.7601.23471_none_ee0e0e23fc773db4
    amd64_microsoft-windows-scavenge-cleanup_31bf3856ad364e35_6.1.7601.23517_none_b6df009be20ddf34
    x86_microsoft-windows-i..nal-core-locale-nls_31bf3856ad364e35_6.1.7601.23529_none_6d4339a020a94b65
    amd64_microsoft-windows-i..nal-core-locale-nls_31bf3856ad364e35_6.1.7601.23529_none_c961d523d906bc9b
    amd64_microsoft-windows-cryptsp-dll_31bf3856ad364e35_6.1.7601.23471_none_87c8fe8536bd4108
    amd64_microsoft-windows-mfplat_31bf3856ad364e35_6.1.7601.23471_none_5516292583660fc2
    x86_microsoft-windows-mfplat_31bf3856ad364e35_6.1.7601.23471_none_f8f78da1cb089e8c
    amd64_20345e442b807538fbdee878b626642b_31bf3856ad364e35_6.1.7601.23471_none_2aa4e466af681a34
    amd64_microsoft-windows-cryptui-dll_31bf3856ad364e35_6.1.7601.23471_none_e459ebd6c81411b7
    wow64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_6.1.7601.23471_none_d6ee560d291e6ee4
    amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_6.1.7601.23471_none_cc99abbaf4bdace9
    amd64_microsoft-windows-crypt32-dll.resources_31bf3856ad364e35_6.1.7601.23471_en-us_2c926e06ea37333f
    amd64_c1c1695b009afb7f57840b83a849129a_31bf3856ad364e35_6.1.7601.23529_none_cd73237b454e3320
    x86_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_6.1.7601.23471_none_b99aae8c1c7f6d35
    amd64_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_6.1.7601.23471_none_15b94a0fd4dcde6b
    amd64_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.23471_none_facabfb43cb26923
    wow64_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.23471_none_051f6a0671132b1e
    amd64_microsoft-windows-a..atibility-assistant_31bf3856ad364e35_6.1.7601.23471_none_9232168c5317c0ca
    amd64_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7601.23471_none_7584d1922bc677e4
    amd64_microsoft-windows-capi2-instrumentation_31bf3856ad364e35_6.1.7601.23471_none_1c19a0bd36224e40
    x86_microsoft-windows-capi2-instrumentation_31bf3856ad364e35_6.1.7601.23471_none_bffb05397dc4dd0a
    amd64_microsoft-windows-capi2-wintrust-reg_31bf3856ad364e35_6.1.7601.23471_none_e767ea91c37deca7
    amd64_microsoft-windows-wintrust-dll_31bf3856ad364e35_6.1.7601.23471_none_4e19ca3dca01a3a3
    amd64_microsoft-windows-cryptsvc-dll_31bf3856ad364e35_6.1.7601.23471_none_d46b29dccac00c89
    amd64_microsoft-windows-directshow-core_31bf3856ad364e35_6.1.7601.23471_none_04dbc8591dd6ea2c
    wow64_microsoft-windows-directshow-core_31bf3856ad364e35_6.1.7601.23471_none_0f3072ab5237ac27
    x86_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_6.1.7601.23471_none_934439ba2f95552f
    amd64_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_6.1.7601.23471_none_ef62d53de7f2c665
    x86_microsoft-windows-capi2-wintrust-reg_31bf3856ad364e35_6.1.7601.23471_none_8b494f0e0b207b71
    x86_microsoft-windows-wintrust-dll_31bf3856ad364e35_6.1.7601.23471_none_f1fb2eba11a4326d
    x86_microsoft-windows-cryptsvc-dll_31bf3856ad364e35_6.1.7601.23471_none_784c8e5912629b53
    x86_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7601.23471_none_1966360e736906ae
    x86_microsoft-windows-cryptui-dll_31bf3856ad364e35_6.1.7601.23471_none_883b50530fb6a081
    amd64_48476352256e86f7da428a6d35c94414_31bf3856ad364e35_6.1.7601.23471_none_d3a5bda34471b9c2
    amd64_microsoft-windows-d..providers.resources_31bf3856ad364e35_6.1.7601.23471_en-us_cf6e52a4987c86ca
    x86_microsoft-windows-d..providers.resources_31bf3856ad364e35_6.1.7601.23471_en-us_734fb720e01f1594
    amd64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_6.1.7601.23471_none_36a0dee2348e195e
    amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.1.7601.23517_none_6ad4abcc220717f8
    wow64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.1.7601.23517_none_7529561e5667d9f3
    x86_microsoft-windows-cryptsp-dll_31bf3856ad364e35_6.1.7601.23471_none_2baa63017e5fcfd2
    amd64_580807f24a5eb57168ac0d945203760a_31bf3856ad364e35_6.1.7601.23471_none_83a382d42af32706
    amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.23517_none_6a1c36c17ed465c0
    wow64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.23517_none_7470e113b33527bb
    amd64_microsoft-windows-m..ayer-core.resources_31bf3856ad364e35_6.1.7601.23517_en-us_822e36c8115c97d7
    wow64_microsoft-windows-m..ayer-core.resources_31bf3856ad364e35_6.1.7601.23517_en-us_8c82e11a45bd59d2
    amd64_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.1.7601.23471_none_d50b549f14907e7a
    wow64_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.1.7601.23471_none_df5ffef148f14075
    x86_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_6.1.7601.23471_none_da82435e7c30a828
    x86_microsoft-windows-capi2-certs_31bf3856ad364e35_6.1.7601.23471_none_c4dbb02c0bb8e6fb
    amd64_microsoft-windows-capi2-certs_31bf3856ad364e35_6.1.7601.23471_none_20fa4bafc4165831
    amd64_microsoft-windows-directshow-dvdsupport_31bf3856ad364e35_6.1.7601.23471_none_b28dbb4a03c951fc
    x86_microsoft-windows-directshow-dvdsupport_31bf3856ad364e35_6.1.7601.23471_none_566f1fc64b6be0c6
    x86_microsoft-windows-crypt32-dll_31bf3856ad364e35_6.1.7601.23471_none_5dbcb6d055671444
    amd64_microsoft-windows-mountpointmanager_31bf3856ad364e35_6.1.7601.23471_none_5103b53e36f68234
    amd64_microsoft-windows-g..cycacheclean-russia_31bf3856ad364e35_6.1.7601.23529_none_b7fde6472be36e7a
    amd64_microsoft-windows-crypt32-dll_31bf3856ad364e35_6.1.7601.23471_none_b9db52540dc4857a
    amd64_microsoft-windows-g..checlean-azerbaijan_31bf3856ad364e35_6.1.7601.23529_none_483ce59ea50469b0
    amd64_microsoft-windows-g..lean-canada-refresh_31bf3856ad364e35_6.1.7601.23529_none_7b13bc47c7262ad6
  • Save any work you have open, and close every programs;
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it;
    1p8eDnI.gif
  • 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;
 
Here's the output:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-09-29 19:43:41.825
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at SFCFixScript.txt [0]




Trace::
Successfully traced component amd64_f1ac3c38cd05aa1d6f33d5a2f5281973_31bf3856ad364e35_6.1.7601.23539_none_a7bb3d6fd73ea3fc.
Package_237_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-377_neutral_LDR16

Successfully traced component amd64_4a0d0a605c9b19f8b6caef959e9893cd_31bf3856ad364e35_6.1.7601.23529_none_7ed809bff59147ed.
Package_415_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-614_neutral_LDR

Successfully traced component wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.23512_none_336791e21127bbc8.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-w..for-management-core_31bf3856ad364e35_6.1.7601.23512_none_2912e78fdcc6f9cd.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_006f1bee347aa0a86984388c82ccb379_31bf3856ad364e35_6.1.7601.23529_none_4683d079b6ce11b3.
Package_415_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-614_neutral_LDR

Successfully traced component amd64_microsoft-windows-peauth_31bf3856ad364e35_6.1.7601.23471_none_668ad6dcb996dbd7.
Package_124_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-207_neutral_LDR5

Successfully traced component x86_microsoft-windows-crypt32-dll.resources_31bf3856ad364e35_6.1.7601.23471_en-us_d073d28331d9c209.
Package_85_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-140_neutral_LDR16

Successfully traced component amd64_907cf4d1d0cc728778468171e48b478c_31bf3856ad364e35_6.1.7601.23539_none_ad2ddac781c26559.
Package_238_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-378_neutral_LDR4

Successfully traced component x86_microsoft-windows-enhancedvideorenderer_31bf3856ad364e35_6.1.7601.23471_none_91ef72a04419cc7e.
Package_60_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-114_neutral_LDR5

Successfully traced component amd64_microsoft-windows-enhancedvideorenderer_31bf3856ad364e35_6.1.7601.23471_none_ee0e0e23fc773db4.
Package_60_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-114_neutral_LDR5

Successfully traced component amd64_microsoft-windows-scavenge-cleanup_31bf3856ad364e35_6.1.7601.23517_none_b6df009be20ddf34.
Package_126_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-220_neutral_LDR4

Successfully traced component x86_microsoft-windows-i..nal-core-locale-nls_31bf3856ad364e35_6.1.7601.23529_none_6d4339a020a94b65.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-i..nal-core-locale-nls_31bf3856ad364e35_6.1.7601.23529_none_c961d523d906bc9b.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-cryptsp-dll_31bf3856ad364e35_6.1.7601.23471_none_87c8fe8536bd4108.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-mfplat_31bf3856ad364e35_6.1.7601.23471_none_5516292583660fc2.
Package_127_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-221_neutral_LDR17

Successfully traced component x86_microsoft-windows-mfplat_31bf3856ad364e35_6.1.7601.23471_none_f8f78da1cb089e8c.
Package_127_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-221_neutral_LDR17

Successfully traced component amd64_20345e442b807538fbdee878b626642b_31bf3856ad364e35_6.1.7601.23471_none_2aa4e466af681a34.
Package_239_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-379_neutral_LDR4

Successfully traced component amd64_microsoft-windows-cryptui-dll_31bf3856ad364e35_6.1.7601.23471_none_e459ebd6c81411b7.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component wow64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_6.1.7601.23471_none_d6ee560d291e6ee4.
Package_127_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-221_neutral_LDR17

Successfully traced component amd64_microsoft-windows-mediaplayer-drm_31bf3856ad364e35_6.1.7601.23471_none_cc99abbaf4bdace9.
Package_127_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-221_neutral_LDR17

Successfully traced component amd64_microsoft-windows-crypt32-dll.resources_31bf3856ad364e35_6.1.7601.23471_en-us_2c926e06ea37333f.
Package_168_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-264_neutral_LDR16

Successfully traced component amd64_c1c1695b009afb7f57840b83a849129a_31bf3856ad364e35_6.1.7601.23529_none_cd73237b454e3320.
Package_415_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-614_neutral_LDR

Successfully traced component x86_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_6.1.7601.23471_none_b99aae8c1c7f6d35.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_6.1.7601.23471_none_15b94a0fd4dcde6b.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.23471_none_facabfb43cb26923.
Package_60_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-114_neutral_LDR5

Successfully traced component wow64_microsoft-windows-mediafoundation_31bf3856ad364e35_6.1.7601.23471_none_051f6a0671132b1e.
Package_60_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-114_neutral_LDR5

Successfully traced component amd64_microsoft-windows-a..atibility-assistant_31bf3856ad364e35_6.1.7601.23471_none_9232168c5317c0ca.
Package_61_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-115_neutral_LDR16

Successfully traced component amd64_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7601.23471_none_7584d1922bc677e4.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-capi2-instrumentation_31bf3856ad364e35_6.1.7601.23471_none_1c19a0bd36224e40.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component x86_microsoft-windows-capi2-instrumentation_31bf3856ad364e35_6.1.7601.23471_none_bffb05397dc4dd0a.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-capi2-wintrust-reg_31bf3856ad364e35_6.1.7601.23471_none_e767ea91c37deca7.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-wintrust-dll_31bf3856ad364e35_6.1.7601.23471_none_4e19ca3dca01a3a3.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-cryptsvc-dll_31bf3856ad364e35_6.1.7601.23471_none_d46b29dccac00c89.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-directshow-core_31bf3856ad364e35_6.1.7601.23471_none_04dbc8591dd6ea2c.
Package_124_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-207_neutral_LDR5

Successfully traced component wow64_microsoft-windows-directshow-core_31bf3856ad364e35_6.1.7601.23471_none_0f3072ab5237ac27.
Package_124_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-207_neutral_LDR5

Successfully traced component x86_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_6.1.7601.23471_none_934439ba2f95552f.
Package_63_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-117_neutral_LDR17

Successfully traced component amd64_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_6.1.7601.23471_none_ef62d53de7f2c665.
Package_63_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-117_neutral_LDR17

Successfully traced component x86_microsoft-windows-capi2-wintrust-reg_31bf3856ad364e35_6.1.7601.23471_none_8b494f0e0b207b71.
Package_87_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-142_neutral_LDR17

Successfully traced component x86_microsoft-windows-wintrust-dll_31bf3856ad364e35_6.1.7601.23471_none_f1fb2eba11a4326d.
Package_87_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-142_neutral_LDR17

Successfully traced component x86_microsoft-windows-cryptsvc-dll_31bf3856ad364e35_6.1.7601.23471_none_784c8e5912629b53.
Package_87_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-142_neutral_LDR17

Successfully traced component x86_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.1.7601.23471_none_1966360e736906ae.
Package_87_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-142_neutral_LDR17

Successfully traced component x86_microsoft-windows-cryptui-dll_31bf3856ad364e35_6.1.7601.23471_none_883b50530fb6a081.
Package_87_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-142_neutral_LDR17

Successfully traced component amd64_48476352256e86f7da428a6d35c94414_31bf3856ad364e35_6.1.7601.23471_none_d3a5bda34471b9c2.
Package_232_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-372_neutral_LDR4

Successfully traced component amd64_microsoft-windows-d..providers.resources_31bf3856ad364e35_6.1.7601.23471_en-us_cf6e52a4987c86ca.
Package_165_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-260_neutral_LDR5

Successfully traced component x86_microsoft-windows-d..providers.resources_31bf3856ad364e35_6.1.7601.23471_en-us_734fb720e01f1594.
Package_165_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-260_neutral_LDR5

Successfully traced component amd64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_6.1.7601.23471_none_36a0dee2348e195e.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.1.7601.23517_none_6ad4abcc220717f8.
Package_124_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-207_neutral_LDR5

Successfully traced component wow64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_6.1.7601.23517_none_7529561e5667d9f3.
Package_124_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-207_neutral_LDR5

Successfully traced component x86_microsoft-windows-cryptsp-dll_31bf3856ad364e35_6.1.7601.23471_none_2baa63017e5fcfd2.
Package_87_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-142_neutral_LDR17

Successfully traced component amd64_580807f24a5eb57168ac0d945203760a_31bf3856ad364e35_6.1.7601.23471_none_83a382d42af32706.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.23517_none_6a1c36c17ed465c0.
Package_129_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-224_neutral_LDR5

Successfully traced component wow64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.23517_none_7470e113b33527bb.
Package_129_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-224_neutral_LDR5

Successfully traced component amd64_microsoft-windows-m..ayer-core.resources_31bf3856ad364e35_6.1.7601.23517_en-us_822e36c8115c97d7.
Package_128_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-223_neutral_LDR17

Successfully traced component wow64_microsoft-windows-m..ayer-core.resources_31bf3856ad364e35_6.1.7601.23517_en-us_8c82e11a45bd59d2.
Package_128_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-223_neutral_LDR17

Successfully traced component amd64_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.1.7601.23471_none_d50b549f14907e7a.
Package_124_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-207_neutral_LDR5

Successfully traced component wow64_microsoft-windows-audio-audiocore_31bf3856ad364e35_6.1.7601.23471_none_df5ffef148f14075.
Package_124_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-207_neutral_LDR5

Successfully traced component x86_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_6.1.7601.23471_none_da82435e7c30a828.
Package_86_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-141_neutral_LDR4

Successfully traced component x86_microsoft-windows-capi2-certs_31bf3856ad364e35_6.1.7601.23471_none_c4dbb02c0bb8e6fb.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-capi2-certs_31bf3856ad364e35_6.1.7601.23471_none_20fa4bafc4165831.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-directshow-dvdsupport_31bf3856ad364e35_6.1.7601.23471_none_b28dbb4a03c951fc.
Package_124_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-207_neutral_LDR5

Successfully traced component x86_microsoft-windows-directshow-dvdsupport_31bf3856ad364e35_6.1.7601.23471_none_566f1fc64b6be0c6.
Package_124_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-207_neutral_LDR5

Successfully traced component x86_microsoft-windows-crypt32-dll_31bf3856ad364e35_6.1.7601.23471_none_5dbcb6d055671444.
Package_232_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-372_neutral_LDR4

Successfully traced component amd64_microsoft-windows-mountpointmanager_31bf3856ad364e35_6.1.7601.23471_none_5103b53e36f68234.
Package_125_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-214_neutral_LDR17

Successfully traced component amd64_microsoft-windows-g..cycacheclean-russia_31bf3856ad364e35_6.1.7601.23529_none_b7fde6472be36e7a.
Package_415_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-614_neutral_LDR

Successfully traced component amd64_microsoft-windows-crypt32-dll_31bf3856ad364e35_6.1.7601.23471_none_b9db52540dc4857a.
Package_239_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-379_neutral_LDR4

Successfully traced component amd64_microsoft-windows-g..checlean-azerbaijan_31bf3856ad364e35_6.1.7601.23529_none_483ce59ea50469b0.
Package_415_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-614_neutral_LDR

Successfully traced component amd64_microsoft-windows-g..lean-canada-refresh_31bf3856ad364e35_6.1.7601.23529_none_7b13bc47c7262ad6.
Package_415_for_KB3185278~31bf3856ad364e35~amd64~~6.1.1.4.3185278-614_neutral_LDR
Trace:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-09-29 19:43:42.606
Script hash: 6khvpVOvsQScalpJ5lxX0wWn8p1mUUWsMT/7iv/m7yc=
----------------------EOF-----------------------

Thanks!
 
Alright follow the instructions below please.

IGJdB0T.png
System Update Readiness Tool (SURT) - Fix

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to fix the errors reported by the System Update Readiness Tool (SURT);
  • Download the attached archive file, Packs.zip and save it on your Desktop;
  • Once it's downloaded, right-click on it and select Extract All...;
  • Check the Show extracted files when complete checkbox, and click on Extract;
  • On completion, a folder will open with two folders inside it, Manifests and Packages;
    • Copy and paste the files of the Manifests folder (if there are any) inside C:\Windows\Temp\CheckSur\winsxs\Manifests
    • Copy and paste the files of the Packages folder (if there are any) inside C:\Windows\Temp\CheckSur\servicing\Packages
  • Run the System Update Readiness Tool (SURT) again;
  • On completion, attach the log located at C:\Windows\Logs\CBS\CheckSUR.log in your next reply;
Packs.zip
 
Thanks I'll be updating my canned. The fix went through without a hitch. Let's see if SFC have anything to report before moving on.

EndqYRa.png
System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;
  • On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select
    Spcusrh.png
    Run as Administrator
  • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
  • On Windows 8.1 and Windows 10, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command below and press on Enter;
    Code:
    sfc /scannow
    Note: There's a space between "sfc" and "/scannow";
  • Once the scan is complete, enter the command below and press on Enter
    Code:
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  • A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't have the information from the scan anymore. So archive it and upload it as soon as you can.
 
SFC reported only one corrupt file, we'll replace it.

myjIXnC.png
SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.
  • Download SFCFix and move the executable on your Desktop;
  • Download the attached SFCFix.zip and move the archive to your Desktop;
    Note: Make sure that the file is named SFCFix.zip, do not rename it.
  • Save any work you have open, and close every programs;
  • Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it;
    mMabJGT.gif
  • 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;
View attachment SFCFix.zip
 
Output attached. Looking good!

---------------------------------------------------------
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-09-30 22:02:26.509
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Alias\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-notepad_31bf3856ad364e35_6.1.7601.18917_none_d7982eeabafd61f1\notepad.exe

Successfully copied file C:\Users\Alias\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-notepad_31bf3856ad364e35_6.1.7601.18917_none_d7982eeabafd61f1\notepad.exe to C:\Windows\winsxs\wow64_microsoft-windows-notepad_31bf3856ad364e35_6.1.7601.18917_none_d7982eeabafd61f1\notepad.exe.

Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-notepad_31bf3856ad364e35_6.1.7601.18917_none_d7982eeabafd61f1\notepad.exe
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-notepad_31bf3856ad364e35_6.1.7601.18917_none_d7982eeabafd61f1\notepad.exe
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2016-09-30 22:02:26.626
Script hash: 1/0442yiWjFolSWEve1QbnuWzu2xRDg/Ynrr/X2fFv0=
----------------------EOF-----------------------

Thanks!
 
Good! Run SFC again and provide me the new CBS.txt log after.
 
Good! SFC returned a clean log. Please try to install your update again, and if it fails, upload the two logs below for me to review.

C:\Windows\WindowsUpdate.log
C:\Windows\Logs\CBS\CBS.log
 
Problem solved! Was able to install the update with no issues. Was also able to install additional updated afterward with no issues.

Thanks so much! Donation incoming.
 
No problem optikal you're welcome!

And thank you for your contribution, it is greatly appreciated :)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top