File system errors

[Good News!]

I have tried running chkdsk/f and chkdsk/r a number of times on my C: drive
(during reboot of course) but no errors are found.

But, running chkdsk while Windows is booted keeps finding errors.

"Correcting errors in the master file table's (MFT) DATA attribute.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these."

I found a lot of corruption on the drive that was initially corrected, but
Symantec Antivirus failed to execute and I had to manually uninstall it.
This now fails to reinstall, and it's frustrating as hell. I assume these
file errors are the problem.

Can anyone suggest how to fix this? I'm not too happy about having a PC
without virus protection these days!

Thanks.

 

[Guest]

dump norton and get something that works like Kaspersky.
The install issue is one of many problems that norton is known for.

 

[Good News!]

: dump norton and get something that works like Kaspersky.
: The install issue is one of many problems that norton is known for.

Well this is the first time it has happened on hundreds of machines since
version 5 was released, so that's not it!

Glad to see you completely ignored the file corruption.

 

[Good News!]

"
Windows will now check the disk.

Cleaning up minor inconsistencies on the drive.

Cleaning up 8 unused index entries from index $SII of file 0x9.

Cleaning up 8 unused index entries from index $SDH of file 0x9.

Cleaning up 8 unused security descriptors.

CHKDSK is verifying Usn Journal...

Usn Journal verification completed."



As you can see, during reboot with chkdsk/f, nothing of any significance is
detected! What is causing the problem?

 

[witan]

"
Windows will now check the disk.

Cleaning up minor inconsistencies on the drive.

Cleaning up 8 unused index entries from index $SII of file 0x9.

Cleaning up 8 unused index entries from index $SDH of file 0x9.

Cleaning up 8 unused security descriptors.

CHKDSK is verifying Usn Journal...

Usn Journal verification completed."

As you can see, during reboot with chkdsk/f, nothing of any significance is
detected! What is causing the problem?

Running chkdsk on the drive on which Windows is installed usually
gives error messages, apparently because chkdsk has interrupted some
background disk-writing operation. This has been my personal
experience also. If chkdsk is repeated once or twice, the error is no
longer seen. AFAIK, this is nothing to worry about, and I have also
seen that faithfully obeying the instruction to run chkdsk /f at
boottime does not show up any errors..