Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Command Prompt Flashes Just Before Desktop Icons Show on Startup?


  • Please log in to reply

#16
radiuss

radiuss

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts
when I do that, notepad pops up but nothing is written.
  • 0

Advertisements


#17
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,010 posts
  • MVP
Try running sfc /scannow again just before doing:


findstr /c:"[SR]" \windows\logs\cbs\cbs.log > \windows\logs\cbs\junk.txt
notepad \windows\logs\cbs\junk.txt

The cbs.log gets periodically flushed so it might have been empty when you ran the command.
  • 0

#18
radiuss

radiuss

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

Try running sfc /scannow again just before doing:


findstr /c:"[SR]" \windows\logs\cbs\cbs.log > \windows\logs\cbs\junk.txt
notepad \windows\logs\cbs\junk.txt

The cbs.log gets periodically flushed so it might have been empty when you ran the command.


You were right, it worked, here it is, thanks:

2013-07-28 10:22:12, Info CSI 00000009 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:12, Info CSI 0000000a [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:15, Info CSI 0000000c [SR] Verify complete
2013-07-28 10:22:15, Info CSI 0000000d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:15, Info CSI 0000000e [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:19, Info CSI 00000010 [SR] Verify complete
2013-07-28 10:22:19, Info CSI 00000011 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:19, Info CSI 00000012 [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:22, Info CSI 00000014 [SR] Verify complete
2013-07-28 10:22:22, Info CSI 00000015 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:22, Info CSI 00000016 [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:26, Info CSI 00000018 [SR] Verify complete
2013-07-28 10:22:26, Info CSI 00000019 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:26, Info CSI 0000001a [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:29, Info CSI 0000001c [SR] Verify complete
2013-07-28 10:22:29, Info CSI 0000001d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:29, Info CSI 0000001e [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:34, Info CSI 00000020 [SR] Verify complete
2013-07-28 10:22:34, Info CSI 00000021 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:34, Info CSI 00000022 [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:38, Info CSI 00000024 [SR] Verify complete
2013-07-28 10:22:38, Info CSI 00000025 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:38, Info CSI 00000026 [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:42, Info CSI 00000028 [SR] Verify complete
2013-07-28 10:22:42, Info CSI 00000029 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:42, Info CSI 0000002a [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:46, Info CSI 0000002c [SR] Verify complete
2013-07-28 10:22:47, Info CSI 0000002d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:47, Info CSI 0000002e [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:51, Info CSI 00000030 [SR] Verify complete
2013-07-28 10:22:51, Info CSI 00000031 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:51, Info CSI 00000032 [SR] Beginning Verify and Repair transaction
2013-07-28 10:22:58, Info CSI 00000034 [SR] Verify complete
2013-07-28 10:22:58, Info CSI 00000035 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:22:58, Info CSI 00000036 [SR] Beginning Verify and Repair transaction
2013-07-28 10:23:03, Info CSI 00000038 [SR] Verify complete
2013-07-28 10:23:03, Info CSI 00000039 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:23:03, Info CSI 0000003a [SR] Beginning Verify and Repair transaction
2013-07-28 10:23:07, Info CSI 0000003c [SR] Verify complete
2013-07-28 10:23:07, Info CSI 0000003d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:23:07, Info CSI 0000003e [SR] Beginning Verify and Repair transaction
2013-07-28 10:23:10, Info CSI 00000040 [SR] Verify complete
2013-07-28 10:23:10, Info CSI 00000041 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:23:10, Info CSI 00000042 [SR] Beginning Verify and Repair transaction
2013-07-28 10:23:18, Info CSI 00000045 [SR] Verify complete
2013-07-28 10:23:18, Info CSI 00000046 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:23:18, Info CSI 00000047 [SR] Beginning Verify and Repair transaction
2013-07-28 10:23:27, Info CSI 0000004a [SR] Verify complete
2013-07-28 10:23:28, Info CSI 0000004b [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:23:28, Info CSI 0000004c [SR] Beginning Verify and Repair transaction
2013-07-28 10:23:35, Info CSI 0000004f [SR] Verify complete
2013-07-28 10:23:35, Info CSI 00000050 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:23:35, Info CSI 00000051 [SR] Beginning Verify and Repair transaction
2013-07-28 10:23:41, Info CSI 00000054 [SR] Verify complete
2013-07-28 10:23:41, Info CSI 00000055 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:23:41, Info CSI 00000056 [SR] Beginning Verify and Repair transaction
2013-07-28 10:23:47, Info CSI 0000005a [SR] Verify complete
2013-07-28 10:23:48, Info CSI 0000005b [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:23:48, Info CSI 0000005c [SR] Beginning Verify and Repair transaction
2013-07-28 10:23:55, Info CSI 0000005e [SR] Verify complete
2013-07-28 10:23:55, Info CSI 0000005f [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:23:55, Info CSI 00000060 [SR] Beginning Verify and Repair transaction
2013-07-28 10:24:04, Info CSI 00000082 [SR] Verify complete
2013-07-28 10:24:04, Info CSI 00000083 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:24:04, Info CSI 00000084 [SR] Beginning Verify and Repair transaction
2013-07-28 10:24:12, Info CSI 00000089 [SR] Verify complete
2013-07-28 10:24:12, Info CSI 0000008a [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:24:12, Info CSI 0000008b [SR] Beginning Verify and Repair transaction
2013-07-28 10:24:20, Info CSI 0000008d [SR] Verify complete
2013-07-28 10:24:20, Info CSI 0000008e [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:24:20, Info CSI 0000008f [SR] Beginning Verify and Repair transaction
2013-07-28 10:24:26, Info CSI 00000091 [SR] Verify complete
2013-07-28 10:24:26, Info CSI 00000092 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:24:26, Info CSI 00000093 [SR] Beginning Verify and Repair transaction
2013-07-28 10:24:32, Info CSI 00000095 [SR] Verify complete
2013-07-28 10:24:32, Info CSI 00000096 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:24:32, Info CSI 00000097 [SR] Beginning Verify and Repair transaction
2013-07-28 10:24:38, Info CSI 00000099 [SR] Cannot repair member file [l:30{15}]"Display.dll.mui" of Microsoft-Windows-Display.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:24:39, Info CSI 0000009b [SR] Cannot repair member file [l:30{15}]"Display.dll.mui" of Microsoft-Windows-Display.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:24:39, Info CSI 0000009c [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ko-KR~6.1.7601.17514.Windows Foundation Language Pack"
2013-07-28 10:24:39, Info CSI 0000009f [SR] Could not reproject corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\ko-KR"\[l:30{15}]"Display.dll.mui"; source file in store is also corrupted
2013-07-28 10:24:40, Info CSI 000000a1 [SR] Verify complete
2013-07-28 10:24:40, Info CSI 000000a2 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:24:40, Info CSI 000000a3 [SR] Beginning Verify and Repair transaction
2013-07-28 10:24:47, Info CSI 000000a5 [SR] Verify complete
2013-07-28 10:24:47, Info CSI 000000a6 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:24:47, Info CSI 000000a7 [SR] Beginning Verify and Repair transaction
2013-07-28 10:24:52, Info CSI 000000a9 [SR] Verify complete
2013-07-28 10:24:53, Info CSI 000000aa [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:24:53, Info CSI 000000ab [SR] Beginning Verify and Repair transaction
2013-07-28 10:25:01, Info CSI 000000ad [SR] Verify complete
2013-07-28 10:25:01, Info CSI 000000ae [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:25:01, Info CSI 000000af [SR] Beginning Verify and Repair transaction
2013-07-28 10:25:14, Info CSI 000000d2 [SR] Verify complete
2013-07-28 10:25:14, Info CSI 000000d3 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:25:14, Info CSI 000000d4 [SR] Beginning Verify and Repair transaction
2013-07-28 10:25:23, Info CSI 000000d6 [SR] Verify complete
2013-07-28 10:25:23, Info CSI 000000d7 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:25:23, Info CSI 000000d8 [SR] Beginning Verify and Repair transaction
2013-07-28 10:25:40, Info CSI 000000da [SR] Verify complete
2013-07-28 10:25:40, Info CSI 000000db [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:25:40, Info CSI 000000dc [SR] Beginning Verify and Repair transaction
2013-07-28 10:25:50, Info CSI 000000de [SR] Verify complete
2013-07-28 10:25:50, Info CSI 000000df [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:25:50, Info CSI 000000e0 [SR] Beginning Verify and Repair transaction
2013-07-28 10:25:54, Info CSI 000000e4 [SR] Verify complete
2013-07-28 10:25:55, Info CSI 000000e5 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:25:55, Info CSI 000000e6 [SR] Beginning Verify and Repair transaction
2013-07-28 10:25:59, Info CSI 000000e8 [SR] Verify complete
2013-07-28 10:25:59, Info CSI 000000e9 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:25:59, Info CSI 000000ea [SR] Beginning Verify and Repair transaction
2013-07-28 10:26:02, Info CSI 000000ec [SR] Verify complete
2013-07-28 10:26:02, Info CSI 000000ed [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:26:02, Info CSI 000000ee [SR] Beginning Verify and Repair transaction
2013-07-28 10:26:05, Info CSI 000000f0 [SR] Verify complete
2013-07-28 10:26:05, Info CSI 000000f1 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:26:05, Info CSI 000000f2 [SR] Beginning Verify and Repair transaction
2013-07-28 10:26:09, Info CSI 000000f4 [SR] Verify complete
2013-07-28 10:26:10, Info CSI 000000f5 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:26:10, Info CSI 000000f6 [SR] Beginning Verify and Repair transaction
2013-07-28 10:26:22, Info CSI 00000109 [SR] Verify complete
2013-07-28 10:26:22, Info CSI 0000010a [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:26:22, Info CSI 0000010b [SR] Beginning Verify and Repair transaction
2013-07-28 10:26:25, Info CSI 0000010d [SR] Verify complete
2013-07-28 10:26:26, Info CSI 0000010e [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:26:26, Info CSI 0000010f [SR] Beginning Verify and Repair transaction
2013-07-28 10:26:28, Info CSI 00000111 [SR] Verify complete
2013-07-28 10:26:28, Info CSI 00000112 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:26:28, Info CSI 00000113 [SR] Beginning Verify and Repair transaction
2013-07-28 10:26:33, Info CSI 00000115 [SR] Verify complete
2013-07-28 10:26:33, Info CSI 00000116 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:26:33, Info CSI 00000117 [SR] Beginning Verify and Repair transaction
2013-07-28 10:26:40, Info CSI 00000119 [SR] Verify complete
2013-07-28 10:26:40, Info CSI 0000011a [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:26:40, Info CSI 0000011b [SR] Beginning Verify and Repair transaction
2013-07-28 10:26:49, Info CSI 0000011e [SR] Verify complete
2013-07-28 10:26:49, Info CSI 0000011f [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:26:49, Info CSI 00000120 [SR] Beginning Verify and Repair transaction
2013-07-28 10:26:57, Info CSI 00000123 [SR] Verify complete
2013-07-28 10:26:58, Info CSI 00000124 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:26:58, Info CSI 00000125 [SR] Beginning Verify and Repair transaction
2013-07-28 10:27:02, Info CSI 00000127 [SR] Verify complete
2013-07-28 10:27:02, Info CSI 00000128 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:27:02, Info CSI 00000129 [SR] Beginning Verify and Repair transaction
2013-07-28 10:27:07, Info CSI 0000012b [SR] Verify complete
2013-07-28 10:27:07, Info CSI 0000012c [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:27:07, Info CSI 0000012d [SR] Beginning Verify and Repair transaction
2013-07-28 10:27:11, Info CSI 0000012f [SR] Verify complete
2013-07-28 10:27:11, Info CSI 00000130 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:27:11, Info CSI 00000131 [SR] Beginning Verify and Repair transaction
2013-07-28 10:27:20, Info CSI 00000133 [SR] Verify complete
2013-07-28 10:27:20, Info CSI 00000134 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:27:20, Info CSI 00000135 [SR] Beginning Verify and Repair transaction
2013-07-28 10:27:27, Info CSI 00000137 [SR] Verify complete
2013-07-28 10:27:28, Info CSI 00000138 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:27:28, Info CSI 00000139 [SR] Beginning Verify and Repair transaction
2013-07-28 10:27:33, Info CSI 0000013b [SR] Verify complete
2013-07-28 10:27:33, Info CSI 0000013c [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:27:33, Info CSI 0000013d [SR] Beginning Verify and Repair transaction
2013-07-28 10:27:45, Info CSI 00000141 [SR] Verify complete
2013-07-28 10:27:45, Info CSI 00000142 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:27:45, Info CSI 00000143 [SR] Beginning Verify and Repair transaction
2013-07-28 10:27:56, Info CSI 00000159 [SR] Verify complete
2013-07-28 10:27:56, Info CSI 0000015a [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:27:56, Info CSI 0000015b [SR] Beginning Verify and Repair transaction
2013-07-28 10:28:04, Info CSI 0000015d [SR] Verify complete
2013-07-28 10:28:05, Info CSI 0000015e [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:28:05, Info CSI 0000015f [SR] Beginning Verify and Repair transaction
2013-07-28 10:28:26, Info CSI 00000161 [SR] Verify complete
2013-07-28 10:28:27, Info CSI 00000162 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:28:27, Info CSI 00000163 [SR] Beginning Verify and Repair transaction
2013-07-28 10:28:40, Info CSI 00000165 [SR] Verify complete
2013-07-28 10:28:41, Info CSI 00000166 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:28:41, Info CSI 00000167 [SR] Beginning Verify and Repair transaction
2013-07-28 10:28:52, Info CSI 0000016a [SR] Verify complete
2013-07-28 10:28:52, Info CSI 0000016b [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:28:52, Info CSI 0000016c [SR] Beginning Verify and Repair transaction
2013-07-28 10:29:03, Info CSI 0000016e [SR] Verify complete
2013-07-28 10:29:04, Info CSI 0000016f [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:29:04, Info CSI 00000170 [SR] Beginning Verify and Repair transaction
2013-07-28 10:29:16, Info CSI 00000172 [SR] Verify complete
2013-07-28 10:29:16, Info CSI 00000173 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:29:16, Info CSI 00000174 [SR] Beginning Verify and Repair transaction
2013-07-28 10:29:22, Info CSI 00000177 [SR] Verify complete
2013-07-28 10:29:23, Info CSI 00000178 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:29:23, Info CSI 00000179 [SR] Beginning Verify and Repair transaction
2013-07-28 10:29:31, Info CSI 0000017b [SR] Verify complete
2013-07-28 10:29:31, Info CSI 0000017c [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:29:31, Info CSI 0000017d [SR] Beginning Verify and Repair transaction
2013-07-28 10:29:39, Info CSI 0000017f [SR] Verify complete
2013-07-28 10:29:39, Info CSI 00000180 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:29:39, Info CSI 00000181 [SR] Beginning Verify and Repair transaction
2013-07-28 10:29:44, Info CSI 00000183 [SR] Verify complete
2013-07-28 10:29:44, Info CSI 00000184 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:29:44, Info CSI 00000185 [SR] Beginning Verify and Repair transaction
2013-07-28 10:29:53, Info CSI 00000189 [SR] Verify complete
2013-07-28 10:29:53, Info CSI 0000018a [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:29:53, Info CSI 0000018b [SR] Beginning Verify and Repair transaction
2013-07-28 10:30:00, Info CSI 0000018d [SR] Verify complete
2013-07-28 10:30:00, Info CSI 0000018e [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:30:00, Info CSI 0000018f [SR] Beginning Verify and Repair transaction
2013-07-28 10:30:26, Info CSI 00000191 [SR] Verify complete
2013-07-28 10:30:26, Info CSI 00000192 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:30:26, Info CSI 00000193 [SR] Beginning Verify and Repair transaction
2013-07-28 10:30:35, Info CSI 00000196 [SR] Verify complete
2013-07-28 10:30:35, Info CSI 00000197 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:30:35, Info CSI 00000198 [SR] Beginning Verify and Repair transaction
2013-07-28 10:30:41, Info CSI 0000019a [SR] Verify complete
2013-07-28 10:30:41, Info CSI 0000019b [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:30:41, Info CSI 0000019c [SR] Beginning Verify and Repair transaction
2013-07-28 10:30:46, Info CSI 0000019e [SR] Verify complete
2013-07-28 10:30:46, Info CSI 0000019f [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:30:46, Info CSI 000001a0 [SR] Beginning Verify and Repair transaction
2013-07-28 10:30:55, Info CSI 000001a3 [SR] Verify complete
2013-07-28 10:30:56, Info CSI 000001a4 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:30:56, Info CSI 000001a5 [SR] Beginning Verify and Repair transaction
2013-07-28 10:30:57, Info CSI 000001a7 [SR] Cannot repair member file [l:18{9}]"slmgr.vbs" of Microsoft-Windows-Security-SPP-Tools, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:31:10, Info CSI 000001a9 [SR] Cannot repair member file [l:18{9}]"slmgr.vbs" of Microsoft-Windows-Security-SPP-Tools, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:31:10, Info CSI 000001aa [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2013-07-28 10:31:10, Info CSI 000001ac [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"slmgr.vbs"; source file in store is also corrupted
2013-07-28 10:31:11, Info CSI 000001af [SR] Verify complete
2013-07-28 10:31:11, Info CSI 000001b0 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:31:11, Info CSI 000001b1 [SR] Beginning Verify and Repair transaction
2013-07-28 10:31:21, Info CSI 000001b3 [SR] Verify complete
2013-07-28 10:31:21, Info CSI 000001b4 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:31:21, Info CSI 000001b5 [SR] Beginning Verify and Repair transaction
2013-07-28 10:31:27, Info CSI 000001b7 [SR] Verify complete
2013-07-28 10:31:27, Info CSI 000001b8 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:31:27, Info CSI 000001b9 [SR] Beginning Verify and Repair transaction
2013-07-28 10:31:38, Info CSI 000001bb [SR] Verify complete
2013-07-28 10:31:39, Info CSI 000001bc [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:31:39, Info CSI 000001bd [SR] Beginning Verify and Repair transaction
2013-07-28 10:31:49, Info CSI 000001bf [SR] Verify complete
2013-07-28 10:31:49, Info CSI 000001c0 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:31:49, Info CSI 000001c1 [SR] Beginning Verify and Repair transaction
2013-07-28 10:31:55, Info CSI 000001c4 [SR] Verify complete
2013-07-28 10:31:55, Info CSI 000001c5 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:31:55, Info CSI 000001c6 [SR] Beginning Verify and Repair transaction
2013-07-28 10:32:05, Info CSI 000001c8 [SR] Verify complete
2013-07-28 10:32:05, Info CSI 000001c9 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:32:05, Info CSI 000001ca [SR] Beginning Verify and Repair transaction
2013-07-28 10:32:09, Info CSI 000001cc [SR] Cannot repair member file [l:32{16}]"themecpl.dll.mui" of Microsoft-Windows-themecpl.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:32:12, Info CSI 000001ce [SR] Cannot repair member file [l:32{16}]"themecpl.dll.mui" of Microsoft-Windows-themecpl.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:32:12, Info CSI 000001cf [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ko-KR~6.1.7601.17514.Windows Foundation Language Pack"
2013-07-28 10:32:12, Info CSI 000001d2 [SR] Could not reproject corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\ko-KR"\[l:32{16}]"themecpl.dll.mui"; source file in store is also corrupted
2013-07-28 10:32:12, Info CSI 000001d4 [SR] Verify complete
2013-07-28 10:32:13, Info CSI 000001d5 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:32:13, Info CSI 000001d6 [SR] Beginning Verify and Repair transaction
2013-07-28 10:32:20, Info CSI 000001d8 [SR] Verify complete
2013-07-28 10:32:20, Info CSI 000001d9 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:32:20, Info CSI 000001da [SR] Beginning Verify and Repair transaction
2013-07-28 10:32:27, Info CSI 000001dd [SR] Verify complete
2013-07-28 10:32:27, Info CSI 000001de [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:32:27, Info CSI 000001df [SR] Beginning Verify and Repair transaction
2013-07-28 10:32:36, Info CSI 000001e2 [SR] Verify complete
2013-07-28 10:32:36, Info CSI 000001e3 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:32:36, Info CSI 000001e4 [SR] Beginning Verify and Repair transaction
2013-07-28 10:32:43, Info CSI 000001e7 [SR] Verify complete
2013-07-28 10:32:44, Info CSI 000001e8 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:32:44, Info CSI 000001e9 [SR] Beginning Verify and Repair transaction
2013-07-28 10:32:50, Info CSI 000001ec [SR] Verify complete
2013-07-28 10:32:50, Info CSI 000001ed [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:32:50, Info CSI 000001ee [SR] Beginning Verify and Repair transaction
2013-07-28 10:32:56, Info CSI 000001f0 [SR] Verify complete
2013-07-28 10:32:56, Info CSI 000001f1 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:32:56, Info CSI 000001f2 [SR] Beginning Verify and Repair transaction
2013-07-28 10:32:58, Info CSI 000001f4 [SR] Cannot repair member file [l:20{10}]"winver.exe" of Microsoft-Windows-winver, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:33:05, Info CSI 000001f6 [SR] Cannot repair member file [l:20{10}]"winver.exe" of Microsoft-Windows-winver, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:33:05, Info CSI 000001f7 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2013-07-28 10:33:05, Info CSI 000001f9 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"winver.exe"; source file in store is also corrupted
2013-07-28 10:33:06, Info CSI 000001fb [SR] Verify complete
2013-07-28 10:33:07, Info CSI 000001fc [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:33:07, Info CSI 000001fd [SR] Beginning Verify and Repair transaction
2013-07-28 10:33:14, Info CSI 00000200 [SR] Verify complete
2013-07-28 10:33:14, Info CSI 00000201 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:33:14, Info CSI 00000202 [SR] Beginning Verify and Repair transaction
2013-07-28 10:33:21, Info CSI 00000204 [SR] Verify complete
2013-07-28 10:33:21, Info CSI 00000205 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:33:21, Info CSI 00000206 [SR] Beginning Verify and Repair transaction
2013-07-28 10:33:23, Info CSI 00000208 [SR] Verify complete
2013-07-28 10:33:23, Info CSI 00000209 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:33:23, Info CSI 0000020a [SR] Beginning Verify and Repair transaction
2013-07-28 10:33:30, Info CSI 0000020c [SR] Verify complete
2013-07-28 10:33:31, Info CSI 0000020d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:33:31, Info CSI 0000020e [SR] Beginning Verify and Repair transaction
2013-07-28 10:33:35, Info CSI 00000210 [SR] Verify complete
2013-07-28 10:33:35, Info CSI 00000211 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:33:35, Info CSI 00000212 [SR] Beginning Verify and Repair transaction
2013-07-28 10:33:42, Info CSI 00000214 [SR] Verify complete
2013-07-28 10:33:42, Info CSI 00000215 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:33:42, Info CSI 00000216 [SR] Beginning Verify and Repair transaction
2013-07-28 10:33:51, Info CSI 00000218 [SR] Verify complete
2013-07-28 10:33:51, Info CSI 00000219 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:33:51, Info CSI 0000021a [SR] Beginning Verify and Repair transaction
2013-07-28 10:33:55, Info CSI 0000021c [SR] Verify complete
2013-07-28 10:33:55, Info CSI 0000021d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:33:55, Info CSI 0000021e [SR] Beginning Verify and Repair transaction
2013-07-28 10:34:00, Info CSI 00000220 [SR] Verify complete
2013-07-28 10:34:00, Info CSI 00000221 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:34:00, Info CSI 00000222 [SR] Beginning Verify and Repair transaction
2013-07-28 10:34:08, Info CSI 00000224 [SR] Verify complete
2013-07-28 10:34:08, Info CSI 00000225 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:34:08, Info CSI 00000226 [SR] Beginning Verify and Repair transaction
2013-07-28 10:34:22, Info CSI 00000228 [SR] Verify complete
2013-07-28 10:34:22, Info CSI 00000229 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:34:22, Info CSI 0000022a [SR] Beginning Verify and Repair transaction
2013-07-28 10:34:36, Info CSI 0000022c [SR] Verify complete
2013-07-28 10:34:36, Info CSI 0000022d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:34:36, Info CSI 0000022e [SR] Beginning Verify and Repair transaction
2013-07-28 10:34:40, Info CSI 00000230 [SR] Verify complete
2013-07-28 10:34:41, Info CSI 00000231 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:34:41, Info CSI 00000232 [SR] Beginning Verify and Repair transaction
2013-07-28 10:34:47, Info CSI 00000234 [SR] Verify complete
2013-07-28 10:34:47, Info CSI 00000235 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:34:47, Info CSI 00000236 [SR] Beginning Verify and Repair transaction
2013-07-28 10:34:51, Info CSI 00000238 [SR] Verify complete
2013-07-28 10:34:51, Info CSI 00000239 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:34:51, Info CSI 0000023a [SR] Beginning Verify and Repair transaction
2013-07-28 10:34:54, Info CSI 0000023c [SR] Verify complete
2013-07-28 10:34:55, Info CSI 0000023d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:34:55, Info CSI 0000023e [SR] Beginning Verify and Repair transaction
2013-07-28 10:34:59, Info CSI 00000240 [SR] Verify complete
2013-07-28 10:34:59, Info CSI 00000241 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:34:59, Info CSI 00000242 [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:03, Info CSI 00000244 [SR] Verify complete
2013-07-28 10:35:03, Info CSI 00000245 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:03, Info CSI 00000246 [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:08, Info CSI 00000248 [SR] Verify complete
2013-07-28 10:35:08, Info CSI 00000249 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:08, Info CSI 0000024a [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:13, Info CSI 0000024c [SR] Verify complete
2013-07-28 10:35:14, Info CSI 0000024d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:14, Info CSI 0000024e [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:15, Info CSI 00000250 [SR] Verify complete
2013-07-28 10:35:16, Info CSI 00000251 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:16, Info CSI 00000252 [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:18, Info CSI 00000254 [SR] Verify complete
2013-07-28 10:35:18, Info CSI 00000255 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:18, Info CSI 00000256 [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:26, Info CSI 00000261 [SR] Verify complete
2013-07-28 10:35:26, Info CSI 00000262 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:26, Info CSI 00000263 [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:31, Info CSI 00000265 [SR] Verify complete
2013-07-28 10:35:31, Info CSI 00000266 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:31, Info CSI 00000267 [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:37, Info CSI 00000269 [SR] Verify complete
2013-07-28 10:35:37, Info CSI 0000026a [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:37, Info CSI 0000026b [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:41, Info CSI 0000026d [SR] Verify complete
2013-07-28 10:35:42, Info CSI 0000026e [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:42, Info CSI 0000026f [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:48, Info CSI 00000271 [SR] Verify complete
2013-07-28 10:35:48, Info CSI 00000272 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:48, Info CSI 00000273 [SR] Beginning Verify and Repair transaction
2013-07-28 10:35:54, Info CSI 00000275 [SR] Verify complete
2013-07-28 10:35:54, Info CSI 00000276 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:35:54, Info CSI 00000277 [SR] Beginning Verify and Repair transaction
2013-07-28 10:36:03, Info CSI 00000279 [SR] Verify complete
2013-07-28 10:36:03, Info CSI 0000027a [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:36:03, Info CSI 0000027b [SR] Beginning Verify and Repair transaction
2013-07-28 10:36:12, Info CSI 0000027e [SR] Verify complete
2013-07-28 10:36:12, Info CSI 0000027f [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:36:12, Info CSI 00000280 [SR] Beginning Verify and Repair transaction
2013-07-28 10:36:15, Info CSI 00000282 [SR] Verify complete
2013-07-28 10:36:15, Info CSI 00000283 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:36:15, Info CSI 00000284 [SR] Beginning Verify and Repair transaction
2013-07-28 10:36:19, Info CSI 00000286 [SR] Verify complete
2013-07-28 10:36:19, Info CSI 00000287 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:36:19, Info CSI 00000288 [SR] Beginning Verify and Repair transaction
2013-07-28 10:36:34, Info CSI 0000028d [SR] Verify complete
2013-07-28 10:36:35, Info CSI 0000028e [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:36:35, Info CSI 0000028f [SR] Beginning Verify and Repair transaction
2013-07-28 10:36:47, Info CSI 00000291 [SR] Verify complete
2013-07-28 10:36:48, Info CSI 00000292 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:36:48, Info CSI 00000293 [SR] Beginning Verify and Repair transaction
2013-07-28 10:36:55, Info CSI 00000298 [SR] Verify complete
2013-07-28 10:36:55, Info CSI 00000299 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:36:55, Info CSI 0000029a [SR] Beginning Verify and Repair transaction
2013-07-28 10:37:04, Info CSI 0000029d [SR] Verify complete
2013-07-28 10:37:04, Info CSI 0000029e [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:37:04, Info CSI 0000029f [SR] Beginning Verify and Repair transaction
2013-07-28 10:37:17, Info CSI 000002ab [SR] Verify complete
2013-07-28 10:37:18, Info CSI 000002ac [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:37:18, Info CSI 000002ad [SR] Beginning Verify and Repair transaction
2013-07-28 10:37:28, Info CSI 000002b3 [SR] Verify complete
2013-07-28 10:37:28, Info CSI 000002b4 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:37:28, Info CSI 000002b5 [SR] Beginning Verify and Repair transaction
2013-07-28 10:37:36, Info CSI 000002b7 [SR] Verify complete
2013-07-28 10:37:36, Info CSI 000002b8 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:37:36, Info CSI 000002b9 [SR] Beginning Verify and Repair transaction
2013-07-28 10:37:43, Info CSI 000002bd [SR] Verify complete
2013-07-28 10:37:43, Info CSI 000002be [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:37:43, Info CSI 000002bf [SR] Beginning Verify and Repair transaction
2013-07-28 10:37:50, Info CSI 000002c1 [SR] Verify complete
2013-07-28 10:37:50, Info CSI 000002c2 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:37:50, Info CSI 000002c3 [SR] Beginning Verify and Repair transaction
2013-07-28 10:37:55, Info CSI 000002c5 [SR] Verify complete
2013-07-28 10:37:56, Info CSI 000002c6 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:37:56, Info CSI 000002c7 [SR] Beginning Verify and Repair transaction
2013-07-28 10:38:04, Info CSI 000002ec [SR] Verify complete
2013-07-28 10:38:05, Info CSI 000002ed [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:38:05, Info CSI 000002ee [SR] Beginning Verify and Repair transaction
2013-07-28 10:38:11, Info CSI 000002f0 [SR] Verify complete
2013-07-28 10:38:11, Info CSI 000002f1 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:38:11, Info CSI 000002f2 [SR] Beginning Verify and Repair transaction
2013-07-28 10:38:15, Info CSI 000002f4 [SR] Verify complete
2013-07-28 10:38:16, Info CSI 000002f5 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:38:16, Info CSI 000002f6 [SR] Beginning Verify and Repair transaction
2013-07-28 10:38:22, Info CSI 000002f8 [SR] Verify complete
2013-07-28 10:38:22, Info CSI 000002f9 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:38:22, Info CSI 000002fa [SR] Beginning Verify and Repair transaction
2013-07-28 10:38:23, Info CSI 000002fc [SR] Cannot repair member file [l:30{15}]"Display.dll.mui" of Microsoft-Windows-Display.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:38:26, Info CSI 000002fe [SR] Cannot repair member file [l:30{15}]"Display.dll.mui" of Microsoft-Windows-Display.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:38:26, Info CSI 000002ff [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ko-KR~6.1.7601.17514.Windows Foundation Language Pack"
2013-07-28 10:38:26, Info CSI 00000302 [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\ko-KR"\[l:30{15}]"Display.dll.mui"; source file in store is also corrupted
2013-07-28 10:38:26, Info CSI 00000304 [SR] Verify complete
2013-07-28 10:38:26, Info CSI 00000305 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:38:26, Info CSI 00000306 [SR] Beginning Verify and Repair transaction
2013-07-28 10:38:32, Info CSI 00000314 [SR] Verify complete
2013-07-28 10:38:32, Info CSI 00000315 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:38:32, Info CSI 00000316 [SR] Beginning Verify and Repair transaction
2013-07-28 10:38:39, Info CSI 00000318 [SR] Verify complete
2013-07-28 10:38:39, Info CSI 00000319 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:38:39, Info CSI 0000031a [SR] Beginning Verify and Repair transaction
2013-07-28 10:38:45, Info CSI 0000031c [SR] Verify complete
2013-07-28 10:38:45, Info CSI 0000031d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:38:45, Info CSI 0000031e [SR] Beginning Verify and Repair transaction
2013-07-28 10:38:54, Info CSI 0000032c [SR] Verify complete
2013-07-28 10:38:54, Info CSI 0000032d [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:38:54, Info CSI 0000032e [SR] Beginning Verify and Repair transaction
2013-07-28 10:38:57, Info CSI 00000330 [SR] Verify complete
2013-07-28 10:38:58, Info CSI 00000331 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:38:58, Info CSI 00000332 [SR] Beginning Verify and Repair transaction
2013-07-28 10:39:03, Info CSI 00000334 [SR] Verify complete
2013-07-28 10:39:03, Info CSI 00000335 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:39:03, Info CSI 00000336 [SR] Beginning Verify and Repair transaction
2013-07-28 10:39:10, Info CSI 00000339 [SR] Verify complete
2013-07-28 10:39:10, Info CSI 0000033a [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:39:10, Info CSI 0000033b [SR] Beginning Verify and Repair transaction
2013-07-28 10:39:14, Info CSI 0000033d [SR] Verify complete
2013-07-28 10:39:14, Info CSI 0000033e [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:39:14, Info CSI 0000033f [SR] Beginning Verify and Repair transaction
2013-07-28 10:39:17, Info CSI 00000341 [SR] Verify complete
2013-07-28 10:39:18, Info CSI 00000342 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:39:18, Info CSI 00000343 [SR] Beginning Verify and Repair transaction
2013-07-28 10:39:25, Info CSI 00000345 [SR] Verify complete
2013-07-28 10:39:25, Info CSI 00000346 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:39:25, Info CSI 00000347 [SR] Beginning Verify and Repair transaction
2013-07-28 10:39:31, Info CSI 00000349 [SR] Verify complete
2013-07-28 10:39:32, Info CSI 0000034a [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:39:32, Info CSI 0000034b [SR] Beginning Verify and Repair transaction
2013-07-28 10:39:37, Info CSI 0000034d [SR] Verify complete
2013-07-28 10:39:37, Info CSI 0000034e [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:39:37, Info CSI 0000034f [SR] Beginning Verify and Repair transaction
2013-07-28 10:39:38, Info CSI 00000351 [SR] Cannot repair member file [l:22{11}]"migcore.dll" of Microsoft-Windows-MigrationEngine, Version = 6.1.7601.17514, 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
2013-07-28 10:39:42, Info CSI 00000355 [SR] Cannot repair member file [l:22{11}]"migcore.dll" of Microsoft-Windows-MigrationEngine, Version = 6.1.7601.17514, 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
2013-07-28 10:39:42, Info CSI 00000356 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2013-07-28 10:39:42, Info CSI 00000359 [SR] Could not reproject corrupted file [ml:62{31},l:60{30}]"\??\C:\Windows\SysWOW64\migwiz"\[l:22{11}]"migcore.dll"; source file in store is also corrupted
2013-07-28 10:39:47, Info CSI 00000371 [SR] Verify complete
2013-07-28 10:39:47, Info CSI 00000372 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:39:47, Info CSI 00000373 [SR] Beginning Verify and Repair transaction
2013-07-28 10:39:53, Info CSI 00000375 [SR] Verify complete
2013-07-28 10:39:53, Info CSI 00000376 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:39:53, Info CSI 00000377 [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:10, Info CSI 00000379 [SR] Verify complete
2013-07-28 10:40:10, Info CSI 0000037a [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:10, Info CSI 0000037b [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:14, Info CSI 0000037d [SR] Verify complete
2013-07-28 10:40:15, Info CSI 0000037e [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:15, Info CSI 0000037f [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:19, Info CSI 00000381 [SR] Verify complete
2013-07-28 10:40:20, Info CSI 00000382 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:20, Info CSI 00000383 [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:23, Info CSI 00000387 [SR] Verify complete
2013-07-28 10:40:24, Info CSI 00000388 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:24, Info CSI 00000389 [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:27, Info CSI 0000038b [SR] Verify complete
2013-07-28 10:40:28, Info CSI 0000038c [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:28, Info CSI 0000038d [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:32, Info CSI 0000038f [SR] Verify complete
2013-07-28 10:40:32, Info CSI 00000390 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:32, Info CSI 00000391 [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:37, Info CSI 00000393 [SR] Verify complete
2013-07-28 10:40:37, Info CSI 00000394 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:37, Info CSI 00000395 [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:44, Info CSI 00000397 [SR] Verify complete
2013-07-28 10:40:44, Info CSI 00000398 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:44, Info CSI 00000399 [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:49, Info CSI 0000039b [SR] Verify complete
2013-07-28 10:40:49, Info CSI 0000039c [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:49, Info CSI 0000039d [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:54, Info CSI 000003a0 [SR] Verify complete
2013-07-28 10:40:55, Info CSI 000003a1 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:55, Info CSI 000003a2 [SR] Beginning Verify and Repair transaction
2013-07-28 10:40:55, Info CSI 000003a4 [SR] Cannot repair member file [l:32{16}]"themecpl.dll.mui" of Microsoft-Windows-themecpl.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:40:59, Info CSI 000003a6 [SR] Cannot repair member file [l:32{16}]"themecpl.dll.mui" of Microsoft-Windows-themecpl.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:40:59, Info CSI 000003a7 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ko-KR~6.1.7601.17514.Windows Foundation Language Pack"
2013-07-28 10:40:59, Info CSI 000003aa [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\ko-KR"\[l:32{16}]"themecpl.dll.mui"; source file in store is also corrupted
2013-07-28 10:40:59, Info CSI 000003ac [SR] Verify complete
2013-07-28 10:40:59, Info CSI 000003ad [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:40:59, Info CSI 000003ae [SR] Beginning Verify and Repair transaction
2013-07-28 10:41:04, Info CSI 000003b1 [SR] Verify complete
2013-07-28 10:41:04, Info CSI 000003b2 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:41:04, Info CSI 000003b3 [SR] Beginning Verify and Repair transaction
2013-07-28 10:41:11, Info CSI 000003b5 [SR] Verify complete
2013-07-28 10:41:11, Info CSI 000003b6 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:41:11, Info CSI 000003b7 [SR] Beginning Verify and Repair transaction
2013-07-28 10:41:16, Info CSI 000003b9 [SR] Verify complete
2013-07-28 10:41:16, Info CSI 000003ba [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:41:16, Info CSI 000003bb [SR] Beginning Verify and Repair transaction
2013-07-28 10:41:23, Info CSI 000003be [SR] Verify complete
2013-07-28 10:41:23, Info CSI 000003bf [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:41:23, Info CSI 000003c0 [SR] Beginning Verify and Repair transaction
2013-07-28 10:41:28, Info CSI 000003c2 [SR] Verify complete
2013-07-28 10:41:28, Info CSI 000003c3 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:41:28, Info CSI 000003c4 [SR] Beginning Verify and Repair transaction
2013-07-28 10:41:34, Info CSI 000003c6 [SR] Verify complete
2013-07-28 10:41:34, Info CSI 000003c7 [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:41:34, Info CSI 000003c8 [SR] Beginning Verify and Repair transaction
2013-07-28 10:41:39, Info CSI 000003ca [SR] Verify complete
2013-07-28 10:41:39, Info CSI 000003cb [SR] Verifying 100 (0x0000000000000064) components
2013-07-28 10:41:39, Info CSI 000003cc [SR] Beginning Verify and Repair transaction
2013-07-28 10:41:46, Info CSI 000003ce [SR] Verify complete
2013-07-28 10:41:46, Info CSI 000003cf [SR] Verifying 21 (0x0000000000000015) components
2013-07-28 10:41:46, Info CSI 000003d0 [SR] Beginning Verify and Repair transaction
2013-07-28 10:41:47, Info CSI 000003d2 [SR] Verify complete
2013-07-28 10:41:47, Info CSI 000003d3 [SR] Repairing 7 components
2013-07-28 10:41:47, Info CSI 000003d4 [SR] Beginning Verify and Repair transaction
2013-07-28 10:41:47, Info CSI 000003d6 [SR] Cannot repair member file [l:30{15}]"Display.dll.mui" of Microsoft-Windows-Display.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:49, Info CSI 000003d8 [SR] Cannot repair member file [l:18{9}]"slmgr.vbs" of Microsoft-Windows-Security-SPP-Tools, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:49, Info CSI 000003da [SR] Cannot repair member file [l:32{16}]"themecpl.dll.mui" of Microsoft-Windows-themecpl.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:49, Info CSI 000003dc [SR] Cannot repair member file [l:20{10}]"winver.exe" of Microsoft-Windows-winver, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:49, Info CSI 000003de [SR] Cannot repair member file [l:30{15}]"Display.dll.mui" of Microsoft-Windows-Display.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:50, Info CSI 000003e0 [SR] Cannot repair member file [l:22{11}]"migcore.dll" of Microsoft-Windows-MigrationEngine, Version = 6.1.7601.17514, 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
2013-07-28 10:41:50, Info CSI 000003e2 [SR] Cannot repair member file [l:32{16}]"themecpl.dll.mui" of Microsoft-Windows-themecpl.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:50, Info CSI 000003e4 [SR] Cannot repair member file [l:30{15}]"Display.dll.mui" of Microsoft-Windows-Display.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:50, Info CSI 000003e5 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ko-KR~6.1.7601.17514.Windows Foundation Language Pack"
2013-07-28 10:41:50, Info CSI 000003e8 [SR] Could not reproject corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\ko-KR"\[l:30{15}]"Display.dll.mui"; source file in store is also corrupted
2013-07-28 10:41:50, Info CSI 000003ea [SR] Cannot repair member file [l:32{16}]"themecpl.dll.mui" of Microsoft-Windows-themecpl.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:50, Info CSI 000003eb [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ko-KR~6.1.7601.17514.Windows Foundation Language Pack"
2013-07-28 10:41:50, Info CSI 000003ee [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\ko-KR"\[l:32{16}]"themecpl.dll.mui"; source file in store is also corrupted
2013-07-28 10:41:50, Info CSI 000003f0 [SR] Cannot repair member file [l:18{9}]"slmgr.vbs" of Microsoft-Windows-Security-SPP-Tools, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:50, Info CSI 000003f1 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2013-07-28 10:41:50, Info CSI 000003f3 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"slmgr.vbs"; source file in store is also corrupted
2013-07-28 10:41:50, Info CSI 000003f5 [SR] Cannot repair member file [l:32{16}]"themecpl.dll.mui" of Microsoft-Windows-themecpl.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:50, Info CSI 000003f6 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ko-KR~6.1.7601.17514.Windows Foundation Language Pack"
2013-07-28 10:41:50, Info CSI 000003f9 [SR] Could not reproject corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\ko-KR"\[l:32{16}]"themecpl.dll.mui"; source file in store is also corrupted
2013-07-28 10:41:50, Info CSI 000003fb [SR] Cannot repair member file [l:20{10}]"winver.exe" of Microsoft-Windows-winver, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:50, Info CSI 000003fc [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2013-07-28 10:41:50, Info CSI 000003fe [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"winver.exe"; source file in store is also corrupted
2013-07-28 10:41:50, Info CSI 00000400 [SR] Cannot repair member file [l:22{11}]"migcore.dll" of Microsoft-Windows-MigrationEngine, Version = 6.1.7601.17514, 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
2013-07-28 10:41:50, Info CSI 00000401 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2013-07-28 10:41:50, Info CSI 00000404 [SR] Could not reproject corrupted file [ml:62{31},l:60{30}]"\??\C:\Windows\SysWOW64\migwiz"\[l:22{11}]"migcore.dll"; source file in store is also corrupted
2013-07-28 10:41:50, Info CSI 00000406 [SR] Cannot repair member file [l:30{15}]"Display.dll.mui" of Microsoft-Windows-Display.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"ko-KR", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-07-28 10:41:50, Info CSI 00000407 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~ko-KR~6.1.7601.17514.Windows Foundation Language Pack"
2013-07-28 10:41:50, Info CSI 0000040a [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\ko-KR"\[l:30{15}]"Display.dll.mui"; source file in store is also corrupted
2013-07-28 10:41:50, Info CSI 0000040c [SR] Repair complete
2013-07-28 10:41:50, Info CSI 0000040d [SR] Committing transaction
2013-07-28 10:41:50, Info CSI 00000411 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
  • 0

#19
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,010 posts
  • MVP
It appears that the errors are in the Windows Foundation Language Pack so I don't think they are anything to worry about. I get the feeling that the Windows Foundation Language Pack must have a problem on 64 bit systems as this is the second one I've seen that had these errors. There is one error that is not part of the Language Pack: slmgr.vbs This is something called Software License Manager. Don't think it's important for non-enterprise PCs. I don't have a 64 bit Win 7 but I know a couple of people who do and I will ask them if their sfc has the same problems. I'll get back to you on that. My 32 bit win 7 goes through sfc without an error.

Can you run the Event Viewer Tool and post the logs. Let's see if anything is broken.
  • 0

#20
radiuss

radiuss

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

It appears that the errors are in the Windows Foundation Language Pack so I don't think they are anything to worry about. I get the feeling that the Windows Foundation Language Pack must have a problem on 64 bit systems as this is the second one I've seen that had these errors. There is one error that is not part of the Language Pack: slmgr.vbs This is something called Software License Manager. Don't think it's important for non-enterprise PCs. I don't have a 64 bit Win 7 but I know a couple of people who do and I will ask them if their sfc has the same problems. I'll get back to you on that. My 32 bit win 7 goes through sfc without an error.

Can you run the Event Viewer Tool and post the logs. Let's see if anything is broken.



Here ya go:

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 28/07/2013 10:04:17 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 28/07/2013 7:23:51 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/07/2013 5:01:55 AM
Type: Error Category: 0
Event: 34 Source: Microsoft-Windows-Time-Service
The time service has detected that the system time needs to be changed by -57558 seconds. The time service will not change the system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->65.55.56.206:123) is working properly.

Log: 'System' Date/Time: 28/07/2013 8:24:32 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The WebCakeUpdater service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.

Log: 'System' Date/Time: 28/07/2013 8:07:12 AM
Type: Error Category: 0
Event: 34 Source: Microsoft-Windows-Time-Service
The time service has detected that the system time needs to be changed by -57558 seconds. The time service will not change the system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->65.55.56.206:123) is working properly.

Log: 'System' Date/Time: 28/07/2013 7:28:05 AM
Type: Error Category: 0
Event: 34 Source: Microsoft-Windows-Time-Service
The time service has detected that the system time needs to be changed by -57558 seconds. The time service will not change the system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->64.4.10.33:123) is working properly.

Log: 'System' Date/Time: 28/07/2013 7:25:18 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® PROSet/Wireless Event Log service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 28/07/2013 7:25:18 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Intel® PROSet/Wireless Event Log service to connect.

Log: 'System' Date/Time: 28/07/2013 7:24:41 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 12:22:02 AM on ?7/?28/?2013 was unexpected.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/07/2013 4:54:56 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 29/07/2013 4:54:56 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll

Log: 'System' Date/Time: 29/07/2013 4:49:46 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 29/07/2013 4:49:44 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll

Log: 'System' Date/Time: 29/07/2013 4:05:06 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 10:23:44 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name dns.msftncsi.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 7:27:52 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name inferno.demonoid.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 7:11:08 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name inferno.demonoid.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 6:42:22 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.rafaelangulofineart.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 6:37:14 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.rafaelangulofineart.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 3:52:40 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name inferno.demonoid.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 3:31:41 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name inferno.demonoid.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 3:31:26 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name inferno.demonoid.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 3:31:11 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name inferno.demonoid.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 3:30:15 PM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 9:11:36 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name inferno.demonoid.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 9:02:04 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.jameswolcott.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/07/2013 8:40:46 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 28/07/2013 8:40:43 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll

Log: 'System' Date/Time: 28/07/2013 8:28:16 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name inferno.demonoid.com timed out after none of the configured DNS servers responded.
  • 0

#21
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,010 posts
  • MVP

Log: 'System' Date/Time: 28/07/2013 7:28:05 AM
Type: Error Category: 0
Event: 34 Source: Microsoft-Windows-Time-Service
The time service has detected that the system time needs to be changed by -57558 seconds. The time service will not change the system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->64.4.10.33:123) is working properly.


Right click on the time in the bottom right and Adjust Date/Time. Click on Change Time Zone. Verify that you have the correct time Zone and that if Daylight Savings Time is used where you are that the box for it is checked. OK. Click on Change Date and Time. Make sure the date and year are correct then adjust the time to the current time. Click on Internet Time. Does it say it successfully synced? If not you can try the Change Settings button and Update Now but it's not working on mine right now. What does seem to work is to stop and restart the time service. In the Search box type services.msc and when it finds it, right click on the found services.msc and Run AS Admin. OK. Find Windows Time and right click on it and select Properties. Stop the Service. After it stops, START the service. Now go back into Adjust Date/Time, Internet Time and it should have Synced. Did it?


Log: 'System' Date/Time: 28/07/2013 7:25:18 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® PROSet/Wireless Event Log service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.


This is not a service that you need so let's turn it off:

In the Search box type services.msc and when it finds it, right click on the found services.msc and Run AS Admin. OK. Find Intel® PROSet/Wireless Event Log and right click on it and select Properties. Change the Startup Type: to Disabled and then OK.

Log: 'System' Date/Time: 28/07/2013 8:24:32 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The WebCakeUpdater service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.



Also not needed. Don't even know what it does. Sounds like adware. I would turn it off the same way as the previous service.

Now let's clear the alarms and see if we have fixed those 3 errors:


Right click on (My) Computer and select Manage (Continue) Then click on the arrow in front of Event Viewer. Next Click on the arrow in front of Windows Logs Right click on System and Clear Log, Clear. Repeat for Application.

Reboot.




2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:

* System
4. Under 'Select type to list', select:
* Error
* Warning


Then use the 'Number of events' as follows:


1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.


Please post the Output log in your next reply then repeat but select Application.

Ron
  • 0

#22
radiuss

radiuss

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

Log: 'System' Date/Time: 28/07/2013 7:28:05 AM
Type: Error Category: 0
Event: 34 Source: Microsoft-Windows-Time-Service
The time service has detected that the system time needs to be changed by -57558 seconds. The time service will not change the system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->64.4.10.33:123) is working properly.


Right click on the time in the bottom right and Adjust Date/Time. Click on Change Time Zone. Verify that you have the correct time Zone and that if Daylight Savings Time is used where you are that the box for it is checked. OK. Click on Change Date and Time. Make sure the date and year are correct then adjust the time to the current time. Click on Internet Time. Does it say it successfully synced? If not you can try the Change Settings button and Update Now but it's not working on mine right now. What does seem to work is to stop and restart the time service. In the Search box type services.msc and when it finds it, right click on the found services.msc and Run AS Admin. OK. Find Windows Time and right click on it and select Properties. Stop the Service. After it stops, START the service. Now go back into Adjust Date/Time, Internet Time and it should have Synced. Did it?


Log: 'System' Date/Time: 28/07/2013 7:25:18 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® PROSet/Wireless Event Log service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.


This is not a service that you need so let's turn it off:

In the Search box type services.msc and when it finds it, right click on the found services.msc and Run AS Admin. OK. Find Intel® PROSet/Wireless Event Log and right click on it and select Properties. Change the Startup Type: to Disabled and then OK.

Log: 'System' Date/Time: 28/07/2013 8:24:32 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The WebCakeUpdater service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.



Also not needed. Don't even know what it does. Sounds like adware. I would turn it off the same way as the previous service.

Now let's clear the alarms and see if we have fixed those 3 errors:


Right click on (My) Computer and select Manage (Continue) Then click on the arrow in front of Event Viewer. Next Click on the arrow in front of Windows Logs Right click on System and Clear Log, Clear. Repeat for Application.

Reboot.




2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:

* System
4. Under 'Select type to list', select:
* Error
* Warning


Then use the 'Number of events' as follows:


1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.


Please post the Output log in your next reply then repeat but select Application.

Ron

Thanks Ron, I will got on all of this in the morning (I live in Korea now and it's bed time).
  • 0

#23
radiuss

radiuss

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

Log: 'System' Date/Time: 28/07/2013 7:28:05 AM
Type: Error Category: 0
Event: 34 Source: Microsoft-Windows-Time-Service
The time service has detected that the system time needs to be changed by -57558 seconds. The time service will not change the system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->64.4.10.33:123) is working properly.


Right click on the time in the bottom right and Adjust Date/Time. Click on Change Time Zone. Verify that you have the correct time Zone and that if Daylight Savings Time is used where you are that the box for it is checked. OK. Click on Change Date and Time. Make sure the date and year are correct then adjust the time to the current time. Click on Internet Time. Does it say it successfully synced? If not you can try the Change Settings button and Update Now but it's not working on mine right now. What does seem to work is to stop and restart the time service. In the Search box type services.msc and when it finds it, right click on the found services.msc and Run AS Admin. OK. Find Windows Time and right click on it and select Properties. Stop the Service. After it stops, START the service. Now go back into Adjust Date/Time, Internet Time and it should have Synced. Did it?


Log: 'System' Date/Time: 28/07/2013 7:25:18 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® PROSet/Wireless Event Log service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.


This is not a service that you need so let's turn it off:

In the Search box type services.msc and when it finds it, right click on the found services.msc and Run AS Admin. OK. Find Intel® PROSet/Wireless Event Log and right click on it and select Properties. Change the Startup Type: to Disabled and then OK.

Log: 'System' Date/Time: 28/07/2013 8:24:32 AM
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The WebCakeUpdater service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.



Also not needed. Don't even know what it does. Sounds like adware. I would turn it off the same way as the previous service.

Now let's clear the alarms and see if we have fixed those 3 errors:


Right click on (My) Computer and select Manage (Continue) Then click on the arrow in front of Event Viewer. Next Click on the arrow in front of Windows Logs Right click on System and Clear Log, Clear. Repeat for Application.

Reboot.




2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:

* System
4. Under 'Select type to list', select:
* Error
* Warning


Then use the 'Number of events' as follows:


1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.


Please post the Output log in your next reply then repeat but select Application.

Ron


Ok, my internet time was wrong--it was set to US/Canada and I am in Korea. So I successfully synced it to Korean time. Check.

Next, I disabled the startup to disabled in the Intel® PROSet/Wireless Event Log. Check.

Now, for the third step, I can not get into "Manage" in "my Computer." When I click "Manage" I get an error (This file does have a program associated with it for performing this action. Please install a program, if one is already installed, create an association in the Default Programs Control panel."

So I am stuck there. Any way around this?

Thanks Ron, you are awesome for stepping me through all of this. All of your instructions are precise and easy to follow. You should be a teacher!

Daniel
  • 0

#24
radiuss

radiuss

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts
ah never mind I fixed the "manage" failure, let me work on what you suggested before...
  • 0

#25
radiuss

radiuss

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts
Here is the updated VEW.exe log, Ron:

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 29/07/2013 9:42:31 AM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/07/2013 12:40:38 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® PROSet/Wireless Registry Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 29/07/2013 12:40:38 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Intel® PROSet/Wireless Registry Service service to connect.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/07/2013 12:38:55 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 29/07/2013 12:38:55 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll
  • 0

Advertisements


#26
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,010 posts
  • MVP

Log: 'System' Date/Time: 29/07/2013 12:40:38 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® PROSet/Wireless Registry Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 29/07/2013 12:40:38 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Intel® PROSet/Wireless Registry Service service to connect.


I think this is something that is useful in an Enterprise environment but not needed on a home PC so I would go in to services and turn it off too. If it turns out you need it then I think you need to download the latest version of Intel® PROSet, uninstall the old and reinstall the new.

Otherwise it looks good. How is it running now?
  • 0

#27
radiuss

radiuss

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts

Log: 'System' Date/Time: 29/07/2013 12:40:38 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® PROSet/Wireless Registry Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 29/07/2013 12:40:38 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Intel® PROSet/Wireless Registry Service service to connect.


I think this is something that is useful in an Enterprise environment but not needed on a home PC so I would go in to services and turn it off too. If it turns out you need it then I think you need to download the latest version of Intel® PROSet, uninstall the old and reinstall the new.

Otherwise it looks good. How is it running now?


Hey Ron,
I disabled the Intel® PROSet/Wireless Registry Service and ran the VEW.exe again and this is what came up:

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 29/07/2013 7:39:40 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/07/2013 10:34:28 AM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Intel® PROSet/Wireless Zero Configuration Service service terminated with the following error: %%-2147196306

Log: 'System' Date/Time: 29/07/2013 12:40:38 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® PROSet/Wireless Registry Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 29/07/2013 12:40:38 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Intel® PROSet/Wireless Registry Service service to connect.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/07/2013 10:32:44 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 29/07/2013 10:32:43 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll

Log: 'System' Date/Time: 29/07/2013 2:30:13 AM
Type: Warning Category: 0
Event: 2 Source: HidBth
Bluetooth HID device (00:1d:d8:3a:8b:d2) either went out of range or became unresponsive.

Log: 'System' Date/Time: 29/07/2013 2:12:40 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name stats.big-boards.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 29/07/2013 1:56:55 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 29/07/2013 12:38:55 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 29/07/2013 12:38:55 AM
Type: Warning Category: 0
Event: 10002 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has stopped. Module Path: C:\Windows\System32\bcmihvsrv64.dll
  • 0

#28
radiuss

radiuss

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts
and the sfc /scannow still shows "corrupted files that cannot be fixed." I am willing to just let it go, Ron, I don't think there is any legitimate threat to my system. What do you think?
  • 0

#29
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,010 posts
  • MVP
No threat that I see. Looks like ProSet is not going to be happy unless you reinstall it and I don't have a 64-bit system so I can't get the files for you that SFC is complaining about but if it is working OK then we can stop.

OTL has a cleanup tab but DO NOT USE IT!. There are reports that it leaves the PC unbootable. Instead just delete OTL.exe and the folder c:\_OTL.

To hide hidden files again:

Vista or Win7

# Open the Control Panel menu and click Folder Options.
# After the new window appears select the View tab.
# Remove the check in the checkbox labeled Display the contents of system folders.
# Under the Hidden files and folders section select the radio button labeled Do not Show hidden files and folders.
# Check the checkbox labeled Hide protected operating system files.
# Press the Apply button and then the OK button and exit My Computer.

Also make sure you have the latest versions of any adobe.com products you use like Shockwave, Flash or Acrobat.

Whether you use adobe reader, acrobat or fox-it to read pdf files you need to disable Javascript in the program. There is an exploit out there now that can use it to get on your PC. For Adobe Reader: Start, All Programs, Adobe Reader, Edit, Preferences, Click on Javascript in the left column and uncheck Enable Acrobat Javascript. OK Close program. It's the same for Foxit reader except you uncheck Enable Javascript Actions.

To help keep your programs up-to-date you should download and run the UpdateChecker:
http://www.filehippo.../updatechecker/
(You don't need to download Betas and if there is a program you don't use you can just uninstall it rather than update it. Exception is MSN messenger which appears to be part of Windows.)
If you get a blocked program notice after installing updatechecker then change it to not run at start then manually run it once a week.
Seems to work best if Firefox is the default browser. You can also try Secunia PSI http://secunia.com/v...l/download_psi/ Same kind of info. You don't need both.
If you use Firefox then get the AdBlock Plus Add-on. WOT (Web of Trust) is another you might want to try.
The equivalent to AdBlock Plus for IE is called Simple Adblock and you should install it too: http://simple-adblock.com/
The free version only blocks 200 ads a day so another reason to use Firefox or Chrome.

If Firefox is slow loading make sure it only has the current Java add-on. Then download and run Speedy Fox.
http://www.crystalidea.com/speedyfox . You can run it any time that Firefox seems slow.

Be warned: If you use Limewire, utorrent or any of the other P2P programs you will almost certain be coming back to the Malware Removal forum. If you must use P2P then submit any files you get to http://virustotal.com before you open them.


If you have a router, log on to it today and change the default password! If using a Wireless router you really should be using encryption on the link. Use the strongest (newest) encryption method that your router and PC wireless adapter support especially if you own a business. See http://www.king5.com...-120637284.html and http://www.seattlepi...ted-1344185.php for why encryption is important. If you don't know how, visit the router maker's website. They all have detailed step by step instructions or a wizard you can download.

Special note on Java. Old Java versions should be removed after first clearing the Java Cache by following the instructions in:
http://www.java.com/...lugin_cache.xml
Then remove the old versions by going to Control Panel, Programs and Features and Uninstall all Java programs which are not Java Version 7 update 9 or better. These may call themselves: Java Runtime, Runtime Environment, Runtime, JRE, Java Virtual Machine, Virtual Machine, Java VM, JVM, VM, J2RE, J2SE. Get the latest version from Java.com. They will usually attempt to foist some garbage like the Ask toolbar, Yahoo toolbar or McAfee Security Scan on you as part of the download. Just uncheck the garbage before the download (or install) starts. If you use a 64-bit browser and want the 64-bit version of Java you need to use it to visit java.com.
Due to multiple security problems with Java we are now recommending that it not be installed unless you absolutely know you need it. IF that is the case then go to Control Panel, Java, Security and slide it up to the highest level. OK.

Make sure Windows Updates is turned and that it works. Go to Control panel, Windows Updates and see if it works.

If you are feeling especially paranoid you can install the free firewall called Online Armor:
http://www.online-armor.com/


My help is free but if you wish to show your appreciation, please donate to Kwiaht instead of me. It's a local environmental organization that I volunteer with: http://www.kwiaht.org/donate.htm
(The name means something like "clean place" in one of the local native-American dialects)

Ron
  • 0

#30
radiuss

radiuss

    Member

  • Topic Starter
  • Member
  • PipPip
  • 32 posts
Thanks for all of your help, Ron. I will visit the Kwiaht website you linked.
Have a great day!
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP