After deleting the c:\windows\inf\msports.inf file and exiting the command prompt, the repair has remained stuck at 33 minutes to completion over night.
In the last block of the setupapi.log file it shows that *PNP0501 is found twice (supposedly within msports.inf) and given a different "Rank:" each time. Why does this happen? Could this be part of the problem? Should it only be found once?
Also in the very last line of the setupapi.log file where it states the following:
#I289 Removing device "ROOT\*PNP0501\1_0_17_0_0_0".
This is the only time within the entire file that any attempt is ever made at removing a device, and this is where the file ends and possibly but not necessarily where the computer hangs. So why is it trying to remove this device? Is there a way to force the repair process to stop trying to remove devices or at least to skip that step and continue? Should we attempt to manually remove the device mentioned?
Note: "ROOT\*PNP0501\1_0_17_0_0_0" is a key with subkeys located within the system registry in at least two places.
Instance #1: "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\*PNP0501\1_0_17_0_0_0"
Instance #2: "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\*PNP0501\1_0_17_0_0_0"
Note: That there are many other instances of "PNP0501" with many branches rooted throughout the system registry.
Also PNP0501 seems to be registered / defined as Com1. What is typically hooked up to Com1? Is it the mouse? A modem?
I'm using DSL so there is a network card but I unplugged it at the modem side...
Could removing all non-essential hardware before starting the repair process make a difference or is the repair process trying to repair the OS back to where all the hardware was already installed?
I am attaching copies of both msports.inf and the setupapi.log file from this last attempt.
Edited by geekstogouser, 25 November 2007 - 11:43 AM.