Empty Device Manager after SP2 Upgrade from SP1

[Guest]

I have several boxes, about 25-30, which now have empty device managers after
the SP2 upgrade.

The upgrades went smoothly as far as I could tell. I upgraded using the
install file, not windows update.

The symptoms are the following:

- The device manager only shows the computer name at the top of the list,
the rest is blank. If you try to scan for new hardware, the screen flashes
to black as if I was changing resolutions on the video adapter, then it comes
back and the device manager is still empty.

- Network connections no longer shows any LAN connections, and the dial-up
connections, if present, do not function because the modem is not listed.

- I can, oddly enough, still access properties for the video adapter and
monitor.

- These systems had Symantec PCAnywhere installed, and after the SP2
upgrade there are system errors in the event viewer related to the PCAnywhere
process.

I am at a loss. I can recreate this problem over and over. The only common
thread is PCAnywhere. But even if I uninstall it prior to the SP2 upgrade I
still loose the device manager.

Any Ideas?

Sean

 

[Guest]

Install xp cd,exit the info page,go to run,type:cmd In cmd type:Sfc /Scannow
When the graph is thru,type:CHKDSK C: /F Agree to restart,then type:EXIT
Restart computer remove xp cd.Run the DOS window in min.,sometimes the
bar graph runs behind it,if this wont correct the problem,create a new user
account,restart computer,open in new,chk device mgr.,if the icons/info is
correct,you have a corrupt user acount,delete the account.

 

[Wesley Vogel]

create a new user account, that sounds like a brilliant good idea for 25-30
machines.

 

[Kelly]

Hi Sean,

If the Device Manager is empty:

Go the Start/Administrative Tools/Services. Scroll down to Plug and Play
Service and stop and restart it. Once done the Device Manager will populate
again.

To extract: Go to Start/Run/CMD and type in the command below: (Substitute
C and D accordingly).

C:\>extract d:\i386\devmgmt.ms_ c:\windows\system32
\devmgmt.msc

where d: is your CD rom Drive with your windows XP CD.
Whatever your CD rom drive letter is then substitute it in
the command line.

/taskbarplus!.htm

 

[Guest]

Thanks for the responses, guys, but, unfortunately, none of them helped.
These are non-domain boxes. I deleted the user accounts and added a new one,
but the device manager is still empty.

I've had already tried Kelly's suggestion of re-extracting the devmgmt
snap-in.

Nothing is working.

Another thing I've discovered: Our domain is kept updated by a sus server;
but these boxes that are giving me trouble are remote, so we were using CD's
with the SP2 exe file to do the update. So I decided to connect one of them
to our network and update it to SP2 via the sus server, and it didn't have
the problem with the device manager. If I reimaged the same box to pre SP2
and ran the update form the CD, then the device manager is empty. ??? What
would be different between an "Automatic Updates" install vs. the CD install?

Sean

 

[Guest]

Here is another thing I've noticed on these boxes after installing SP2: The
reg key "HKLM\system\currentcontrolset\enum" contains about 50 subkeys which
all contain names like @-!@$%^$. It appears to be garbage. None of the
hardware info is there. The first subkey under "enum" should be "acpi", not
"$@@%@#" Controlsets 1, 2 and 3 all look the same way, therefore I have no
"good" control set to revert to.

What do you think about exporting those keys prior to the upgrade, then
importing them afterward? I'm not very encouraged.

Sean

 

[J. S. Pack]

I have several boxes, about 25-30, which now have empty device managers after
the SP2 upgrade.

The upgrades went smoothly as far as I could tell. I upgraded using the
install file, not windows update.

The symptoms are the following:

- The device manager only shows the computer name at the top of the list,
the rest is blank. If you try to scan for new hardware, the screen flashes
to black as if I was changing resolutions on the video adapter, then it comes
back and the device manager is still empty.

- Network connections no longer shows any LAN connections, and the dial-up
connections, if present, do not function because the modem is not listed.

- I can, oddly enough, still access properties for the video adapter and
monitor.

- These systems had Symantec PCAnywhere installed, and after the SP2
upgrade there are system errors in the event viewer related to the PCAnywhere
process.

I am at a loss. I can recreate this problem over and over. The only common
thread is PCAnywhere. But even if I uninstall it prior to the SP2 upgrade I
still loose the device manager.

Any Ideas?

Sean

I had EXACTLY this problem (w/o PC Anywhere) and googled and struggled for
a couple of days to fix it. Nothing worked (if some other solution is found
here, great) except to do a repair install from the original XP disk and
then install SP2 on top of it. Repair installing from a slipstreamed SP2
did NOT work.

The Plug&Play service could not be stopped and restarted as the button was
grayed out.

So it seems to have had something do with the SP1 on that machine or other
updates (which worked fine before the SP2 installation) but I can't imagine
what. Unfortunately I didn't have the option to try uninstalling the SP1
(had it occured to me to do so) before the SP2.

This was only on one machine. Other machines configured similarly had no
such problem, which made it even more puzzling.

 

[Guest]

I was able to restore my device manager by deleted the "enum" registry keys
from the currentcontrolset and controlsets 1-3. I rebooted and the system
re-created them and the device manager was back.

Now, everything is working fine except the modem. It shows up in device
manager, but when I try to dial out I get a 733 or 633 RAS error--port not
open or device busy. This is occurring on 3 different modems, so I don't
think it's the modem itself. I have tried uninstalling it and re-creating
the dial-up accounts, but the modem will still return the RAS errors. I can
dial via telnet and the modem diagnostics return the correct responses.

Any ideas?

Thanks, guys.