[SOLVED] [Win7SP1] CheckSUR: Checking Component Store (Found 18 errors)

lomas · Jun 2, 2017

Thanks in advance.

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.23471
2017-06-02 19:41

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Payload File Missing 0x00000000 sage100.format.ubl.dll x86_com.sage.format.ubl_77d7af533b8e0189_3.0.0.2_none_ae7ab487c89b961a
(f) CSI Payload File Missing 0x00000000 sage100.cbase.local.dll x86_com.sage.cbase.local_77d7af533b8e0189_14.0.0.3_none_6ab108049a10232c
(f) CSI Payload File Missing 0x00000000 sage100.cbase.interface.dll x86_com.sage.cbase.interface_77d7af533b8e0189_14.0.0.3_none_97c9f0e7ec738ada
(f) CSI Payload File Missing 0x00000000 sage100registration.dll x86_com.sage.common.registration_77d7af533b8e0189_5.0.0.2_none_e5da880a7151aa52
(f) CSI Payload File Missing 0x00000000 sage100.core.runtime.dll x86_com.sage.core.runtime_77d7af533b8e0189_7.0.0.2_none_46a70ae8fdbf9371
(f) CSI Payload File Missing 0x00000000 sage100.core.runtime.dll amd64_com.sage.core.runtime_77d7af533b8e0189_7.0.0.2_none_fef9d411e9436a6b
(f) CSI Missing Winning Component Key 0x00000000 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8 Error deleting winners map value.

Summary:
Seconds executed: 196
Found 18 errors
CSI Unexpected Failure Total count: 6
CSI Payload File Missing Total count: 6
CSI Missing Winning Component Key Total count: 6

lomas · Jun 3, 2017

I did a "sfc /scannow" it return that I may have some damaged files, but when I look for CBS.log I can't find it.

ChuckR · Jun 3, 2017

If you are running Windows 7 it should be in C:\Windows\Logs\CBS. That is where I find mine. The one problem I have is that if I try and look at it when I have run SFC /SCANNOW it is active and I can't look at it. I forgot how to force close it.

lomas · Jun 3, 2017

I can't find CBS.log file in CBS directory?

This is the first time that happen to me!

lomas · Jun 3, 2017

View attachment CBS + CheckSUR + ChechSUR.presist + DeepClean .rar

CBS.log is empty nothing logged in it I created it before I use SFC /scannow and nothing was logged after the scan.

Other attachment are found in CBS Directory for more information.

lomas · Jun 4, 2017

I reply here only because I want to help people in future, if they search for the same problem.
This forum was of no use to me.

I traced the problem without CBS.log available.

I used windows events log + registry (regedit) or any third party (registrar registry manager).

I found that RPCRT4.dll is corrupt causing Microsoft Windows Servicing not logging error in CBS.log

Now I'm stuck with DISM giving me this error I uninstall "windows 7 assessment and development kit" it fixes DISM for me cause it's related because of some drivers that DISM need to load to be able to work.

Check DISM.log for information.

I will share next steps when I fix RPCRT4 problem and check if CBS.log is fixed.

Tasks:

1 - Fix DISM (done)
2 - Fix RPCRT4 (not done yet)
3 - Fix CBS.log (not done yet)

P.S: I will update this thread with every step I made to fix everything on Win SP1 X64.

lomas · Jun 4, 2017

I started Task Scheduler an error message pops up.

SvcRestartTask is corrupt

\Microsoft\Windows\SoftwareProtectionPlatform

I find this tutorial to fix it :

https://support.microsoft.com/en-us...eduler-could-allow-for-elevation-of-privilege

lomas · Jun 4, 2017

Additional help:

Here how to repair and restore corrupted "task scheduler" tasks by default for windows 7

Windows 7 Default Scheduled Tasks–Complete Overview | chentiangemalc

lomas · Jun 4, 2017

Tasks:

1 - Fix DISM (done)
2 - Fix Corrupted tasks (done)
3 - Fix RPCRT4 (not done yet)
4 - Fix CBS.log (not done yet)

lomas · Jun 4, 2017

I fixed CBS log missing issue by changing this registry key:

You should take ownership of "Component Based Servicing" registry directory because registry key will not be changed if you don't have permission to do so.
1 - Go to "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing"
2 - Change "EnableLog" Decimal value from "0" to "1"
3 - Reboot your computer
4 - Do a "SFC /Scannow" and check if the log is generated.

P.S: RPCRT4 is fixed automatically after I did an SFC /Scannow

Tasks:

1 - Fix DISM (done)
2 - Fix Corrupted tasks (done)
3 - Fix RPCRT4 (done)
4 - Fix CBS.log (done)
5 - Fixing CheckSUR 18 errors found

Reference: Restrict Windows CBS.log verbosity, set log level, stop hectomegabyte info madness - Super User

lomas · Jun 4, 2017

View attachment CBS.log View attachment SFCFix.txt

Now CBS.log and SFCFix log uploaded.

If anyone interesting to help please help me if you like to do so.

And thanks in advance

lomas · Jun 4, 2017

Only six errors fixed: I deleted files in winsxs directory and traced their keys by using "registrar registry manager" search feature.

This is what's left.

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.23471
2017-06-04 23:56

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Missing Winning Component Key 0x00000000 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8
(f) CSI Unexpected Failure 0x00000005 14.0.24210.0 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8 Error deleting winners map value.

Summary:
Seconds executed: 638
Found 12 errors
CSI Unexpected Failure Total count: 6
CSI Missing Winning Component Key Total count: 6

lomas · Jun 4, 2017

Tasks:

1 - Fix DISM (done)
2 - Fix Corrupted tasks (done)
3 - Fix RPCRT4 (done)
4 - Fix CBS.log (done)
5 - Fixing CheckSUR 18 errors found (done)

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.23471
2017-06-05 01:48

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 1087
No errors detected

I fixed this by uninstalling AVAST then deleting those files, and reinstalling a clean install of AVAST.

I guess I'm done here, I hope this will help people whom will face the same problems in future.

lomas · Jun 5, 2017

Errors appear again I uninstall AVAST install another antivirus, CheckSUR log now is clean.

Mods can name this solved.

Additional information: Uninstalling ‘uninstallable’ Windows Updates | Born's Tech and Windows World

This tutorial will help you remove restricted updates, I did it manually cause PowerRun didn't work for me.

lomas · Jun 16, 2017

1 - RPCRT4.DLL fixed (done)
2 - Fix dot NET 4.7 cause of most issues (Done)

Same issue appeared again "RPCRT4" pushing errors to even log, and causing some reboot issues.

I repair it by uninstalling all dot net framework installed on my PC, using this tool: https://blogs.msdn.microsoft.com/astebner/2008/08/28/net-framework-cleanup-tool-users-guide/

Then installed Dot net framework 4.0 instead of 4.7, old issues back in windows XP using dot net appear again on windows 7 that's what caused my computer to behave strangely.

Microsoft .NET Framework 4 (standalone install) : Download Microsoft .NET Framework 4 (Standalone Installer) from Official Microsoft Download Center

[SOLVED] [Win7SP1] CheckSUR: Checking Component Store (Found 18 errors)

lomas

Member

lomas

Member

ChuckR

Well-known member

lomas

Member

lomas

Member

lomas

Member

lomas

Member

lomas

Member

lomas

Member

lomas

Member

lomas

Member

lomas

Member

lomas

Member

lomas

Member

lomas

Member