14 Errors from Avast in Win 7 System Update Readiness Tool log

Avast Free Antivirus / Premium Security
1

I have Win 7 Pro 64-bit on a PC with 16GB RAM, and Avast AV Free. (My Avast Free is version 18.6.2349 (build 18.6.3983.371).)

Just the last 24 hours, the machine has had INTERMITTENT internet connectivity issues on reboots, even after sfc /scannow.

So I’ve also run System Update Readiness Tool a few times (which is for Win 7 what the DISM tools is for Win 10).
ALL THE REMAINING ERRORS ARE FROM AVAST - not other source !!! My Avast is 18.6.2349 (build 18.6.3983.371).

Here is the latest log (just now), from C:\Windows\Logs\CBS\CheckSUR.log:

================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2018-09-30 14:04

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.crt_fcc99ee6193ebbca_14.0.25325.0_none_a01bd4182e9569cc
(f) CSI Unexpected Failure 0x00000005 14.0.25325.0 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_a01bd4182e9569cc Error deleting winners map value.
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_0b20a8ff883c3a4a x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c
(f) CSI Missing Winning Component Key 0x00000000 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_586e9d411a1940c6
(f) CSI Unexpected Failure 0x00000005 14.0.25325.0 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_586e9d411a1940c6 Error deleting winners map value.
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_c373722873c01144 amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396
(f) CSI Missing Winning Component Key 0x00000000 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_4b5d1834d3072800
(f) CSI Unexpected Failure 0x00000005 14.0.25325.0 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_4b5d1834d3072800 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_97ea50fde4578039
(f) CSI Unexpected Failure 0x00000005 14.0.25325.0 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_97ea50fde4578039 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_a4fbd60a2b6998ff
(f) CSI Unexpected Failure 0x00000005 14.0.25325.0 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_a4fbd60a2b6998ff Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_930a4f0be7835106
(f) CSI Unexpected Failure 0x00000005 14.0.25325.0 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_930a4f0be7835106 Error deleting winners map value.

Summary:
Seconds executed: 656
Found 14 errors
CSI Unexpected Failure Total count: 6
CSI C Mark Deployment Missing Total count: 2
CSI Missing Winning Component Key Total count: 6

[b] [/b][b] [/b][b]--- Hey, Avast - come fix. ♪ ♫ [/b]
2

♪
(Bump.)

3

Hi glnz, please take a look at this previous post: https://forum.avast.com/index.php?topic=211301.0 The errors you’re seeing are expected if you’ve previously had Avast installed. Repairing Avast should resolve. To do this, please follow the steps in the guide located here: https://support.avast.com/en-us/article/Repair-Antivirus

4

BWhit - I’ve run Avast Repair and the System Update Readiness (SUR) Tool a few times, and SUR continues to show eight ( 8 ) persistent errors, all caused by Avast. Here’s the latest checksur.log:

================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2018-10-15 15:24

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_a01bd4182e9569cc x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_a01bd4182e9569cc
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_0b20a8ff883c3a4a x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_586e9d411a1940c6 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_586e9d411a1940c6
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_c373722873c01144 amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0…t.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_4b5d1834d3072800 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_4b5d1834d3072800
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0…t.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_97ea50fde4578039 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_97ea50fde4578039
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_a4fbd60a2b6998ff x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_a4fbd60a2b6998ff
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0…t.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_930a4f0be7835106 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_930a4f0be7835106

Summary:
Seconds executed: 156
Found 8 errors
CSI C Mark Deployment Not Marked Total count: 6
CSI C Mark Deployment Missing Total count: 2

Why does Avast cause errors in the system?
Thanks.

5

By the way - to clarify - when I “Repair” Avast, reboot, and then run System Update Readiness tool (SUR), the first SUR report shows about 100 errors, ALL FROM AVAST. But the SUR tool fixes most of them, but not the final eight above.

When I reboot and run the SUR tool again, I get the report immediately above only about the last eight items that cannot be fixed, ALL OF WHICH COME FROM AVAST.

Again, Avast is not playing nice with our PCs. This should NOT be happening.

6

Hi glnz,

I’m sorry that the repair option didn’t work successfully for you. The next step would be to verify if the intermittent connection issues are being caused by the errors that SUR highlights. To do this, please fully uninstall Avast Free according to the instructions in this guide: https://support.avast.com/en-ww/article/94/, and then verify if the connectivity issues are still present. If so, then the issues are not being caused by the Avast application. Either way, please download the latest installation files from here and reinstall: https://support.avast.com/en-ww/article/Install-Free-Antivirus. Please let us know if the connectivity issues re-occur only once you have reinstalled.

7

Update - I have not noticed the intermittent internet connections in a while, so they may have been caused by something else.

However …

I have done a complete, strong UNinstallation and REinstallation of Avast on my Win 7 Pro 64-bit machine, and these “checksur” errors continue - with the very latest Avast 19-1-2360 –

Here are the latest results - all errors are from Avast:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2019-01-13 09:53

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0…t.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_945e8bd9e5efd44e x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_none_945e8bd9e5efd44e
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_0b20a8ff883c3a4a x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0…t.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_4cb15502d173ab48 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_none_4cb15502d173ab48
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0…t.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_993e8dcbe2c40381 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_none_993e8dcbe2c40381
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_c373722873c01144 amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_59c2da0f1885c40e amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_none_59c2da0f1885c40e
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0…t.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_519156f4ce47da7b amd64_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_none_519156f4ce47da7b
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_5ea2dc011559f341 amd64_avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_none_5ea2dc011559f341
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_a65012d829d61c47 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.26706.0_none_a65012d829d61c47
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_a17010e62d01ed14 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.26706.0_none_a17010e62d01ed14

Summary:
Seconds executed: 179
Found 10 errors
CSI C Mark Deployment Not Marked Total count: 8
CSI C Mark Deployment Missing Total count: 2

8

This continues to happen.
In the latest System Update Readiness Tool scan on my Win7 Pro 64-bit machine, I get 18 “hits”, and they are ALL Avast.
Here the are:

================================= Checking System Update Readiness. Binary Version 6.1.7601.24435 2019-05-16 18:48

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_0b20a8ff883c3a4a x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c
(f) CSI C Mark Deployment Missing 0x00000000 c!avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_c373722873c01144 amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396
(f) CSI Missing Winning Component Key 0x00000000 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_5ca6eb17137337f1
(f) CSI Unexpected Failure 0x00000005 14.0.27012.0 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_5ca6eb17137337f1 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_9c229ed3ddb17764
(f) CSI Unexpected Failure 0x00000005 14.0.27012.0 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_9c229ed3ddb17764 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_4f95660acc611f2b
(f) CSI Unexpected Failure 0x00000005 14.0.27012.0 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_4f95660acc611f2b Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_a93423e024c3902a
(f) CSI Unexpected Failure 0x00000005 14.0.27012.0 x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_a93423e024c3902a Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 amd64_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_547567fcc9354e5e
(f) CSI Unexpected Failure 0x00000005 14.0.27012.0 amd64_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_547567fcc9354e5e Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_a45421ee27ef60f7
(f) CSI Unexpected Failure 0x00000005 14.0.27012.0 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_a45421ee27ef60f7 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_97429ce1e0dd4831
(f) CSI Unexpected Failure 0x00000005 14.0.27012.0 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_97429ce1e0dd4831 Error deleting winners map value.
(f) CSI Missing Winning Component Key 0x00000000 amd64_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_6186ed0910476724
(f) CSI Unexpected Failure 0x00000005 14.0.27012.0 amd64_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_6186ed0910476724 Error deleting winners map value.

Summary:
Seconds executed: 466
Found 18 errors
CSI Unexpected Failure Total count: 8
CSI C Mark Deployment Missing Total count: 2
CSI Missing Winning Component Key Total count: 8

Absurd that Avast will not fix this.

9

I recently noticed the avast free installation indeed causing a ‘dirty’ CheckSUR log on Win 7. Really strange.
Thought at first, these corruptions was made by a recent disk file data corruption, but it really seems a long known thing related to avast. I can even easily replicate this in VM.
I had to seek professional help at Sysnatives, to get the last unfixable component store entries repaired. And it doesn’t really end here. Every time I reinstall avast via the uninstall utility, make a program update, or attempt repair avast, via the control panel, I have to do the other repairs all over again, to maintain a clean CheckSUR log.

I will state here though, I yet to experience anything bad with avast’s functionality, nor with Windows Update. The remaining non-repairable component store entries are likely harmless to the system and may be possible to ignore.
I did however one time experienced some registry entries in CCleaner wouldn’t go away, before the attached CheckSUR entries was repaired first. Don’t think this is supposed to be normal.

ActiveX/COM problem VirtualBoxAsw.SessionAsw - {A4AB08B7-35EE-4f75-BE0A-D8F9630D755E} HKCR\VirtualBoxAsw.SessionAsw ActiveX/COM problem VirtualBoxAsw.SessionAsw.1 - {A4AB08B7-35EE-4f75-BE0A-D8F9630D755E} HKCR\VirtualBoxAsw.SessionAsw.1 ActiveX/COM problem VirtualBoxAsw.VirtualBoxAsw - {F319F1B8-7587-4146-AF9C-0D6D77819BF1} HKCR\VirtualBoxAsw.VirtualBoxAsw ActiveX/COM problem VirtualBoxAsw.VirtualBoxAsw.1 - {F319F1B8-7587-4146-AF9C-0D6D77819BF1} HKCR\VirtualBoxAsw.VirtualBoxAsw.1 ActiveX/COM problem VirtualBoxAsw.VirtualBoxClientAsw - {262E45B9-36DA-43ac-ABF4-C546A7EA3BFC} HKCR\VirtualBoxAsw.VirtualBoxClientAsw ActiveX/COM problem VirtualBoxAsw.VirtualBoxClientAsw.1 - {262E45B9-36DA-43ac-ABF4-C546A7EA3BFC} HKCR\VirtualBoxAsw.VirtualBoxClientAsw.1

Entries from backup reg file:

[HKEY_CLASSES_ROOT\VirtualBoxAsw.SessionAsw]
@=“SessionAsw Class”

[HKEY_CLASSES_ROOT\VirtualBoxAsw.SessionAsw\CLSID]
@=“{A4AB08B7-35EE-4f75-BE0A-D8F9630D755E}”

[HKEY_CLASSES_ROOT\VirtualBoxAsw.SessionAsw\CurVer]
@=“VirtualBoxAsw.SessionAsw.1”

[HKEY_CLASSES_ROOT\VirtualBoxAsw.SessionAsw.1]
@=“SessionAsw Class”

[HKEY_CLASSES_ROOT\VirtualBoxAsw.SessionAsw.1\CLSID]
@=“{A4AB08B7-35EE-4f75-BE0A-D8F9630D755E}”

[HKEY_CLASSES_ROOT\VirtualBoxAsw.VirtualBoxAsw]
@=“VirtualBoxAsw Class”

[HKEY_CLASSES_ROOT\VirtualBoxAsw.VirtualBoxAsw\CLSID]
@=“{F319F1B8-7587-4146-AF9C-0D6D77819BF1}”

[HKEY_CLASSES_ROOT\VirtualBoxAsw.VirtualBoxAsw\CurVer]
@=“VirtualBoxAsw.VirtualBoxAsw.1”

[HKEY_CLASSES_ROOT\VirtualBoxAsw.VirtualBoxAsw.1]
@=“VirtualBoxAsw Class”

Technical information for reference:

Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601

Avast Free:
19.5.2378 (build 19.5.4444.495)
Definition version: 190523-4
UI version 1.0.370