Que dudoso es todo esto. Hay un bug registrado sobre el "error comun" en donde aparecen 26 dispositivos usb conectados? Los numeros de serie de los dispositivos conectados se los invento windows o son dispositivos conectados previamente?

Con este programita ves cuando se conectaron: http://www.nirsoft.net/utils/usb_devices_view.html

Puedo ser perito y cobrar 40 mil pesos ahora?

I had a similar issue with unity games, left stick input even with everything unplugged. I ended up using usbdeviewx64 to find and kill any usb irq's still being used that I didn't need or that were duplicates.

Once I whittled down to only the currently used devices in the list, I launched a Unity based game and was able to play as normal. I believe Windows fucked up the USB assignment somehow when I connected my Xbox One Controller.

Just to confirm, I'm assuming that when you've connected your device that you unlocked the lockscreen, correct?

Within Storage settings, tap the menu icon to bring up the options to select 'USB computer connection', such as Media Device (MTP) or Camera (PTP). You'll want to use MTP for transferring files to/from your internal SDCard.

If this doesn't help, you can use USBDeview to view and manually cleanup the USB devices associated to your phone in case it is driver related:

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

It's a handy util that came bundled with Wugfresh's Nexus Root Toolkit which helped me cleanup and correct my Android USB devices when things got messed up, for whatever reason (i.e. managing multiple Nexus 5/7 devices).

I had this problem for a while, it turned out to be a USB 3.0 adapter inside my case that was loose - I used this tool to check when and what USB device was disconnecting.

Nirsoft's USBDeview

I use this program to determine what USB devices are randomly disconnecting. Prior to getting a dedicated USB card I had problems with my keyboard randomly disconnecting every 10 or so seconds.

I wont say unusual, rather handy: sysinternals suite

USBdeview to view, disable/enable, delete all USB connected devices

Does the system see it but Windows doesn't, or does the system not see it?

Use a tool like USBDeview, and see if it shows up: http://www.nirsoft.net/utils/usb_devices_view.html

That'll at least narrow down if its the PC, or the OS on it. Just make sure, under options, you turn on to show devices without drivers if you use USBDeview.

I've dealt with this so much I made a go to debug process that has worked anytime regardless of the error code.

1. install USBDeview
2. unplug everything USB or HDMI except your Vive and basics like M+KB
3. Uninstall all non green drivers in USBDeview (most are plug and play)
4. Uninstall SteamVR and disable or uninstall RivaTuner if installed.
5. completely unplug your Vive from the link box including power.
6. Uninstall all non green drivers that have appeared in UsbDeview.
7. hook up your linkbox and wait for fresh install to finish.
8. install SteamVR and run room setup again.
9. Celebrate the re birth of your Vive.

I can offer you two workaround solutions as honestly I wouldn't hold up any hope of the devs implementing what you're looking for.

There is a crafty piece of software called USBDview which will allow you control over the USB ports on an individual basis. This allows you to essentially kill a single USB port whenever you want to.

The other solution will cost you some dough as it involves buying yourself a powered USB hub with individual power buttons for each port on the hub.

Hopefully you can just use the software solution instead and save yourself some bucks. http://www.nirsoft.net/utils/usb_devices_view.html

Edit: I forgot to mention I have only used this on Windows 7 myself so if you're on W10 I don't know with any certainty if it will work just the same. Either way its worth a shot.

I won't give you the entire walkthrough, but your problem can be fixed as long as you can access fastboot. Simply install the relevant fastboot drivers and then proceed to run with flashing the relevant image using whatever toolset you're comfortable with (Android SDK, or the GUI toolkit. I suggest using USBDeview if you're having connectivity issues on the PC side of things. Have fun!

I didn't try with w10 but this program is the only one who can fix these problems (also with android devices and some mp3players).

Donwload it, start it and search for everything related to nokia/lumia/925/RM-892 and unistall them. Reboot the pc before plugging the 925.

Btw: I'm not 100% sure that usbdeview can fix your problem but it's one of the best for fixing usb problems.

only thing I can think of is using a third party utility to see if drivers are all gone, sometimes device manager doesn't clean out properly (also make sure you dl correct 32 bit and 64bit)

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

On your netbook, does it work reliably? I haven't kept up with CUE + steam issues and I'm away from my k70 RGB blue. maybe you can try updating firmware on kb from netbook?

I think you did, but did you try the following steps from this guide? It's pretty much applicable to any of the drivers you mentioned. I also recommend using USBDeview to remove old drivers.

I've been wanting to be able to shut off a single USB port due to a light on a button box that has no way to turn off...your post inspired me to look again I found this like 30 seconds before typing this. It looks promising.

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

I haven't tried it but this thread (where I found the app...from 2009 lol) the guy inquiring said it worked. Its been updated to work with windows 10 both 32 & 64 bit versions.

Download a utility called USB Devices View (usbdeview) at http://www.nirsoft.net/utils/usb_devices_view.html . This utility shows all of the USB devices that have ever connected to your PC. Delete all the entries that you see in the list. You may lose access to your keyboard and mouse momentarily, but a full reboot will bring them back, and your PC will reenumerate the rest of your USB devices.

Good luck.

You can use this utility to remove all USB drivers. After that, plug in the Vive again. The drivers are in the linkbox and will auto-install themselves. See this thread for more information on USB issues and hopefully it helps.

It depends on what the ducky is configured to do. If it exfils data, phones home, or does anything else on the network, then Wireshark might see it. Otherwise, probably not. Forensically, there are probably artifacts that you could look for. Dump memory and look at command history. You could also check Windows Event logs for things like powershell commands.

Lastly, I'm not sure what it shows up as, but check the output of USBDeview. It shows keyboards and other HID type devices. However, it shows a LOT of stuff. Much like the memory analysis above, if you don't already know what is good, then it makes it hard to find evil, and it makes everything unknown look evil.

The TL;DR here is that yes, there are a lot of ways to detect ducky type attacks. However, none of them are exactly easy. I think your best bet is USBDeview. Purchase your own Ducky and see what it identifies as when you plug it in. Download some of the ducky scripts and see what they look like in logs or memory when they're executed.

Installa questo, attacca il mouse e disinstallalo direttamente dal programma USBDeview; cancella ogni traccia del mouse che vedrai in quell'elenco, dai una riavviata e riprova

Good to know.

In regards to your USB issue: Download a utility called USB Devices View (usbdeview) at http://www.nirsoft.net/utils/usb_devices_view.html . This utility shows all of the USB devices that have ever connected to your PC. Delete the entries that correspond to your failed device, and try again.

I get this problem when I have too many device drivers installed on my USB ports (even if they aren't currently plugged in).

I used a program called USBDeview to delete old ones that aren't in use and it fixed the issue for me.

Edit: Program is actually called USBDeview --- fixed my comment and added link

I had this same problem. If your issue is that you're using a wireless controlled + a cord like someone suggested that's one thing. If you're using a wired controller and can't get it to work then you cna try this

Download a program called "USB Deview" Run it Plug in your controller and see what lights up in deview.. if it sees it as a controller GREAT! if not no big deal.. click on the thing that lights up.. right click.. uninstall. Restart machine with controller plugged in. Windows SHOULD see the controller and re-install the correct drivers.

For some reason this worked for me when just manually uninstalling from control panel didn't. I have no idea why.

Usb Deview is a kick ass tool. The download link is about half way down the page http://www.nirsoft.net/utils/usb_devices_view.html

In regards to your USB flash drive issue:

Download a utility called USB Devices View (usbdeview) at http://www.nirsoft.net/utils/usb_devices_view.html .

This utility shows all of the USB devices that have ever connected to your PC. Delete the entries that correspond to your failed device, and try again.

This technique has never failed me, it even fixed my dentist's USB reader for X-Rays.

First try a different cable. If that still doesn't work, try this: At your own risk, you can use the USBDeview utility to view all the USB devices currently and previously connected to your computer. Look for all the items that are related to your phone (Nexus 6, Android ADB Interface, Android Composite ADB Interface, etc...) and uninstall them. Your computer will recreate these when you plug the phone back into the computer.

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

Have you used USBdeview to remove all Android/HTC/Google/Samsung related usb devices, then remove usb RSA authorization before plugging the device back in?

Make sure you create a windows restore point before using USBdeview. If you break windows without a restore point remember that you get to keep the pieces.

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

Cool, the tool mentioned is here, the one I linked is really barebones, but small. This other one seems more complete.
USBDevicesView from Nirsoft seems useful too! here

Run USB Deview as administrator, find the device, right-click and uninstall it, then unplug it and plug it back in. Should give it afresh install and hopefully solve your issue!

I'm getting these intermittent messages for HDMI connector but the pins appear fine. I do notice my other USB devices sometimes go missing. I'm suspecting the Rift is reporting HDMI connection lost when it loses USB power. Try installing USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html). You should see Rift, Rift Audio, Rift Sensor when all are working. If you are only seeing Rift Sensor, disconnect your other USB devices and or change the Rift USB to another hub.

After doing some research, I have another suggestion for you.

Using NirSoft USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html), together with the vendor ID file (usb.ids, available on the same URL), it's very easy to find the joysticks as USB devices and uninstall them.

Try uninstalling them, then replugging them in the correct order.

On my machine, I see 6 entries for the two joysticks I have. 2 from the time they were plugged in directly, 2 from the time they were plugged in the hub in the incorrect order and 2 for now when they are in the USB hub correctly. As expected.

I just posted this in another topic and it looks like it might be helpful here:

>Since it's looking like the issue may be connected to USB and/or associated drivers you may find this utility from Nirsoft helpful: USBDeview

>Among other things it lets you remove a USB device, forcing Windows to rediscover it the next time it's plugged in. Once Windows has discovered a device and found it's drivers it'll continue to use those same drivers every time that device is plugged in. So if the driver is corrupt it keeps loading the same corrupt driver.

>Using USBDeview you can highlight any USB, right click, and select "Uninstall". Then Windows will have to reinstall the appropriate driver.

So make sure the drive isn't connected, look for the entry related to the external drive, right click, choose uninstall. Now cross your fingers and plug the drive back in.

Edit: The link for USBDeview didn't come through: USBDeview.

Powershell ?

Some creative trickery with USBDeviceView ( http://www.nirsoft.net/utils/usb_devices_view.html ) and/or Sysinternals "psexec" ?.... (pipe the output to a TXT file and remotely-parse that ?)

Just random ideas...

Before reinstall drivers, use usbdeview to delete all the entries about Nokia/lumia/rm-xxx ecc. and reboot pc and phone

Lumia 909 is 1020, 909 was the rumored name, as you can see here

Download and start this program, open it and connect the 1020. If 1020 shows up, unistall it (and unistall everything related to nokia), reboot PC and phone and try again.

Download Nirsoft's USBDeview. Run it and ID the MP3 player then delete that line. Windows remembers each device, and it's settings, that have ever been plugged into a USB. Removing the MP3 player's reference in USBDeview will force Window to recognize it as if it's never been connected.

I would highly recommend the SCP Drivers, far better than Motioninjoy.

Note that if you have used Motioninjoy in the past, you'll want to remove the drivers for it, check out USBDeview, that'll help you take care of it.

Agree with all. The moment windows recognizes the device registry changes begin to occur. See tools: http://www.nirsoft.net/utils/usb_devices_view.html http://www.woanware.co.uk/forensics/usbdeviceforensics.html

If you're on Windows.. you could use a program like USBDeView = http://www.nirsoft.net/utils/usb_devices_view.html ... which might give you an indication if the e-cig is broadcasting it's HID (Hardware ID) to the Computer. If it is.. then it's probably using all 4pins and not just 2 for power. (NOTE:.. I don't claim to be any USB-expert)... I have worked in the IT field for about 20 years.. but would never claim to "know everything" by any stretch of the imagination.

I had this problem I fixed it by using this software to uninstall anything related to nexus 4 and adb

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

then I used wugfresh to reinstall the nexus 4 drivers

http://www.wugfresh.com/nrt/

Hope you get the problem fixed I know the frustration

Here's a low-tech way of figuring out if the user has used any flash drives. If you have a policy that states users aren't to use personal devices on the corporate network, this could help. You can run it remotely against their machine: http://www.nirsoft.net/utils/usb_devices_view.html#DownloadLinks

Uninstall the drivers and just plug the nexus 4 back in. Google: USB usbdeview to uninstall the drivers.

Edit: Here's the link the download should be near the bottom

Try clearing the USB Device cache to delete all cached drivers for current and previous devices.

Or you can selectively delete the drivers you wish (like the one for your mouse) using this software.

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

A few folks suggested that if you don't know what you're doing, don't bother trying, as this is dangerous territory. A counterpoint to that: if you don't try, how will you learn?

The Nexus 5 has a ton of developer support and is relatively easy to root compared to other phones. I say give it a shot - worst that can happen is you brick it, and a new Nexus 5 will set you back $350. More likely than that, though, is you might need to factory reset your phone, which is really a piece of cake.

There is no simple guide that tells you everything - it's just not a simple process. Here are some tips:

• Start with a backup of your phone. Titanium Backup is the common go-to app for this.

• Before you plug in your phone and begin, delete any Nexus drivers, Google drivers, or drivers from previous phones from your computer. They might interfere with your process, and if/when they do, it can be very frustrating. This tool helped with driver deletion: http://www.nirsoft.net/utils/usb_devices_view.html (note: comes with WugFresh's tool, below)

• Download this for Nexus 5 drivers: http://koush.com/post/universal-adb-driver

• Root requires an unlocked bootloader, and unlocking your bootloader wipes your phone in the process (this step is built in for security reasons). Unlocking your bootloader is as easy as downloading a ZIP, extracting the files, and running a program from the command line provided you have the right drivers.

• WugFresh's tool worked for my root, but I had to call an audible and switch on/off MTP storage several times during the process for the tool to its job, as well as guess on a few steps. It was not as easy as advertised, so I can't recommend it.

Good luck.

USBDeview

100k of original awesome. It is a great little prog that shows you all your USB devices and allows you some utility with them. Uninstall USB devices is my favorite function.

Nirsoft has a utility, USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html), that allows you to see the various USB devices that have been connected to Windows.

Windows "remembers" every device. What I'd suggest is run the utility, then plug in the device. ID in USBDeview which entry is for it, then uninstall that entry through the utility. You may have plug and unplug it a few times in order to spot which one is the problem drive, there will probably be a LOT of entries.

That will force windows to recognize it all over, as if it's never been used on that machine.

If that fails, go with the previous suggestion of Testdisk.

I would remove usb devices from device manager (including hidden) and then restart and see what happens. It looks like the devices are receiving power, so may not be hardware related. However, if the power is fluctuating because of degradation then this could be very bad for your hard drive plugged into it. (I have never seen a usb port do that, but your description sounds a bit peculiar, so you never know)

Even though this issue sounds like hardware failure, I am leaning towards software. The fact that your disk spins up intermittently is strange. For shitz you can consider malicious activity. Try ariad.exe from Didier Stevens Ariad is a nice tool for protecting and mitigating usb executing code.

There is also USB Deview which is another handy USB tool to add/remove hidden usb devices.

I find using the freeware Nirsoft USB Device View quite helpful when dealing with broken usb drivers. It allows you to delete or reset the drivers. Here is the description from there Webpage.

Description

USBDeview is a small utility that lists all USB devices that currently connected to your computer, as well as all USB devices that you previously used. For each USB device, extended information is displayed: Device name/description, device type, serial number (for mass storage devices), the date/time that device was added, VendorID, ProductID, and more... USBDeview also allows you to uninstall USB devices that you previously used, disconnect USB devices that are currently connected to your computer, as well as to disable and enable USB devices. You can also use USBDeview on a remote computer, as long as you login to that computer with admin user.

This is a really interesting question, and I've just sunk the last hour into Google. I thought there must be some utilities out there that cater for this by spoofing hardware IDs or just applying aliases or something, but nope! I've come across people using a similar setup to you for public installations, or using an array of gamepads as controllers for live music performance, and they're all faced with the same problem. Each time they boot their systems, they run through a procedure of connecting & testing one device at a time to establish which is which. It's madness.

I came across an interesting free utility called USBDeview, which won't solve your problem but does give you a little window into the USB devices on your system. Definitely worth a peek.

Another free utility worth looking at is HID Macros. I use it at work to map keys on a USB numpad to multi-key commands in AutoCAD. The handy thing about HID Macros is that it identifies devices based not only on the hardware ID built into the device, but the port they're plugged into. That means that four identical devices can be given their own names.

But these handy names are only seen within HID Macros itself - so your emulator is still going to see four of the same device. To make it work for you, you'd have to map all your emulator functions to the keyboard, then use HID Macros to map gamepad functions to those keys. So your gamepads would not be controlling the emulator directly, but through HID Macros.

To be honest, the way you're doing it now is probably less painful.

You can test drives/readers on Windows with usbdeview by looking at the Power column and looking for devices that draw under like 200mA.

--

My go-to has always been these type of little microsd readers that draw like 120mA (or 150mA for ones from a later run/revision that used slightly-transparent plastic).

--

Sadly they're from years ago...back when they were plentiful and flooding every China/etc seller, they used to be like 99c shipped...but nowadays they're just silly-priced :/

Easy way:

Get USBDeview - http://www.nirsoft.net/utils/usb_devices_view.html

Run as admin - otherwise you don't get the disconnect time populated

If you leave it running, there is a column on there to sort by time (Disconnect Time)

When you hear the mysterious unplugging going on the item will be at the bottom/top of the list if you re-sort it by time again ;)

Does anything else work in that port, or is it just the X56? Have you added any other USB devices recently?

Sometimes, Windows USB devices get "stuck." It usually happens if you have had power or other issues that caused the computer to shutdown abnormally. I had the same problem with my X56 a while ago and this worked: If you can eject the X56, do so , and then unplug it. Power down the computer and then unplug the power supply. Leave it sit for a minute or two. This allows all the power caps to drain and totally reset. Plug the computer back in and reboot. Plug the X56 back in and test. It should work after this.

You can try using USBDeview to locate and remove the device if it has somehow gotten "stuck." After you reconnect, it should work.

I assumed this was a newer Windows - I'm not terribly familiar with XP but you may have luck by looking at the Plug and Play manager logs which on XP are apparently here...

\Windows\setupapi.log \Windows\setupapi.log.old

That page also lists this tool that may be useful (and works on XP.)

Try plugging the fans into the motherboard fan headers instead of the hub,if you can, and see if they works that way. As for the Corsair h100i, make sure the USB is plugged in properly. You can download http://www.nirsoft.net/utils/usb_devices_view.html to see if the USB is recognized, Corsair devices have an id of 1b1c.

There’s no way that I am familiar with, would love to find out otherwise.

If it was USB there are applications that will do that. I like USBDevView: http://www.nirsoft.net/utils/usb_devices_view.html

Have you updated all drivers like chipset etc from your motherboard website page?

Turn off all overclocks on cpu gpu and ram (you can try restoring bios to defaults too to see if it helps). Use DDU to uninstall Geforce experience and all drivers. Reinstall only the latest driver without Geforce experience for now. See if it still crashes.

Also this program might be helpful to see what keeps getting disconnected: http://www.nirsoft.net/utils/usb_devices_view.html

Wild guess buy I think it might work:

Uninstall Viveport or any other HTC software if you have those installed, unplug the Vive, uninstall SteamVR, then use this utility to uninstall all non-active USB drivers:

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

Then install SteamVR and then plug in the Vive.

Put SteamVR back in Direct Mode. You want that. After that, close SteamVR

Next, let's try reinstalling USB drivers as that tracking drivers issue is a good clue. Unplug the link box from the graphics card and disconnect all USB devices except a mouse and keyboard. Then download this utility (it's a trustworthy utility) and run the exe as administrator. Select all USB drivers except those in green, which are in use, and uninstall them. This will remove all plug-and-play devices, forcing them to reinstall again. Then close the utility. Disconnect the Vive from the linkbox, ensure that the link box has incoming power, then connect the link box's USB to the USB 2.0 port on your motherboard. Wait for any drivers to install. Then plug in the Vive to the orange side of the link box. Wait for the multiple drivers to install. Then connect the link box's HDMI directly to your graphics card. Launch SteamVR. Did it work?

When drivers go corrupt I have had a lot of luck with a little tool called USBDeview (scroll WAY down the page for the download links).

Just install USBDeview then open it and find the drivers you are having problems with. Right-click and "Uninstall Selected Devices". A restart after uninstalling the driver(s) might be a good idea.

Now plug in the device and Windows should reinstall the drivers and hopefully they work as they should.

Try one of my previous comments:

I've dealt with this so much I made a go to debug process that has worked anytime regardless of the error code.

1. install USBDeview
2. unplug everything USB or HDMI except your Vive and basics like M+KB
3. Uninstall all non green drivers in USBDeview (most are plug and play)
4. Uninstall SteamVR and disable or uninstall RivaTuner if installed.
5. completely unplug your Vive from the link box including power.
6. Uninstall all non green drivers that have appeared in UsbDeview.
7. hook up your linkbox and wait for fresh install to finish.
8. install SteamVR and run room setup again.
9. Celebrate the re birth of your Vive.

Looks like you got hit with the typical Logitech shitty drivers problem after a silent/slight windows update.

You can either....

A1: Remove the Logitech software first

A2: Remove the busted ass HID drivers from device manager

A3: Clean up the registry files, reboot the computer & pray it senses the mouse

OR you can...

B1: use Nirsoft usbDriver (http://www.nirsoft.net/utils/usb_devices_view.html) & redo the entire clusterfuck known as Logitech drivers yourself. If you chose option B, I hope you know what you are doing & have system restores plus multiple backups.

You can really, really, really, fuck your computer up with option B but I was able to sucessfully get both my G602's working again & the one computer that does not recognize it I have the USB ported forwarded via LAN (7575) to the PC I want to use it on.

Try either of those, but IMO just but a new mouse that is not Logitech

Download a utility called USB Devices View (usbdeview) at http://www.nirsoft.net/utils/usb_devices_view.html . This utility shows all of the USB devices that have ever connected to your PC. Delete all the entries that you see in the list. You may lose access to your keyboard and mouse momentarily, but a full reboot will bring them back, and your PC will reenumerate the rest of your USB devices.

Good luck.

You might try to remove existing drivers which may interfere with a tool like that before doing a clean wipe. http://www.nirsoft.net/utils/usb_devices_view.html Or you might try following this example: https://www.faqforge.com/windows/uninstall-usb-drivers-on-windows-7/

Unplug the Rift and Sensors, download USBDeview from HERE , run it and remove all the inactive USB drivers.

Start over from scratch. I had this problem when I first installed my Rift, and even though it's showing as a HDMI issue, this sorted my problem. I was desperate, I would try anything at the time.

Even if it doesn't work, at least you'll have cleaned out all your unused USB crap.

I had a look at the device manager and can't determine which it could be, however I used USBDeview, and that clearly list devices as 'HTC Vive' in green if active/plugged in. Just right click and 'Uninstall Selected Devices'

Sounds like Windows being Windows. Unplug as many USB devices as you can (minus the mouse) and use USBDeview to remove all known USB devices from your system, then reboot and plug everything back in. This won't uninstall any device drivers, but rather "reset" your USB ports, as far as Windows is concerned. You'll see the normal "Windows is installing your device" popup near the taskbar when plugging everything back in. Sometimes, random shit happens and causes Windows to refuse to accept certain devices in certain USB ports, so this is basically giving you a fresh start.

If the machine's old enough to have USB 1.1, released 20 years ago and replaced by USB 2 in 2000, then it's entirely possible the issue's with the PC.

There are a few other things to check though, besides trying it on another PC. What's the make/model of the drive?

Also, Nirsoft has a utility called USBDeview that lets you look at the history of the USB ports. The first time a device is plugged in Windows searches for and installs the needed driver. It then stores that info so it doesn't have to do the search each time it's plugged in.

USBDeview lets you see that stored info, and remove it. That forces Windows to rediscover the device.

Run the program and look for your drive. It may be listed with it's name, or just "Mass Storage Device". If you sort the results on the "Connected" column it'll bring things currently plugged in to the top. If which one is the drive isn't obvious you can plug/unplug it and see which device changes from connected to unconnected.

Once you've ID'd the drive, unplug it, right click the line for it and choose "Uninstall Selected Device". Now plug the drive back in. Windows will show the "new device found" notice and reinstall everything.

If there was a problem with the drivers this should fix it. It's a long shot but worth trying.

Edit: Btw, USB 3 ports have a blue connector. If you look at the connection and see blue inside it it's USB 3.

Sometimes it is a pain in the ass when a USB device is disconnecting and reconnecting every 10 minutes or so. So I use 'USBDeview' http://www.nirsoft.net/utils/usb_devices_view.html. To easily see what USB devices are connected and others that have conneted but are not currently plugged in. When a device looses connection USBDeview stops showing the device with a green background. I have found that a Xbox 360 controller does not like to be plugged into a USB hub and instead I have to plug it in directly to a USB port on the back of the motherboard. Also a highly likely scenario for USB trouble is if a USB hub is being used that does not have its own power supply to feed power hungry devices like smartphones, tablets etc.

In regards to your USB issue: Download a utility called USB Devices View (usbdeview) at http://www.nirsoft.net/utils/usb_devices_view.html . This utility shows all of the USB devices that have ever connected to your PC. Delete the entries that correspond to your failed device, and try again.

In regards to your USB flash drive issue: Download a utility called USB Devices View (usbdeview) at http://www.nirsoft.net/utils/usb_devices_view.html . This utility shows all of the USB devices that have ever connected to your PC. Delete the entries that correspond to your failed device, and try again.

In regards to your USB issue: Download a utility called USB Devices View (usbdeview) at http://www.nirsoft.net/utils/usb_devices_view.html . This utility shows all of the USB devices that have ever connected to your PC. Delete the entries that correspond to your failed device, and try again.

If you can't find the entry you need to remove for sure, disconnect all of your unnecessary devices and remove all of the entries marked "safe to remove" and then try your "failed" device(s).

At your own risk, you can use the USBDeview utility to view all the USB devices currently and previously connected to your computer. Look for all the items that are related to your phone (Nexus 6, Android ADB Interface, Android Composite ADB Interface, etc...) and uninstall them. Your computer will recreate these when you plug the phone back into the computer.

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

For the ~1 second pauses, I seem to have got rid of them. It's one of two things, though I haven't tested to see which.

• Installed USBDeview which allows you to see much more than device manager shows - was able to disable anything Xbox-related and just leave the one for DS4Windows running.
• Went into Geforce Experience and completely disabled the overlay - including the little thing that pops up and says to press Alt+Z for sharing and stuff.

Did those two things last night before bed. Played an hour or so this morning with no hiccups whatsoever.

For the framerate drops, I'm less sure - some areas are just a bit busy with particle effects and stuff and even though your rig is beefy as hell I think they're just not terribly well optimised :( Keep an eye out though for if they happen while the "saving" flame is in the top-right as I do recall some folk having issues with the game running on an SSD back at launch.

Good luck :)

EDIT: Reason I'm still using DS4Windows is that, for some reason, DS3 doesn't play well with Steam's inbuilt DS4 support - keeps seeing the right stick as a mouse, even though it's been configured as a controller in the Big Picture Mode control settings. I'd much sooner ditch DS4Windows altogether so if anyone happens to know a way around the jankiness I'm getting from using the Steam native support then I'd love to hear it :)

I used this program to see what has the Xbox 360 driver, and disabled it.

I use the wireless reciever so it's in a different section, but if you use a wired controller, maybe try to enable one at a time to see which one is the real one.

Also, I know I'm 21 days late, but I just saw this thread and your comment today.

If its accessible to the OS, then in theory an application could make use of it.

For instance this reads and display all USB devices that are <em>or have been</em> connected and if they have a serial number it displays that as well.

Importantly, this information does not require admin privileges to view, so conceivably any application can pull this info and do whatever it likes with it.

edit: I just realised you meant can Windows work out what accounts you have. Yes, depending on how the account information is stored. If it is stored in the registry, then yes, windows (and anything else that can read the registry) could pull that info. At the very minimum, assuming your account name is stored encrypted within a programme data file instead of the registry, then at minimum the OS knows the client is installed.

I don't use Steam personally, but I don't believe your credit card info is stored locally, it will (hopefully) be tokenized and encrypted on the Steam account servers, so the OS (and by extension other applications) could not get at that directly.

At a certain point you have to point at least a level of trust into the OS, as the OS always has ways of getting at anything/everything stored on the computer simply because everything on the computer runs through the OS.

Solved my problem. With the help of USBDeview I uninstalled all the SC devices, unplugged & replugged the dongle to let them install, and then was able to pair the controller to the desktop.

I think the takeaway lesson here is when reinstalling windows, unplug your SC dongle first.

Try running USBDeview (scroll way down for the install link) to uninstall any corrupt or unidentified drivers. Unplug the USB cable before uninstalling. Right click > Uninstall Selected Device

Then plug in the USB and see if it installs it correctly.

So after many attempts and reading a bunch of forums, I think I've finally found a fix that works.

I had been using SDI (Snappy Driver installer) to get the lastest drivers.. (which isn't always the best approach) but i experienced mixed results with that. Sometimes things would work OK, but then next update, usb would just blow up again. I went through all the power management tabs but still nothing.

Finally, I found Driver Explorer, which allowed me to see all the drivers loaded on the machine. And I found that there were many cases of multiple drivers of different versions being held by the OS. So, i deleted all the duplicate drivers and have not had a USB controller reset since.

https://driverstoreexplorer.codeplex.com/

also helpful

• http://www.nirsoft.net/utils/usb_log_view.html - usb log viewer
• http://www.nirsoft.net/utils/usb_devices_view.html - usb device viewer

USBDeview will tell you.

Download and run (no installation required) with your HDD connected, and sort on the connected column. Identify your drive and scroll across to the USB Version column.

Sounds like the drivers for your USB stick have got themselves in a pickle.

Download and run this on your PC - USBDeview from Nirsoft (http://www.nirsoft.net/utils/usb_devices_view.html)

Sort the results by Device Type and scroll to the Mass Storage devices. Identify your "faulty" drive (the description column should help here), right click and select "Uninstall Selected Devices".

A reboot shouldn't be necessary but might be prudent. Reconnect your drive and the device drivers will re-install. Cross your fingers and test your drive.

Good luck!

I ran into this same issue & believe I've solved it once and for all. I have an Asus z97 Deluxe USB 3.1 motherboard with no added USB cards. I, like many others, thought USB plug-and-play was a solved problem & have used 2.0 hubs in series for years with many added peripherals.

I solved this by first understanding the nature of the problem on my particular system. Given the discussion in this thread it seemed that the USB 3.0/3.1 controller was unable to deal with the number of connected devices I had. In order to understand how this manifested on my machine, I used USB Device Tree Viewer here: http://www.uwe-sieber.de/usbtreeview_e.html This lead me to discover that my 3.0 controller was connecting the majority of my devices. (You can see this here: http://imgur.com/ZKirUVE ) The viewer in conjunction with my motherboard manual allowed me to understand which USB plugs were associated with which controller visible in the tree viewer. I noticed that the "ASMedia USB3.1 eXtensible Host Controller" had only 4 ports, all of which were unused. Using my motherboard manual I figured out which USB ports were associated with this controller, then I picked one. Then... (not sure if this step is necessary), I used this tool: http://www.nirsoft.net/utils/usb_devices_view.html to select-all my devices and "uninstall" them, then I rebooted - letting Windows 10 re-install all connected devices.

I'd expect that following the above steps with a bit of trial-and-error would guide anyone having this issue to a solution unique to your motherboard, USB controllers & attached peripherals.

There is a program called "USBDeview" . Download and run that.

When it runs you want to check to see what is plugged in.. does it show your Yeti? If not try unplugging it and plugging it back.. can you see anything else lighting up and disappearing? If it DOES show your yeti, unplug it.. right click... uninstall.. then plug it back

The other thing you can try is unplugging everything usb and then "uninstalling" everything and then plugging them back 1 by 1 and watching them load.. if when you do this with your Mic, making sure you are using a good usb port nothing lights up then there's a good chance it's hardware related.

Edit: When I say uninstalling everything.. I mean in usbdeview.. not in windows.. it'll all auto install when you plug them back.

I have found a little program which enables you to enable/disable any usb port. It seems to work perfectly and no need to physically unplug the joysticks. It could do with a filter as it displays ALL ports! Need to experiment more.

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

Since they are having the same issue on other apps I think that rules out Discord as the issue, so have your friend:

1. Test if it's the mic: find or buy a different mic and see if the issue persists on the new mic.
2. Test if it's the jack: if aux have them plug in their mic on the other (mobo/front panel) mic jack. If USB then have them delete the device in USBDeview and re-connect their mic.
3. Seriously check the OS settings, Windows (depending on the driver controlling the mic) may have several options to control the overall volume.

and don't be an ass to someone just trying to help.

[edit:] hold on, I just re-read your post and you tried to plug it into a usb charger and it wouldn't come on? RIP Blue.

Here's a few things you can try.

unplug the mic and run usbdev. delete everything not attached at the moment.

The download link is near the bottom of this page. http://www.nirsoft.net/utils/usb_devices_view.html

You can read everything,... or you can just download, run, and delete everything relevant cause that's what you're going to do anyway.

In the audio control panel, make sure your default recording device defaults to the mic. do this first, of course.

Last resort, in the control panel device manager, delete everything usb and reboot.

I had the same problem tonight. It turned out to be my G15 keyboard causing the issue.

My solution:

1) disconnect all usb devices other than keyboard and mouse. This includes the vive.

2) Use USBDeview to uninstall everything other than my keyboard and mouse.

3) Reboot

4) Plug the vive back in.

5) Reset the controller

6) Re-pair the controller

7) All was well at that point and I could play.

Another potential issue is with USB 3.0/high speed charging ports. Have seen several instances where anything other than a vanilla 2.0 port causes this issue.

Try using USBDEVVIEW,

"it is a USB utility that can be used to remove old USB device records from Windows. Removing these records can help with certain situations with SteamVR does not recognize your HMD or controllers.

Download USBDEVVIEW from the link on this page http://www.nirsoft.net/utils/usb_devices_view.html and unzip the archive.

Turn off the HMD breakout box and unplug the controller dongles.

Launch USBDEVIEW

From the Options menu turn on "Display disconnected devices".

Sort the list by VendorID.

Find the items marked as VendorID 28de and select them all.

Right click on them and select "Uninstall selected devices". If you turned off user account control (UAC) this should work promptly otherwise you will have to say yes to a dialog for each one.

Quit and reboot your PC.

Turn on the HMD breakout box. Wait for Windows to install the devices. Make sure that the 2nd display shows up in the Displays control panel.

Run VR Monitor and make sure it recognizes the HMD.

Turn on your controllers. Wait for Windows to install the devices and make sure VR Monitor shows them"

EDIT: Also try to remove any device that you are not using. I have seen compatibility problem with USB device and software like Razer product and Razer synapse.

I have had luck using USBDeview a few times when USB drives become corrupt.

Don't have the phone plugged in when you run it.

Right click the Samsung entries and uninstall them then plug in the phone/usb and the computer should install a new driver.

You can also uninstall any "unknown" entries. One of those could be the culprit as well.

> USBDeview doesn't require any installation process or additional DLL files. Just copy the executable file (USBDeview.exe) to any folder you like, and run it.

> The main window of USBDeview displays all USB devices installed on your system. You can select one or more items, and then disconnect (unplug) them , uninstall them, or just save the information into text/xml/html file.

If that fails to work, you're going to need a utility called USBDeview. Here's a handy link. Note that you MUST use the x64 version for 64-bit systems. Use of the 32 bit version will break things.

You need to disconnect, uninstall the device and driver association forcibly, reboot, and reinstall CAM. But I don't know what the device or driver is for Grid+ so you'll have to do some sleuthing.

THE FOLLOWING IS ENTIRELY UNSUPPORTED. PERFORM THESE STEPS AT YOUR OWN RISK.

In all seriousness though, this is really low risk. But you do have the potential to blow up your operating system with it. So you're on the hook if this goes wrong and neither I nor NZXT can help you.

1. Unzip USBDeview into a folder on your C: or D: drive. It must be on a system drive.
2. Right click USBDeview.exe and Run As Administrator.
3. Select the broken device (I don't know what the NZXT Grid+ identifies as but it may be NZXT.)
4. Select any other devices with the same Driver Filename and same USB\VID_xxxxstring in Instance ID.
5. Under File select Disconnect Selected Devices or press F9. This ensures the OS recognizes them as disconnected.
6. Under File select Uninstall Devices - this removes them completely from the OS.
7. Reboot and wait for Windows to re-detect and reinstall the drivers.

WARNING: IF YOU UNINSTALL A USB KEYBOARD YOU MAY BE UNABLE TO LOG ON WITH ANY USB KEYBOARD!

This will probably solve close to 90% of the issues with CAM not installing drivers or not detecting any NZXT devices after you move them. However, if you do it wrong, you can completely break your OS. (Accidentally removing a disconnected device will almost never cause issues though. You'll just have to reinstall the driver if you connect it again.) But it will always be an at your own risk procedure.

I'd uninstall LGS, usbdeview (http://www.nirsoft.net/utils/usb_devices_view.html)to remove the USB driver, reboot.... install an older LGS version(ftp://ftp.logitech.com/pub/techsupport/gaming/) . I use 8.70.315 You can edit the resources.xml to help with the auto shut off. These instructions can be found in this sub as well.

1. try to remove all usb drivers for card readers with this free tool http://www.nirsoft.net/utils/usb_devices_view.html

sometimes old drivers get stuck and then os try to use wrong one

1. sometimes mapped drives dont allow to mount card ... try do unmap ... it happed to me

Using USBDeview to remove all old ADB/MTP/Android drivers has helped me a lot.

Usually I end up grabbing the driver folder out of Android SDK and modifying the .inf myself with the hardware IDs of my new phone, pulled from Device Manager.

Since it's looking like the issue may be connected to USB and/or associated drivers you may find this utility from Nirsoft helpful: USBDeview

Among other things it lets you remove a USB device, forcing Windows to rediscover it the next time it's plugged in. Once Windows has discovered a device and found it's drivers it'll continue to use those same drivers every time that device is plugged in. So if the driver is corrupt it keeps loading the same corrupt driver.

Using USBDeview you can highlight any USB, right click, and select "Uninstall". Then Windows will have to reinstall the appropriate driver.

I have an ATR2100 that worked fine before and works fine now. The only issue is sometimes windows decides the headphone jack is the default speakers.

Also, if you have a webcam with a microphone might be the default microphone.

It seems pretty bulletproof if you have 1 and only 1 mic attached to your computer.

The bluemic is pretty good, I'm surprised you are having problems. Have you checked your recording devices for any mics that shouldn't be there, or if it's been disabled? Also, some USB parts do not like going through hubs. Plug it directly into the MB.

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

I can't remember for sure if Corsair came with a dedicated drive or has had a recent firmware release/upgrade. I known it has utility software and firmware; it's also standard usb3 (usb2 back capt) attachment.

Here's what I would do:

1) Go to Nirsoft and get the portable USB Devices View. With the keyboard plugged in, run devices view and find out which hub it's using. Then unplug the keyboad and delete that hub assignment.

2) Either see if you have the drivers and firmware, or go to Corsair, enter you model, and get them.

3) Plug your keyboard back in to the same, or any usb port, new assignment now, and run driver updates and firmware.

4) Restart

It sounds like the USB drivers are corrupt. Run USBDeview on the computer. (Scroll down the page for the download links). Find the Samsung drivers and right click > uninstall. The description name should be something like "SAMSUNG Mobile USB Composite Device"

Be sure the phone isn't connected to the PC when uninstalling the drivers.

Now connect the phone and see if you can find it.

Last i checked a fastboot cable doesn't exist for the 8.9, only the 7. What happens when you plug in the device to a computer when it's showing the recovery screen? Is it detected as anything? You might have to get a USB monitoring program (USBDeview is a particularly good one). If it's at least detected by the computer then there's a chance it's in a mode that will allow you to repair it.

Install USBDeview and remove anything and everything that looks like it might be related to Samsung or the S5.

What the program does is remove the entries for the device from the registry so your computer will "re-discover" the device when plugged back in. There can/might be multiple entries due to having multiple USB ports on your computer. Nuke them all.

EDIT: Here's the latest USB driver I could find. I'm actually using v1.5.42.0 but this one should work too.

If you're on 8.1 the phone must be recognized.

So, download and install this ; open it, search for nokia device/lumia device/MTP device or everything related and delete it. Reboot your pc and try connect your phone.

If it's not working, do again the clean, reboot and change usb port.

If this doesn't help install Microsoft SDK.

Maybe you've already tried this. But NirSoft USBDeview v2.40 will show all the drivers installed by the USB devices that have been used on that computer and will let you uninstall them. Maybe you could uninstall some of the "weird ones". I had a USB DVD burner plugged in to my laptop and all other USB devices wouldn't show up when plugged in. I uninstalled the USB driver for the DVD burner and all was good again.

This worked on my note 4 when I did exactly the same thing. Remove all phone related USB drivers with this http://www.nirsoft.net/utils/usb_devices_view.html install these drivers http://www.koushikdutta.com/post/universal-adb-driver

Might be because of a Windows 8.x update by Microsoft of mtp driver. Causes this issue a lot. Search function in your reddit app for tens of topics same problem.

Out of my head- but search anyway to be certain !!!- remove driver via device manager, re-install driver. But sometimes special application was necessary to remove conflicting driver: http://www.nirsoft.net/utils/usb_devices_view.html

Use this tool remove the drivers completely, anything with the name samsung and then plug in your S3 to your PC. if the drivers don't install properly try a different cable.

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