• Still running Windows 7 or earlier? Support for Windows 7 ended on January 14th 2020. Please review the thread here for more details.

Defender error code 0x8007007e.

Hi! I'm bowing out. It seems to me you have more than one anti-virus program (Avast) running on your PC. That is a no no!
I already have Avast in use and I have IObit malware down loaded but not in use along with various comp health and cleaners that I use quite often and have been for sometime without problems. It was only when I got the defender error that I started to panic.
Click to expand...
Tekno will fix you up, I'm sure!! I'm not a fan of IObit for any thing.
Good luck!
Gary!!
 
Oneman said:
Will a admin/command prompt sfc/scannow. Help?
Click to expand...
Give it a try. Follow the below instructions:

SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.


Stephen
 
Thanks Tekno.
I am just getting access is denied even as Administrator:Command Prompt.
The scan says it has found corrupt files but could not fix some of them.
I managed to get this report a few days back (as posted earlier) so i will have to look into how i did it.
 
OK got it.
The report is rather long but I hope it helps.:noidea::smile9:

I used. findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

2015-04-26 20:26:35, Info CSI 00000006 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:35, Info CSI 00000007 [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:39, Info CSI 00000009 [SR] Verify complete
2015-04-26 20:26:40, Info CSI 0000000a [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:40, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:44, Info CSI 0000000d [SR] Verify complete
2015-04-26 20:26:44, Info CSI 0000000e [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:44, Info CSI 0000000f [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:45, Info CSI 00000011 [SR] Verify complete
2015-04-26 20:26:46, Info CSI 00000012 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:46, Info CSI 00000013 [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:47, Info CSI 00000015 [SR] Verify complete
2015-04-26 20:26:47, Info CSI 00000016 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:47, Info CSI 00000017 [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:48, Info CSI 00000019 [SR] Verify complete
2015-04-26 20:26:49, Info CSI 0000001a [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:49, Info CSI 0000001b [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:50, Info CSI 0000001d [SR] Verify complete
2015-04-26 20:26:50, Info CSI 0000001e [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:50, Info CSI 0000001f [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:51, Info CSI 00000021 [SR] Verify complete
2015-04-26 20:26:51, Info CSI 00000022 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:51, Info CSI 00000023 [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:52, Info CSI 00000025 [SR] Verify complete
2015-04-26 20:26:53, Info CSI 00000026 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:53, Info CSI 00000027 [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:54, Info CSI 00000029 [SR] Verify complete
2015-04-26 20:26:54, Info CSI 0000002a [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:54, Info CSI 0000002b [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:55, Info CSI 0000002d [SR] Verify complete
2015-04-26 20:26:56, Info CSI 0000002e [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:56, Info CSI 0000002f [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:57, Info CSI 00000031 [SR] Verify complete
2015-04-26 20:26:57, Info CSI 00000032 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:57, Info CSI 00000033 [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:58, Info CSI 00000035 [SR] Verify complete
2015-04-26 20:26:58, Info CSI 00000036 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:58, Info CSI 00000037 [SR] Beginning Verify and Repair transaction
2015-04-26 20:26:59, Info CSI 00000039 [SR] Verify complete
2015-04-26 20:26:59, Info CSI 0000003a [SR] Verifying 100 (0x00000064) components
2015-04-26 20:26:59, Info CSI 0000003b [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:00, Info CSI 0000003d [SR] Verify complete
2015-04-26 20:27:01, Info CSI 0000003e [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:01, Info CSI 0000003f [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:02, Info CSI 00000041 [SR] Verify complete
2015-04-26 20:27:02, Info CSI 00000042 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:02, Info CSI 00000043 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:04, Info CSI 00000045 [SR] Verify complete
2015-04-26 20:27:04, Info CSI 00000046 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:04, Info CSI 00000047 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:05, Info CSI 00000049 [SR] Verify complete
2015-04-26 20:27:06, Info CSI 0000004a [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:06, Info CSI 0000004b [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:07, Info CSI 0000004d [SR] Verify complete
2015-04-26 20:27:07, Info CSI 0000004e [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:07, Info CSI 0000004f [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:08, Info CSI 00000051 [SR] Verify complete
2015-04-26 20:27:09, Info CSI 00000052 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:09, Info CSI 00000053 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:10, Info CSI 00000055 [SR] Verify complete
2015-04-26 20:27:10, Info CSI 00000056 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:10, Info CSI 00000057 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:11, Info CSI 00000059 [SR] Verify complete
2015-04-26 20:27:11, Info CSI 0000005a [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:11, Info CSI 0000005b [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:12, Info CSI 0000005d [SR] Verify complete
2015-04-26 20:27:13, Info CSI 0000005e [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:13, Info CSI 0000005f [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:14, Info CSI 00000061 [SR] Verify complete
2015-04-26 20:27:14, Info CSI 00000062 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:14, Info CSI 00000063 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:15, Info CSI 00000065 [SR] Verify complete
2015-04-26 20:27:16, Info CSI 00000066 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:16, Info CSI 00000067 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:17, Info CSI 00000069 [SR] Verify complete
2015-04-26 20:27:17, Info CSI 0000006a [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:17, Info CSI 0000006b [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:19, Info CSI 0000006d [SR] Verify complete
2015-04-26 20:27:19, Info CSI 0000006e [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:19, Info CSI 0000006f [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:20, Info CSI 00000071 [SR] Verify complete
2015-04-26 20:27:20, Info CSI 00000072 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:20, Info CSI 00000073 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:22, Info CSI 00000075 [SR] Verify complete
2015-04-26 20:27:22, Info CSI 00000076 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:22, Info CSI 00000077 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:23, Info CSI 00000079 [SR] Verify complete
2015-04-26 20:27:23, Info CSI 0000007a [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:23, Info CSI 0000007b [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:25, Info CSI 0000007d [SR] Verify complete
2015-04-26 20:27:26, Info CSI 0000007e [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:26, Info CSI 0000007f [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:27, Info CSI 00000081 [SR] Verify complete
2015-04-26 20:27:27, Info CSI 00000082 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:27, Info CSI 00000083 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:28, Info CSI 00000085 [SR] Verify complete
2015-04-26 20:27:28, Info CSI 00000086 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:28, Info CSI 00000087 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:30, Info CSI 00000089 [SR] Verify complete
2015-04-26 20:27:31, Info CSI 0000008a [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:31, Info CSI 0000008b [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:32, Info CSI 0000008d [SR] Verify complete
2015-04-26 20:27:32, Info CSI 0000008e [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:32, Info CSI 0000008f [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:33, Info CSI 00000091 [SR] Verify complete
2015-04-26 20:27:33, Info CSI 00000092 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:33, Info CSI 00000093 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:35, Info CSI 00000095 [SR] Verify complete
2015-04-26 20:27:35, Info CSI 00000096 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:35, Info CSI 00000097 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:38, Info CSI 00000099 [SR] Verify complete
2015-04-26 20:27:38, Info CSI 0000009a [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:38, Info CSI 0000009b [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:42, Info CSI 0000009d [SR] Verify complete
2015-04-26 20:27:43, Info CSI 0000009e [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:43, Info CSI 0000009f [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:47, Info CSI 000000a1 [SR] Verify complete
2015-04-26 20:27:48, Info CSI 000000a2 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:48, Info CSI 000000a3 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:52, Info CSI 000000a6 [SR] Verify complete
2015-04-26 20:27:52, Info CSI 000000a7 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:52, Info CSI 000000a8 [SR] Beginning Verify and Repair transaction
2015-04-26 20:27:57, Info CSI 000000ab [SR] Verify complete
2015-04-26 20:27:57, Info CSI 000000ac [SR] Verifying 100 (0x00000064) components
2015-04-26 20:27:57, Info CSI 000000ad [SR] Beginning Verify and Repair transaction
2015-04-26 20:28:01, Info CSI 000000af [SR] Verify complete
2015-04-26 20:28:01, Info CSI 000000b0 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:28:01, Info CSI 000000b1 [SR] Beginning Verify and Repair transaction
2015-04-26 20:28:09, Info CSI 000000ba [SR] Verify complete
2015-04-26 20:28:09, Info CSI 000000bb [SR] Verifying 100 (0x00000064) components
2015-04-26 20:28:09, Info CSI 000000bc [SR] Beginning Verify and Repair transaction
2015-04-26 20:28:16, Info CSI 000000bf [SR] Verify complete
2015-04-26 20:28:16, Info CSI 000000c0 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:28:16, Info CSI 000000c1 [SR] Beginning Verify and Repair transaction
2015-04-26 20:28:20, Info CSI 000000c3 [SR] Verify complete
2015-04-26 20:28:21, Info CSI 000000c4 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:28:21, Info CSI 000000c5 [SR] Beginning Verify and Repair transaction
2015-04-26 20:28:25, Info CSI 000000c7 [SR] Verify complete
2015-04-26 20:28:26, Info CSI 000000c8 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:28:26, Info CSI 000000c9 [SR] Beginning Verify and Repair transaction
2015-04-26 20:28:32, Info CSI 000000cb [SR] Verify complete
2015-04-26 20:28:32, Info CSI 000000cc [SR] Verifying 100 (0x00000064) components
2015-04-26 20:28:32, Info CSI 000000cd [SR] Beginning Verify and Repair transaction
2015-04-26 20:28:40, Info CSI 000000cf [SR] Verify complete
2015-04-26 20:28:41, Info CSI 000000d0 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:28:41, Info CSI 000000d1 [SR] Beginning Verify and Repair transaction
2015-04-26 20:28:51, Info CSI 000000d5 [SR] Verify complete
2015-04-26 20:28:52, Info CSI 000000d6 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:28:52, Info CSI 000000d7 [SR] Beginning Verify and Repair transaction
2015-04-26 20:29:05, Info CSI 000000d9 [SR] Verify complete
2015-04-26 20:29:06, Info CSI 000000da [SR] Verifying 100 (0x00000064) components
2015-04-26 20:29:06, Info CSI 000000db [SR] Beginning Verify and Repair transaction
2015-04-26 20:29:18, Info CSI 000000dd [SR] Verify complete
2015-04-26 20:29:18, Info CSI 000000de [SR] Verifying 100 (0x00000064) components
2015-04-26 20:29:18, Info CSI 000000df [SR] Beginning Verify and Repair transaction
2015-04-26 20:29:22, Info CSI 000000e1 [SR] Verify complete
2015-04-26 20:29:22, Info CSI 000000e2 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:29:22, Info CSI 000000e3 [SR] Beginning Verify and Repair transaction
2015-04-26 20:29:23, Info CSI 000000e5 [SR] Verify complete
2015-04-26 20:29:23, Info CSI 000000e6 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:29:23, Info CSI 000000e7 [SR] Beginning Verify and Repair transaction
2015-04-26 20:29:25, Info CSI 000000e9 [SR] Verify complete
2015-04-26 20:29:25, Info CSI 000000ea [SR] Verifying 100 (0x00000064) components
2015-04-26 20:29:25, Info CSI 000000eb [SR] Beginning Verify and Repair transaction
2015-04-26 20:29:39, Info CSI 0000010a [SR] Verify complete
2015-04-26 20:29:40, Info CSI 0000010b [SR] Verifying 100 (0x00000064) components
2015-04-26 20:29:40, Info CSI 0000010c [SR] Beginning Verify and Repair transaction
2015-04-26 20:29:44, Info CSI 0000010e [SR] Verify complete
2015-04-26 20:29:45, Info CSI 0000010f [SR] Verifying 100 (0x00000064) components
2015-04-26 20:29:45, Info CSI 00000110 [SR] Beginning Verify and Repair transaction
2015-04-26 20:29:48, Info CSI 00000112 [SR] Verify complete
2015-04-26 20:29:49, Info CSI 00000113 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:29:49, Info CSI 00000114 [SR] Beginning Verify and Repair transaction
2015-04-26 20:29:51, Info CSI 00000116 [SR] Verify complete
2015-04-26 20:29:52, Info CSI 00000117 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:29:52, Info CSI 00000118 [SR] Beginning Verify and Repair transaction
2015-04-26 20:29:58, Info CSI 0000011a [SR] Verify complete
2015-04-26 20:29:58, Info CSI 0000011b [SR] Verifying 100 (0x00000064) components
2015-04-26 20:29:58, Info CSI 0000011c [SR] Beginning Verify and Repair transaction
2015-04-26 20:30:09, Info CSI 0000011f [SR] Verify complete
2015-04-26 20:30:09, Info CSI 00000120 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:30:09, Info CSI 00000121 [SR] Beginning Verify and Repair transaction
2015-04-26 20:30:12, Info CSI 00000123 [SR] Verify complete
2015-04-26 20:30:13, Info CSI 00000124 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:30:13, Info CSI 00000125 [SR] Beginning Verify and Repair transaction
2015-04-26 20:30:19, Info CSI 00000127 [SR] Verify complete
2015-04-26 20:30:19, Info CSI 00000128 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:30:19, Info CSI 00000129 [SR] Beginning Verify and Repair transaction
2015-04-26 20:30:23, Info CSI 0000012b [SR] Verify complete
2015-04-26 20:30:23, Info CSI 0000012c [SR] Verifying 100 (0x00000064) components
2015-04-26 20:30:23, Info CSI 0000012d [SR] Beginning Verify and Repair transaction
2015-04-26 20:30:28, Info CSI 0000012f [SR] Verify complete
2015-04-26 20:30:28, Info CSI 00000130 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:30:28, Info CSI 00000131 [SR] Beginning Verify and Repair transaction
2015-04-26 20:30:37, Info CSI 00000133 [SR] Verify complete
2015-04-26 20:30:37, Info CSI 00000134 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:30:37, Info CSI 00000135 [SR] Beginning Verify and Repair transaction
2015-04-26 20:30:48, Info CSI 0000015a [SR] Verify complete
2015-04-26 20:30:49, Info CSI 0000015b [SR] Verifying 100 (0x00000064) components
2015-04-26 20:30:49, Info CSI 0000015c [SR] Beginning Verify and Repair transaction
2015-04-26 20:30:59, Info CSI 0000015e [SR] Verify complete
2015-04-26 20:30:59, Info CSI 0000015f [SR] Verifying 100 (0x00000064) components
2015-04-26 20:30:59, Info CSI 00000160 [SR] Beginning Verify and Repair transaction
2015-04-26 20:31:23, Info CSI 00000162 [SR] Verify complete
2015-04-26 20:31:23, Info CSI 00000163 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:31:23, Info CSI 00000164 [SR] Beginning Verify and Repair transaction
2015-04-26 20:31:40, Info CSI 00000166 [SR] Verify complete
2015-04-26 20:31:40, Info CSI 00000167 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:31:40, Info CSI 00000168 [SR] Beginning Verify and Repair transaction
2015-04-26 20:31:50, Info CSI 0000016a [SR] Verify complete
2015-04-26 20:31:51, Info CSI 0000016b [SR] Verifying 100 (0x00000064) components
2015-04-26 20:31:51, Info CSI 0000016c [SR] Beginning Verify and Repair transaction
2015-04-26 20:31:51, Info CSI 0000016e [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-04-26 20:31:56, Info CSI 00000170 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-04-26 20:31:56, Info CSI 00000171 [SR] This component was referenced by [l:160{80}]"Package_30_for_KB936330~31bf3856ad364e35~x86~~6.0.1.18000.936330-187_neutral_GDR"
2015-04-26 20:31:56, Info CSI 00000174 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
2015-04-26 20:31:58, Info CSI 00000176 [SR] Verify complete
2015-04-26 20:31:58, Info CSI 00000177 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:31:58, Info CSI 00000178 [SR] Beginning Verify and Repair transaction
2015-04-26 20:32:02, Info CSI 0000017a [SR] Verify complete
2015-04-26 20:32:02, Info CSI 0000017b [SR] Verifying 100 (0x00000064) components
2015-04-26 20:32:02, Info CSI 0000017c [SR] Beginning Verify and Repair transaction
2015-04-26 20:32:08, Info CSI 0000017f [SR] Verify complete
2015-04-26 20:32:08, Info CSI 00000180 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:32:08, Info CSI 00000181 [SR] Beginning Verify and Repair transaction
2015-04-26 20:32:24, Info CSI 00000183 [SR] Verify complete
2015-04-26 20:32:24, Info CSI 00000184 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:32:24, Info CSI 00000185 [SR] Beginning Verify and Repair transaction
2015-04-26 20:32:33, Info CSI 00000187 [SR] Verify complete
2015-04-26 20:32:33, Info CSI 00000188 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:32:33, Info CSI 00000189 [SR] Beginning Verify and Repair transaction
2015-04-26 20:32:41, Info CSI 0000018b [SR] Verify complete
2015-04-26 20:32:41, Info CSI 0000018c [SR] Verifying 100 (0x00000064) components
2015-04-26 20:32:41, Info CSI 0000018d [SR] Beginning Verify and Repair transaction
2015-04-26 20:32:52, Info CSI 0000018f [SR] Verify complete
2015-04-26 20:32:53, Info CSI 00000190 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:32:53, Info CSI 00000191 [SR] Beginning Verify and Repair transaction
2015-04-26 20:32:59, Info CSI 00000193 [SR] Verify complete
2015-04-26 20:32:59, Info CSI 00000194 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:32:59, Info CSI 00000195 [SR] Beginning Verify and Repair transaction
2015-04-26 20:33:08, Info CSI 00000197 [SR] Verify complete
2015-04-26 20:33:08, Info CSI 00000198 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:33:08, Info CSI 00000199 [SR] Beginning Verify and Repair transaction
2015-04-26 20:33:39, Info CSI 0000019c [SR] Verify complete
2015-04-26 20:33:39, Info CSI 0000019d [SR] Verifying 100 (0x00000064) components
2015-04-26 20:33:39, Info CSI 0000019e [SR] Beginning Verify and Repair transaction
2015-04-26 20:33:44, Info CSI 000001a0 [SR] Verify complete
2015-04-26 20:33:44, Info CSI 000001a1 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:33:44, Info CSI 000001a2 [SR] Beginning Verify and Repair transaction
2015-04-26 20:33:50, Info CSI 000001a4 [SR] Verify complete
2015-04-26 20:33:51, Info CSI 000001a5 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:33:51, Info CSI 000001a6 [SR] Beginning Verify and Repair transaction
2015-04-26 20:33:59, Info CSI 000001a8 [SR] Verify complete
2015-04-26 20:33:59, Info CSI 000001a9 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:33:59, Info CSI 000001aa [SR] Beginning Verify and Repair transaction
2015-04-26 20:34:07, Info CSI 000001af [SR] Verify complete
2015-04-26 20:34:08, Info CSI 000001b0 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:34:08, Info CSI 000001b1 [SR] Beginning Verify and Repair transaction
2015-04-26 20:34:16, Info CSI 000001b3 [SR] Verify complete
2015-04-26 20:34:17, Info CSI 000001b4 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:34:17, Info CSI 000001b5 [SR] Beginning Verify and Repair transaction
2015-04-26 20:34:25, Info CSI 000001b7 [SR] Verify complete
2015-04-26 20:34:25, Info CSI 000001b8 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:34:25, Info CSI 000001b9 [SR] Beginning Verify and Repair transaction
2015-04-26 20:34:27, Info CSI 000001bb [SR] Verify complete
2015-04-26 20:34:27, Info CSI 000001bc [SR] Verifying 100 (0x00000064) components
2015-04-26 20:34:27, Info CSI 000001bd [SR] Beginning Verify and Repair transaction
2015-04-26 20:34:32, Info CSI 000001bf [SR] Verify complete
2015-04-26 20:34:33, Info CSI 000001c0 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:34:33, Info CSI 000001c1 [SR] Beginning Verify and Repair transaction
2015-04-26 20:34:37, Info CSI 000001c3 [SR] Verify complete
2015-04-26 20:34:38, Info CSI 000001c4 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:34:38, Info CSI 000001c5 [SR] Beginning Verify and Repair transaction
2015-04-26 20:34:43, Info CSI 000001c7 [SR] Verify complete
2015-04-26 20:34:43, Info CSI 000001c8 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:34:43, Info CSI 000001c9 [SR] Beginning Verify and Repair transaction
2015-04-26 20:34:56, Info CSI 000001cb [SR] Verify complete
2015-04-26 20:34:57, Info CSI 000001cc [SR] Verifying 100 (0x00000064) components
2015-04-26 20:34:57, Info CSI 000001cd [SR] Beginning Verify and Repair transaction
2015-04-26 20:34:59, Info CSI 000001ce [SR] Cannot repair member file [l:22{11}]"MsMpCom.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-04-26 20:35:00, Info CSI 000001cf [SR] Cannot repair member file [l:22{11}]"MsMpCom.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-04-26 20:35:00, Info CSI 000001d0 [SR] This component was referenced by [l:158{79}]"Package_16_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-49_neutral_GDR"
2015-04-26 20:35:00, Info CSI 000001d1 [SR] Could not reproject corrupted file [ml:520{260},l:74{37}]"\??\C:\Program Files\Windows Defender"\[l:22{11}]"MsMpCom.dll"; source file in store is also corrupted
2015-04-26 20:35:01, Info CSI 000001d3 [SR] Verify complete
2015-04-26 20:35:01, Info CSI 000001d4 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:35:01, Info CSI 000001d5 [SR] Beginning Verify and Repair transaction
2015-04-26 20:35:04, Info CSI 000001d7 [SR] Verify complete
2015-04-26 20:35:05, Info CSI 000001d8 [SR] Verifying 100 (0x00000064) components
2015-04-26 20:35:05, Info CSI 000001d9 [SR] Beginning Verify and Repair transaction
2015-04-26 20:35:11, Info CSI 000001e4 [SR] Verify complete
2015-04-26 20:35:11, Info CSI 000001e5 [SR] Verifying 44 (0x0000002c) components
2015-04-26 20:35:11, Info CSI 000001e6 [SR] Beginning Verify and Repair transaction
2015-04-26 20:35:12, Info CSI 000001e8 [SR] Verify complete
2015-04-26 20:35:12, Info CSI 000001e9 [SR] Repairing 2 components
2015-04-26 20:35:12, Info CSI 000001ea [SR] Beginning Verify and Repair transaction
2015-04-26 20:35:12, Info CSI 000001ec [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-04-26 20:35:13, Info CSI 000001ed [SR] Cannot repair member file [l:22{11}]"MsMpCom.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-04-26 20:35:13, Info CSI 000001ef [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-04-26 20:35:13, Info CSI 000001f0 [SR] This component was referenced by [l:160{80}]"Package_30_for_KB936330~31bf3856ad364e35~x86~~6.0.1.18000.936330-187_neutral_GDR"
2015-04-26 20:35:13, Info CSI 000001f3 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
2015-04-26 20:35:13, Info CSI 000001f4 [SR] Cannot repair member file [l:22{11}]"MsMpCom.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-04-26 20:35:13, Info CSI 000001f5 [SR] This component was referenced by [l:158{79}]"Package_16_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-49_neutral_GDR"
2015-04-26 20:35:13, Info CSI 000001f6 [SR] Could not reproject corrupted file [ml:520{260},l:74{37}]"\??\C:\Program Files\Windows Defender"\[l:22{11}]"MsMpCom.dll"; source file in store is also corrupted
2015-04-26 20:35:13, Info CSI 000001f8 [SR] Repair complete
2015-04-26 20:35:13, Info CSI 000001f9 [SR] Committing transaction
2015-04-26 20:35:13, Info CSI 000001fd [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2015-04-27 08:28:03, Info CSI 00000006 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:03, Info CSI 00000007 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:08, Info CSI 00000009 [SR] Verify complete
2015-04-27 08:28:09, Info CSI 0000000a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:09, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:13, Info CSI 0000000d [SR] Verify complete
2015-04-27 08:28:14, Info CSI 0000000e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:14, Info CSI 0000000f [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:15, Info CSI 00000011 [SR] Verify complete
2015-04-27 08:28:16, Info CSI 00000012 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:16, Info CSI 00000013 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:17, Info CSI 00000015 [SR] Verify complete
2015-04-27 08:28:18, Info CSI 00000016 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:18, Info CSI 00000017 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:19, Info CSI 00000019 [SR] Verify complete
2015-04-27 08:28:19, Info CSI 0000001a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:19, Info CSI 0000001b [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:21, Info CSI 0000001d [SR] Verify complete
2015-04-27 08:28:21, Info CSI 0000001e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:21, Info CSI 0000001f [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:22, Info CSI 00000021 [SR] Verify complete
2015-04-27 08:28:23, Info CSI 00000022 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:23, Info CSI 00000023 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:24, Info CSI 00000025 [SR] Verify complete
2015-04-27 08:28:24, Info CSI 00000026 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:24, Info CSI 00000027 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:25, Info CSI 00000029 [SR] Verify complete
2015-04-27 08:28:26, Info CSI 0000002a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:26, Info CSI 0000002b [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:27, Info CSI 0000002d [SR] Verify complete
2015-04-27 08:28:28, Info CSI 0000002e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:28, Info CSI 0000002f [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:29, Info CSI 00000031 [SR] Verify complete
2015-04-27 08:28:29, Info CSI 00000032 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:29, Info CSI 00000033 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:30, Info CSI 00000035 [SR] Verify complete
2015-04-27 08:28:31, Info CSI 00000036 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:31, Info CSI 00000037 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:32, Info CSI 00000039 [SR] Verify complete
2015-04-27 08:28:32, Info CSI 0000003a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:32, Info CSI 0000003b [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:33, Info CSI 0000003d [SR] Verify complete
2015-04-27 08:28:34, Info CSI 0000003e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:34, Info CSI 0000003f [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:35, Info CSI 00000041 [SR] Verify complete
2015-04-27 08:28:35, Info CSI 00000042 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:35, Info CSI 00000043 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:37, Info CSI 00000045 [SR] Verify complete
2015-04-27 08:28:38, Info CSI 00000046 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:38, Info CSI 00000047 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:39, Info CSI 00000049 [SR] Verify complete
2015-04-27 08:28:39, Info CSI 0000004a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:39, Info CSI 0000004b [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:40, Info CSI 0000004d [SR] Verify complete
2015-04-27 08:28:41, Info CSI 0000004e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:41, Info CSI 0000004f [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:43, Info CSI 00000051 [SR] Verify complete
2015-04-27 08:28:43, Info CSI 00000052 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:43, Info CSI 00000053 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:44, Info CSI 00000055 [SR] Verify complete
2015-04-27 08:28:45, Info CSI 00000056 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:45, Info CSI 00000057 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:46, Info CSI 00000059 [SR] Verify complete
2015-04-27 08:28:46, Info CSI 0000005a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:46, Info CSI 0000005b [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:48, Info CSI 0000005d [SR] Verify complete
2015-04-27 08:28:48, Info CSI 0000005e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:48, Info CSI 0000005f [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:49, Info CSI 00000061 [SR] Verify complete
2015-04-27 08:28:50, Info CSI 00000062 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:50, Info CSI 00000063 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:51, Info CSI 00000065 [SR] Verify complete
2015-04-27 08:28:52, Info CSI 00000066 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:52, Info CSI 00000067 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:53, Info CSI 00000069 [SR] Verify complete
2015-04-27 08:28:54, Info CSI 0000006a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:54, Info CSI 0000006b [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:55, Info CSI 0000006d [SR] Verify complete
2015-04-27 08:28:56, Info CSI 0000006e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:56, Info CSI 0000006f [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:57, Info CSI 00000071 [SR] Verify complete
2015-04-27 08:28:57, Info CSI 00000072 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:28:57, Info CSI 00000073 [SR] Beginning Verify and Repair transaction
2015-04-27 08:28:59, Info CSI 00000075 [SR] Verify complete
2015-04-27 08:29:00, Info CSI 00000076 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:00, Info CSI 00000077 [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:01, Info CSI 00000079 [SR] Verify complete
2015-04-27 08:29:01, Info CSI 0000007a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:01, Info CSI 0000007b [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:03, Info CSI 0000007d [SR] Verify complete
2015-04-27 08:29:03, Info CSI 0000007e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:03, Info CSI 0000007f [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:04, Info CSI 00000081 [SR] Verify complete
2015-04-27 08:29:05, Info CSI 00000082 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:05, Info CSI 00000083 [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:06, Info CSI 00000085 [SR] Verify complete
2015-04-27 08:29:06, Info CSI 00000086 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:06, Info CSI 00000087 [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:09, Info CSI 00000089 [SR] Verify complete
2015-04-27 08:29:09, Info CSI 0000008a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:09, Info CSI 0000008b [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:10, Info CSI 0000008d [SR] Verify complete
2015-04-27 08:29:10, Info CSI 0000008e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:10, Info CSI 0000008f [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:12, Info CSI 00000091 [SR] Verify complete
2015-04-27 08:29:12, Info CSI 00000092 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:12, Info CSI 00000093 [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:14, Info CSI 00000095 [SR] Verify complete
2015-04-27 08:29:14, Info CSI 00000096 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:14, Info CSI 00000097 [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:17, Info CSI 00000099 [SR] Verify complete
2015-04-27 08:29:17, Info CSI 0000009a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:17, Info CSI 0000009b [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:23, Info CSI 0000009d [SR] Verify complete
2015-04-27 08:29:23, Info CSI 0000009e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:23, Info CSI 0000009f [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:27, Info CSI 000000a1 [SR] Verify complete
2015-04-27 08:29:28, Info CSI 000000a2 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:28, Info CSI 000000a3 [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:32, Info CSI 000000a6 [SR] Verify complete
2015-04-27 08:29:33, Info CSI 000000a7 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:33, Info CSI 000000a8 [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:37, Info CSI 000000ab [SR] Verify complete
2015-04-27 08:29:38, Info CSI 000000ac [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:38, Info CSI 000000ad [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:43, Info CSI 000000af [SR] Verify complete
2015-04-27 08:29:43, Info CSI 000000b0 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:43, Info CSI 000000b1 [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:52, Info CSI 000000ba [SR] Verify complete
2015-04-27 08:29:52, Info CSI 000000bb [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:52, Info CSI 000000bc [SR] Beginning Verify and Repair transaction
2015-04-27 08:29:59, Info CSI 000000bf [SR] Verify complete
2015-04-27 08:29:59, Info CSI 000000c0 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:29:59, Info CSI 000000c1 [SR] Beginning Verify and Repair transaction
2015-04-27 08:30:05, Info CSI 000000c3 [SR] Verify complete
2015-04-27 08:30:05, Info CSI 000000c4 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:30:05, Info CSI 000000c5 [SR] Beginning Verify and Repair transaction
2015-04-27 08:30:10, Info CSI 000000c7 [SR] Verify complete
2015-04-27 08:30:11, Info CSI 000000c8 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:30:11, Info CSI 000000c9 [SR] Beginning Verify and Repair transaction
2015-04-27 08:30:18, Info CSI 000000cb [SR] Verify complete
2015-04-27 08:30:18, Info CSI 000000cc [SR] Verifying 100 (0x00000064) components
2015-04-27 08:30:18, Info CSI 000000cd [SR] Beginning Verify and Repair transaction
2015-04-27 08:30:27, Info CSI 000000cf [SR] Verify complete
2015-04-27 08:30:27, Info CSI 000000d0 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:30:27, Info CSI 000000d1 [SR] Beginning Verify and Repair transaction
2015-04-27 08:30:39, Info CSI 000000d5 [SR] Verify complete
2015-04-27 08:30:40, Info CSI 000000d6 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:30:40, Info CSI 000000d7 [SR] Beginning Verify and Repair transaction
2015-04-27 08:30:53, Info CSI 000000d9 [SR] Verify complete
2015-04-27 08:30:54, Info CSI 000000da [SR] Verifying 100 (0x00000064) components
2015-04-27 08:30:54, Info CSI 000000db [SR] Beginning Verify and Repair transaction
2015-04-27 08:31:08, Info CSI 000000dd [SR] Verify complete
2015-04-27 08:31:08, Info CSI 000000de [SR] Verifying 100 (0x00000064) components
2015-04-27 08:31:08, Info CSI 000000df [SR] Beginning Verify and Repair transaction
2015-04-27 08:31:13, Info CSI 000000e1 [SR] Verify complete
2015-04-27 08:31:13, Info CSI 000000e2 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:31:13, Info CSI 000000e3 [SR] Beginning Verify and Repair transaction
2015-04-27 08:31:15, Info CSI 000000e5 [SR] Verify complete
2015-04-27 08:31:15, Info CSI 000000e6 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:31:15, Info CSI 000000e7 [SR] Beginning Verify and Repair transaction
2015-04-27 08:31:17, Info CSI 000000e9 [SR] Verify complete
2015-04-27 08:31:18, Info CSI 000000ea [SR] Verifying 100 (0x00000064) components
2015-04-27 08:31:18, Info CSI 000000eb [SR] Beginning Verify and Repair transaction
2015-04-27 08:31:29, Info CSI 00000109 [SR] Verify complete
2015-04-27 08:31:29, Info CSI 0000010a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:31:29, Info CSI 0000010b [SR] Beginning Verify and Repair transaction
2015-04-27 08:31:32, Info CSI 0000010d [SR] Verify complete
2015-04-27 08:31:33, Info CSI 0000010e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:31:33, Info CSI 0000010f [SR] Beginning Verify and Repair transaction
2015-04-27 08:31:36, Info CSI 00000111 [SR] Verify complete
2015-04-27 08:31:37, Info CSI 00000112 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:31:37, Info CSI 00000113 [SR] Beginning Verify and Repair transaction
2015-04-27 08:31:40, Info CSI 00000115 [SR] Verify complete
2015-04-27 08:31:40, Info CSI 00000116 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:31:40, Info CSI 00000117 [SR] Beginning Verify and Repair transaction
2015-04-27 08:31:47, Info CSI 00000119 [SR] Verify complete
2015-04-27 08:31:48, Info CSI 0000011a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:31:48, Info CSI 0000011b [SR] Beginning Verify and Repair transaction
2015-04-27 08:31:59, Info CSI 0000011e [SR] Verify complete
2015-04-27 08:31:59, Info CSI 0000011f [SR] Verifying 100 (0x00000064) components
2015-04-27 08:31:59, Info CSI 00000120 [SR] Beginning Verify and Repair transaction
2015-04-27 08:32:04, Info CSI 00000122 [SR] Verify complete
2015-04-27 08:32:04, Info CSI 00000123 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:32:04, Info CSI 00000124 [SR] Beginning Verify and Repair transaction
2015-04-27 08:32:11, Info CSI 00000126 [SR] Verify complete
2015-04-27 08:32:12, Info CSI 00000127 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:32:12, Info CSI 00000128 [SR] Beginning Verify and Repair transaction
2015-04-27 08:32:25, Info CSI 0000012a [SR] Verify complete
2015-04-27 08:32:26, Info CSI 0000012b [SR] Verifying 100 (0x00000064) components
2015-04-27 08:32:26, Info CSI 0000012c [SR] Beginning Verify and Repair transaction
2015-04-27 08:32:52, Info CSI 0000012e [SR] Verify complete
2015-04-27 08:32:53, Info CSI 0000012f [SR] Verifying 100 (0x00000064) components
2015-04-27 08:32:53, Info CSI 00000130 [SR] Beginning Verify and Repair transaction
2015-04-27 08:33:11, Info CSI 00000132 [SR] Verify complete
2015-04-27 08:33:11, Info CSI 00000133 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:33:11, Info CSI 00000134 [SR] Beginning Verify and Repair transaction
2015-04-27 08:33:23, Info CSI 00000159 [SR] Verify complete
2015-04-27 08:33:24, Info CSI 0000015a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:33:24, Info CSI 0000015b [SR] Beginning Verify and Repair transaction
2015-04-27 08:33:35, Info CSI 0000015d [SR] Verify complete
2015-04-27 08:33:36, Info CSI 0000015e [SR] Verifying 100 (0x00000064) components
2015-04-27 08:33:36, Info CSI 0000015f [SR] Beginning Verify and Repair transaction
2015-04-27 08:34:08, Info CSI 00000161 [SR] Verify complete
2015-04-27 08:34:09, Info CSI 00000162 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:34:09, Info CSI 00000163 [SR] Beginning Verify and Repair transaction
2015-04-27 08:34:22, Info CSI 00000165 [SR] Verify complete
2015-04-27 08:34:23, Info CSI 00000166 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:34:23, Info CSI 00000167 [SR] Beginning Verify and Repair transaction
2015-04-27 08:34:34, Info CSI 00000169 [SR] Verify complete
2015-04-27 08:34:34, Info CSI 0000016a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:34:34, Info CSI 0000016b [SR] Beginning Verify and Repair transaction
2015-04-27 08:34:35, Info CSI 0000016d [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-04-27 08:34:41, Info CSI 0000016f [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-04-27 08:34:41, Info CSI 00000170 [SR] This component was referenced by [l:160{80}]"Package_30_for_KB936330~31bf3856ad364e35~x86~~6.0.1.18000.936330-187_neutral_GDR"
2015-04-27 08:34:41, Info CSI 00000173 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
2015-04-27 08:34:42, Info CSI 00000175 [SR] Verify complete
2015-04-27 08:34:42, Info CSI 00000176 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:34:42, Info CSI 00000177 [SR] Beginning Verify and Repair transaction
2015-04-27 08:34:47, Info CSI 00000179 [SR] Verify complete
2015-04-27 08:34:48, Info CSI 0000017a [SR] Verifying 100 (0x00000064) components
2015-04-27 08:34:48, Info CSI 0000017b [SR] Beginning Verify and Repair transaction
2015-04-27 08:34:55, Info CSI 0000017e [SR] Verify complete
2015-04-27 08:34:55, Info CSI 0000017f [SR] Verifying 100 (0x00000064) components
2015-04-27 08:34:55, Info CSI 00000180 [SR] Beginning Verify and Repair transaction
2015-04-27 08:35:13, Info CSI 00000182 [SR] Verify complete
2015-04-27 08:35:13, Info CSI 00000183 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:35:13, Info CSI 00000184 [SR] Beginning Verify and Repair transaction
2015-04-27 08:35:22, Info CSI 00000186 [SR] Verify complete
2015-04-27 08:35:23, Info CSI 00000187 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:35:23, Info CSI 00000188 [SR] Beginning Verify and Repair transaction
2015-04-27 08:35:32, Info CSI 0000018a [SR] Verify complete
2015-04-27 08:35:33, Info CSI 0000018b [SR] Verifying 100 (0x00000064) components
2015-04-27 08:35:33, Info CSI 0000018c [SR] Beginning Verify and Repair transaction
2015-04-27 08:35:45, Info CSI 0000018e [SR] Verify complete
2015-04-27 08:35:46, Info CSI 0000018f [SR] Verifying 100 (0x00000064) components
2015-04-27 08:35:46, Info CSI 00000190 [SR] Beginning Verify and Repair transaction
2015-04-27 08:35:53, Info CSI 00000192 [SR] Verify complete
2015-04-27 08:35:54, Info CSI 00000193 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:35:54, Info CSI 00000194 [SR] Beginning Verify and Repair transaction
2015-04-27 08:36:04, Info CSI 00000196 [SR] Verify complete
2015-04-27 08:36:05, Info CSI 00000197 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:36:05, Info CSI 00000198 [SR] Beginning Verify and Repair transaction
2015-04-27 08:36:20, Info CSI 0000019b [SR] Verify complete
2015-04-27 08:36:20, Info CSI 0000019c [SR] Verifying 100 (0x00000064) components
2015-04-27 08:36:20, Info CSI 0000019d [SR] Beginning Verify and Repair transaction
2015-04-27 08:36:26, Info CSI 0000019f [SR] Verify complete
2015-04-27 08:36:27, Info CSI 000001a0 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:36:27, Info CSI 000001a1 [SR] Beginning Verify and Repair transaction
2015-04-27 08:36:33, Info CSI 000001a3 [SR] Verify complete
2015-04-27 08:36:34, Info CSI 000001a4 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:36:34, Info CSI 000001a5 [SR] Beginning Verify and Repair transaction
2015-04-27 08:36:42, Info CSI 000001a7 [SR] Verify complete
2015-04-27 08:36:42, Info CSI 000001a8 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:36:42, Info CSI 000001a9 [SR] Beginning Verify and Repair transaction
2015-04-27 08:36:52, Info CSI 000001ae [SR] Verify complete
2015-04-27 08:36:53, Info CSI 000001af [SR] Verifying 100 (0x00000064) components
2015-04-27 08:36:53, Info CSI 000001b0 [SR] Beginning Verify and Repair transaction
2015-04-27 08:37:01, Info CSI 000001b2 [SR] Verify complete
2015-04-27 08:37:02, Info CSI 000001b3 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:37:02, Info CSI 000001b4 [SR] Beginning Verify and Repair transaction
2015-04-27 08:37:13, Info CSI 000001b6 [SR] Verify complete
2015-04-27 08:37:13, Info CSI 000001b7 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:37:13, Info CSI 000001b8 [SR] Beginning Verify and Repair transaction
2015-04-27 08:37:16, Info CSI 000001ba [SR] Verify complete
2015-04-27 08:37:16, Info CSI 000001bb [SR] Verifying 100 (0x00000064) components
2015-04-27 08:37:16, Info CSI 000001bc [SR] Beginning Verify and Repair transaction
2015-04-27 08:37:24, Info CSI 000001be [SR] Verify complete
2015-04-27 08:37:25, Info CSI 000001bf [SR] Verifying 100 (0x00000064) components
2015-04-27 08:37:25, Info CSI 000001c0 [SR] Beginning Verify and Repair transaction
2015-04-27 08:37:33, Info CSI 000001c2 [SR] Verify complete
2015-04-27 08:37:34, Info CSI 000001c3 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:37:34, Info CSI 000001c4 [SR] Beginning Verify and Repair transaction
2015-04-27 08:37:41, Info CSI 000001c6 [SR] Verify complete
2015-04-27 08:37:42, Info CSI 000001c7 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:37:42, Info CSI 000001c8 [SR] Beginning Verify and Repair transaction
2015-04-27 08:38:01, Info CSI 000001ca [SR] Verify complete
2015-04-27 08:38:01, Info CSI 000001cb [SR] Verifying 100 (0x00000064) components
2015-04-27 08:38:01, Info CSI 000001cc [SR] Beginning Verify and Repair transaction
2015-04-27 08:38:05, Info CSI 000001cd [SR] Cannot repair member file [l:22{11}]"MsMpCom.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-04-27 08:38:06, Info CSI 000001ce [SR] Cannot repair member file [l:22{11}]"MsMpCom.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-04-27 08:38:06, Info CSI 000001cf [SR] This component was referenced by [l:158{79}]"Package_16_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-49_neutral_GDR"
2015-04-27 08:38:06, Info CSI 000001d0 [SR] Could not reproject corrupted file [ml:520{260},l:74{37}]"\??\C:\Program Files\Windows Defender"\[l:22{11}]"MsMpCom.dll"; source file in store is also corrupted
2015-04-27 08:38:07, Info CSI 000001d2 [SR] Verify complete
2015-04-27 08:38:07, Info CSI 000001d3 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:38:07, Info CSI 000001d4 [SR] Beginning Verify and Repair transaction
2015-04-27 08:38:12, Info CSI 000001d6 [SR] Verify complete
2015-04-27 08:38:13, Info CSI 000001d7 [SR] Verifying 100 (0x00000064) components
2015-04-27 08:38:13, Info CSI 000001d8 [SR] Beginning Verify and Repair transaction
2015-04-27 08:38:21, Info CSI 000001e3 [SR] Verify complete
2015-04-27 08:38:21, Info CSI 000001e4 [SR] Verifying 44 (0x0000002c) components
2015-04-27 08:38:21, Info CSI 000001e5 [SR] Beginning Verify and Repair transaction
2015-04-27 08:38:24, Info CSI 000001e7 [SR] Verify complete
2015-04-27 08:38:24, Info CSI 000001e8 [SR] Repairing 2 components
2015-04-27 08:38:24, Info CSI 000001e9 [SR] Beginning Verify and Repair transaction
2015-04-27 08:38:24, Info CSI 000001eb [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-04-27 08:38:24, Info CSI 000001ec [SR] Cannot repair member file [l:22{11}]"MsMpCom.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-04-27 08:38:24, Info CSI 000001ee [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-04-27 08:38:24, Info CSI 000001ef [SR] This component was referenced by [l:160{80}]"Package_30_for_KB936330~31bf3856ad364e35~x86~~6.0.1.18000.936330-187_neutral_GDR"
2015-04-27 08:38:24, Info CSI 000001f2 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"tcpmon.ini"; source file in store is also corrupted
2015-04-27 08:38:24, Info CSI 000001f3 [SR] Cannot repair member file [l:22{11}]"MsMpCom.dll" of Security-Malware-Windows-Defender, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-04-27 08:38:24, Info CSI 000001f4 [SR] This component was referenced by [l:158{79}]"Package_16_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-49_neutral_GDR"
2015-04-27 08:38:24, Info CSI 000001f5 [SR] Could not reproject corrupted file [ml:520{260},l:74{37}]"\??\C:\Program Files\Windows Defender"\[l:22{11}]"MsMpCom.dll"; source file in store is also corrupted
2015-04-27 08:38:24, Info CSI 000001f7 [SR] Repair complete
2015-04-27 08:38:24, Info CSI 000001f8 [SR] Committing transaction
2015-04-27 08:38:25, Info CSI 000001fc [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
 
I did say it was long but i do not think that the printer issue is of any worry. ( mine works fine)

I also think (with your help and others) that the defender issue is now sorted.

My start up time has gone up 30% with adding MSE. and donetao . says my Avast security will cause problems, but it caught out a virus today, where MSE did not.
Why should I be worried and why is it a No,No???? to have Avast extra security.
Avast works for me and I have used (advanced system care 8) for years. IObit has never been a problem and never let me down. (defrag/malware when i want to check and driver boost. ) They have all been good for years.
Why would he say that when I have had no problems with them for years???
 
I only meant that it's not good to have two anti-virus programs running together in real time as there could be a conflict. If IOit works for you and there aren't any conflicts running two anti-virus programs and your issues have all been settled, then good for you.
Thanks for your feedback!
 
Oneman said:
No problem donetao.

Thanks for your time and help. It's much appreciated.:smile:
Click to expand...
Your very welcome my friend. Thanks for making my day. I was thinking my day was a total loss until your reply!. I run MSE and MBAM premium on my machine and there are no conflicts. If MSE and Avast run together in real time with no conflicts, then I say go for it. They are both good programs!!
I'm glad your issues are solved friend!!
 
Personally, I would stay away from IObit products, since most of them are useless and can at one point be dangerous for your system. I can list you my reasons if needed, but I don't want to start a debate here so I'll do so only if you want me to.
 
Hi all.

Thanks for the replies.
I take it there are some issues with using IObit? I use quite a few bits of their software and have been for about 5 years without problems.
I did a search on here for IObit and found a article dated 2009 that refers to them as stealing intellectual property/database.
I must admit that I do not fully understand the full issue other than it might me morally wrong to use their stuff.
So please do explain and tell me about it as I have nothing to lose by looking into this issue.
I can start a new thread on this but I am quite happy to continue on this one if that is ok with you all.
Aura I would be interested to hear what dangers to my system IObit can cause and what the alternatives are.
Looking forward to hearing your replies.

Regards
Oneman1.
 
Hi, Oneman.

There are several things of note here.

1. Using two antivirus software programs can cause conflicts on your computer and is not advisable. That said, Microsoft Security Essentials would not have/should not have installed unless or until Avast was uninstalled/disabled.

2. Regarding iObit stealing intellectual property -- this is more than a moral issue. It is downright thievery. I certainly would not trust a company that stole from another company.

3. The issue regarding iObit's registry cleaner is not restricted to their product. Rather, because Windows is a closed source system, developers of registry cleaners do not have the core code of Windows and are not working on definitive information, but rather they are going on past knowledge and experience. Automatic cleaners will usually have to do some guesswork. In addition, modifying registry keys incorrectly can cause Windows instability, or make Windows unbootable. No registry cleaner is completely safe and the potential is ever present to cause more problems than they claim to fix. Consider also that Microsoft does not support the use of registry cleaners. See Microsoft support policy for the use of registry cleaning utilities.
 
Here's what I usually post when someone uses IObit products. Keep in mind that these are what we call "canned" replies. I just put together all the information needed in order to the reader to understand what dangers IObit products represents and what are the alternatives.

warning.gif
IObit Software Warning!
IObit have been accused in the past from using shady techniques in order to promote and enhance their products, one of which was to steal Malwarebytes' definition database to include it in their "Antimalware", IObit Malware Fighter. On top of that, their main product, Advanced SystemCare, goes into the "PC Booster" category of program, which are useless programs since there's no proofs or facts that these actually boost the performance of a system, and are borderline "scamware". In fact, these programs have a tendency to cause a variety of issues under Windows, that can be solved by uninstalling the software, ironic isn't it? Most of their features can be replaced by using other programs, often, utilities that requires no installation or that are already "built-in" inside Windows.

Below are articles that relates the Malwarebytes VS IObit episode and also why IObit failed as a company and within it's products.

The next one applies to their principal program, IObit Advanced SystemCare.

warning.gif
PC Booster/Tune-Up Program Warning!
"PC Booster/Tune Up" programs are part of the worst programs you can install on a system. When it comes to messing up your system (Windows), these are as worst as malware. They are completely worthless and useless to use. The worst is that they'll often take action on your system without you knowing, nor authorizing it, which could lead to your system being altered in a way you don't want it to be or even worst, a "broke" system. Every feature they provide, you can either do it natively under Windows, do it via another standalone executable (which is way easier and safer to use) or they aren't providing something you need. Here's a few examples:
  • Cleaning temporary files: TFC (standalone executable), CCleaner (installed), Cleanmgr.exe (in-built);
  • Managing start-up entries: Autoruns (standalone executable), CCleaner (installed), Task Manager and Registry (in-built);
  • Driver Updater: Not needed, all you need is to go on your manufacturer website so you'll be sure to get the right, official, working drivers for your computer or hardware;
  • Registry Cleaner/Defragger: Completely useless and also dangerous;
  • Disk Defragging: Disk Defrag (in-built), O&O Disk Defrag (installed), Defraggler (installed);
  • Powerful uninstaller: Not needed, only needed when you have to make sure a program is completely uninstalled. Revo Uninstaller have a portable version you can use;
  • "Enhanced" Task Manager: Procexp (standalone executable), Process Hacker (portable or installed);
  • "Active security": Any Antivirus and Antimalware can beat that, easily. These programs aren't made to replace Antivirus or Antimalware products and shouldn't be seen as such;
  • Repair Hard Drive issues: Simple chkdsk /r command under Windows (in-built);
Having such program installing on your system will just bloat it down and you have more chances to have issues by using them than without. These products are advertised as a program that can solve all your issues, remove every malware, speed up your computer performance over 100%, etc. The truth is that there's not a single program that can do that. First of all, these programs aren't made to remove virus and malware, leave this in the hands of Antivirus and Antimalware, period. Secondly, there's so many kind of issues under Windows that there's not a single program that can address them all. If you think that BSOD (Blue Screen of Death) issues can be solved by opening a program and clicking on a "Fix" button, then I'm sorry to tell you but, you're wrong. Also, you cannot boost the performance of a hardware over it's hardware capabilities. Of course you can overclock some components, like your CPU, RAM and GPU, but these aren't done via these programs, but via your BIOS interface. I could recommend you a program for every feature these programs advertise, and also tell you exactly in detail why most of them are completely useless, such as Registry cleaner (dangerous to use), and driver updater (dangerous to use, and also completely useless, it'll not improve your system performance). In the end, buying such programs is the exact same as being scammed (because this is what it is, a pure scam) and using one of these programs will result you in having a system less performant than prior to using it.

Relevant articles if you want to read more about PC Boosters/Optimizers and why they are useless:

And last the last applies to one of their program, Driver Booster.

warning.gif
Driver Updater Warning!
Driver Updaters can damage your system at a point where a reinstallation of Windows might be needed.
  • Drivers are "middlemen" between your OS (Windows) and your hardware (computer). They control and facilitate the interaction between Windows and hardware components, to deliver a "message", nothing more;
  • Having all of your drivers up to date, all the time, will not improve the performance of your system, nor your computer. You cannot increase the hardware performance of a component over the current capabilities it have;
  • Driver updates are released to fix a bug or an issue with a previous release of that driver. Not everyone with the same drivers will experience the issue, so if you are having no problems with the drivers you are running, you don't need to update them. "If it's not broken, don't fix it";
  • You can download drivers for free from your computer/laptop manufacturers website, or from the hardware component manufacturers website. You don't need to pay for any of them, if you are being asked to pay for drivers it is likely a scam;
  • Only drivers from the computer/laptop manufacturers website, or the hardware component manufacturers website are considered official (legitimate and working). You should not download drivers from anywhere else;
  • Driver Updaters are a scam, they try to convince you that you need these programs in order to make your system perform well, which is false;
  • It has been tested and proven that these programs will detect outdated drivers on a system that have the most updated drivers from the manufacturer, which shows that they don't work and/or they try to make you install "newer" suspicious drivers;
  • The goal of the distributors of such programs is to make money by making you buy their useless product, or install additional software (PUPs) when you install their program. Your system will perform worse with these programs installed than without;
This being said, such programs could be seen as "pure scam" and should be avoided at all cost.

Here's some articles that talks about Driver Updater programs and why they shouldn't be used:

Looking more into it, I also wrote this one which applies to Advanced SystemCare since it have a "Registry Cleaner".

warning.gif
Registry Cleaners Warning!
Registry Cleaners are known to be harmful to the system and should not be used for any reason there is. It's a known fact that using such programs can easily break a Windows installation, to the point where a complete reinstallation might be needed. Here's a few myths about using these programs, and why they are just plainly false.
  • "Using a Registry Cleaner will improve a system's performance" - False. The Windows Registry is a big database which contains information on everything present on the system, from the boot settings to how your programs looks when you open them. There's so many entries in it that cleaning even thousands of them isn't enough to boost a system performance. Also, there's no studies, tests, benchmarks, etc. which shows that using Registry Cleaners actually improve a system speed;
  • "Using a Registry Cleaner will fix all your errors" - False. Using a Registry Cleaner won't fix any problems at all. In fact, it have more chances to create them if anything. There's no program that can fix every problems in a simple click, and there probably never will. If you have an error, it's better to troubleshoot that error in particuliar by finding what's causing it and fixing it than using a software that might give you more errors;
  • "If you don't use a Registry Cleaner, you'll leave a door open for malware" - False. It is rare that malware will actually hijack orpheans keys and keypairs in the Registry to create persistence or install themself. They'll usually create their own keys/keypairs since they have been instructed (coded) to do so, and the creator cannot expect every system he'll infect to have leftover keys. Also, pretty much only Reg Loading Points in the Registry would be of any interest for a malware to hijack, and these are usually occupied already, or quickly deleted when empty;
  • Registry Cleaners aren't Registry Defraggers - These are two different kind of software who have two distinct function each.
  • On a last note, there's a lot of Registry Cleaners out here that won't create a back-up of your Registry before applying the changes they make. Which means that if you use them and clean entries that prevents Windows to reboot after, locking you out of your computer, you won't be able to restore a precedent Registry back-up via the Recovery PE. This means that if you can't fix the boot issue after that, you'll most likely be forced to reinstall Windows;
Registry Cleaners were used back in the days by developers who were using a OLE-schema for their applications. They used these to clean the Registry after uninstalling their programs, just in case there was traces of it left behind that could affect a reinstallation. These were back in the Windows 95 and Windows 98 days and this practice isn't in effect anymore. Therefore, there's no reason for you to use such programs and quite a few to avoid them instead.

Here's more articles on Registry Cleaners that are worth a read if you want to learn more about them and why you shouldn't use them.

This should give you a good read. If you have any questions or you would like me to give more details on a certain point, feel free to ask.
 
Hi Corrine.

Thanks for the post.
I am new to this techie stuff but I am becoming a fast learner with the help on here thanks.:smile9:
I have just been reading this article that explains why the reg cleaners are not much cop and how they can be a bit aggressive. It has made things a lot clearer now.
https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/7869-need-help-random-bsods-packard-bell-easynote-ml61.html?highlight=IObit

I guess IObit have never owned up to the theft and have just been caught out. Has there been any update or come back since the article in 2009?

Not sure why the MSE installed while the Avast system was running but there does not seem to be any problems with them running along side each other. I do seem to be getting a lot of updates for MSE each day (2 yesterday and 3 today) Is this normal?

What are the alternatives to using IObit. I have all 3 of the items in jcgriff2 link above and also have IObit uninstaller. I must say I do find them useful but if it is a no no then I will have to find alternatives.

Thanks for your time.

Oneman.

Edit: Hi Aura you must have snook in while I was typing just reading through your post now.:s2:
 
Has there been any update or come back since the article in 2009?
Click to expand...


IObit removed every Malwarebytes definitions from their database, and their detection ratio fail around the 30% after that.

Not sure why the MSE installed while the Avast system was running but there does not seem to be any problems with them running along side each other. I do seem to be getting a lot of updates for MSE each day (2 yesterday and 3 today) Is this normal?
Click to expand...


You should never have two Antivirus installed side-by-side, since it can cause system instability and conflict. quietman, a Microsoft MVP on BleepingComputer, wrote an article on Antivirus programs. Pay attention to the "IMPORTANT NOTE" at the end.

Choosing an Anti-Virus Program

What are the alternatives to using IObit. I have all 3 of the items in jcgriff2 link above and also have IObit uninstaller. I must say I do find them useful but if it is a no no then I will have to find alternatives.
Click to expand...


If you didn't find alternatives in my last post, list me the IObit programs you are using and I'll find you alternatives for all of them.
 
Thanks Aura.
I have just read your post and I'm about to start running through the articles included. Lots of reading to do so I could be some time. I do have a few things I would like to ask about but they may have be answered in the articles so please bear with me.
 
No problem Oneman you can take your time :)
 
You should never have two Antivirus installed side-by-side, since it can cause system instability and conflict
Click to expand...
I think the advice today is still sound, but not so much for the reasons commonly given any more - at least with the more reputable programs. I used to say having two running at once was like having two dogs guarding the same bone - each wondering what the other was up too. That may still apply but generally they still work and don't conflict any more as having two did many years ago with XP. I have to say again as I now do often, W7, W8, W10 are NOT XP and I think that applies here too.

But having two anti-malware programs running at once IS a waste of resources and can bog systems downs needlessly without making you more secure. So it still is not advisable.

There is a notable exception, however. And that is MBAM Premium. It plays very well in-resident with other programs. I run MSE and MBAM Premium on my main W7 system and WD and MBAM Premium on my main W8 systems with no issues with conflicts, stability or performance.
 
Hi Digerati.

I have seen MBAM Premium crop up in quite a few articles so it is something else I will have to read up on. Thanks.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top