windows 10 Android USB Device Failed Enumeration - Error Code 43 on Windows 10

[geeteam]

Not here to talk much, but this issue have been in existence since Windows 8. And it's still happening in Windows 10 even with the recent build (11082.1000).

Am an insider and I have reported the case via Windows Feedback app, Tweeted Windows Insiders and Gaul but no responds.

I have searched on all other forums I know but nothing better has come out of it.

But since I have trusted Nsaners to provide fast and quick and reliable solutions. I thought of sharing it.

 

I don't have to explain further, I found similar post related to the same issue on Microsoft Technet.

Windows 10 & Android Fastboot (Device Failed Enumeration - Error Code 43)

 

Other Interesting post related to USB devices found on Microsoft Windows USB Core Team Blog

How does USB stack enumerate a device?

Why is my USB device not detected or comes up as "Unknown Device"?

 

Two things

1. I want to find out whether this is related to only HTC devices or it's across on all Android devices.
2. How can I push this forward to the noses of MS development team.

 

Thank you

geeteam

[straycat19]

Out of curiosity, since I only use Windows 10 as a test bed and not for general use, I tried several of my cell phones  (All Samsungs) and they work fine.  I don't think Microsoft is going to take an interest in this since it is HTC's responsibility to provide drivers that work with the various OSes.  This isn't a very high priority for them when they are struggling to get Windows 10 running correctly and coming up with the constant fixes, updates, and new releases.  Remember what happened when Windows 7 came out and all of a sudden printers and other peripherals wouldn't work because of the drivers and neither Microsoft nor the device makers provided updated drivers.  Overnight a lot of printers became doorstops.

[geeteam]

1 hour ago, straycat19 said:

Out of curiosity, since I only use Windows 10 as a test bed and not for general use, I tried several of my cell phones  (All Samsungs) and they work fine.  I don't think Microsoft is going to take an interest in this since it is HTC's responsibility to provide drivers that work with the various OSes.  This isn't a very high priority for them when they are struggling to get Windows 10 running correctly and coming up with the constant fixes, updates, and new releases.  Remember what happened when Windows 7 came out and all of a sudden printers and other peripherals wouldn't work because of the drivers and neither Microsoft nor the device makers provided updated drivers.  Overnight a lot of printers became doorstops.

 

Sorry of being rude, but did you really understand the issue? Android Debugging Bridge (ADB) works fine even across WiFi. The issue is when you reboot device into bootloader or hboot, and you want to use fastboot commands, that is when you see the Device Failed Enumeration error. 

[john petal]

3 hours ago, geeteam said:

 

Sorry of being rude, but did you really understand the issue? Android Debugging Bridge (ADB) works fine even across WiFi. The issue is when you reboot device into bootloader or hboot, and you want to use fastboot commands, that is when you see the Device Failed Enumeration error. 

Your problem is " device failed enumeration when fastboot "

I'm android user too (Sony Ericsson) and i don't have any problem with android usb 

So i will give you 2 solution (maybe this will help you solve the problem)

1. Install your HTC fastboot driver with "disable driver signature verification"

2. Change your usb cable (because I have experienced errors when fastboot because the usb cable slightly damaged)

[straycat19]

11 hours ago, geeteam said:

 

Sorry of being rude, but did you really understand the issue? Android Debugging Bridge (ADB) works fine even across WiFi. The issue is when you reboot device into bootloader or hboot, and you want to use fastboot commands, that is when you see the Device Failed Enumeration error. 

 

I understood your problem and I don't have it.  I even tested my Nexus and ASUS devices and they don't have that problem either.  I can reboot any of them into fastboot with no problem.  Several of them are highly modified with custom ROMs and use CWM or TWRP and I have no problem with them either.  Sorry it took me so long to answer, busy day and I squeezed in a couple hours sleep.  I suspect your problem is with your driver and HTC has not always been the friendliest android device maker.

[geeteam]

4 hours ago, straycat19 said:

 

I understood your problem and I don't have it.  I even tested my Nexus and ASUS devices and they don't have that problem either.  I can reboot any of them into fastboot with no problem.  Several of them are highly modified with custom ROMs and use CWM or TWRP and I have no problem with them either.  Sorry it took me so long to answer, busy day and I squeezed in a couple hours sleep.  I suspect your problem is with your driver and HTC has not always been the friendliest android device maker.

So what's the appropriate channel I can communicate or log complains to HTC support or some kind of way I can get HTC to be aware of this issue?

[geeteam]

11 hours ago, john petal said:

Your problem is " device failed enumeration when fastboot "

I'm android user too (Sony Ericsson) and i don't have any problem with android usb 

So i will give you 2 solution (maybe this will help you solve the problem)

1. Install your HTC fastboot driver with "disable driver signature verification"

2. Change your usb cable (because I have experienced errors when fastboot because the usb cable slightly damaged)

I have the appropriate drivers installed and adb is working perfectly well expect for fastboot but I think is not hardware related, I also tried several USB cables and same issue.

[john petal]

2 hours ago, geeteam said:

I have the appropriate drivers installed and adb is working perfectly well expect for fastboot but I think is not hardware related, I also tried several USB cables and same issue.

Are you sure already installed the fastboot driver? 

WARNING: ADB Driver and Fastboot Driver are not same

 

Here screenshot fastboot driver from sony device

[geeteam]

3 hours ago, john petal said:

Are you sure already installed the fastboot driver? 

WARNING: ADB Driver and Fastboot Driver are not same

 

Here screenshot fastboot driver from sony device

 

Well maybe, but as I have the HTC USB Driver installed I believe it has installed both ADB and fastboot drivers because the same driver worked on Windows 7 with any issue both ADB and fastboot.

[john petal]

5 hours ago, geeteam said:

 

Well maybe, but as I have the HTC USB Driver installed I believe it has installed both ADB and fastboot drivers because the same driver worked on Windows 7 with any issue both ADB and fastboot.

Windows 7 no need to "disable driver signature enforcement" before install any android driver

Windows 8 and higher need to "disable driver signature enforcement" before  install any android driver

 

So have you already tried to install HTC driver with "disable driver signature enforcement"? Go to settings>Update&Security>Recovery>Advanced startup>Restart now
On the screen "startup option" you must press 7 or F7

After boot to desktop connect your device in fastboot mode and do manual update driver via device manager

 

If you already tried it, wait...i will help you to find the thread about your problem

HTC which type?

 

Good luck

[geeteam]

19 hours ago, john petal said:

Windows 7 no need to "disable driver signature enforcement" before install any android driver

Windows 8 and higher need to "disable driver signature enforcement" before  install any android driver

 

So have you already tried to install HTC driver with "disable driver signature enforcement"? Go to settings>Update&Security>Recovery>Advanced startup>Restart now
On the screen "startup option" you must press 7 or F7

After boot to desktop connect your device in fastboot mode and do manual update driver via device manager

 

If you already tried it, wait...i will help you to find the thread about your problem

HTC which type?

 

Good luck

I have tried all the possible solution I found here and here as I have indicated in the first post but no luck. I have also tried UniversalAdbDriver by koush. I have tested on the Desire HD Custom & One Max Stock. 

[john petal]

56 minutes ago, geeteam said:

I have tried all the possible solution I found here and here as I have indicated in the first post but no luck. I have also tried UniversalAdbDriver by koush. I have tested on the Desire HD Custom & One Max Stock. 

Well, maybe the problem came from USB 3.0 or HTC driver not installed successfull

Do you have "windows security" warning like mine when installing driver/updating the HTC driver?

Screenshot

[geeteam]

On 1/6/2016 at 4:51 PM, john petal said:

Windows 7 no need to "disable driver signature enforcement" before install any android driver

Windows 8 and higher need to "disable driver signature enforcement" before  install any android driver

 

So have you already tried to install HTC driver with "disable driver signature enforcement"? Go to settings>Update&Security>Recovery>Advanced startup>Restart now
On the screen "startup option" you must press 7 or F7

After boot to desktop connect your device in fastboot mode and do manual update driver via device manager

 

If you already tried it, wait...i will help you to find the thread about your problem

HTC which type?

 

Good luck

I have tried all the possible solution I found here and here as I have indicated in the first post but no luck. I have also tried UniversalAdbDriver by koush. I have tested on the Desire HD Custom & One Max Stock.

 

I don't see it, It's quite strange even device manager doesn't show anything like an Android device though I have all the drivers installed.
Meanwhile ADB commands works fine, Android studio is also able to Identify it. But when rebooted into bootloader, first notification pops up showing USB device not recognized. Diagnosing further into it by going to device manager shows Device Failed Enumeration fail under Universal Serial Bus Controllers. Which build are you on? am on Windows 10 Pro Insider build 11082. I will hold on for the meantime and see if a newer build will show up from next week and see what will happen in that build.

7 hours ago, john petal said:

Well, maybe the problem came from USB 3.0 or HTC driver not installed successfull

Do you have "windows security" warning like mine when installing driver/updating the HTC driver?

Screenshot

 

I don't see it, It's quite strange even device manager doesn't show anything like an Android device though I have all the drivers installed.
Meanwhile ADB commands works fine, Android studio is also able to Identify it. But when rebooted into bootloader, first notification pops up showing USB device not recognized. Diagnosing further into it by going to device manager shows Device Failed Enumeration fail under Universal Serial Bus Controllers. Which build are you on? am on Windows 10 Pro Insider build 11082. I will hold on for the meantime and see if a newer build will show up from next week and see what will happen in that build.

[john petal]

23 minutes ago, geeteam said:

I don't see it, It's quite strange even device manager doesn't show anything like an Android device though I have all the drivers installed.
Meanwhile ADB commands works fine, Android studio is also able to Identify it. But when rebooted into bootloader, first notification pops up showing USB device not recognized. Diagnosing further into it by going to device manager shows Device Failed Enumeration fail under Universal Serial Bus Controllers. Which build are you on? am on Windows 10 Pro Insider build 11082. I will hold on for the meantime and see if a newer build will show up from next week and see what will happen in that build.

 

Do same method as the video...Hope it can help you

I'm running on WIndows 10 Enterprise build 10586.36...