KB3055999 failed to install with error 8007371B in every tentative, even after using DISM. Considering the WU tells exactly the error (8007371B), is there a solution for this error? What should I do? (Network Steve Forum)

KB3055999 failed to install with error 8007371B in every tentative, even after using DISM. Considering the WU tells exactly the error (8007371B), is there a solution for this error? What should I do?

I have tried using WindowsUpdateDiagnostic.diagcab, sfc.exe /scannow and dism.exe /online /cleanup-image /restorehealth, many times without success: the error code for the failed Windows update was 8007371B.

Eventually, I got success using dism.exe /online /cleanup-image /restorehealth. The final output told me it concluded the operation with success and repaired the corruption. Immediately, I tried again to install KB3055999 via Windows Update, and it failed with the same error code: 8007371B.

Considering Windows Update tells exactly the error (8007371B), is there a solution for this error? What should I do? Maybe hiding the update and forget it forever? Any MS engineer can give some guide?

Thanks.

ADDED: I forgot to say that I also tried the Windows Update Problem Solution built in the OS.

Edited by __arpoador 12 hours 54 minutes ago corrected a word in the title

May 26th, 2015 11:06pm

I've just succeeded running dism.exe /online /cleanup-image /restorehealth, for the 2nd time. Then, I downloaded the standalone package for KB3055999 and tried to install it. After 15 minutes, the installation failed. The standalone package does not write any error code.

Immediately, I ran WindowsUpdateDiagnostic.diagcab and it wrote some errors were found and corrected. I ran, again, the standalone package for KB3055999, and it failed once more.

Thanks.

Free Windows Admin Tool Kit Click here and download it now

May 27th, 2015 12:57am

Hi,

Firstly, access to the path below to check if Pending.xml here, if that it is, remove the file and restart the computer for test:

C:\Windows\WinSXS

Secondly, I have seen other people in our forum encounter similar problem, you can access to the path below find cbs.log for more details about update installation failed:

C:\Windows\Logs\CBS.log

You can also upload the log file to OneDrive, then post the download link here, we could help you analyze the file together.

May 27th, 2015 6:53am

Hi,

I have tried to install the KB3055999 many times without success; the error code is always the same: 8007371B.

( Note that my system is pt-BR, so, some translations into english language might be a little bit different. )

Whenever I run sfc.exe /scannow, at the end of execution it writes a message telling "The Windows Resource Protection found some corrupted files but could not correct some of them".

Right after the command above, I run dism.exe /online /cleanup-image /restorehealth, and this command completes execution successfully: "Restoration operation concluded successfully. The component repository was fixed."

Trying to install the KB3055999 after the successful operation above, always result in failure, with the error code 8007371B.

I then tried to run the commands below in a row, and then tried to install the KB, and it failed with the same error code.

sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
( here I tried to install the KB via Windows Update and using the standalone package, without success )

The sfc.exe /scannow writes the following in the C:\Windows\Logs\CBS\CBS.log, at the end of it:

2015-05-27 13:09:54, Info CSI 0000051e [DIRSD OWNER WARNING] Directory [ml:520{260},l:56{28}]"\??\C:\WINDOWS\system\Speech" is not owned but specifies SDDL in component Windows-Media-SpeechSynthesis-WinRT, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-05-27 13:09:56, Info CSI 0000051f [SR] Verify complete

2015-05-27 13:09:56, Info CSI 00000520 [SR] Verifying 61 (0x0000003d) components

2015-05-27 13:09:56, Info CSI 00000521 [SR] Beginning Verify and Repair transaction

2015-05-27 13:10:00, Info CSI 00000522 [SR] Verify complete

2015-05-27 13:10:00, Info CSI 00000523 [SR] Repairing 3 components

2015-05-27 13:10:00, Info CSI 00000524 [SR] Beginning Verify and Repair transaction

2015-05-27 13:10:00, Info CSI 00000525 [SR] Cannot repair member file [l:22{11}]"drvmain.sdb" of Microsoft-Windows-Application-Experience-Mitigations-C7, Version = 6.3.9600.17725, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2015-05-27 13:10:00, Info CSI 00000526 [SR] Cannot repair member file [l:24{12}]"AcGenral.dll" of Microsoft-Windows-Application-Experience-Mitigations-C3, Version = 6.3.9600.17725, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2015-05-27 13:10:00, Info CSI 00000527 [SR] Cannot repair member file [l:22{11}]"sysmain.sdb" of Microsoft-Windows-Application-Experience-Mitigations-C1, Version = 6.3.9600.17725, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2015-05-27 13:10:00, Info CSI 00000528 [SR] Cannot repair member file [l:24{12}]"AcGenral.dll" of Microsoft-Windows-Application-Experience-Mitigations-C3, Version = 6.3.9600.17725, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2015-05-27 13:10:00, Info CSI 00000529 [SR] Cannot repair member file [l:22{11}]"sysmain.sdb" of Microsoft-Windows-Application-Experience-Mitigations-C1, Version = 6.3.9600.17725, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2015-05-27 13:10:00, Info CSI 0000052a [SR] Cannot repair member file [l:22{11}]"drvmain.sdb" of Microsoft-Windows-Application-Experience-Mitigations-C7, Version = 6.3.9600.17725, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

2015-05-27 13:10:00, Info CSI 0000052b [SR] Repair complete

2015-05-27 13:10:00, Info CSI 0000052c [SR] Committing transaction

2015-05-27 13:10:00, Info CSI 0000052d Creating NT transaction (seq 2), objectname [6]"(null)"

2015-05-27 13:10:00, Info CSI 0000052e Created NT transaction (seq 2) result 0x00000000, handle @0xc18

2015-05-27 13:10:00, Info CSI 0000052f@2015/5/27:16:10:00.793Beginning NT transaction commit...

2015-05-27 13:10:00, Info CSI 00000530@2015/5/27:16:10:00.887CSI perf trace:

CSIPERF:TXCOMMIT;116272

2015-05-27 13:10:00, Info CSI 00000531 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

2015-05-27 13:12:07, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

2015-05-27 13:12:07, Info CBS TiWorker signaled for shutdown, going to exit.

2015-05-27 13:12:07, Info CBS Ending the TiWorker main loop.

2015-05-27 13:12:07, Info CBS Starting TiWorker finalization.

2015-05-27 13:12:07, Info CBS Ending the TrustedInstaller main loop.

2015-05-27 13:12:07, Info CBS Starting TrustedInstaller finalization.

2015-05-27 13:12:07, Info CBS Ending TrustedInstaller finalization.

2015-05-27 13:12:07, Info CBS Ending TiWorker finalization.

The CBS.log gets full of warnings [DIRSD OWNER WARNING] like the first one in the listing above.

The files that sfc.exe /scannow cannot repair are always the same.

The dism.exe /online /cleanup-image /restorehealth writes the following (an excerpt) in the C:\Windows\Logs\CBS\CBS.log:

CSIPERF:TXCOMMIT;539

2015-05-27 13:22:42, Info CSI 00000008 CSI Store 6922752 (0x0069a200) initialized

2015-05-27 13:22:42, Info CSI 00000009 StoreCorruptionRepair transaction begun. WcpVersion: [l:78{39}]"6.3.9600.17709 (winblue_r9.150219-1500)".

2015-05-27 13:22:42, Info CSI 0000000a@2015/5/27:16:22:42.082Starting corruption detection (InnerFlags=5)

2015-05-27 13:34:46, Info CSI 0000000b@2015/5/27:16:34:46.365Corruption detection complete. numCorruptions = 0, Disp = 1.

2015-05-27 13:34:46, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.

2015-05-27 13:34:46, Info CBS Repr: CSI Store check completes

2015-05-27 13:34:46, Info CBS Exec:Only CSI metadata corruption found, Process CSI repair.

2015-05-27 13:34:46, Info CSI 0000000c Creating NT transaction (seq 2), objectname [6]"(null)"

2015-05-27 13:34:46, Info CSI 0000000d Created NT transaction (seq 2) result 0x00000000, handle @0x244

2015-05-27 13:34:46, Info CSI 0000000e@2015/5/27:16:34:46.365Beginning NT transaction commit...

2015-05-27 13:34:46, Info CSI 0000000f@2015/5/27:16:34:46.521CSI perf trace:

CSIPERF:TXCOMMIT;188825

2015-05-27 13:34:46, Info CSI 00000010 StoreCorruptionRepair transaction completed.

2015-05-27 13:34:46, Info CBS Repr: Finished repairing CSI store.

2015-05-27 13:34:46, Info CBS Ensure CBS corruption flag is clear

2015-05-27 13:34:46, Info CBS Ensure WCP corruption flag is clear

2015-05-27 13:34:46, Info CBS

=================================

Checking System Update Readiness.

Summary:

Operation: Detect and Repair

Operation result: 0x0

Last Successful Step: Entire operation completes.

Total Detected Corruption: 0

CBS Manifest Corruption: 0

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: 854 seconds.

That's it; I'm trying not to upload files because my internet connection is dial-up, but if you still need it, let me know.

Thanks for any help.

ADDED: it's important to say that sfc.exe always finds the corrupted files mentioned above, although dism.exe says the corruption was fixed.

Edited by __arpoador 13 hours 15 minutes ago

Free Windows Admin Tool Kit Click here and download it now

May 27th, 2015 2:04pm

Hi,

According to your description, it seems like Component Servicing Infrastructure (CSI) was corrupt. But we couldn't say that this is the reason of this update installation failed.

According to the description of this update:KB3055999

Language is probably the factor of this update installation.

However, we do need cbs.log to get more information about this problem. If you concerned the cbs.log file was too large, you can rename it to .old extension name. Then trying to install the update, during the installation, system would generate a new cbs.log. You can upload this file to your OndeDrive and post the sharing link here.

May 27th, 2015 10:01pm

This topic is archived. No further replies will be accepted.