Our company creates software that occasionally conflicts with the Shell
Hardware Detect Service following installation and a reboot. The symptoms
and work around are identical to what is described in Microsoft Knowledge
Base article 913630, ( http://www.yqcomputer.com/
) - the
computer startup process takes a long time to run and computer responds very
slowly. Stopping the Shell Hardware Detect Service resolves the slowness.
This incident only occurs on Windows XP Professional systems and happens
more often on laptops than desktop systems.
Does anyone have any idea what is causing the conflict with the service?
Are there files or settings that we are overwriting on our install that
conflict with the service?
Any information would be appreciated.