corrupt file

[chimpy]

I did a sfc /scannow in command prompt and it said it found corrupt files some of which it could not fix and gave me a C:\windows\logs\cbs file to check what they where but all I get is a access denied when I try to open them in both user and admin!

Any clue how to get access?

EDIT

I worked out how too, but the results are long and bafferling! I think I saw only one file that could not be fixed, "hosts" winsock inferstructure or something like that, anyone any good at reading these results?

I only scanned as I was having a little WD problem.

[chimpy]

No one got any clues?

I re did the sfc /scannow and it said "Windows Resource Protection did not find any integrity violations" so I have no clue what happened to the ones it could not fix

[Firefox]

you could try also running a program called dial-a-fix to reset some of the default windows settings and re-register some dll files....

[chimpy]

Thing is I am not sure that anything needs fixing now The re scan did not make a log this time and did not find anything to fix so I am not sure how or why I seemed to have lots and lots of them in the first place!

[Firefox]

too many corrupt files happening could be a sign of bad ram or a going bad hard disk. Runs some tests on your memory and your hard disk.

[chimpy]

How do I test for those?

My computers less that 2 years old I hope its nothing like that...

[Firefox]

get a hold of a Hiren's BootCD that will have some tools for testing your memory and your hard drive as well. As with all tools be careful what you do so you do not damage your operating system

[chimpy]

I googled that and wiki said some tools on it might be illegal due to licensing laws in differing countrys http://en.wikipedia.org/wiki/Hiren%27s_BootCD

Is there not a way on my computer I can test for these?

I do not seem to have anything wrong with my computer but then again I am not sure what the symptons of a failing HD or bad RAM would be.

[Firefox]

you can download Memtest86 and try it.

you can also download hard drive testers from you hard drive manufactures web site as well.

[chimpy]

Memory seems to be fine and I have no signs of bad RAM, I had a look on "event viewer" and saw one critical even that happened 8 months ago.

(event ID 2, source Appilcationexperienceinfrastructure) something to do with "windows media technologies" and all the info it gives is .. "This version of Windows Media Technologies is incompatible with or has been superseded by this version of Windows. For more information, view the information at the Microsoft web site." It says that version was hard blocked.

I also seem to have had 7 errors and 15 warning in the past 24 hours!

My computer seems to be running ok though.

EDIT

I also have found that Windows Installer 3.1 failed to install on the 5/5/09

its says this

"The description for Event ID 4373 from source Windows Installer 3.1 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Windows

Not enough storage is available to process this command." which is strange as I have lots of free space on my C drive.

"Microsoft-Windows-Search

Date: 01/04/2009 05:06:04

Event ID: 3013

Level: Error

The entry <C:\USERS\*****\APPDATA\LOCAL\MICROSOFT\WINDOWS\HISTORY\HISTORY.IE5\MSHIST012009040120090402> in the hash map cannot be updated.

Context: Application, SystemIndex Catalog

Details:

A device attached to the system is not functioning. (0x8007001f)"

"Log Name: Application

Source: Microsoft-Windows-Search

Date: 05/05/2009 16:42:25

Event ID: 3024

Task Category: Gatherer

Level: Error

Description:

The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Application, SystemIndex Catalog"

"Log Name: Application

Source: Microsoft-Windows-Search

Date: 23/07/2009 02:58:19

Event ID: 3036

Task Category: Gatherer

Level: Warning

Description:

The content source <iehistory://{s-1-5-21-2069415660-1087055719-4139926696-1000}/> cannot be accessed.

Context: Application, SystemIndex Catalog

Details:

Unspecified error (0x80004005)"

"Log Name: Application

Source: SDWinSec.exe

Date: 28/11/2008 16:07:46

Event ID: 0

Task Category: None

Level: Error

Description:

The description for Event ID 0 from source SDWinSec.exe cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

A system shutdown is in progress"

and this one

"Log Name: Application

Source: Microsoft-Windows-RestartManager

Date: 16/03/2009 19:29:15

Event ID: 10007

Task Category: None

Level: Error

Description:

Application or service 'Messenger Sharing Folders USN Journal Reader service' could not be restarted."

"Log Name: Application

Source: MsiInstaller

Date: 12/11/2008 23:30:29

Event ID: 1001

Task Category: None

Level: Warning

Description:

Detection of product '{5C82DAE5-6EB0-4374-9254-BE3319BA4E82}', feature 'Phone' failed during request for component '{57FF4446-590E-4894-AE39-D55928DBDE01}'"

"Log Name: Application

Source: MsiInstaller

Date: 06/03/2009 05:24:22

Event ID: 11316

Task Category: None

Level: Error

Description:

Product: Windows Live Sign-in Assistant -- Error 1316. A network error occurred while attempting to read from the file: C:\Windows\TEMP\IXP000.TMP\Install_{AFA4E5FD-ED70-4D92-99D0-162FD56DC986}.msi"

"Log Name: Application

Source: Microsoft-Windows-EventSystem

Date: 26/06/2009 17:28:28

Event ID: 4609

Task Category: Event System

Level: Error

Description:

The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\longhorn\com\complus\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error."

"Log Name: Application

Source: Microsoft-Windows-EventSystem

Date: 18/07/2009 15:55:26

Event ID: 4621

Task Category: Event System

Level: Error

Description:

The COM+ Event System could not remove the EventSystem.EventSubscription object {2A2B3574-0F82-4535-9907-9C953BB12A5D}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The HRESULT was 80070005."

(those I checked on MS and all the componants that it said needed to "start" for it to work were in place)

"Log Name: Application

Source: Microsoft-Windows-CAPI2

Date: 28/06/2009 02:01:49

Event ID: 11

Task Category: None

Level: Error

Description:

Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file."

(there was a link in this that opened up a DL for something called "authrootstl.cab" which I cancelled, should I have done? there where alot of errors for this for june this year.)

Sorry if this is too much info (I left most the errors out), I just am wondering what all this means....

Thanks.

[chimpy]

Can anyone take a look at this for me?

[exile360]

Is Windows Installer 3.1 listed in Add\Remove Programs? The rest of it doesn't look too severe.

[chimpy]

Thanks for checking, Nope I cannot find a windows installer at all.

EDIT

I had a google to see if there was another way of checking so I opened command prompt and typed in msiexec and I got a pop up saying I had V 4.5.6002.18005 the forums say thats not the true version

One common point of confusion is that even if you have the latest version of Windows Installer 3.1 on your system and you type in msiexec.exe /? from a command-window, you will still be told that you are on version 3.1.4000.1823 or 3.1.4000.1830. This is because msiexec.exe /? will only give you the version of msiexec on the system -- not the other Windows Installer-related dll's. (The version of msiexec was not updated to 3.1.4000.2435 with the (v2) redistributable, just msi.dll was updated.)"

Is that of any help to you?

[exile360]

Good, that means you're running 4.5 which is the latest version . If you didn't have at least 3.1 installed properly then Windows Updates would fail to install as they rely on it so you should be OK. The most recent errors I'm seeing listed are from July so you should be OK. There are a few from the search service which could mean disk corruption, but it could also be related to disk permissions.

Has everything been running OK now? If so, it's likely that you had some bad permissions or files corrupted that SFC repaired. You could also try a CheckDisk scan. Copy and paste cmd into the Run box then copy/paste this into the command prompt window:

ECHO Y|CHKDSK %systemdrive% /F

Then press Enter and reboot your PC. When it starts up it will say that a disk check has been scheduled, don't press anything and just let it run. It will check for bad sectors on the disk and repair them if found, then it will reboot again and start up normally. Let me know how it goes.

[chimpy]

Yup everything is pretty fine as far as I can tell.

I did that and I think this is the log from it

Log Name:	  Application
Source:		Microsoft-Windows-Wininit
Date:		  29/08/2009 07:41:07
Event ID:	  1001
Task Category: None
Level:		 Information
Keywords:	  Classic
User:		  N/A
Computer:	  *********-pc
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


A disk check has been scheduled.
Windows will now check the disk.						 
  138176 file records processed.								  

  763 large file records processed.							

  0 bad file records processed.							  

  0 EA records processed.									

  56 reparse records processed.							   

  176274 index entries processed.								 

  0 unindexed files processed.							   

  138176 security descriptors processed.						  

Cleaning up 38 unused index entries from index $SII of file 0x9.
Cleaning up 38 unused index entries from index $SDH of file 0x9.
Cleaning up 38 unused security descriptors.
  19050 data files processed.									

CHKDSK is verifying Usn Journal...
  37692992 USN bytes processed.									 

Usn Journal verification completed.
Windows has checked the file system and found no problems.

 233596927 KB total disk space.
  81063008 KB in 104479 files.
	 67292 KB in 19051 indexes.
		 0 KB in bad sectors.
	258907 KB in use by the system.
	 65536 KB occupied by the log file.
 152207720 KB available on disk.

	  4096 bytes in each allocation unit.
  58399231 total allocation units on disk.
  38051930 allocation units available on disk.

Internal Info:
c0 1b 02 00 5b e2 01 00 f3 5a 03 00 00 00 00 00  ....[....Z......
11 51 00 00 38 00 00 00 00 00 00 00 00 00 00 00  .Q..8...........
42 00 00 00 12 75 0d 77 60 86 1e 00 60 7e 1e 00  B....u.w`...`~..

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
	<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
	<EventID Qualifiers="16384">1001</EventID>
	<Version>0</Version>
	<Level>4</Level>
	<Task>0</Task>
	<Opcode>0</Opcode>
	<Keywords>0x80000000000000</Keywords>
	<TimeCreated SystemTime="2009-08-29T06:41:07.000Z" />
	<EventRecordID>55387</EventRecordID>
	<Correlation />
	<Execution ProcessID="0" ThreadID="0" />
	<Channel>Application</Channel>
	<Computer>***********-pc</Computer>
	<Security />
  </System>
  <EventData>
	<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


A disk check has been scheduled.
Windows will now check the disk.						 
  138176 file records processed.								  

  763 large file records processed.							

  0 bad file records processed.							  

  0 EA records processed.									

  56 reparse records processed.							   

  176274 index entries processed.								 

  0 unindexed files processed.							   

  138176 security descriptors processed.						  

Cleaning up 38 unused index entries from index $SII of file 0x9.
Cleaning up 38 unused index entries from index $SDH of file 0x9.
Cleaning up 38 unused security descriptors.
  19050 data files processed.									

CHKDSK is verifying Usn Journal...
  37692992 USN bytes processed.									 

Usn Journal verification completed.
Windows has checked the file system and found no problems.

 233596927 KB total disk space.
  81063008 KB in 104479 files.
	 67292 KB in 19051 indexes.
		 0 KB in bad sectors.
	258907 KB in use by the system.
	 65536 KB occupied by the log file.
 152207720 KB available on disk.

	  4096 bytes in each allocation unit.
  58399231 total allocation units on disk.
  38051930 allocation units available on disk.

Internal Info:
c0 1b 02 00 5b e2 01 00 f3 5a 03 00 00 00 00 00  ....[....Z......
11 51 00 00 38 00 00 00 00 00 00 00 00 00 00 00  .Q..8...........
42 00 00 00 12 75 0d 77 60 86 1e 00 60 7e 1e 00  B....u.w`...`~..

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
  </EventData>
</Event>

I did this a few weeks ago and it took hours but this one took minutes!

[exile360]

The one you did a few weeks ago most likely fixed some serious problems, which were likely the origin of this mess. I didn't know you'd already run CheckDisk. The log from your last run is clean, no errors so I'd say it looks like you're in excellent shape now .

[chimpy]

I did not know if the one you pasted was a different one as I ran it a different way sorry!

is there a way to show you the other log or is that over written/not needed?

Also if you do not mind I found a few things in the sfc/scannow, well alot of things, can I show you a few of them if you have time?

[exile360]

No need to see the old log, the current one is all that matters . The older one will only show what was already fixed, and therefore no longer a problem. The same goes for SFC, as long as SFC scans run cleanly now then there's no issue. It's likely the file corruption which was corrected by CheckDisk fixed the files that SFC couldn't read as they were corrupted, but once CheckDisk repaired them, SFC no longer had a problem reading the files .

[chimpy]

They seem to be fixed before I ran the first CHKDSK but now it says "Windows Resource Protection did not find any integrity violations" So that must be good news.

Great to hear all is well

Is it good to run both the scannow and the CHKDSK on a regular basis? say twice a year?

Thanks a lot Exile360

[exile360]

You're welcome .

You usually don't need to run them at all unless you're having issues, as they're generally used to repair an existing problem and sometimes also as a means of diagnosis for other problems. They aren't really maintenance tools like Defrag.

[chimpy]

Ah right, I did only run them because I was having a little windows defender scheduling problem (you can hear it starting up but if you then click on it, it seems to just start then which is weird) But as it seems to run I am just going to leave it be.

And I have my defrag set to run once a month which might be a little too often but I doubt it defrags the whole thing as I am normally only on the computer for short bursts.

Once again thanks.

[exile360]

No problem, if you have any more issues just post .