2 Intern

 • 

12.7K Posts

December 23rd, 2006 15:00

2 Intern

 • 

12.7K Posts

December 23rd, 2006 16:00

You might want to run "Hijackthis" and post over on that forum..
 

2 Intern

 • 

7.9K Posts

December 23rd, 2006 16:00

The only thing that looks like it should be running (but is disabled) is
 
Human Interface Device Access ...   upon trying to start it I receive:
 
Could not start the Human Interface Device Access service on Local Computer.
Error 126: The specified module could not be found.

2 Intern

 • 

12.7K Posts

December 23rd, 2006 17:00

I feel for you, :smileysad:

2 Intern

 • 

7.9K Posts

December 23rd, 2006 17:00

i don't think it's anything like that but you never know ... probably worth a try.   SFC didn't help either :(
 
 

2 Intern

 • 

7.9K Posts

December 23rd, 2006 19:00

Well, a couple of system retores and multiple resets later, I have nailed the problem down to logitech quickcam software v8.4.8 for my quickcam pro 4000.    I was doing some other upgrades and thought I'd install the latest drivers.
 
Removing the old drivers was easy enough.  Unfortunately, installing their package
 
1) prevents device manager from functioning
2) makes 'my computer' extremely slow
3) prevents the network connection screen from functioning
4) to top it off, doesn't detect the webcam
 
So ...  now the question becomes, what to do to get my webcam to work without destroying my system in the process. 

2 Intern

 • 

12.7K Posts

December 23rd, 2006 19:00

We call that junkware, stores are full of this stuff, its like they make it but never try to use it before selling it to anyone, we are all just a bunch of lab rats.

2 Intern

 • 

7.9K Posts

December 23rd, 2006 20:00

well, i gave it another try.  fully uninstalled quickcam software.  removed cam from device mananger.  restarted.  reinstalled their software (forced reset after).  webcam was detected and worked.  device manager was killed again though.
 
i don't know what the heck they're doing but it's definitely not good for my system.  naturally they don't post old versions of their software.

2 Intern

 • 

7.9K Posts

December 23rd, 2006 20:00

changing HKLM\CCS\Enum permissions per that thread you posted worked.  I'm not sure if there are any broader implications to giving 'everyone' full read of that area and administrators and system 'full control' but at least it's working.

10 Elder

 • 

45.2K Posts

December 23rd, 2006 23:00

The Apropos trojan can cause an empty Device Manager too, so I'd be really, really careful about granting too many permissions until/unless you're certain you're not infected. You may want to run HijackThis to see if you've got apropos, and you'll need apropos.fix to remove it.

Read this:
http://www.annoyances.org/exec/forum/winxp/1132724135

Ron

Message Edited by RoHe on 12-23-200605:45 PM

33 Posts

December 24th, 2006 04:00

Hi,
Go to Start > Run. Type MSCONFIG and click on OK.
On the General tab, select Normal Startup, click on OK and restart the system.
It happens when a microsoft service gets disabled.
I hope it will help you..
--Max--

2 Intern

 • 

7.9K Posts

December 24th, 2006 13:00

in my case it was not a service issue, but it does seem like PNP getting turned off will do it as well..

2 Intern

 • 

12.7K Posts

December 24th, 2006 16:00

Nemesis, did you get solved?  was it the PNP thing?

2 Intern

 • 

7.9K Posts

December 24th, 2006 22:00

yes it was solved.  per one of my posts above it was not PNP related though.  that thread you posted did have the solution in it.
 
the registry permissions for HKLM\CCS\Enum got messed up by the logitech software (someone posting in that thread had the exact same issue).  reset the permissions so that 'system' could access the enum folder solved the problem.

2 Intern

 • 

12.7K Posts

December 24th, 2006 22:00

Missed an email I guess, thanks.
No Events found!

Top