windows update problem

Status
Not open for further replies.
T

tomekniemcy

Well-known member
Joined
Apr 20, 2022
Posts
72
Hello, i have problem with update on my computer. file C:\Windows\System32\config\components has only 8kB SFCfix says:
AutoAnalysis::
WARNING: Failed to check store directories with return code 1 and error code ERROR_FILE_NOT_FOUND. COMPONENTS hive may be corrupt.


WARNING: Components hive failed size test and may be corrupt.

IS there any way to repair or rebuld this file C:\Windows\System32\config\components ?
 
I used componentscanner and it gave some new informations:
ComponentsScanner Version 1.3.0.0 by sysnative.com
Windows Version: Windows 10 21H2 x64 (10.0.19044.1620)
Start time: 24.04.2022 10:04:46
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 2
Number of values: 0

==== Critical Errors ====
COMPONENTS hive is very small (<6MB). This could indicate major corruption & large missing sections of data
COMPONENTS hive contains no parsable registry values
Critical registry key "COMPONENTS\CanonicalData\Catalogs" does not exist or could not be loaded
Critical registry key "COMPONENTS\CanonicalData\Deployments" does not exist or could not be loaded
Critical registry key "COMPONENTS\DerivedData\Components" does not exist or could not be loaded
Critical registry key "COMPONENTS\DerivedData\VersionedIndex" does not exist or could not be loaded
Critical registry key "COMPONENTS\ServicingStackVersions" does not exist or could not be loaded
Critical registry key "COMPONENTS\Installers" does not exist or could not be loaded
 
Looks at the size of your COMPONENTS hive and the keys which are missing. This is going to be impossible repair unfortunately. Do you have any suitable backups which you can restore from? If not, then you're going to have to perform a clean install.
 
I dont have any backups... So i have to reinstall my WIndows ? By the way how to reapir broken components file ? is there any software ?
 
Yes, you need to perform a clean install. There is no way to repair a COMPONENTS hive which is that corrupt unfortunately. Your COMPONENTS hive is 8KB, it's basically an empty hive with no information whatsoever.
 
I found corrupted components file bigger than 8Kb and succesfully repaired using componentsscanner.exe
Now i have errors as below: (CBS.log)
Code: 
2022-04-25 08:41:11, Info                  CBS    Setting ExecuteState key to: ExecuteStateNone
2022-04-25 08:41:11, Info                  CBS    Setting RollbackFailed flag to 0
2022-04-25 08:41:11, Info                  CBS    Clearing HangDetect value
2022-04-25 08:41:11, Info                  CBS    Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone
2022-04-25 08:41:11, Info                  CBS    Configured poqexec to pend to SetupExecute.
2022-04-25 08:41:11, Info                  CBS    Exec: Restoring driver operations because of a CSI commit failure.
2022-04-25 08:41:11, Error                 CBS    Exec: Failed to pend CSI transaction because transactions cannot be merged: 0. [HRESULT = 0x800703f1 - ERROR_BADDB]
2022-04-25 08:41:11, Info                  CBS    Perf: InstallUninstallChain complete.
2022-04-25 08:41:11, Info                  CSI    000011fa@2022/4/25:06:41:11.862 CSI Transaction @0x1eb4dcb6450 destroyed
2022-04-25 08:41:11, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x800703f1 - ERROR_BADDB]
2022-04-25 08:41:11, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800703f1 - ERROR_BADDB]
2022-04-25 08:41:11, Info                  CBS    WER: Generating failure report for package: Package_for_ServicingStack_2744~31bf3856ad364e35~amd64~~17763.2744.1.2, status: 0x800703f1, failure source: Execute, start state: Installed, target state: Installed, client id: WindowsUpdateAgent
2022-04-25 08:41:11, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-04-25 08:41:11, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2022-04-25 08:41:11, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220424184720.log to WER report.
2022-04-25 08:41:11, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220424120601.log to WER report.
2022-04-25 08:41:11, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220424114729.log to WER report.
2022-04-25 08:41:11, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220424113248.log to WER report.
2022-04-25 08:41:11, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220424111721.log to WER report.
2022-04-25 08:41:11, Info                  CBS    Not able to add %windir%\winsxs\poqexec.log to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-04-25 08:41:11, Info                  CBS    Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-04-25 08:41:11, Info                  CBS    Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-04-25 08:41:12, Info                  CBS    Reboot mark cleared
2022-04-25 08:41:12, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
2022-04-25 08:41:12, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2022-04-25 08:41:12, Info                  CBS    FinalCommitPackagesState: Started persisting state of packages
2022-04-25 08:41:12, Info                  CBS    Reporting package change for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.2803.1.3, current: Staged, pending: Default, start: Staged, applicable: Installed, target: Installed, limit: Installed, status: 0x0, failure source: Execute, reboot required: False, client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 251, first merged sequence: 251, reboot reason: DRIVERSPRESENT, RM App session: -1, RM App name: N/A, FileName in use: N/A, release type: Security Update, OC operation: False, download source: 0, download time (secs): 4294967295, download status: 0x0 (S_OK), Express download: False, Download Size: 0
2022-04-25 08:41:12, Info                  CBS    Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.2803.1.3, current: Staged, original: Staged, target: Installed, status: 0x800703f1, failure source: Execute, failure details: "(null)", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 251, first merged sequence: 251, pending decision: PackagePended_NoSmartPendingFlagSet, primitive execution context: Interactive
2022-04-25 08:41:12, Info                  CBS    The store corruption status report is incomplete. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-04-25 08:41:12, Info                  CBS    Execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2022-04-25 08:41:13, Info                  CBS    FinalCommitPackagesState: Completed persisting state of packages
2022-04-25 08:41:13, Info                  CBS    Enabling LKG boot option
2022-04-25 08:41:22, Info                  CBS    Exec: Will not run corruption repair because no store corruption found.
2022-04-25 08:41:22, Info                  CBS    Exec: Processing complete.  Session: 30955629_4043404150, Package: Package_for_ServicingStack_2744~31bf3856ad364e35~amd64~~17763.2744.1.2, Identifier: KB5011574 [HRESULT = 0x800703f1 - ERROR_BADDB]
2022-04-25 08:44:52, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2022-04-25 08:44:52, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2022-04-25 08:44:52, Info                  CBS    Execution Engine Finalize
2022-04-25 08:44:52, Info                  CBS    Execution Engine Finalize
2022-04-25 08:44:52, Info                  CBS    Ending the TiWorker main loop.
2022-04-25 08:44:52, Info                  CBS    Starting TiWorker finalization.
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2022-04-25 08:44:52, Info                  CBS    CBS Engine already deativated
2022-04-25 08:44:52, Info                  CBS    CBS Engine already deativated
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: WcpUnload
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: DrupUnload
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: DpxUnload
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2022-04-25 08:44:52, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2022-04-25 08:44:52, Info                  CBS    Ending TiWorker finalization.
2022-04-25 08:44:52, Info                  CBS    Ending the TrustedInstaller main loop.
2022-04-25 08:44:52, Info                  CBS    Starting TrustedInstaller finalization.
2022-04-25 08:44:52, Info                  CBS    Winlogon: Stopping notify server
2022-04-25 08:44:52, Info                  CBS    Winlogon: Unloading SysNotify DLL
2022-04-25 08:44:52, Info                  CBS    Ending TrustedInstaller finalization.
Can You advise something ?
 
tomekniemcy said:
I found corrupted components file bigger than 8Kb
Click to expand...
Was this from a backup of the same machine?

Could you please provide your COMPONENTS hive using the following instructions:

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
 
tomekniemcy said:
Windows Version: Windows 10 21H2 x64 (10.0.19044.1620)
Click to expand...
Did you run the ComponentsScanner on the same machine which the COMPONENTS hive is from?

Could you please provide your DRIVERS hive as well because there doesn't appear to be any immediate issues with the COMPONENTS hive which you provided me with.

Upload Drivers Hive
  1. Navigate to C:\Windows\System32\config
  2. Right-click on the current DRIVERS file and select copy
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  3. Right-click on your Desktop and select paste
  4. Right-click on the DRIVERS file on your Desktop and select Send To -> Compressed (zipped) Folder
  5. Upload the zip from your Desktop to a file sharing service such as Dropbox or OneDrive or SendSpace and include the link with your reply.
 
Hello repair process i did on another machine because i was not shure that componentsscanner is safe to use on the server. It was my mistake? I have problem with update on windows server 2019
 
That doesn't make any sense, your original problem was with a Windows 10 21H2 machine which had a completely corrupt COMPONENTS hive as shown from your ComponentScanner log header:

Rich (BB code): 
ComponentsScanner Version 1.3.0.0 by sysnative.com
Windows Version: Windows 10 21H2 x64 (10.0.19044.1620)
Start time: 24.04.2022 10:04:46
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 2
Number of values: 0

Since I told you that the machine is corrupt beyond repair, I asked if you had any backups and you said no. I then reiterated that you will need to perform a clean install. Afterwards, you miraculously found a supposed backup from the same machine, yet it was from a Windows Server 2019 build and didn't have any issues, although, you're still getting the BADDB error in your CBS log.

x BlueRobot said:
Do you have any suitable backups which you can restore from? If not, then you're going to have to perform a clean install.
Click to expand...
tomekniemcy said:
I found corrupted components file bigger than 8Kb and succesfully repaired using componentsscanner.exe
Click to expand...
x BlueRobot said:
Was this from a backup of the same machine?
Click to expand...
tomekniemcy said:
I recovered it from backup of the same machine
Click to expand...

So, it seems to me, since I said you had to do a clean install, you thought it was a good idea to download a COMPONENTS hive from either another machine or another Windows Update thread on Sysnative and then pretend that it was the COMPONENTS hive of the Windows 10 21H2 machine.
 
I was trying to simulate problem on my windows 10 machine... and it was not good idea.... SORRY... Can we back to the main problem on Windows Server 2019. Which files or logs do You need if we want to resolve problem with update KB5012647 ?
 
I think we can close this thread now. The solution to resolve your problem with your Windows 10 21H2 is to perform a clean install since your COMPONENTS hive is corrupt beyond repair.
 
Status
Not open for further replies.

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

Back
Top