Windows can not boot due to missing MSVCP60.DLL File.

B

Babych

I can not boot up my computer. I have xp pro sp2. When I turn it on it says
that windows can not boot up due to missing MSVCP60.DLL. I can not go to safe
mode or use last know working configuration.

Any Ideas?
 
A

Anna

M

M.I.5¾

Anna said:
Babych:
Well, before running a Repair install of the XP operating system, run the
XP System File Checker process (commonly called "scannow sfc"). It's a lot
simpler to run and less intrusive than the Repair install process and
should correct your problem. See the following link for instructions...
http://www.updatexp.com/scannow-sfc.html

But in order to run this, won't the OP need to be able to boot his PC first?
 
A

Anna

Anna said:
Babych:
Well, before running a Repair install of the XP operating system, run the
XP System File Checker process (commonly called "scannow sfc"). It's a lot
simpler to run and less intrusive than the Repair install process and
should correct your problem. See the following link for instructions...
http://www.updatexp.com/scannow-sfc.html
Anna


Babych:
It just occurred to me that since your system is unbootable you will not be
able to run the sfc /scannow process I recommended. Sorry for the
misinformation.

Mark's suggestion re running a Repair install should correct your problem.
Another alternative would be to Google for MSVCP60.DLL and you'll be
referred to a number of links describing issues involving that missing file.
Anna
 
A

Anna

M.I.5¾ said:
But in order to run this, won't the OP need to be able to boot his PC
first?


M.I.53/4:
You are most certainly correct. I corrected the misinformation I originally
provided the OP in a later post.

I had been thinking along lines when we've encountered that "missing
MSVCP60.DLL"
message. In every similar situation (as I recall) the problem we ran into
involved the inability to access this or that program because of the missing
(or corrupt) dll. I can't recall a situation that we encountered where the
system was unbootable because of the missing dll. Although it's obviously
possible as reported by the OP. So I was (mistakenly) thinking of using the
usual Start > Run "sfc /scannow" command that (as I recall) invariably
corrected the problem.
Anna
 

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

Top