Windows Update failure, components corrupt.

G

ggregd

Member
Joined
Jul 28, 2015
Posts
6
I have been unable to successfully run Windows update for some time now. I have tried running the Windows Update troubleshoot and repair tool, and I ran DSIM. Reading other posts here related to the errors I see in the CBS log it appears that my components file is corrupted. I have uploaded the components file, the CBS log and the DSIM log here:

https://onedrive.live.com/redir?resid=EE0DFE43F1C7C89F!104

Thank you!

Greg
 
Hi ggregd :)

My name is Aura and I'll be assisting you with your issue. Follow the instructions below please.

myjIXnC.png
SFCFix - Run Only
Follow the instructions below to download and execute SFCFix, and provide the log.
  • Download SFCFix and move the executable on your Desktop;
  • Right-click on SFCFix.exe and select
    Spcusrh.png
    Run as Administrator;
  • Follow the instructions displayed in the console;
  • On completion, a log will open in Notepad. Copy and paste the content of that log in your next reply;
    Note: The log (SFCFix.txt) will be created in the same directory where SFCFix is run if it doesn't open automatically on completion.
 
I ran SFCFix but it did not complete, No SFCFix.txt file was created. This is the text from the command line where it ran:

-------------------------------------------------------------------------------------------------------

Welcome to SFCFix by niemiro and sysnative.com.


Checking for updates . . .
No new update is available at this time.


Processing directive 1 of 1 (AutoAnalysis::)
Checking store directories . . .
Checking CBS.log . . .
Checking CBS.persist.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .


Attempting repair . . .
Stage 1
Stage 2
Stage 3


Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.




Deployment Image Servicing and Management tool
Version: 6.2.9200.16384


Image Version: 6.2.9200.16384


[==========================100.0%==========================]


Error: 14098


The component store has been corrupted.


The DISM log file can be found at C:\windows\Logs\DISM\dism.log

-------------------------------------------------------------------------------------------------------------------------

This is the end of the DSIM.log file with the relevant error logging:

--------------------------------------------------------------------------------------------------------------------------


2015-08-01 13:25:34, Info DISM DISM Provider Store: PID=3928 TID=3260 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-08-01 13:25:34, Info DISM DISM Package Manager: PID=3928 TID=3260 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2015-08-01 13:25:34, Info DISM DISM Package Manager: PID=3928 TID=3260 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2015-08-01 13:25:34, Info DISM DISM Package Manager: PID=3928 TID=3260 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2015-08-01 13:25:34, Info DISM DISM Package Manager: PID=3928 TID=3260 CBS session options=0x48100! - CDISMPackageManager::Internal_Finalize
2015-08-01 13:28:08, Info DISM DISM Package Manager: PID=3928 TID=10892 Error in operation: (null) (CBS HRESULT=0x80073712) - CCbsConUIHandler::Error
2015-08-01 13:28:08, Error DISM DISM Package Manager: PID=3928 TID=3260 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80073712)
2015-08-01 13:28:08, Error DISM DISM Package Manager: PID=3928 TID=3260 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80073712)
2015-08-01 13:28:08, Error DISM DISM Package Manager: PID=3928 TID=3260 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80073712)
2015-08-01 13:28:08, Error DISM DISM Package Manager: PID=3928 TID=3260 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80073712)
2015-08-01 13:28:08, Info DISM DISM Package Manager: PID=3928 TID=3260 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2015-08-01 13:28:08, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80073712
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Package Manager: PID=3928 TID=3260 Finalizing CBS core. - CDISMPackageManager::Finalize
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:08, Info DISM DISM Provider Store: PID=3928 TID=3260 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:09, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2015-08-01 13:28:09, Info DISM DISM.EXE:
2015-08-01 13:28:09, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2015-08-01 13:28:09, Info DISM DISM.EXE:
2015-08-01 13:28:09, Info DISM DISM Provider Store: PID=11224 TID=10804 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-08-01 13:28:09, Info DISM DISM Provider Store: PID=11224 TID=10804 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2015-08-01 13:28:09, Info DISM DISM Provider Store: PID=11224 TID=10804 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
 
Alright, follow the instructions below please.

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, 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 contains the information from the scan anymore. So archive it and upload it as soon as you can.
 
I did as requested and got an error:

---------------------------------------------------------------------------------------

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.


C:\windows\system32>sfc /scannow


Beginning system scan. This process will take some time.


Windows Resource Protection could not perform the requested operation.

-----------------------------------------------


I uploaded the cbs.txt file anyway, in case the error was expected. It is on OneDrive here:

https://onedrive.live.com/?cid=ee0dfe43f1c7c89f&id=EE0DFE43F1C7C89F!104
 
Alright, follow the instructions below please.

EndqYRa.png
DISM - Fixing Component Store Corruption
Follow the instructions below to run a DISM scan on your system:
  • 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, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command DISM /Online /Cleanup-Image /RestoreHealth and press on Enter;
  • Let the scan run until the end (100%);
  • Copy the C:\Windows\Logs\DISM folder and C:\Windows\Logs\CBS\CBS.log file on your Desktop, then right-click on it, go to Send to... and select Compressed .zip archive;
  • Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
 
Alright, we'll need your COMPONENTS Hive next since there's corruption in it that needs to be fixed. Follow the instructions below please.

Retrieving the COMPONENTS Hive
Follow the instructions below to retrieve your COMPONENTS Hive and send me it.
  • Open your Windows Explorer, and navigate to the C:\Windows\System32\Config folder;
  • In this folder, find the COMPONENTS file (there's no extension), and copy it to your Desktop;
    Note: If you receive an error message saying that the COMPONENTS file is in use, restart your computer and try again. If the error message persist, let me know.
  • Right-click on it, and select Send to... and choose Compressed (zipped) folder;
  • Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
 
Your COMPONENTS Hive is only of 256KB, which usually means that it's corrupted beyond repair. Let's see if you have a Restore Point where we could find a good copy of it.

List Volume Shadow Copies
Follow the instructions below to list all the Volume Shadow copies on your system.
  • 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 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, 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: 
    vssadmin list shadows >1 && notepad 1
  • On completion, Notepad will open with information in it. Copy and paste the content in your next reply;
 
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.


Contents of shadow copy set ID: {d9e65601-9b41-4a2b-81c4-b2627d60c39f}
Contained 1 shadow copies at creation time: 8/11/2015 4:16:06 PM
Shadow Copy ID: {fb73bbfe-22a7-40ac-8b13-34d5a4c77973}
Original Volume: (C:)\\?\Volume{d5739fc5-8691-4f33-bb4b-49d1df9e695c}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: Dads-Series7
Service Machine: Dads-Series7
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered


Contents of shadow copy set ID: {15e144dc-be7b-4890-8c5e-fc8adf12b8c5}
Contained 1 shadow copies at creation time: 8/14/2015 10:24:34 PM
Shadow Copy ID: {c7bf1be0-0b55-470e-a2b6-a9e9dbbc31ee}
Original Volume: (C:)\\?\Volume{d5739fc5-8691-4f33-bb4b-49d1df9e695c}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
Originating Machine: Dads-Series7
Service Machine: Dads-Series7
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered
 
I'm sorry to tell you this, but your COMPONENTS Hive is beyond repair. You'll have to do a repair install of your Windows system if you want to solve your issues. Do you know how to do that?
 
You must log in or register to reply here.

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

Back
Top