Link to home
Start Free TrialLog in
Avatar of mgross333
mgross333

asked on

Device Manager fails; how do I fix it

Windows XP Home, SP1. I install a vid cam (for internet vid conferncing and IM conferencing) but make a mistake and install it for Win ME. I get error messages including something about startup.dll. So I realize my mistake and install it for XP. All iinstalls are from the CD that came with the vidcam.

Next I find that when I select Device Manager in the System Properties window, it comes up in a separate window and the window is empty. Meaning I cannot delete the vid cam device and start over. Also a Creative Soundblaster driver installed just before the vid cam (from Creative CD) now fails because there is no sound any more ! And Audio properties says No Audio Device even though audi was fine after the Creative Install and before the vid cam install.

Question: How can I get Device Manager to work? Hint if I do a repair install it works again but that is a lot of trouble. I mean can I use SFC or the Recovery Console to replace a specific EXE or DLL that is damaged and which is needed for Device Manager to display the devices; the NAME OF THE SYSTEM FILE NEEDED TO GET DEVICE MANAGER TO DISPLAY DEVICES would really help me !!!

Also there is a possibility that if I had done the vidcam install for XP, not ME, I would still get the same problem. I am calling the vidcam manufacturer's tech support department (D-link) about that.

Mike
Avatar of MiguelSilvestre
MiguelSilvestre

try running mmc from the run box

file , add / remove snap-in

in the add snap-in window click device manager then click local the finish then close

once back in the main window click device managment

then you may be able to use device mgr from there

Hi mgross333,

1. Go to to Windows Update.

www.windowsupdate.com

2. Choose Express to download all the necessary windows updates automatically and specific to your OS and hardware.

Regards,
Start->Run and type: sfc /scannow

This will automatically replace any/all damaged system files.
(EDIT: And you don't need to know the specific name of the damaged file(s) when using SFC, it will check all of them for you)
ASKER CERTIFIED SOLUTION
Avatar of LeeTutor
LeeTutor
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mgross333

ASKER

Thanks for all the replies.

I will try Karvala and then LeeTutor's suggestion. And then post and assign points if either works.

To IanTh, I tried your instructions on a my own working XP Home SP2 PC and in the snap-in window, Device Manager was not shown (windows was completely empty) so there would be no way to proceed with the rest of your instructions. PLEASE REPLY on this. Is the answer that I do not see Device Manger because it runs properly on my Windows XP PC; but if Device Manager is broke it will show up (or might show up) in the snap in window?
Also can you provide a sentence of two on what the snap in window does at a high-level? I am not familiar with it or with mmc.

Regarding MiguelSivestre and GabrielN's ideas: It takes about 45 min to 1 hr to install SP2 as the MS server is quite slow and it is a long procedure. And updating  SP1, I don't know. The Dell Cd used to do the repair install said Sp1a on it and may already have a lot of updates and the Express install only updates things not already there. On the other hand, doing lots of SP1 updates can also take a lot of time.

Karvala's and LeeTutor's suggestions are short and not time consuming and LeeTutor's suggestion (if you click his link) refers to EXACTLY the problem I am having. Now that does not mean that Lee Tutor's link will work; my problem may have a different cause.  

Karvala's suggestion will (in principle) find bad system files; I am not sure upgrading SP1 will do that. Now upgrading to SP2 would probably do that (as it changes a lot of files) but may not change the system file causing the problem. As I already know that repair install works and DOES restore Device Manager to a working state and it takes no longer than the SP2 upgrade, I will go with that if Karvala's and LeeTutor's ideas both fail.

Any additional comments on my plan and/or my reasoning above would be appreciated. I will not be returning to the customer till 5:30 PM EST tomorrow Thursday Jan. 26.

Regards,
   Michael

 
the snap-in is a window for adding snap-ins to mmc, mmc is a admin tool that allows you to make a util that does what you want by adding snap-ins as and when needed and save them as well
IanTh,

Thanks for the quick reply. However I still NEED TO KNOW THIE FOLLOWING: After adding Device Manager, you say to run it from the Main mmc window. Does that mean that I cannot run it from System Properties but only in the mmc Window?

That will not help UNLESS I can go into Device Manager within mmc, delete the two problem devices (vid cam and audio card) and THEN DEVICE MANAGER runs from System Properties, not just from within mmc. This might happen as the VidCam install caused Device Manager to fail but I would not count on it !!!

So do I have to run Device Manager in mmc after your instructions or will it run from System Properties too in the usual way immediately after executing your instructions?

Regards,
  Mike
To check up on devices and whats what, you can use a free tool
called Aida32, this will probably not allow to roll back drivers like
device manager would but it will allow you to see exact driver
versions and so on...

http://www.majorgeeks.com/download181.html [Aida32]

If not may I suggest the old universal answer...

Ad-Aware Personal, then SpyBotSD, then you might be able to access Device Manager!
Lee Tutor's solution worked. Karvala's solution failed because sfc wanted the XP Pro CD to be inserted when the OS running was XP Home so the XP Home CD I had was not the right one and sfc would not continue. I did not ry the mmc solution.

Thanks again to all who replied.

Mike