Error checking problem, XP pro

  • Thread starter Thread starter sarah morgan
  • Start date Start date
S

sarah morgan

Hello,

Hopefully someone here can help! My problem: I cannot
run the error-checking tool on my disk. After I set it up
to rum when I re-start my computer, I get the following
message after re-starting:

"File type: NTFS"
"Cannot open for direct access"

The utility cannot check my disk for errors. It might be
related to a similar issue I am having, since both started
at the same time. When I open Outlook, I recieve the
following message:

"The add
in "C:\ProgramFiles\Symantec_Client_Security\Symantec
Antivirus..." could not be installed or loaded. This
problem might be resolved by using Detect and Repair on
the help menu. "

Detect and Repair did not fix the problem. I am wondering
if the two issues are related, and if I might be able to
fix both at once, or if I can at least get my error-
checking to work again.

I am also contacting the Symantec folks for help!

Thank-you in advance!
-Sarah.
 
You can convert you filesystem to fat32, but that requires
a format.

you can also run a 3rd party disk checking software.
windows diskchecking is very good, but sometimes a second
opinion is better
 
sarah morgan said:
Hello,

Hopefully someone here can help! My problem: I cannot
run the error-checking tool on my disk. After I set it up
to rum when I re-start my computer, I get the following
message after re-starting:

"File type: NTFS"
"Cannot open for direct access"

The utility cannot check my disk for errors. It might be
related to a similar issue I am having, since both started
at the same time.

That could be a known problem that Microsoft is currently working on
but does not presently have a fix for:

"Cannot Open Volume for Direct Access" Error Message When Chkdsk Runs
at Startup
Microsoft Knowledge Base Article - 823439
http://support.microsoft.com?kbid=823439

A couple of other things to try.

1. Open a DOS Command Prompt window (Start - All Programs -
Accessories - Command Prompt) and enter the following command:

CHKDSK /F /X

That may just work. But also may not.

2. If you have a Windows XP installation CD (not a "System Recovery"
disk that came with a new computer) then you can boot the computer
with the CD and choose the Repair (Recovery Console) option from the
first menu.

When it completes loading and stops at the command prompt enter the
following command:

CHKDSK /R

That should fix it.

When I open Outlook, I recieve the
following message:

"The add
in "C:\ProgramFiles\Symantec_Client_Security\Symantec
Antivirus..." could not be installed or loaded. This
problem might be resolved by using Detect and Repair on
the help menu. "

Detect and Repair did not fix the problem. I am wondering
if the two issues are related, and if I might be able to
fix both at once, or if I can at least get my error-
checking to work again.

I am also contacting the Symantec folks for help!

You will probably have to end up uninstalling your Symantec
product(s), then running a special utility from Symantec to uninstall
all of the additional crud and corruption that Symanetec products
deliberately leave behind when they "uninstall", and then finally
reinstall them all and redo all of the updates.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."
 
You can convert you filesystem to fat32, but that requires
a format.

you can also run a 3rd party disk checking software.
windows diskchecking is very good, but sometimes a second
opinion is better

Note: It is not mandatory that you a reformat is necessary to go to
FAT32 from NTFS Some commercial programs can do it like partition magic.
 
sarah said:
Hopefully someone here can help! My problem: I cannot
run the error-checking tool on my disk. After I set it up
to rum when I re-start my computer, I get the following
message after re-starting:

"File type: NTFS"
"Cannot open for direct access"

The utility cannot check my disk for errors. It might be
related to a similar issue I am having, since both started
at the same time.

One identified cause is having installed the new version 5 of Zone
Alarm. If you have done so, uninstall it and go back to ver 4.5
 
One identified cause is having installed the new version 5 of Zone
Alarm. If you have done so, uninstall it and go back to ver 4.5


Thanks Alex.

Is that documented anywhere yet?


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top