Unknown device (usb)

I have windows 7 64bits with an unknown device (usb). Looking at the
registry I found three entries with unknown device. Tried every
suggestion on internet. What I would like to do is just delete those
three devices from the registry from the top. Problem is Windows won't
let me delete those. I get a refusal code 5.

Any suggestions ?

Den

Den wrote:
I have windows 7 64bits with an unknown device (usb). Looking at the
registry I found three entries with unknown device. Tried every
suggestion on internet. What I would like to do is just delete those
three devices from the registry from the top. Problem is Windows won't
let me delete those. I get a refusal code 5.

Any suggestions ?

Den

This list would include USB controllers (i.e. the part
inside the Southbridge that supports the ports on the
motherboard. For example, my Southbridge is an ICH9R,
while the Northbridge is X48.

http://pciids.sourceforge.net/pci.ids

8086 Intel Corporation
2934 82801I (ICH9 Family) USB UHCI Controller #1

Whereas this is a list for USB devices, such as a
USB flash stick. In this example, this is my optical mouse
on USB bus.

http://www.linux-usb.org/usb.ids

046d Logitech, Inc.
c01a M-BQ85 Optical Wheel Mouse

The Properties of devices in Device Manager, have those
numeric IDs under the HardwareID property.

And this is how the system tracks them down.

*******

This article has some pictures, of tracking down the number.
When you get your VID and PID, those would be listed in
the usb.ids file.

http://www.howtogeek.com/193798/how-...evice-manager/

Paul

Den wrote:

I have windows 7 64bits with an unknown device (usb). Looking at the
registry I found three entries with unknown device. Tried every
suggestion on internet. What I would like to do is just delete those
three devices from the registry from the top. Problem is Windows won't
let me delete those. I get a refusal code 5.

You don't say under which category are the unknown USB devices or even
mention using Device Manager (devmgmt.msc). For example, it could be a
USB mouse and would be listed under Human Interface Devices (HID) as a
HID device. Could be it is under the USB Serial Bus controllers
category (on mobo or daughtercard) which probably means you have yet to
install the chipset drivers for the mobo or those for the daughtercard.
You may need to use View - Show hidden devices" to show all devices.

Where in the registry did you look? Under the USB enumeration keys?
Did you make sure you were looking under HKLM\System\CurrentControlSet
to ensure you were looking at your current config and not an old one?
There are usually multiple ControlSetnnn (where nnn = 3-digit number)
and you can find out in the registry which is the current one but it is
easier to just use the CurrentControlSet pseudo-key. The 3 USB
enumeration keys under HKLM\System\CurrentControlSet a

USB
USBPRINT
USBSTOR

USBSTOR are for mass storage devices, like USB drives you attach and
detach from USB ports. USBPRINT is obvious. Under each, the VID
(Vendor ID) often is unique to a vendor and even to a particular product
of theirs so you can look that up online. Often the next subkey has
data items with descriptive values to tell you for which USB device is
that enumeration entry.

Some subkeys are protected. They have permissions not assigned to the
Windows account under which you are currently logged into. Not even the
Administrator account may have the required permissions; however, using
an admin-level account, you can often right-click on a registry key,
select Permissions, and change the owner of the object, and then change
permissions (to Full), including the child objects (more subkeys). When
you have changed the permissions to grant yourself the required ones,
you can then delete that key.

In the past, I had to delete some old USB enumerations because the old
definitions interfered with a reinstall of the product (e.g., MagicJack
and its USB dongle with its softdialer). Be careful here. You are
editing the registry. You better not only export the keys you intend to
delete but also have a means to restore (from a backup image) in case
the OS becomes unbootable (which means you won't have an OS to then
imported the exported key back into the registry).

Have you unplugged all the externally attached USB devices to see if the
unknown device is internal or external?

You could use Microsoft's USBview to get more information on each USB
device. That might hint at what is the device. See about USBview at:

https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

However, many sites have USBview available for separate download, like:

http://www.softpedia.com/get/System/.../USBView.shtml.

Nirsoft also has their USBDeview utilitye at:

http://www.nirsoft.net/utils/usb_devices_view.html.

On Tue, 10 Jan 2017 18:16:44 -0500, Den wrote:

Here is the attachment that made me cause this double post: Just hope
it's Ok with the server.





I have windows 7 64bits with an unknown device (usb). Looking at the
registry I found three entries with unknown device. Tried every
suggestion on internet. What I would like to do is just delete those
three devices from the registry from the top. Problem is Windows won't
let me delete those. I get a refusal code 5.

Any suggestions ?

Den

On 1/11/2017 5:37 AM, Den wrote:
On Tue, 10 Jan 2017 18:16:44 -0500, Den wrote:

Here is the attachment that made me cause this double post: Just hope
it's Ok with the server.





I have windows 7 64bits with an unknown device (usb). Looking at the
registry I found three entries with unknown device. Tried every
suggestion on internet. What I would like to do is just delete those
three devices from the registry from the top. Problem is Windows won't
let me delete those. I get a refusal code 5.

Any suggestions ?

Den

No attachment appeared with your reply. Some news servers reject
messages containing attachments. Others merely strip away attachments.
I suggest you upload your attachment to a Web server and post the link
in a message.

--
David E. Ross
http://www.rossde.com/

When the President of the United States makes a statement of
national importance, I want to see his face as he is talking.
At the least, I want to hear his voice. Presidents should
not be making public statements that are of no importance.

Donald: Stop tweeting. Otherwise, how do we know the message
really comes from you?

Den wrote:
On Tue, 10 Jan 2017 18:16:44 -0500, Den wrote:

Here is the attachment that made me cause this double post: Just hope
it's Ok with the server.

Post a picture here.

https://postimage.org/index.php?um=flash

From the URL table that the web page returns after
your upload, test the URL and verify it points properly
to the picture.

Then post that URL here.

Paul

On Wed, 11 Jan 2017 15:33:06 -0500, Paul
wrote:

Thanks for the information Paul. Hope this works.
The picture is at:
https://postimg.org/image/we0wukytf/

Those are the unknown devices. I made a copy of my registry in case
something goes wrong, and tried to delete those three as a possible
solution. But windows won't let me.

Den



Den wrote:
On Tue, 10 Jan 2017 18:16:44 -0500, Den wrote:

Here is the attachment that made me cause this double post: Just hope
it's Ok with the server.

Post a picture here.

https://postimage.org/index.php?um=flash

From the URL table that the web page returns after
your upload, test the URL and verify it points properly
to the picture.

Then post that URL here.

Paul

Den wrote:
I have windows 7 64bits with an unknown device (usb). Looking at the
registry I found three entries with unknown device. Tried every
suggestion on internet. What I would like to do is just delete those
three devices from the registry from the top. Problem is Windows
won't let me delete those. I get a refusal code 5.

Any suggestions ?

Den



http://www.pcworld.com/article/20894...n-windows.html

On Thu, 12 Jan 2017 16:17:48 +0100, Z wrote:

Thanks for your suggestion. I'll study that. Sorry for my multiple
posts. I had a problem with the attachment that was over 32kb.

Den


Den wrote:
I have windows 7 64bits with an unknown device (usb). Looking at the
registry I found three entries with unknown device. Tried every
suggestion on internet. What I would like to do is just delete those
three devices from the registry from the top. Problem is Windows
won't let me delete those. I get a refusal code 5.

Any suggestions ?

Den



http://www.pcworld.com/article/20894...n-windows.html

Den wrote:
On Wed, 11 Jan 2017 15:33:06 -0500, Paul
wrote:

Thanks for the information Paul. Hope this works.
The picture is at:
https://postimg.org/image/we0wukytf/

Those are the unknown devices. I made a copy of my registry in case
something goes wrong, and tried to delete those three as a possible
solution. But windows won't let me.

Den

So what we know, is it's something that formed "end-points",
yet the config space is pretty strange. A completely dead
USB device wouldn't register like that. Of course VID_0000 PID_0000
is not a valid value, and is not going to be in usb.ids file.

Now, take a snapshot of the window from this program
and post the URL to the results.

http://www.uwe-sieber.de/usbtreeview_e.html

The download is at the bottom of the page. Uwe occasionally shows
up in the WinXP group, so he knows about newsgroups. His program
is similar to Microsoft UVCView, only he has made it easy to download,
while Microsoft wants you to "go on a little adventure" to
get theirs.

http://www.uwe-sieber.de/files/usbtreeview.zip

Paul

On Thu, 12 Jan 2017 16:39:27 -0500, Paul
wrote:

Den wrote:
On Wed, 11 Jan 2017 15:33:06 -0500, Paul
wrote:

Thanks for the information Paul. Hope this works.
The picture is at:
https://postimg.org/image/we0wukytf/

Those are the unknown devices. I made a copy of my registry in case
something goes wrong, and tried to delete those three as a possible
solution. But windows won't let me.

Den

So what we know, is it's something that formed "end-points",
yet the config space is pretty strange. A completely dead
USB device wouldn't register like that. Of course VID_0000 PID_0000
is not a valid value, and is not going to be in usb.ids file.

Now, take a snapshot of the window from this program
and post the URL to the results.

http://www.uwe-sieber.de/usbtreeview_e.html

The download is at the bottom of the page. Uwe occasionally shows
up in the WinXP group, so he knows about newsgroups. His program
is similar to Microsoft UVCView, only he has made it easy to download,
while Microsoft wants you to "go on a little adventure" to
get theirs.

http://www.uwe-sieber.de/files/usbtreeview.zip

Paul


Here's the picture at: https://postimg.org/image/616vivcsd/

Den

Den wrote:
On Thu, 12 Jan 2017 16:39:27 -0500, Paul
wrote:

Den wrote:
On Wed, 11 Jan 2017 15:33:06 -0500, Paul
wrote:

Thanks for the information Paul. Hope this works.
The picture is at:
https://postimg.org/image/we0wukytf/

Those are the unknown devices. I made a copy of my registry in case
something goes wrong, and tried to delete those three as a possible
solution. But windows won't let me.

Den
So what we know, is it's something that formed "end-points",
yet the config space is pretty strange. A completely dead
USB device wouldn't register like that. Of course VID_0000 PID_0000
is not a valid value, and is not going to be in usb.ids file.

Now, take a snapshot of the window from this program
and post the URL to the results.

http://www.uwe-sieber.de/usbtreeview_e.html

The download is at the bottom of the page. Uwe occasionally shows
up in the WinXP group, so he knows about newsgroups. His program
is similar to Microsoft UVCView, only he has made it easy to download,
while Microsoft wants you to "go on a little adventure" to
get theirs.

http://www.uwe-sieber.de/files/usbtreeview.zip

Paul


Here's the picture at: https://postimg.org/image/616vivcsd/

Den


You have a Bluetooth nanoplug in one of the ports.

But I can't tell you what is going on, on the others.
The picture claims enumeration is failing. It got an
end-point, started communicating with some device,
and could not complete the communication before
something happened (bus reset, power fail, etc).

Check the Bluetooth device and make sure it isn't
shorting and/or overheating. I've heard of Bluetooth
plugs doing that (hardware failure of some sort).

The Bluetooth thing could be a stubby device like this.
Review what is plugged into your ports.

http://www.newegg.com/Product/Produc...9SIA6PF4837790

Paul

On Fri, 13 Jan 2017 13:36:33 -0500, Paul
wrote:

Den wrote:
On Thu, 12 Jan 2017 16:39:27 -0500, Paul
wrote:

Den wrote:
On Wed, 11 Jan 2017 15:33:06 -0500, Paul
wrote:

Thanks for the information Paul. Hope this works.
The picture is at:
https://postimg.org/image/we0wukytf/

Those are the unknown devices. I made a copy of my registry in case
something goes wrong, and tried to delete those three as a possible
solution. But windows won't let me.

Den
So what we know, is it's something that formed "end-points",
yet the config space is pretty strange. A completely dead
USB device wouldn't register like that. Of course VID_0000 PID_0000
is not a valid value, and is not going to be in usb.ids file.

Now, take a snapshot of the window from this program
and post the URL to the results.

http://www.uwe-sieber.de/usbtreeview_e.html

The download is at the bottom of the page. Uwe occasionally shows
up in the WinXP group, so he knows about newsgroups. His program
is similar to Microsoft UVCView, only he has made it easy to download,
while Microsoft wants you to "go on a little adventure" to
get theirs.

http://www.uwe-sieber.de/files/usbtreeview.zip

Paul


Here's the picture at: https://postimg.org/image/616vivcsd/

Den


You have a Bluetooth nanoplug in one of the ports.

But I can't tell you what is going on, on the others.
The picture claims enumeration is failing. It got an
end-point, started communicating with some device,
and could not complete the communication before
something happened (bus reset, power fail, etc).

Check the Bluetooth device and make sure it isn't
shorting and/or overheating. I've heard of Bluetooth
plugs doing that (hardware failure of some sort).

The Bluetooth thing could be a stubby device like this.
Review what is plugged into your ports.

http://www.newegg.com/Product/Produc...9SIA6PF4837790

Paul


I've remove the Bluetooth plug and uninstall software. It didn't
change anything on the USBTreeView. But I also notice possible
problems elsewhere in the tree.

I think my motherboard (Asus P5Q SE) is getting too old (5 yrs). In
the past, I always had Asus motherboards and they all failed after 5
years.

Thanks Paul for your help and very educating comments. I also
appreciate the new utilities you suggested that will be very helpfull
in the future.

This time I may try an other brand of MB
(I also be more prudent with attachements.... ;-)

Den

Den wrote:


I've remove the Bluetooth plug and uninstall software. It didn't
change anything on the USBTreeView. But I also notice possible
problems elsewhere in the tree.

I think my motherboard (Asus P5Q SE) is getting too old (5 yrs). In
the past, I always had Asus motherboards and they all failed after 5
years.

Thanks Paul for your help and very educating comments. I also
appreciate the new utilities you suggested that will be very helpfull
in the future.

This time I may try an other brand of MB
(I also be more prudent with attachements.... ;-)

Den

One other thought comes to mind.

Turn off the ATX power supply, and let the +5VSB drain.
Maybe leave it unpowered over night.

This is in case the chipset is merely latched up
and not damaged.

And you want that Bluetooth out of there as well,
until you power up the next morning and verify what
state the other USB ports are in.

I've not heard of Intel chipset going into
micro-latchup. They do go into the "incendary"
flavor of latchup, but that was ICH5 and some time ago.
P5Q SE is ICH10, and so separated quite a bit in time.

Paul

On Sat, 14 Jan 2017 11:10:48 -0500, Paul
wrote:

Den wrote:


I've remove the Bluetooth plug and uninstall software. It didn't
change anything on the USBTreeView. But I also notice possible
problems elsewhere in the tree.

I think my motherboard (Asus P5Q SE) is getting too old (5 yrs). In
the past, I always had Asus motherboards and they all failed after 5
years.

Thanks Paul for your help and very educating comments. I also
appreciate the new utilities you suggested that will be very helpfull
in the future.

This time I may try an other brand of MB
(I also be more prudent with attachements.... ;-)

Den

One other thought comes to mind.

Turn off the ATX power supply, and let the +5VSB drain.
Maybe leave it unpowered over night.

This is in case the chipset is merely latched up
and not damaged.

And you want that Bluetooth out of there as well,
until you power up the next morning and verify what
state the other USB ports are in.

I've not heard of Intel chipset going into
micro-latchup. They do go into the "incendary"
flavor of latchup, but that was ICH5 and some time ago.
P5Q SE is ICH10, and so separated quite a bit in time.

Paul


Hi Paul,

Same old usbtreeview. Not a single change.

Den