Windows 10: Getting Code 10 error on usb microphone

I have a editor keys sl300, which works on another computer. When I plug it into my computer though, I get a message saying "troubleshoot device" in devices and printers. The troubleshoot says that there is a problem with the drivers, which I have reinstalled multiple times. Under task manager, it says that it it caused by:

This device cannot start. (Code 10)

{Operation Failed} The requested operation was unsuccessful.

How would I fix this?

I have tried reinstalling drivers, changing USB ports, uninstalling and disabling the microphone to no avail.

Thanks in advance.

:)

 

"This device cannot start. (Code 10) {Operation Failed} The requested operation was unsuccessful" when connecting USB headphone on Windows 10.

Original Title: Badaax UM600 not working with Windows 10

I am unable to use the Badaax UM600 usb microphone with Windows 10. I have tried uninstalling the drivers, rebooting, auto-updating the drivers, using different USB ports and cables but nothing will allow the microphone to work. Device shows as "usb microphone"
in the device manager but shows "This device cannot start. (Code 10) {Operation Failed} The requested operation was unsuccessful" in the properties. Found some updates to my USB host controller drivers but still no success. Microphone did work in Windows 7.
As this is somewhat of a no-name brand, there are no manufacturer drivers that I can find. Any ideas?

 

Windows 10 Start Error Code

I get an error code when I start Windows 10 that follows Skype starting: Run DLL is the box heading and the error reads: There was a problem starting P17RunE.dll / The specified module could not be found. I am wondering if this code appears because I don't
have a (camera and microphone set up yet) to interact with Cortana?

 

Have you downloaded the driver from the vendor's site, for Win 10?

Here is a statement on the vendor's site about this:

Here is the link to the site
The SL300 Condenser USB Microphone - Both Mac PC Compatible - Used by thousands of professional recording artists | Editors Keys


(I have a recording studio using Cakewalk Sonar, but I don't use USB mic's).

 

Yes I have, and have reinstalled it as well. It dosesn't solve the problem unfortunatley.

 

Did you install the drivers first and then connect the mic? If you connect the mic first and then the drivers the installation usually fails.

If you have a System Restore point that is BEFORE you first tried to install the mic, use that to go back (gives a clean start) and then install the drivers first then connect the mic and see if it works.

If you don't have a restore point, connect the mic, go to the Device Manager, uninstall the mic and the drivers in the device manager. Disconnect the mic and reboot the PC. After Windows starts, try another installation, installing the drivers first.

 

I installed the drivers first, but still getting the same issue

 

Select "Run as Administrator" when you install the drivers and see if that makes any difference. Also, since drivers are also for Win 8.1, install the drivers in a Win 8.1 compatibility mode and see if that makes any difference.

 

So after trying that, it now recognised the correct microphone, rather than "USB audio", and says it is working correctly for a few seconds, then reverts to:

This device cannot start. (Code 10)The I/O request was canceled.

 

Go to nirsoft.net. They have a lot of useful utilities. One I believe is called USBDeviceView. May help you troubleshoot. In my case I was constantly getting USB device disconnect dings for no reason, all my devices were working properly. I was able to find a USB device that didn't exist and deleted it.

 

Thanks for the reply. I've tried uninstalling the mic from USBDeviceView, but i'm still getting the same error. Everything else looks normal.

 

You're welcome. Sorry it didn't help.
Of interest, nirsoft.net is blocked by the company I support. Some of the utilities look as if they could be used by hackers.

 

so are you now saying dont use that site you posted ?

 

Sorry, didn't mean that. Just that you may not be allowed to use them in some environments.