[OT] Unidentified USB device on all USB Ports after reboot,...

  • Thread starter Thread starter Kerem Gümrükcü
  • Start date Start date
Hi ALexander,
I guess the best would be remove all USB host adapters and root hub and let
OS reinstall them.
Click to expand...

What i did so far: Deleted the INFCACHE file, removed all USB devices,
including
roothub and any USB driver and "hardware" from my system, deleted any USB*
key
from hklm/system/currentcontrolset/enum*

OS rebooted, everyting was reinstalled from OS, looked fine->plugged USB
device
in->told me "usb device detected" and usb"device installed successfully" and
"usb device
failed", "usb device could not be installed", "usb be device could be faster
with a faster
usb interface", someting like that in german and i am not kidding: all these
messages,
notifyicons and pupups at the same time,...

Now i really dont know what to do,...DevieManager still tells me that
there is a unknown device for usb,....and still teh usb device is
inaccessible,...

I mean, this is where my mind start thinking what really lead to this
disaster.
I, afaik, changed nothing on my system, neither Driver installed, nor
registry
driver entries changed, nothing that could affect the OS core itself,...no
rootkids
afaik, checked with Rootkit Revealer, cheked loded drivers by process
explorer,
made a deep av check,...seems to be clean. There must be someting really
deeply
destroyed or some driver does not allow the USB to communicate with the
syste
as Doron said, but where, why and when did that happen?

I removed any virualization software from my system, that dealed in some way
with
my USB hardware,...no change,...

Really dont know what tp do now,...reinstalling os or something like that is
really no
option for me, since this must be someting that could be repared or better
to say at least found, whats blocking/filtering,etc,...

Regards

Kerem
 
Hi Alexander,
You had virtualization software? Check for any filters left over in USB
class.
Click to expand...

where do i exactly have to look and for what do i have to look for?
Do you mean the hklm\sysem\currentcontrolset\control\deviceclasses?

By the way, here are some screenshot i really dont understand, especially
the one, where every device is listed twice:


http://www.pro-it-education.de/staff/keremg/misc/a.jpg
http://www.pro-it-education.de/staff/keremg/misc/b.jpg
http://www.pro-it-education.de/staff/keremg/misc/c.jpg
http://www.pro-it-education.de/staff/keremg/misc/d.jpg

This is really cross,...


Regards

Kerem

--
 
Hi,

i was about to going nuts and then i found
the solution for this: The Tips with the Filter
Driver and Registry lead me to a right way
and also the hint with the Nirsoft USB Viewer
showed the right way to this. Here are the Steps.
First i searched the Web for something like
a Filter Driver Viewer, then it came to my mind,
that there was something i noticed a couple
of time ago on OSROnline: FilterMan 1.0

I downloaded the Nirsoft USBViewer and the
Filterman App. Then i opened the Registry
Editor pointing to the Enum Keys. After
removing all the Devices holding anything
to USB i reopened Filterman and USB View
and refrehsed my Registry Editor. Then i found
something very interessting: One "Unknown Device"
was left there, a single device! Then i decided to do
this: I saved the still available registry keys to reg files
under HKLM\SYSTEM\CurrentControlSet\Class\*<every still visible USB stuff>
Then i switched over to the Device Manager and did a "Detect
changed Hardware". Then everything went as expected and
all USB Devices and Bridges/Hubs have been installed.
Then i made a F5 just to be sure on the Registry Editor
and i saw all the valid instances of the Hardware there.
Here the "woha" moment comes: Then i plugged my Wireless
USB Adapter in and everything worked fine: Hardware
detected, installed, ready to use. Bingo, that was it,...

Thanks to EVERYBODY here, this was a very "disturbing"
situation for me to having a laptop with 4 USB Ports and
no USB available,...:-/

Here is the Link for the Filterman if someone likes
to see it: http://www.osronline.com/article.cfm?article=154

And here is Link to what i see now:
http://www.pro-it-education.de/staff/keremg/misc/g.jpg
http://www.pro-it-education.de/staff/keremg/misc/f.jpg

This posting comes packed over USB,...:-D

Regards

Kerem



--
 
Hi Kelly,

if you mean IPOD Hardware, by Apples IPOD, then
i can tell you that i never had such a device plugged on
my system, or installed any Drivers/Filters, that changed
this key, as afaik. Or do you mean something different,...?


Regards

Kerem

--
 
hklm\sysem\currentcontrolset\control\class\{36FC9E60-C465-11CF-8056-444553540000}

HKLM\SYSTEM\CCS\Enum\PCI\<USB host controller ID>\<instance ID\
HKLM\SYSTEM\CCS\Enum\USB\ROOT_HUB
HKLM\SYSTEM\CCS\Enum\USB\ROOT_HUB20

Did you change your mainboard, CPU, or type of HAL after you've installed
the OS? Those duplicate Interrupt Controller and other are probably
enumerated off different root.

I suppose the system in question is not a VM?
 
Hi Alexander,
hklm\sysem\currentcontrolset\control\class\{36FC9E60-C465-11CF-8056-444553540000}
Click to expand...
HKLM\SYSTEM\CCS\Enum\PCI\<USB host controller ID>\<instance ID\
HKLM\SYSTEM\CCS\Enum\USB\ROOT_HUB
HKLM\SYSTEM\CCS\Enum\USB\ROOT_HUB20
Click to expand...
Did you change your mainboard,
No,...


No,...

or type of HAL after you've installed
No,...

Those duplicate Interrupt Controller and other are probably enumerated off
different root.
Click to expand...

I changed nothing on the systen, except the USB
devices i plugged in, but this should be really not
change those intergral os parts,..
I suppose the system in question is not a VM?
Click to expand...

No, it is a real hardware system, no emulation,...

But it is solved as you will see on my [SOLVED]
posting,...

Dont ask me what lead to this shit, i really dont know,
but by deleting parts of the USB class keys, the system
started to work again with no problems and now accepts
all devices and installs and configures them properly,...

Regards

Kerem

--
 
Uwe said:
This script removes upper and lower filters for
GUID_DEVCLASS_FLOPPYDISK. Any explanation why
this should affect non floppy devices?
Click to expand...

Correction:
It removes upperfilters for GUID_DEVCLASS_FLOPPYDISK
and lowerfilters for GUID_DEVCLASS_DISKDRIVE.

Maybe the first was intended to be GUID_DEVCLASS_DISKDRIVE
too...


Uwe
 
Back
Top