Windows 10: Info on the Windows components store

Discus and support Info on the Windows components store in Windows 10 Performance & Maintenance to solve the problem; Hi What is the Windows components store and where is it? What is the command that can repair this archive? How the SFC utility is able to use... Discussion in 'Windows 10 Performance & Maintenance' started by balubeto, Oct 26, 2015.

  1. BALUBETO
    balubeto Win User

    Info on the Windows components store


    Hi

    What is the Windows components store and where is it?

    What is the command that can repair this archive?

    How the SFC utility is able to use it?

    Thanks

    Bye

    :)
     
    balubeto, Oct 26, 2015
    #1
  2. TS111111
    TS111111 Win User

    Window/Software freezes when trying to print or use any print functions (such as print preview or select print area in office)

    This is the corrupt logs:

    2017-02-25 13:53:36, Info CSI 000062c7 [SR] Cannot repair member file [l:11]'fdeploy.dll' of Microsoft-Windows-fdeploy, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:53:36, Info CSI 000062c9 [SR] Cannot repair member file [l:7]'fde.dll' of Microsoft-Windows-fde, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:53:36, Info CSI 000062cb [SR] Cannot repair member file [l:10]'gpedit.dll' of Microsoft-Windows-GroupPolicy-Admin-Gpedit, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:53:36, Info CSI 000062cd [SR] Cannot repair member file [l:10]'gptext.dll' of Microsoft-Windows-GroupPolicy-Gptext, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:53:37, Info CSI 000062ed [SR] Cannot repair member file [l:10]'gptext.dll' of Microsoft-Windows-GroupPolicy-Gptext, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:53:37, Info CSI 000062ee [SR] This component was referenced by [l:171]'Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds-Deployment'

    2017-02-25 13:53:37, Info CSI 000062f1 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\gptext.dll; source file in store is also corrupted

    2017-02-25 13:53:37, Info CSI 00006306 [SR] Cannot repair member file [l:11]'fdeploy.dll' of Microsoft-Windows-fdeploy, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:53:37, Info CSI 00006307 [SR] This component was referenced by [l:177]'Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell-Deployment'

    2017-02-25 13:53:37, Info CSI 00006308 [SR] This component was referenced by [l:120]'Microsoft-Windows-UserAccounts-WOW64-shell-Package~31bf3856ad364e35~amd64~~10.0.14393.0.b571b1397b12d9a8fbd6aa3a403d12ef'

    2017-02-25 13:53:37, Info CSI 0000630b [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\fdeploy.dll; source file in store is also corrupted

    2017-02-25 13:53:38, Info CSI 00006320 [SR] Cannot repair member file [l:10]'gpedit.dll' of Microsoft-Windows-GroupPolicy-Admin-Gpedit, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:53:38, Info CSI 00006321 [SR] This component was referenced by [l:171]'Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds-Deployment'

    2017-02-25 13:53:38, Info CSI 00006324 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\gpedit.dll; source file in store is also corrupted

    2017-02-25 13:53:38, Info CSI 0000633f [SR] Cannot repair member file [l:7]'fde.dll' of Microsoft-Windows-fde, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:53:38, Info CSI 00006340 [SR] This component was referenced by [l:177]'Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell-Deployment'

    2017-02-25 13:53:38, Info CSI 00006341 [SR] This component was referenced by [l:120]'Microsoft-Windows-UserAccounts-WOW64-shell-Package~31bf3856ad364e35~amd64~~10.0.14393.0.b571b1397b12d9a8fbd6aa3a403d12ef'

    2017-02-25 13:53:38, Info CSI 00006344 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\fde.dll; source file in store is also corrupted

    2017-02-25 13:53:40, Info CSI 00006371 [SR] Verify complete

    2017-02-25 13:53:40, Info CSI 00006372 [SR] Verifying 100 components

    2017-02-25 13:53:40, Info CSI 00006373 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:53:44, Info CSI 000063e8 [SR] Verify complete

    2017-02-25 13:53:44, Info CSI 000063e9 [SR] Verifying 100 components

    2017-02-25 13:53:44, Info CSI 000063ea [SR] Beginning Verify and Repair transaction

    2017-02-25 13:53:46, Info CSI 00006453 [SR] Verify complete

    2017-02-25 13:53:46, Info CSI 00006454 [SR] Verifying 100 components

    2017-02-25 13:53:46, Info CSI 00006455 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:53:49, Info CSI 000064c2 [SR] Verify complete

    2017-02-25 13:53:49, Info CSI 000064c3 [SR] Verifying 100 components

    2017-02-25 13:53:49, Info CSI 000064c4 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:53:51, Info CSI 0000652a [SR] Verify complete

    2017-02-25 13:53:51, Info CSI 0000652b [SR] Verifying 100 components

    2017-02-25 13:53:51, Info CSI 0000652c [SR] Beginning Verify and Repair transaction

    2017-02-25 13:53:53, Info CSI 00006592 [SR] Verify complete

    2017-02-25 13:53:53, Info CSI 00006593 [SR] Verifying 100 components

    2017-02-25 13:53:53, Info CSI 00006594 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:53:55, Info CSI 000065fc [SR] Verify complete

    2017-02-25 13:53:55, Info CSI 000065fd [SR] Verifying 100 components

    2017-02-25 13:53:55, Info CSI 000065fe [SR] Beginning Verify and Repair transaction

    2017-02-25 13:53:58, Info CSI 00006682 [SR] Verify complete

    2017-02-25 13:53:58, Info CSI 00006683 [SR] Verifying 100 components

    2017-02-25 13:53:58, Info CSI 00006684 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:00, Info CSI 0000670b [SR] Verify complete

    2017-02-25 13:54:00, Info CSI 0000670c [SR] Verifying 100 components

    2017-02-25 13:54:00, Info CSI 0000670d [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:02, Info CSI 00006774 [SR] Verify complete

    2017-02-25 13:54:02, Info CSI 00006775 [SR] Verifying 100 components

    2017-02-25 13:54:02, Info CSI 00006776 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:04, Info CSI 000067db [SR] Verify complete

    2017-02-25 13:54:04, Info CSI 000067dc [SR] Verifying 100 components

    2017-02-25 13:54:04, Info CSI 000067dd [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:06, Info CSI 00006846 [SR] Verify complete

    2017-02-25 13:54:06, Info CSI 00006847 [SR] Verifying 100 components

    2017-02-25 13:54:06, Info CSI 00006848 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:08, Info CSI 000068b1 [SR] Verify complete

    2017-02-25 13:54:08, Info CSI 000068b2 [SR] Verifying 100 components

    2017-02-25 13:54:08, Info CSI 000068b3 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:10, Info CSI 0000691c [SR] Verify complete

    2017-02-25 13:54:10, Info CSI 0000691d [SR] Verifying 100 components

    2017-02-25 13:54:10, Info CSI 0000691e [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:12, Info CSI 00006986 [SR] Verify complete

    2017-02-25 13:54:12, Info CSI 00006987 [SR] Verifying 100 components

    2017-02-25 13:54:12, Info CSI 00006988 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:14, Info CSI 000069ee [SR] Verify complete

    2017-02-25 13:54:14, Info CSI 000069ef [SR] Verifying 100 components

    2017-02-25 13:54:14, Info CSI 000069f0 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:16, Info CSI 00006a57 [SR] Verify complete

    2017-02-25 13:54:16, Info CSI 00006a58 [SR] Verifying 100 components

    2017-02-25 13:54:16, Info CSI 00006a59 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:17, Info CSI 00006ac0 [SR] Verify complete

    2017-02-25 13:54:18, Info CSI 00006ac1 [SR] Verifying 100 components

    2017-02-25 13:54:18, Info CSI 00006ac2 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:20, Info CSI 00006b34 [SR] Verify complete

    2017-02-25 13:54:20, Info CSI 00006b35 [SR] Verifying 100 components

    2017-02-25 13:54:20, Info CSI 00006b36 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:22, Info CSI 00006ba0 [SR] Verify complete

    2017-02-25 13:54:22, Info CSI 00006ba1 [SR] Verifying 100 components

    2017-02-25 13:54:22, Info CSI 00006ba2 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:25, Info CSI 00006c07 [SR] Verify complete

    2017-02-25 13:54:25, Info CSI 00006c08 [SR] Verifying 100 components

    2017-02-25 13:54:25, Info CSI 00006c09 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:27, Info CSI 00006c6f [SR] Verify complete

    2017-02-25 13:54:27, Info CSI 00006c70 [SR] Verifying 100 components

    2017-02-25 13:54:27, Info CSI 00006c71 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:29, Info CSI 00006cd6 [SR] Verify complete

    2017-02-25 13:54:29, Info CSI 00006cd7 [SR] Verifying 100 components

    2017-02-25 13:54:29, Info CSI 00006cd8 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:31, Info CSI 00006d3d [SR] Verify complete

    2017-02-25 13:54:31, Info CSI 00006d3e [SR] Verifying 100 components

    2017-02-25 13:54:31, Info CSI 00006d3f [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:33, Info CSI 00006da5 [SR] Verify complete

    2017-02-25 13:54:33, Info CSI 00006da6 [SR] Verifying 100 components

    2017-02-25 13:54:33, Info CSI 00006da7 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:36, Info CSI 00006e0c [SR] Verify complete

    2017-02-25 13:54:36, Info CSI 00006e0d [SR] Verifying 100 components

    2017-02-25 13:54:36, Info CSI 00006e0e [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:38, Info CSI 00006e73 [SR] Verify complete

    2017-02-25 13:54:38, Info CSI 00006e74 [SR] Verifying 8 components

    2017-02-25 13:54:38, Info CSI 00006e75 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:39, Info CSI 00006e7e [SR] Verify complete

    2017-02-25 13:54:39, Info CSI 00006e7f [SR] Repairing 4 components

    2017-02-25 13:54:39, Info CSI 00006e80 [SR] Beginning Verify and Repair transaction

    2017-02-25 13:54:39, Info CSI 00006e82 [SR] Cannot repair member file [l:10]'gptext.dll' of Microsoft-Windows-GroupPolicy-Gptext, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:54:39, Info CSI 00006e84 [SR] Cannot repair member file [l:11]'fdeploy.dll' of Microsoft-Windows-fdeploy, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:54:39, Info CSI 00006e86 [SR] Cannot repair member file [l:10]'gpedit.dll' of Microsoft-Windows-GroupPolicy-Admin-Gpedit, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:54:39, Info CSI 00006e88 [SR] Cannot repair member file [l:7]'fde.dll' of Microsoft-Windows-fde, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:54:39, Info CSI 00006e8b [SR] Cannot repair member file [l:7]'fde.dll' of Microsoft-Windows-fde, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:54:39, Info CSI 00006e8c [SR] This component was referenced by [l:177]'Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell-Deployment'

    2017-02-25 13:54:39, Info CSI 00006e8d [SR] This component was referenced by [l:120]'Microsoft-Windows-UserAccounts-WOW64-shell-Package~31bf3856ad364e35~amd64~~10.0.14393.0.b571b1397b12d9a8fbd6aa3a403d12ef'

    2017-02-25 13:54:39, Info CSI 00006e90 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\fde.dll; source file in store is also corrupted

    2017-02-25 13:54:39, Info CSI 00006e94 [SR] Cannot repair member file [l:10]'gptext.dll' of Microsoft-Windows-GroupPolicy-Gptext, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:54:39, Info CSI 00006e95 [SR] This component was referenced by [l:171]'Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds-Deployment'

    2017-02-25 13:54:39, Info CSI 00006e98 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\gptext.dll; source file in store is also corrupted

    2017-02-25 13:54:39, Info CSI 00006e9c [SR] Cannot repair member file [l:10]'gpedit.dll' of Microsoft-Windows-GroupPolicy-Admin-Gpedit, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:54:39, Info CSI 00006e9d [SR] This component was referenced by [l:171]'Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds-Deployment'

    2017-02-25 13:54:39, Info CSI 00006ea0 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\gpedit.dll; source file in store is also corrupted

    2017-02-25 13:54:39, Info CSI 00006ea4 [SR] Cannot repair member file [l:11]'fdeploy.dll' of Microsoft-Windows-fdeploy, version 10.0.14393.0, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2017-02-25 13:54:39, Info CSI 00006ea5 [SR] This component was referenced by [l:177]'Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell-Deployment'

    2017-02-25 13:54:39, Info CSI 00006ea6 [SR] This component was referenced by [l:120]'Microsoft-Windows-UserAccounts-WOW64-shell-Package~31bf3856ad364e35~amd64~~10.0.14393.0.b571b1397b12d9a8fbd6aa3a403d12ef'

    2017-02-25 13:54:39, Info CSI 00006ea9 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SysWOW64\fdeploy.dll; source file in store is also corrupted

    2017-02-25 13:54:39, Info CSI 00006eab [SR] Repair complete

    2017-02-25 13:54:39, Info CSI 00006eac [SR] Committing transaction

    2017-02-25 13:54:39, Info CSI 00006eb1 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
     
    TS111111, Oct 26, 2015
    #2
  3. LYDIAWO
    LydiaWo Win User
    Windows 10 wouldn't boot for about 2 hours....

    After the restart I ran chkdsk c: /f /r and let it complete. Then I tried sfc /scannow and it was unable to complete. The output file contained this:

    2018-01-02 18:59:41, Info CSI 00000e51 [SR] Beginning Verify and Repair transaction

    2018-01-02 18:59:42, Info CSI 00000e54 [SR] Cannot verify component files for Microsoft-Windows-CommandPrompt-Shortcut, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, manifest is damaged (true)

    2018-01-02 18:59:47, Info CSI 00000ed8 [SR] Verify complete

    2018-01-02 18:59:47, Info CSI 00000ed9 [SR] Verifying 100 components

    2018-01-02 18:59:47, Info CSI 00000eda [SR] Beginning Verify and Repair transaction

    2018-01-02 18:59:53, Info CSI 00000f47 [SR] Verify complete

    2018-01-02 18:59:54, Info CSI 00000f48 [SR] Verifying 100 components

    2018-01-02 18:59:54, Info CSI 00000f49 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:00:00, Info CSI 00000fba [SR] Verify complete

    2018-01-02 19:00:00, Info CSI 00000fbb [SR] Verifying 100 components

    2018-01-02 19:00:00, Info CSI 00000fbc [SR] Beginning Verify and Repair transaction

    2018-01-02 19:00:05, Info CSI 00001031 [SR] Verify complete

    2018-01-02 19:00:06, Info CSI 00001032 [SR] Verifying 100 components

    2018-01-02 19:00:06, Info CSI 00001033 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:00:11, Info CSI 000010a3 [SR] Verify complete

    2018-01-02 19:00:11, Info CSI 000010a4 [SR] Verifying 100 components

    2018-01-02 19:00:11, Info CSI 000010a5 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:00:16, Info CSI 0000110a [SR] Verify complete

    2018-01-02 19:00:17, Info CSI 0000110b [SR] Verifying 100 components

    2018-01-02 19:00:17, Info CSI 0000110c [SR] Beginning Verify and Repair transaction

    2018-01-02 19:00:22, Info CSI 00001173 [SR] Verify complete

    2018-01-02 19:00:22, Info CSI 00001174 [SR] Verifying 100 components

    2018-01-02 19:00:22, Info CSI 00001175 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:00:28, Info CSI 000011dd [SR] Verify complete

    2018-01-02 19:00:28, Info CSI 000011de [SR] Verifying 100 components

    2018-01-02 19:00:28, Info CSI 000011df [SR] Beginning Verify and Repair transaction

    2018-01-02 19:00:34, Info CSI 0000124e [SR] Verify complete

    2018-01-02 19:00:34, Info CSI 0000124f [SR] Verifying 100 components

    2018-01-02 19:00:34, Info CSI 00001250 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:00:42, Info CSI 000012d1 [SR] Verify complete

    2018-01-02 19:00:42, Info CSI 000012d2 [SR] Verifying 100 components

    2018-01-02 19:00:42, Info CSI 000012d3 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:00:52, Info CSI 00001366 [SR] Verify complete

    2018-01-02 19:00:52, Info CSI 00001367 [SR] Verifying 100 components

    2018-01-02 19:00:52, Info CSI 00001368 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:01:04, Info CSI 0000141a [SR] Verify complete

    2018-01-02 19:01:05, Info CSI 0000141b [SR] Verifying 100 components

    2018-01-02 19:01:05, Info CSI 0000141c [SR] Beginning Verify and Repair transaction

    2018-01-02 19:01:11, Info CSI 0000148c [SR] Verify complete

    2018-01-02 19:01:11, Info CSI 0000148d [SR] Verifying 100 components

    2018-01-02 19:01:11, Info CSI 0000148e [SR] Beginning Verify and Repair transaction

    2018-01-02 19:01:16, Info CSI 000014fa [SR] Verify complete

    2018-01-02 19:01:16, Info CSI 000014fb [SR] Verifying 100 components

    2018-01-02 19:01:16, Info CSI 000014fc [SR] Beginning Verify and Repair transaction

    2018-01-02 19:01:27, Info CSI 0000159b [SR] Verify complete

    2018-01-02 19:01:28, Info CSI 0000159c [SR] Verifying 100 components

    2018-01-02 19:01:28, Info CSI 0000159d [SR] Beginning Verify and Repair transaction

    2018-01-02 19:01:31, Info CSI 00001602 [SR] Verify complete

    2018-01-02 19:01:31, Info CSI 00001603 [SR] Verifying 100 components

    2018-01-02 19:01:31, Info CSI 00001604 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:01:33, Info CSI 00001669 [SR] Verify complete

    2018-01-02 19:01:33, Info CSI 0000166a [SR] Verifying 100 components

    2018-01-02 19:01:33, Info CSI 0000166b [SR] Beginning Verify and Repair transaction

    2018-01-02 19:01:41, Info CSI 000016e2 [SR] Verify complete

    2018-01-02 19:01:41, Info CSI 000016e3 [SR] Verifying 100 components

    2018-01-02 19:01:41, Info CSI 000016e4 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:01:47, Info CSI 00001756 [SR] Verify complete

    2018-01-02 19:01:48, Info CSI 00001757 [SR] Verifying 100 components

    2018-01-02 19:01:48, Info CSI 00001758 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:01:51, Info CSI 0000175a [SR] Cannot repair member file [l:13]'badgelogo.png' of microsoft-windows-inputapp.appxmain, version 10.0.16299.125, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2018-01-02 19:01:54, Info CSI 0000178d [SR] Cannot repair member file [l:13]'badgelogo.png' of microsoft-windows-inputapp.appxmain, version 10.0.16299.125, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2018-01-02 19:01:54, Info CSI 0000178e [SR] This component was referenced by [l:79]'Package_749_for_KB4054517~31bf3856ad364e35~amd64~~10.0.1.6.4054517-1617_neutral'

    2018-01-02 19:01:54, Info CSI 00001791 [SR] Could not reproject corrupted file \??\C:\WINDOWS\SystemApps\InputApp_cw5n1h2txyewy\Assets\badgelogo.png; source file in store is also corrupted

    2018-01-02 19:01:56, Info CSI 000017d3 [SR] Verify complete

    2018-01-02 19:01:56, Info CSI 000017d4 [SR] Verifying 100 components

    2018-01-02 19:01:56, Info CSI 000017d5 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:02:01, Info CSI 00001840 [SR] Verify complete

    2018-01-02 19:02:01, Info CSI 00001841 [SR] Verifying 100 components

    2018-01-02 19:02:01, Info CSI 00001842 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:02:07, Info CSI 000018af [SR] Verify complete

    2018-01-02 19:02:07, Info CSI 000018b0 [SR] Verifying 100 components

    2018-01-02 19:02:07, Info CSI 000018b1 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:02:08, Info CSI 000018b3 [SR] Cannot repair member file [l:27]'Video-TVVideoControl-DL.man' of Microsoft-Windows-Migration-DownlevelManifests-multimedia, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
    in the store, hash mismatch

    2018-01-02 19:02:12, Info CSI 000018f9 [SR] Cannot repair member file [l:27]'Video-TVVideoControl-DL.man' of Microsoft-Windows-Migration-DownlevelManifests-multimedia, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
    in the store, hash mismatch

    2018-01-02 19:02:12, Info CSI 000018fa [SR] This component was referenced by [l:144]'Microsoft-Windows-Client-Features-Package0019~31bf3856ad364e35~amd64~~10.0.16299.15.microsoft-windows-client-features-deployment00190-Deployment'

    2018-01-02 19:02:12, Info CSI 000018fd [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\migwiz\dlmanifests\Video-TVVideoControl-DL.man; source file in store is also corrupted

    2018-01-02 19:02:13, Info CSI 00001929 [SR] Verify complete

    2018-01-02 19:02:13, Info CSI 0000192a [SR] Verifying 100 components

    2018-01-02 19:02:13, Info CSI 0000192b [SR] Beginning Verify and Repair transaction

    2018-01-02 19:02:13, Info CSI 0000192d [SR] Cannot repair member file [l:25]'ADSI-LDAP-Provider-DL.man' of Microsoft-Windows-Migration-DownlevelManifests-onecore, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
    the store, hash mismatch

    2018-01-02 19:02:20, Info CSI 0000197c [SR] Cannot repair member file [l:25]'ADSI-LDAP-Provider-DL.man' of Microsoft-Windows-Migration-DownlevelManifests-onecore, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
    the store, hash mismatch

    2018-01-02 19:02:20, Info CSI 0000197d [SR] This component was referenced by [l:144]'Microsoft-Windows-Client-Features-Package0019~31bf3856ad364e35~amd64~~10.0.16299.15.microsoft-windows-client-features-deployment00190-Deployment'

    2018-01-02 19:02:20, Info CSI 00001980 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\migwiz\dlmanifests\ADSI-LDAP-Provider-DL.man; source file in store is also corrupted

    2018-01-02 19:02:22, Info CSI 000019b6 [SR] Verify complete

    2018-01-02 19:02:22, Info CSI 000019b7 [SR] Verifying 100 components

    2018-01-02 19:02:22, Info CSI 000019b8 [SR] Beginning Verify and Repair transaction

    2018-01-02 19:02:22, Info CSI 000019ba [SR] Cannot repair member file [l:28]'UsbMigPlugin-Replacement.man' of Microsoft-Windows-Migration-ReplacementManifests-drivers, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
    in the store, hash mismatch

    So. Any recommendation on my next steps?
     
    LydiaWo, Oct 26, 2015
    #3
  4. JOHNC
    JohnC Win User

    Info on the Windows components store

    The windows component store services the windows image. It is the WinSxS folder. Use the DISM command to repair this, if needed. SFC uses the WinSxS folder to check system files, if it is corrupt things don't get fixed. This is a bit simplified, but I hope you get the general idea.
     
    JohnC, Oct 26, 2015
    #4
  5. BALUBETO
    balubeto Win User
    I can not understand this phrase: "The Windows component store services the windows image."

    Why?

    Thanks

    Bye
     
    balubeto, Oct 26, 2015
    #5
  6. JOHNC
    JohnC Win User
    SFC uses the WinSxS folder to check and repair if needed (service) the windows image.
     
    JohnC, Oct 27, 2015
    #6
  7. BALUBETO
    balubeto Win User
    Thus, the Windows component store is the C:\Windows\WinSxS directory that contains the files needed SFC utility to restore the offline system image with the sfc /scannow /offbootdir=C:\ /offwindir=D:\windows command.

    If this store is corrupted, the Dism /Online /Cleanup-Image /RestoreHealth command attempts to restore it.

    If this is right, why the sfc uses the "System Reserved" partition?

    Thanks

    Bye
     
    balubeto, Oct 27, 2015
    #7
  8. JOHNC
    JohnC Win User

    Info on the Windows components store

    Google or Bing is a faster place for you to look -lots smarter too.
     
    JohnC, Oct 27, 2015
    #8
  9. LX07
    lx07 Win User
    It doesn't. The system reserved partition is used for bitlocker and booting - nothing to do with sfc or the component store.
     
    lx07, Oct 27, 2015
    #9
  10. BALUBETO
    balubeto Win User
    Excuse, why the sfc /scannow /offbootdir=C:\ /offwindir=D:\windows command has the offwindir option that points to the "System Reserved" partition?

    Thanks

    Bye
     
    balubeto, Oct 27, 2015
    #10
  11. BALUBETO
    balubeto Win User
    How should I do to repair the Windows component store of an offline image of Windows?

    Thanks

    Bye
     
    balubeto, Oct 27, 2015
    #11
  12. BALUBETO
    balubeto Win User
    If, from the "Command prompt" window of a DVD of Windows 10, I had to run the Dism /Image:<Offline_image_primary_partition_letter>:\ /Cleanup-Image /RestoreHealth /Source:wim:<DVD_drive_letter>:\Sources\Install.wim:<Image_Index> /limitaccess or Dism /Image:<Offline_image_primary_partition_letter>:\ /Cleanup-Image /RestoreHealth /Source:esd:<DVD_drive_letter>:\Sources\Install.esd:<Image_Index> /limitaccess command, I could also repair the Windows component store of the offline image?

    Thanks

    Bye
     
    balubeto, Oct 29, 2015
    #12
  13. LX07
    lx07 Win User

    Info on the Windows components store

    you would have to change to c: first (assuming that is where your windows install is) and you don't need the word "costa"

    Code: X:\Sources>c: C:\>dism /image:c:\ /cleanup-image /restorehealth[/quote] The DISM syntax is explained here DISM - Deployment Image Servicing and Management - you may want to give it a read.

    You may want to use this method to do /revertpendingactions if you can't boot after installing some upgrade.
    Getting out of a no boot situation after installing updates on Windows 7-2008R2 - The Windows Servicing Guy - Site Home - TechNet Blogs

    If you need to do sfc at boot it is explained here SFC /SCANNOW : Run in Command Prompt at Boot - Windows 7 Help Forums
     
    lx07, Apr 4, 2018
    #13
Thema:

Info on the Windows components store

Loading...

  1. Info on the Windows components store - Similar Threads - Info components store

  2. the component store is repairable?

    in Windows 10 Software and Apps
    the component store is repairable?: Been having freezing issues with my computer for a while. Been trying to figure out how to resolve it.Trying to check the Window integrity with the DISM commands to resolve my issues but the commands aren't working.The first 2 commands...

  3. the component store is repairable?

    in Windows 10 Gaming
    the component store is repairable?: Been having freezing issues with my computer for a while. Been trying to figure out how to resolve it.Trying to check the Window integrity with the DISM commands to resolve my issues but the commands aren't working.The first 2 commands...

  4. the component store is repairable?

    in Windows 10 BSOD Crashes and Debugging
    the component store is repairable?: Been having freezing issues with my computer for a while. Been trying to figure out how to resolve it.Trying to check the Window integrity with the DISM commands to resolve my issues but the commands aren't working.The first 2 commands...

  5. The component store is repairable

    in Windows 10 BSOD Crashes and Debugging
    The component store is repairable: Hello, my computer has been going slow and crashing since the last update, and I've tried various methods to fix it repairing with media creation tool/windows 10 update assistant, troubleshoot, sfc /scannow, dism ,chkdsk but none seem to work. ScanHealth and CheckHealth...

  6. The component store is corrupted.

    in Windows 10 Ask Insider
    The component store is corrupted.: Hello everyone, I'm experiencing a problem where I can't download any DirectX, NET Framework, etc. because of the Component Store being corrupted with an Error 0x80073712. I tried running DISM /Online /Cleanup-Image /CheckHealth, and it said that the Component Store is...

  7. component store

    in Windows 10 Installation and Upgrade
    component store: I have researched this problem for more than a week and tried all the stock solutions. I can run dism in recovery mode. After running restorehealth, scanhealth and checkhealth both show no corruptions in recovery modee. But in normal booted Windows, checkhealth says that...

  8. The component store

    in Windows 10 Network and Sharing
    The component store: My results from the DISM commands come back and say that the component store has been corrupted. How do I repair it? Kenneth Perry https://answers.microsoft.com/en-us/windows/forum/all/the-component-store/883d8fc6-6d2d-4e5b-b4ba-00018d38ee3c"

  9. The component store is repairable?

    in Windows 10 BSOD Crashes and Debugging
    The component store is repairable?: Hello I had ran DSIM ScanHealth, CheckHealth and CHKDSK and while no errors such as a corruption were noted I did see this result "The Component Store is Repairable" I don't know what this means is it a error? A corruption? Does RestoreHealth need to be ran? I've been...

  10. bios post screen shows incoherent component info

    in Windows 10 Drivers and Hardware
    bios post screen shows incoherent component info: i boot up the computer and the bios post screen shows normal except for 4 keyboards 2 mice 2 hubs. when i only have 1 keyboard and 1 mice connected. what is this all about? idk what hubs is. maybe the dvd rom drive? 40238