Unknown USB Device (Port Reset Failed)

I have a Asus Xonar U7 which faced the same problem.

It is totally a driver issue. I installed a driver updating software and it tried to update my AsMedia XHCI Controller drivers (to ver 1.16.26.1 dtd 6/3/2015 from 1.16.16.0 dtd 3/7/2014). This particular driver update was also causing a BSOD on Win 8.1 x64. Then I installed the default microsoft drivers using device manager by doing a "update driver" and thats when things broke down.

Rolling back the drivers to 1.16.16.0 immediately solved my problems.

SharePointIsNeedlesslyComplex  - My god, what an idiot you are. There was no ranting involved, just a kindly reminder that the user is depending on you to NOT pull a "Geek Squad" ("well, I can't figure it out, and I know everything so, we just wiped your system for you and reload from scratch"). However, in this instance, the news went one better (i.e. Worse) by telling the user, "not only am I incompetent for loading a new Operating System over your old one, without backing it up first or checking for known issues, but I did it KNOWING that there probably won't be any drivers available from the vendor and since, Microsoft, as a standard practice often substitutes generic drivers for the vendors ones (because the .Inf file doesn't show that it is compatible with the new OS), I am going to blame my incompetence on Microsoft instead of accepting full responsibility for screwing up your system ... Sorry about that.

Now, I decided that, instead of being that straightforward, I would explain why the events happened as they did, and suggested that, in the future, it would be far better to swallow your pride and ask someone else to look at it.

Now, you can continue to walk around with that stick up your butt, or you can stop thinking about yourself and your pride, and start thinking about your customer first. I will take a stab and suggest that the real source of the problem was that maybe the upgrade was initiated to cover up the fact that there was a problem with the previous OS and the attempt was made to "upgrade your way out of it". This is another very rookie mistake. NEVER do this until you know how to recover, and NEVER experiment on a user's system.

And BTW, what exactly would you expect Microsoft to do during an upgrade when they run into existing drivers that do NOT show support for the device in the new OS?  How should they handle situations where someone is upgrading a 12 year old computer, whose manufacturer has either been gobbled up by another company or went out of business?  Heck, manufacturers drop support for even 3-4 year old computers, motherboards and other devices.  So, should they not even attempt to get the device working?

I think they (Microsoft) has done an incredible job of getting things going.  The fact that someone puts the usefulness of another person's computer in jeopardy is not the user's fault.  Before 6 weeks ago, everything for Windows 10 was in Beta testing and any good technician knows not to subject a user's computer to a new OS (or Service Pack) until they have tested it out on a "non-production" computer.  If you fail to do this, then you deserve what you get.  However, I don't think your customers do, and I feel for them because they trusted you and you don't even have the guts to own the responsibility for your mistakes.

Sure you can always reload the operating system (an older one yet) but, as I said in my original post, you never learn anything by masking a problem.  You also risk losing the user's programs (can't find software or keys), their data and/or customizations by reloading the original OS and ... what if you can't find drivers for the old OS?  Then there's the fact that, your original intention was to move forwards but, you can't do that by going backwards.  If you are afraid of these problems, and your inability to work past them makes you unhappy, and you can't muster up the courage to ask someone else for help, then don't subject production systems to such idiotic scenarios, stick to stuff you know, or get out of the business.

To address your, "The fact is Microsoft drivers often suck" statement, no, they are generic drivers, designed to be more compatible than "tweaked drivers" the manufacturers often use.  Therein lies one of your problems.  These generic drivers are supplied by the OEMs ... to ensure compatibility with their products.  However, for example, if a 3rd party vendor takes a standard model of an ATI/AMD or NVidia graphics card (i.e. Asus, Diamond, EVGA, Sapphire, XFX, etc.) and alters it in a non-standard way, they will most likely need to create a special driver to handle the new requirements of the device.  This may very well make the card incapable of responding properly to generic drivers.

Over the course of time, this has been a quite frequent problem.  In fact, NVidia and ATI/AMD will tell you on there site to go to the original manufacturer of your machine, or in the case of a modified add-in card, go to the vendor who modified that version.  This is because even they can't guarantee the their drivers will work on a modified card, and using their generic drivers may cause incompatibility issues (even BSODs).  This again, is not Microsoft's fault.  So, get this in your head, once and for all, if Microsoft did not create the device, then Microsoft doesn't write the drivers for it.

However, if you do not understand these complexities, then the problems you run into are ones you caused, due to your own ignorance  Yes, sometimes we tech guys have no other choice but to try them, especially when support has been dropped for a device or the developer hasn't released new versions that are compatible with the new OS but, you can't blame this on Microsoft.  You are the one who chose to go there, so no one else is to blame but you.

Another part of the problem is that the UPnP codes for even altered devices are probably assigned by the original manufacturer and once the device has been altered by the 3rd party, they keep the generic UPnP code.  Unaltered devices should work just fine with generic drivers designed for that UPnP code ... they just won't be as tweaked.  Non-standard devices should be given new UPnP codes to avoid the problems you have been running into.  However, this is unlikely to happen because it would be cost prohibitive.

Normally, I don't mind teaching someone but, you have shown that you have an attitude problem, are too stuck on yourself, too unwilling to learn and too stubborn to admit when you are wrong.  You keep showing your ignorance, over and over. You aren't going to win here because, face it, you are speaking out of the wrong end of your body and have nothing useful to say.

Please go away because, nothing anyone says is going to convince you of anything because you are too close-minded waste everyone's time ... you will never learn anything.

One last thing, I was speaking to "NickBeardshall" in my original post.  No one was speaking to you at all.

This was actually meant as a response to Vijay B's post on May 16, 2013 - but also so others could see how to get around that specific issue.

If you can highlight the item by either tabbing or moving with your cursor keys to the item, you can always (once the item is highlighted) hit Shift+F10 (hold down the Shift Key and tap the F10 key) to bring up the properties window.    This also works for just about any item you can highlight on the Desktop or in Windows Explorer.

You obviously didn't read the subsequent post where i say that reinstalling windows 8.1 fixed the issue in the end.

But good job on your stupid rant.

The fact is microsoft drivers often suck. Always best to go to the manufacturer first. This whole issue was caused by microsoft drivers so what other evidence do you need.

Windows 10 has **** up even more drivers. If you have had to work on any windows 10 system, they are almost always driver problems after an upgrade. And yes most of the times it is  microsoft drivers that are the problem and we have to wait for the manufacturer to release an update to get things working 100%. Microsoft is not apple, its not a closed ecosystem that they control so there will always be edge cases. Always best to wait 1-2 years after an OS comes out, and some OS'es are never ready as VISTA and windows 8 can show you. Windows 7 is still rock solid. Windows 8.1 still has problems years later, such as graphical corruption, wireless disconnection and VPN issues. Sure not every machine has a particular problem, but that's the point. Its a driver issue.

Windows 7 drivers are as stable as windows 2000 was back in the day in my expert opinion on the matter. I see very little issues with win7 that are caused by drivers. It has been out for 6 years and it shows how mature it is as a platform now. I would have no problem recommending it over 8 or 10 still in 2015. no problem. Unless your using touch of course.