KB3055999 failed to install with error 8007371B. What to do?

In a group of 9 optional Win8.1 updates, KB3055999 was the only one to fail (error 8007371B). I rebooted the system (WU asked for it) and tried to install it again to no avail. I found https://support.microsoft.com/en-us/kb/957310, but it is for error 80073712 (maybe they are *twin* errors). The Windows Update LOG brings these  first warning messages:

2015-05-24 18:13:37:957 908 91c DnldMgr Caller SID for retrying failed download job: S-1-5-18
2015-05-24 18:14:54:507 908 954 WS WARNING: Nws Failure: errorCode=0x803d0014
2015-05-24 18:14:54:507 908 954 WS WARNING: Original error code: 0x80072efe

What should I do to successfully install the update?

May 24th, 2015 6:07pm

Try using the Windows Update Troubleshooter to fix the problem.

Alternatively You may try the standalone download manually:

Update for Windows 8.1 (KB3055999)

Free Windows Admin Tool Kit Click here and download it now
May 24th, 2015 8:23pm

a. Press Windows key + X on the desktop screen of the computer.
b. Select Command Prompt (Admin)
c. On the open Command Prompt window copy and paste the commands (all at once).
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
pause
May 24th, 2015 8:39pm

Thanks. Unfortunately, it's still failing, always with the same error code.
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 6:58pm

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 Wednesday, May 27, 2015 6:31 PM corrected a word in the title
  • Merged by Bruce WoodingModerator 6 hours 55 minutes ago Same problem from same originating person
May 26th, 2015 11:06pm

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 Wednesday, May 27, 2015 6:31 PM corrected a word in the title
  • Merged by Bruce WoodingModerator Wednesday, June 03, 2015 12:28 AM Same problem from same originating person
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 11:06pm

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 Wednesday, May 27, 2015 6:31 PM corrected a word in the title
  • Merged by Bruce WoodingModerator Wednesday, June 03, 2015 12:28 AM Same problem from same originating person
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.

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.

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 Wednesday, May 27, 2015 6:09 PM
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 6:03pm

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 Wednesday, May 27, 2015 6:09 PM
May 27th, 2015 6:03pm

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.

Free Windows Admin Tool Kit Click here and download it now
May 28th, 2015 2:00am

Hi,

I uploaded 3 files: 1 for the SFC execution, another one for DISM execution and the last one for the installation via Windows Update (where I tried one more time). The link is  .

  • Edited by __arpoador Friday, May 29, 2015 2:28 PM
May 28th, 2015 9:42pm

Hi,

I uploaded 3 files: 1 for the SFC execution, another one for DISM execution and the last one for the installation via Windows Update (where I tried one more time). The link is  .

  • Edited by __arpoador Friday, May 29, 2015 2:28 PM
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2015 9:42pm

Please, let me know if you still need the link.
May 29th, 2015 2:28pm

Hi

As I know, KB3055999 is an optional update for Saskatchewan Telecommunications (Canada) in Windows 8.1. This update corrects an entry in the APN database for the SaskTel operator. Optional Updates, are new features, updates, Ultimate Extras or improving some third party feature compatibility that are not necessary to install all of them for proper functionality of the operating system or applications. To install this update, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355). This error might occurs due to corruption of these update, first check if this update is necessary for your computer, try re-install these updates then check the issue again if it is necessary.

Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update: April 2014

https://support.microsoft.com/en-us/kb/2919355

Updates 2932046, 2937592, 2938439, 2934018, and 2959977 are included in the installation.

Regards,

D. Wu

Free Windows Admin Tool Kit Click here and download it now
May 31st, 2015 9:20pm

Hi,

According to the CBS..log:

2015-05-28 12:47:34, Info                  CSI    00000016 Changelist shadowed missing its manifest - Microsoft-Windows-WwanApnDatabase, Version = 6.3.9600.17729, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-05-28 12:47:34, Error                 CSI    00000017@2015/5/28:15:47:34.719 (F) base\wcp\componentstore\csd_winners.cpp(1211): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)

For more information about CSI error, see:

https://technet.microsoft.com/en-us/library/cc732334(v=ws.10).aspx#CSI

That's to say, some necessary componments of CSI was missing. In my opinion, this should be the reason of this update installation failed.

However, it's wired that DISM command should already fixed this problem, but the issue still exits.

On the other hand, according to the first log items, it seems like this problem is relate with Wlan driver. Have you installed any Mobile Wlan device to your computer, especially NIC driver?

You can try to upgrade or reinstall the NIC driver for test. If you installed any other network device except NIC driver, just remove them for test.

June 1st, 2015 3:06am

Hi,

Should I hide this optional update and ignore it? Windows 10 is almost RTM, and if this problematic update does not repeat in Windows 10, maybe this is an option.

Free Windows Admin Tool Kit Click here and download it now
June 1st, 2015 7:13pm

Hi,

I haven't installed any NIC driver or anything similar.

In my opinion, the problem is the corruption that's not fixed neither by WindowsUpdateDiagnostic tool nor by DISM.

Should I hide this optional update and ignore it? Windows 10 is almost RTM, and if this problematic update does not repeat in Windows 10, maybe this is an option.

June 1st, 2015 11:13pm

Hi,

In my opinion, you can hide this update temporarily as a workaround method.

About Windows 10 upgrade, I won't suggest you upgrade the edition even you already received the notification, because you may encounter other compatibility problem with your application and hardware device. It would be better to contact the manufacture of your PC to ask for more suggestion about the upgrade.

Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2015 9:24pm

Yes, I guess the best thing to do is hide it until... the sun shines again :)

This morning I received 3 more optional Windows Update: KB3068708, KB3050267  and KB2976978.

I tried to install them all, along with the problematic KB3055999, and the result was bad: 

Success: KB3050267 and KB2976978

Failure: KB3055999 and KB3068708

Curiously, in my 1st computer the situation is the inverse.

Reading the newly available Windows 10 upgrading documentation, I know there'll be a upgrading advisory tool that will check hardware requirements' conformance before installing Windows 10.

I just hope very much they do it before downloading 3GB of data through my slow dial-up connection.

Interesting situation my 2 computers are in, right now:

-

1st computer: AMD CPU, Windows 8.1 Pro with Media Center, 32 bits, did not receive Windows 10 notification, failed to install KB3022345, but succeeded installing KB3055999  and KB2976978. It has not been offered KB3068708 yet.

-

2nd computer: INTEL CPU, Windows 8.1 Pro (no Media Center), 32 bits, received Windows 10 notification, failed to install KB3055999 and KB3068708, but succeeded installing KB3022345 and KB2976978.

-

So, it's exactly the opposite.

Reading the "support" documentation for KB3022345, what I understand is that there are problems among specifics Windows Update and CPU brand; also, there'll be some other version of the update. 

But nothing is crystal clear for me, and I don't understand why I haven't received a Windows 10 notification for my 1st computer too.

Do you have any idea why? Should I post KB3022345's CBS.LOG related to my 1st computer?

Thanks for any help.


CORRECTION: My 1st computer (AMD) did install KB2976978 successfuly too.


  • Edited by __arpoador 8 hours 38 minutes ago a correction
June 3rd, 2015 4:56pm

Yes, I guess the best thing to do is hide it until... the sun shines again :)

This morning I received 3 more optional Windows Update: KB3068708, KB3050267  and KB2976978.

I tried to install them all, along with the problematic KB3055999, and the result was bad: 

Success: KB3050267 and KB2976978

Failure: KB3055999 and KB3068708

Curiously, in my 1st computer the situation is the inverse.

Reading the newly available Windows 10 upgrading documentation, I know there'll be a upgrading advisory tool that will check hardware requirements' conformance before installing Windows 10.

I just hope very much they do it before downloading 3GB of data through my slow dial-up connection.

Interesting situation my 2 computers are in, right now:

-

1st computer: AMD CPU, Windows 8.1 Pro with Media Center, 32 bits, did not receive Windows 10 notification, failed to install KB3022345, but succeeded installing KB3055999  and KB2976978. It has not been offered KB3068708 yet.

-

2nd computer: INTEL CPU, Windows 8.1 Pro (no Media Center), 32 bits, received Windows 10 notification, failed to install KB3055999 and KB3068708, but succeeded installing KB3022345 and KB2976978.

-

So, it's exactly the opposite.

Reading the "support" documentation for KB3022345, what I understand is that there are problems among specifics Windows Update and CPU brand; also, there'll be some other version of the update. 

But nothing is crystal clear for me, and I don't understand why I haven't received a Windows 10 notification for my 1st computer too.

Do you have any idea why? Should I post KB3022345's CBS.LOG related to my 1st computer?

Thanks for any help.


CORRECTION: My 1st computer (AMD) did install KB2976978 successfuly too.


  • Edited by __arpoador Wednesday, June 03, 2015 10:44 PM a correction
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2015 8:54pm

Yes, I guess the best thing to do is hide it until... the sun shines again :)

This morning I received 3 more optional Windows Update: KB3068708, KB3050267  and KB2976978.

I tried to install them all, along with the problematic KB3055999, and the result was bad: 

Success: KB3050267 and KB2976978

Failure: KB3055999 and KB3068708

Curiously, in my 1st computer the situation is the inverse.

Reading the newly available Windows 10 upgrading documentation, I know there'll be a upgrading advisory tool that will check hardware requirements' conformance before installing Windows 10.

I just hope very much they do it before downloading 3GB of data through my slow dial-up connection.

Interesting situation my 2 computers are in, right now:

-

1st computer: AMD CPU, Windows 8.1 Pro with Media Center, 32 bits, did not receive Windows 10 notification, failed to install KB3022345, but succeeded installing KB3055999  and KB2976978. It has not been offered KB3068708 yet.

-

2nd computer: INTEL CPU, Windows 8.1 Pro (no Media Center), 32 bits, received Windows 10 notification, failed to install KB3055999 and KB3068708, but succeeded installing KB3022345 and KB2976978.

-

So, it's exactly the opposite.

Reading the "support" documentation for KB3022345, what I understand is that there are problems among specifics Windows Update and CPU brand; also, there'll be some other version of the update. 

But nothing is crystal clear for me, and I don't understand why I haven't received a Windows 10 notification for my 1st computer too.

Do you have any idea why? Should I post KB3022345's CBS.LOG related to my 1st computer?

Thanks for any help.


CORRECTION: My 1st computer (AMD) did install KB2976978 successfuly too.


  • Edited by __arpoador Wednesday, June 03, 2015 10:44 PM a correction
June 3rd, 2015 8:54pm

Hi,

About your doesn't get Windows 10 notification problem, you can refer to the content of the link below for more details:

http://answers.microsoft.com/en-us/windows/forum/windows_10-win_upgrade/i-want-to-reserve-my-free-copy-of-windows-10-but-i/848b5cce-958b-49ae-a132-a999a883265b

For another computer upate installation problem, try to use the above methods which were provided for test.

Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2015 10:43pm

I noticed about 40 minutes ago, the Windows 10 logo is, finally, on my 1st computer's taskbar. Have you had anything to do with it? Thank you.

June 4th, 2015 3:12am

I'm not get ready to upgrade my own system to Windows 10, therefore, I just let it alone there.
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2015 9:08pm

One good thing to reserve the download, is that GWX.exe and GWXUX.exe and maybe some other, scan the computer to check for compatibility. My system passed the test, 100% (except, of course for the WMC). So far, so good. A second good thing, is that the reservation can be cancelled at any time. This is something I'm never gonna do, because I want to see 7, 8 and 8.1 far in the past. :)

June 5th, 2015 11:22pm

Hi,

About the Windows 10 notification, no, we didn't do anything about that. Actually we can do nothing about it, so I guess it is just a little bit obtuse.

And thanks for your feedback and glad to hear that your machine have 100% compatibility for Windows 10.

Regards,

D. Wu

Free Windows Admin Tool Kit Click here and download it now
June 8th, 2015 9:28pm

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

Other recent topics Other recent topics