Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Won't restore system after driver updates broke cherrytree & ccleaner

26 Sep 2017   #21
treehouse

Win 7 Home Premium x64 SP1
 
 

Part 2...
Code:
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-private-l1_0d9f3732fdca6b03      amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-private-l1_0d9f3732fdca6b03:   api-ms-win-crt-private-l1-1-0.dll
(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 F Mark Bad Type    0x000000DE      f!api-ms-win-crt-heap-l1-1-_489a8453031dbf7e      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-heap-l1-1-_489a8453031dbf7e:   api-ms-win-crt-heap-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE    f!msvcp140.dll      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!msvcp140.dll:   msvcp140.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-runtime-l1_295c38be07a80c5c      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-runtime-l1_295c38be07a80c5c:   api-ms-win-crt-runtime-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-util-l1-1_2fbbddc80bd7b142      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-util-l1-1_2fbbddc80bd7b142:   api-ms-win-core-util-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-time-l1-1-_0a06182b126e5ced      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-time-l1-1-_0a06182b126e5ced:   api-ms-win-crt-time-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-filesystem_4c8d668a165bcfc5      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-filesystem_4c8d668a165bcfc5:   api-ms-win-crt-filesystem-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-rtlsuppor_957ea04417ffd3fd      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-rtlsuppor_957ea04417ffd3fd:   api-ms-win-core-rtlsupport-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-processth_be90e7a218743905      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-processth_be90e7a218743905:   api-ms-win-core-processthreads-l1-1-1.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-processth_bcaa70081b4dec6c      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-processth_bcaa70081b4dec6c:   api-ms-win-core-processthreads-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-synch-l1-_58d5510126a3d0a3      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-synch-l1-_58d5510126a3d0a3:   api-ms-win-core-synch-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-synch-l1-_58b1482526f4e492      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-synch-l1-_58b1482526f4e492:   api-ms-win-core-synch-l1-2-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-stdio-l1-1_91720ce12a362805      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-stdio-l1-1_91720ce12a362805:   api-ms-win-crt-stdio-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-string-l1-_bf364c6133dc5f29      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-string-l1-_bf364c6133dc5f29:   api-ms-win-crt-string-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE    f!vcruntime140.dll      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!vcruntime140.dll:   vcruntime140.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-timezone-_36a3847554301d1b      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-timezone-_36a3847554301d1b:   api-ms-win-core-timezone-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-errorhand_74d332585a874f13      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-errorhand_74d332585a874f13:   api-ms-win-core-errorhandling-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-utility-l1_ee0406a3668937c8      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-utility-l1_ee0406a3668937c8:   api-ms-win-crt-utility-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-debug-l1-_fcf709b567764adb      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-debug-l1-_fcf709b567764adb:   api-ms-win-core-debug-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-convert-l1_ccd6145476992bb5      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-convert-l1_ccd6145476992bb5:   api-ms-win-crt-convert-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-interlock_5b13ca157c86206a      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-interlock_5b13ca157c86206a:   api-ms-win-core-interlocked-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-locale-l1-_78d5406182e89c10      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-locale-l1-_78d5406182e89c10:   api-ms-win-crt-locale-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-memory-l1_b50269be86981cdf      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-memory-l1_b50269be86981cdf:   api-ms-win-core-memory-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-file-l2-1_55576bbe8d24bad1      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-file-l2-1_55576bbe8d24bad1:   api-ms-win-core-file-l2-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-file-l1-2_5641c4568eb992f3      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-file-l1-2_5641c4568eb992f3:   api-ms-win-core-file-l1-2-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-file-l1-1_545b4cbc9193465a      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-file-l1-1_545b4cbc9193465a:   api-ms-win-core-file-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-environmen_51aa2ca79964c47b      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-environmen_51aa2ca79964c47b:   api-ms-win-crt-environment-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE    f!ucrtbase.dll      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!ucrtbase.dll:   ucrtbase.dll
(f)    CSI F Mark Bad Type    0x000000DE    f!concrt140.dll      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!concrt140.dll:   concrt140.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-datetime-_18c69a37b29c8a6b      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-datetime-_18c69a37b29c8a6b:   api-ms-win-core-datetime-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-string-l1_01a67a1eb4a37927      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-string-l1_01a67a1eb4a37927:   api-ms-win-core-string-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-heap-l1-1_287b5c03b6af9938      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-heap-l1-1_287b5c03b6af9938:   api-ms-win-core-heap-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-processen_53b32beeba773f3c      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-processen_53b32beeba773f3c:   api-ms-win-core-processenvironment-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-profile-l_589cdc13bb19940f      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-profile-l_589cdc13bb19940f:   api-ms-win-core-profile-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-math-l1-1-_a0c2a56cbb4edb5a      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-math-l1-1-_a0c2a56cbb4edb5a:   api-ms-win-crt-math-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-console-l_47586507cb37b721      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-console-l_47586507cb37b721:   api-ms-win-core-console-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-process-l1_97bd49b0cc348583      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-process-l1_97bd49b0cc348583:   api-ms-win-crt-process-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-multibyte-_73a631bfd5b88d97      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-multibyte-_73a631bfd5b88d97:   api-ms-win-crt-multibyte-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-localizat_2f8df132e6bb3940      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-localizat_2f8df132e6bb3940:   api-ms-win-core-localization-l1-2-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-conio-l1-1_802b0af5ede3c7ee      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-conio-l1-1_802b0af5ede3c7ee:   api-ms-win-crt-conio-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-namedpipe_45d0ade8ee64997f      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-namedpipe_45d0ade8ee64997f:   api-ms-win-core-namedpipe-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-sysinfo-l_b7a5bdc6f2238ba5      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-sysinfo-l_b7a5bdc6f2238ba5:   api-ms-win-core-sysinfo-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-handle-l1_eb218752f3acd08a      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-handle-l1_eb218752f3acd08a:   api-ms-win-core-handle-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-core-librarylo_8dba425bf95afa18      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-core-librarylo_8dba425bf95afa18:   api-ms-win-core-libraryloader-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE      f!api-ms-win-crt-private-l1_0d9f3732fdca6b03      x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8      
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote   x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8\f!api-ms-win-crt-private-l1_0d9f3732fdca6b03:   api-ms-win-crt-private-l1-1-0.dll
(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: 457
 Found 101 errors
 Fixed 89 errors
  CSI Unexpected Failure Total count: 6
  CSI F Mark Bad Type Total count: 89
  Fixed: CSI F Mark Bad Type.  Total count: 89
  CSI Missing Winning Component Key Total count: 6



My System SpecsSystem Spec
.
26 Sep 2017   #22
torchwood

W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
 
 

Hi John,

I HATE AVAST.
causes more updating problems than any other AV.
It does have one redeeming feature the preboot scan

All of those remaining errors relate to it.
You could uninstall it, worth a shot. dont hold out a lot of hope
PERFORM IN SAFE MODE

Avast Uninstall Utility | Download aswClear for Avast Removal

Back in normal mode rerun SURT.


Updating your computers drivers using Toshiba service Centre
Toshiba How-To: Download updated drivers and software for your Toshiba laptop - YouTube

Macrium or A N Other V System Restore
in my opinion if you store any personal data on a machine and it fails for whatever reason, be it corruption/dying hardware etc then a 3rd party utility is essential, Macriums is just my prefferred.
Another reason its far quicker to get back to where you were, just think how many things youve changed to get the system how you like it and got used to, and all those programs you need to reinstall and reregister, if you need to perform a clean install.
There are also more features within it, the homepage link explains them in more detail
It boils down to which is more reliable >> gotta go 3rd party, as you've found out

Which brings us to CherryTree, your first quote in the last post -where i said create an image now and start playing with Cherrytree
if we take it that CT is breaking the inbuilt System Restore function then were going round in a corrupt OS circle, even in a clean install scenario
Im not advocating making an image of a broken system but using it as a stepping stone

What did make my ears prick up was
I think because the drive I use didn't have enough space
This causes multiple problems you should never let your disk space usage go above 90%
Many processes require and use temp files to work.

Time is relative and as your not a relative it DOESNT matter
so keep posting


Roy

T
My System SpecsSystem Spec
26 Sep 2017   #23
treehouse

Win 7 Home Premium x64 SP1
 
 

Thanks Roy, there's so much to help me here! I've been getting more than a bit fed up with Avast lately anyway. It'll take me a while to catch up with this, as I've got some other work I have to deal with, but I'll just say the disc space I was talking about is on an external drive, not the machine. I use that as the destination for backups. My GoFlex 240 gig has about 80 gig free on it, and I think the Windows Backup routine reported that it wasn't enough space. My machine's HDD (actually SSD) is only 40GB used out of a (nominal) 120GB. I didn't create different partitions on it as the SSD is pretty small and I thought it would be better to shove data mostly on another drive. Maybe you thought I was talking about writing an image to the machine's drive? I could have a clearout of the external or use another one. Memory's getting cheap. Time's relative, lol.
My System SpecsSystem Spec
.

02 Oct 2017   #24
treehouse

Win 7 Home Premium x64 SP1
 
 

Woohoo! Things are looking up today...
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2017-10-02 14:01

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        
(fix)    CSI Missing Winning Component Key    CSI Registry Item Repaired    Deleted winners map value 14.0.24210.0
(f)    CSI Missing Winning Component Key    0x00000000    amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc        
(fix)    CSI Missing Winning Component Key    CSI Registry Item Repaired    Deleted winners map value 14.0.24210.0
(f)    CSI Missing Winning Component Key    0x00000000    x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702        
(fix)    CSI Missing Winning Component Key    CSI Registry Item Repaired    Deleted winners map value 14.0.24210.0
(f)    CSI Missing Winning Component Key    0x00000000    amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2        
(fix)    CSI Missing Winning Component Key    CSI Registry Item Repaired    Deleted winners map value 14.0.24210.0
(f)    CSI Missing Winning Component Key    0x00000000    x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635        
(fix)    CSI Missing Winning Component Key    CSI Registry Item Repaired    Deleted winners map value 14.0.24210.0
(f)    CSI Missing Winning Component Key    0x00000000    x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8        
(fix)    CSI Missing Winning Component Key    CSI Registry Item Repaired    Deleted winners map value 14.0.24210.0

Summary:
Seconds executed: 424
 Found 6 errors
 Fixed 6 errors
  CSI Missing Winning Component Key Total count: 6
  Fixed: CSI Missing Winning Component Key.  Total count: 6
How'd'you like them apples?

Can't thank you enough, Roy (apparently I have to spread the love around first!).

What I did...
I decided to uninstall Avast from Safe Mode, as you recommended, after choosing Avira as its replacement (the free version and just the a/v for now, but tempted partly by the free VPN and other addons). That seemed to go smoothly.

I then opened CherryTree (which previously I had found would show its window if maximized, but not normal, so I'd been using it maximized). At first it didn't open, just like the problem was back - or had it gone normal? Nope, it was maximized but not showing. However, from the right-click on the preview on its taskbar item, I restored it, and it showed normally! Had it reversed the issue? No, once I maximized again, it worked in both, minimized and closed to the tray properly and seems fixed!

Second issue was that Ccleaner had gone weird, not opening and having a default exe icon instead of its own. That was still the same. I thought I'd just try re-installing the latest version (updating from 5.32 to 5.35). Yikes, Avira then reported that this installation file was infected with a trojan. https://www.avira.com/en/support-thr....533.1&track=1
Looking into this, it should be fixed already from 5.34 and this looks like a false positive. It shouldn't even have affected my computer, as it was on the 32 bit and/or cloud-based versions. (I briefly checked out instructions for removing the possible infection, but don't want to screw with the system too much yet, and it involvs the usual multiple installs of malware removal tools.) I also read of infections earlier in the uninstall file, but that ran ok and I've just uninstalled it for now. I didn't know Ccleaner had been taken over by Avast! Maybe that's not a good sign - I used to trust Ccleaner implicitly.

I then ran KB987421, and it looks to my untrained eye like it's finished uninstalling Avast.

Once again, thanks torchwood! I'll mark this thread as fixed unless you have any further concerns! Please let me know if there's anything I should do in addition to checking the system restore works and starting making regular images of the drive as well as file backups. One question left hanging for me is why Backups was reporting a lack of space to save an image - does it save the whole drive including unused space? That would explain it.

Up the Saints!
My System SpecsSystem Spec
Reply

 Won't restore system after driver updates broke cherrytree & ccleaner




Thread Tools




Similar help and support threads
Thread Forum
System restore and Windows updates
Hi everyone.... I did a System Restore shortly after ( about an hour later) A Windows Update ( actually 3 Windows update items). I was curious...will a Sytem Restore remove a very recent Windows Update(s)? I checked in the ADD/Remove .."view installed updates" and those Windows Updates...
Windows Updates & Activation
October 9 updates broke desktop gadgets
Only the CPU, clock and weather that are built into Windows work now. I have Network, Drives and GPU meter from the same author and i first noticed the GPU gadget was just showing a pink background with no graphics and clicking on the config brought up a blank screen. I did try updating to the...
Customization
CI.dll problem running updates after system restore
After a complete system restore everything works fine until Windows update start to configure over 100 updates. The computer restarts and i get the error message: "Windows failed to start. A recent hardware or Software change might be the cause... ... File: CI.dll Status: 0x0000428 Info: Windows...
Windows Updates & Activation
Lost Updates with System Restore?
Hi- I had a problem that developed recently and was characterized by browsers (IE, Firefox and Opera) opening very slowly. I tried to fix it by scanning for and removing malware, which did nothing. I finally resolved the problem by using System Restore, back to Jan 11, 2011. My question is: in...
Windows Updates & Activation
System Restore Points / Windows Updates
Hello Forum, I need to restore my system to a prievious restore point. There have been several 'Windows Critical Updates' to my system after the restore point I'm going back to. I'm assuming that these updates will be removed due to the restore process. My question(s) is, does Windows...
Backup and Restore


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 20:26.
Twitter Facebook Google+