! In dit forumonderdeel kunnen forumgebruikers alleen op eigen onderwerpen reageren.

1. Voor het verhelpen van problemen met Windows Update zijn vaak meerdere stappen nodig, helaas bestaat er geen all-in-one tool om dit soort problemen op te lossen.
2. Neem a.u.b. nooit instructies van gelijkaardige problemen over, dit kan averechts werken en voor problemen zorgen. Open altijd een eigen onderwerp en volg de daarin gegeven instructies op.
Toon berichten van afgelopen
Sorteer op
Plaats reactie
Beste bezoeker, welkom op PC Web Plus!
PC Web Plus is een gratis computer helpdesk, wij helpen u graag verder met al uw vragen en problemen. Ervaar het gemak van hulp op ons forum door een account te registreren.

1 door Jonathan21
Security colleague
Hi Ted,

Windows server 2022 Standard
When you have time, you can watch this, please.
Corrupt registry key and missing files

Code: Selecteer alles

ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows Server 2022 Standard Evaluation x64 (10.0.20348.2461)
Start time: 2024-05-26T10:38:56
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 115212
Number of values: 337634

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====

== Missing Files ==
C:\Windows\winsxs\Catalogs\2a2200185df62663ce8980a7fa56e1f7c6604c36cd7d41e4c5ca3b8bb4db5d55.cat (CanonicalData\Deployments\networkcont..-deployment_31bf3856ad364e35_10.0.20348.1607_fa460206d08778eb contains CatalogThumbprint value 2a2200185df62663ce8980a7fa56e1f7c6604c36cd7d41e4c5ca3b8bb4db5d55 but no corresponding file found in WinSxS)
C:\Windows\winsxs\Catalogs\8c1c61b05b94364a43ec76f8eb5744fa8d6c245d0393209e216e83959d8f653e.cat (CanonicalData\Deployments\networkcont..-deployment_31bf3856ad364e35_10.0.20348.2322_fa68e62cd06cd4c8 contains CatalogThumbprint value 8c1c61b05b94364a43ec76f8eb5744fa8d6c245d0393209e216e83959d8f653e but no corresponding file found in WinSxS)
C:\Windows\winsxs\Catalogs\aa483bf250ab71ed499628544bfa8dac666b6653f82801a74575b334de666f3c.cat (CanonicalData\Deployments\networkcont..-deployment_31bf3856ad364e35_10.0.20348.803_3ab2be9a2826161c contains CatalogThumbprint value aa483bf250ab71ed499628544bfa8dac666b6653f82801a74575b334de666f3c but no corresponding file found in WinSxS)

== Missing Registry Keys ==
CanonicalData\Catalogs\2a2200185df62663ce8980a7fa56e1f7c6604c36cd7d41e4c5ca3b8bb4db5d55 (CanonicalData\Deployments\networkcont..-deployment_31bf3856ad364e35_10.0.20348.1607_fa460206d08778eb has CatalogThumbprint value 2a2200185df62663ce8980a7fa56e1f7c6604c36cd7d41e4c5ca3b8bb4db5d55 but no corresponding Catalog key exists)
CanonicalData\Catalogs\8c1c61b05b94364a43ec76f8eb5744fa8d6c245d0393209e216e83959d8f653e (CanonicalData\Deployments\networkcont..-deployment_31bf3856ad364e35_10.0.20348.2322_fa68e62cd06cd4c8 has CatalogThumbprint value 8c1c61b05b94364a43ec76f8eb5744fa8d6c245d0393209e216e83959d8f653e but no corresponding Catalog key exists)
CanonicalData\Catalogs\aa483bf250ab71ed499628544bfa8dac666b6653f82801a74575b334de666f3c (CanonicalData\Deployments\networkcont..-deployment_31bf3856ad364e35_10.0.20348.803_3ab2be9a2826161c has CatalogThumbprint value aa483bf250ab71ed499628544bfa8dac666b6653f82801a74575b334de666f3c but no corresponding Catalog key exists)



Storing 0KB in C:\Users\Administrator\AppData\Local\Sysnative\ComponentsScanner

Finish Time: 2024-05-26T10:39:57. Corruption scan time: 48,593983s
===========================EOF===========================

Code: Selecteer alles

PS C:\Users\Administrator> sfc /scannow

Start system scanning. This may take some time.

Start the system scan verification phase.
Verification is 100% complete.

The Windows resource protection program found no integrity violations.

PS C:\Users\Administrator> Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Management and Maintenance Tool
Version: 10.0.20348.681

Image version: 10.0.20348.2461

[===========================84.9%=================         ]
[==========================100.0%==========================]The restoration has been carried out.
The operation was successful.
PS C:\Users\Administrator>
Documents attached on this link
https://gofile.io/d/3kERPX

thank you in advance
2 door Maxstar
Administrator
Administrator
Hi Christopher,

In general you can ignore such warnings in the ComponentsScanner log, and they are usually not real problems! But in your logs I noticed other issues which may causing issues with updating this server?

2024-05-25 12:14:46, Info                  CSI    0000006a The queue has completed running, and AI failures have occured.
2024-05-25 12:14:46, Info                  CSI    0000006b ==Error Summary Start==
2024-05-25 12:14:46, Error                 CSI    0000006c (F) Installer: LodCtr Installer	Binary Name: PerfCounterInstaller.dll	ErrorCode: 800707d1	Phase: 31	Mode: Delta	Component: NONE[gle=0x80004005]
2024-05-25 12:14:46, Info                  CSI    0000006d ==Error Summary End==
2024-05-25 12:14:46, Info                  CSI    0000006e Rolling back transactions...

2024-05-25 12:14:47, Error                 CBS    Exec: An error occurred while committing the transaction, the transaction has been rolled back. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]

Are you experiencing rollback issue when attemting to update, this because error 0x800707d1 which could de related to a bad/imcompatible driver?
Member of UNITE Unified Network of Instructors and Trained Eliminators (Unite Against Malware)
4 door Maxstar
Administrator
Administrator
The setupapi.dev.log is clean, as well as the CBS logs except the error line above. The COMPONENTS hive is also clean and the warnings in the ComponentsScanner log will be related to updates which has been superseded already. I've seen multiple systems which such remnants, and I have also VM's with orphaned deployments keys without the associated catalogs keys and .cat file under the catalogs DIR.

networkcont..-deployment_31bf3856ad364e35_10.0.20348.803 = KB5014665 (preview) 23 juni 2022
networkcont..-deployment_31bf3856ad364e35_10.0.20348.1607 = KB5023705 14 maart 2023
networkcont..-deployment_31bf3856ad364e35_10.0.20348.2322 = KB5034770 13 februari 2024
Member of UNITE Unified Network of Instructors and Trained Eliminators (Unite Against Malware)
5 door Jonathan21
Security colleague
Hi,

Possibly delete it with a fixlist.
I found these updates.
For now I am mounting a virtual machine with the package Feature update to Microsoft server operating system, version 21H2 (20348.1607) amd64 to see if I can do a sfcfixScript to modify these incorrect values on the CatalogThumbprint value.
This will give me a practical exercise.
:dank: :goed: Thank you for this information. I did not take the time to analyze the cbs.log file
7 door Jonathan21
Security colleague
Please find below the commands executed.

DISM/online/cleanup-image/AnalyzeComponentStore

Code: Selecteer alles

Microsoft Windows [version 10.0.20348.2461]
(c) Microsoft Corporation. All rights reserved.

C: Users Administrator>DISM/online/cleanup-image/AnalyzeComponentStore

Deployment Image Management and Maintenance Tool
Version: 10.0.20348.681

Image version: 10.0.20348.2461

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

Component Store Information (WinSxS):

Windows Explorer reported the size of the component store. : 11.54 GB

Actual size of component store: 11.40 GB

    Shared with Windows: 6.17 GB
    Backups and features disabled: 3.40 GB
    Cache and temporary data: 1.82 GB

Last cleaning date: 2024-05-24 07:59:56

Number of recoverable packages: 0
Recommended Component Store Cleaning: No

The operation was successful.
Restart Windows to complete this operation.
Do you want to restart the computer now? (Y/N) y

DISM /online /cleanup-image /StartComponentCleanup

Code: Selecteer alles

Microsoft Windows [version 10.0.20348.2461]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Administrator>DISM /online /cleanup-image /StartComponentCleanup

Deployment image management and maintenance tool
Version: 10.0.20348.681

Image version: 10.0.20348.2461

[===== 10.0% ]
[==========================100.0%==========================]
The operation was successful.

C:\Users\Administrator>
Always the same errors in the ComponentsScanner file. I will run a fixlist to remove them and I will make a report.
Laatst gewijzigd door Jonathan21 op 27 mei 2024 08:18, 1 keer totaal gewijzigd.
8 door Jonathan21
Security colleague
Hi Ted, :good:

Code: Selecteer alles

2024-05-25 12:14:46, Error                 CSI    0000006c (F) Installer: LodCtr Installer	Binary Name: PerfCounterInstaller.dll	ErrorCode: 800707d1	Phase: 31	Mode: Delta	Component: NONE[gle=0x80004005]
It’s all good, you can put the subject in solved mode. :goed:
1) I fixed the above error with the LodCtr /R command

2) For registry key remnants, I made a fixlist, run the command

Code: Selecteer alles

sfc /scannow
DISM /online /cleanup-image /AnalyzeComponentStore
DISM /online /cleanup-image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth
ComponentsScanner is clean:
Spoiler: weergeven

Code: Selecteer alles

ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows Server 2022 Standard Evaluation x64 (10.0.20348.2461)
Start time: 2024-05-27T07:01:56
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 115210
Number of values: 339261

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====
None


Storing 5,44KB in C:\Users\Administrator\AppData\Local\Sysnative\ComponentsScanner
Archived report directory contains 2 files

Finish Time: 2024-05-27T07:03:01. Corruption scan time: 53,9926247s
===========================EOF===========================
Regards,
Plaats reactie

Maak een account aan of log in om deel te nemen aan de discussie

Je moet lid zijn om een ​​reactie te kunnen plaatsen

Maak een account aan

Geen lid? Registreer om lid te worden van onze community
Leden kunnen hun eigen onderwerpen starten en zich abonneren op onderwerpen
Het is gratis en duurt maar een minuut

Registreer

Log in

Gebruikersnaam
Wachtwoord

Terug naar “Windows Update problemen & SFC Scannow corrupties”