USB Audio Device – Install Fails

Topic

New Reply

Trying to install this device on my PC.

“Sabrent USB External Stereo Sound Adapter for Windows and Mac. Supposed to be Plug and Play No Drivers Needed.” Model AU-MMSA.

PC is a Dell Optiplex 7040 running Win 10 Pro, ver. 1909 Build 18363.592

Multiple attempts to install and use have failed. Windows Device Manager says “driver unavailable”. I have deleted the device in device manager and re-attempted install several times, same failure. I’ve tried different USB ports, same failure.

I tried Device Manager update/find a driver but that failed too with “driver unavailable”.

It works in my laptop, Dell Latitude E5550,Win 10 Pro, ver 1909, build 18363.657

By looking at the USB device’s properties in the working machine, I verified that the device’s drivers and DLLs <u>ARE present i</u>n the non-working machine’s Sys32 and Sys32/Drivers folders.

If it means anything, the USB device in the non-working machine shows up in device manager’s “other devices” vs. “Sound , video and game controllers” in the working machine.

My guess is that something is either preventing or interrupting the drivers’ install routine? Maybe a security setting? Frustrated.

From event viewer:

~~~~~

Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 10/5/2020 2:21:16 PM
Event ID: 400
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: Ken-Desktop
Description:
Device USB\VID_0D8C&PID_0014&MI_00\7&1168748c&0&0000 was configured.

Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device Id:
Outranked Drivers:
Device Updated: false
Parent Device: USB\VID_0D8C&PID_0014\6&d666e98&0&3
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”Microsoft-Windows-Kernel-PnP” Guid=”{9c205a39-1250-487d-abd7-e831c6290539}” />
<EventID>400</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime=”2020-10-05T18:21:16.455628000Z” />
<EventRecordID>679</EventRecordID>
<Correlation />
<Execution ProcessID=”4″ ThreadID=”6872″ />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>Ken-Desktop</Computer>
<Security UserID=”S-1-5-18″ />
</System>
<EventData>
<Data Name=”DeviceInstanceId”>USB\VID_0D8C&amp;PID_0014&amp;MI_00\7&amp;1168748c&amp;0&amp;0000</Data>
<Data Name=”DriverName”>null</Data>
<Data Name=”ClassGuid”>{00000000-0000-0000-0000-000000000000}</Data>
<Data Name=”DriverDate”>
</Data>
<Data Name=”DriverVersion”>
</Data>
<Data Name=”DriverProvider”>
</Data>
<Data Name=”DriverInbox”>false</Data>
<Data Name=”DriverSection”>
</Data>
<Data Name=”DriverRank”>0x0</Data>
<Data Name=”MatchingDeviceId”>
</Data>
<Data Name=”OutrankedDrivers”>
</Data>
<Data Name=”DeviceUpdated”>false</Data>
<Data Name=”Status”>0x0</Data>
<Data Name=”ParentDeviceInstanceId”>USB\VID_0D8C&amp;PID_0014\6&amp;d666e98&amp;0&amp;3</Data>
</EventData>
</Event>

~~~~

Also from event viewer, source: device setup manager:  “The DSM service was delayed by 55 seconds for a driver query/download/install on device ‘USB\VID_0D8C&PID_0014&MI_00\6&1BF409F&0&0000’

~~~

Any advice sincerely appreciated.

Ken

Reply | Quote

Replies

If the operating system the device is working on is also Windows 10, and the bittedness of Windows 10 on both systems is the same (32-bit or 64-bit), you could try using the DriverBackup! freeware to back up the working Sabrent device drivers (only) on the laptop to a thumbdrive, then use that to install them on your desktop computer.

https://sourceforge.net/projects/drvback

Asus N53SM & N53SN 64-bit laptops (Win7 Pro & Win10 Pro 64-bit multiboots), venerable HP Pavilion t760 32-bit desktop (XP & Win7 Pro multiboot), Oracle VirtualBox VM's: XP & Win7 32-bit, XP Mode, aged Samsung Galaxy S4, Samsung Galaxy Tab A 2019s (8" & 10.1"), Blu-ray burners, digital cameras, ext. HDDs (latest 5TB!), AnyDVD, Easeus ToDo Backup Home, Waterfox, more. Me: Aussie card-carrying Windows geek.

Reply | Quote

[WSkenh999]

The drivers that the device uses, as listed in the device manager properties on the working PC, are present on BOTH the working and non-working PCs. See the screenshot from device properties on working laptop. Those files are in the same folders (Sys32 and Sys32/drivers) as on the laptop.

AFAIK they are native Windows files. For some reason the device install routine is just not  assigning them to the device, I guess.

• This reply was modified 4 years, 6 months ago by WSkenh999.

Reply | Quote

I just checked on my system, and yes, they’re native Windows 10 files. Correct, the device install routine is just not assigning them to the device on your desktop machine.

DriverBackup will also backup a .inf file, which will tell Windows 10 on your desktop how to install the device. I suggest you try it, you have nothing to lose. Make a System Restore Point first, though, just in case.

Asus N53SM & N53SN 64-bit laptops (Win7 Pro & Win10 Pro 64-bit multiboots), venerable HP Pavilion t760 32-bit desktop (XP & Win7 Pro multiboot), Oracle VirtualBox VM's: XP & Win7 32-bit, XP Mode, aged Samsung Galaxy S4, Samsung Galaxy Tab A 2019s (8" & 10.1"), Blu-ray burners, digital cameras, ext. HDDs (latest 5TB!), AnyDVD, Easeus ToDo Backup Home, Waterfox, more. Me: Aussie card-carrying Windows geek.

Reply | Quote

Can you send us some more info from the problem system?

1. Win R
2. msinfo32
3. Components > Problem Devices
4. Edit > Select All, Edit > Copy
5. Paste the data here.

cheers, Paul

Reply | Quote

Does the driver installation process complete when you cold boot with the device inserted into any USB port?

If this is a Cmedia sound chip then most of these have Windows 10 inbox drivers.

Reply | Quote

Paul T wrote:

Can you send us some more info from the problem system?

1. Win R
2. msinfo32
3. Components > Problem Devices
4. Edit > Select All, Edit > Copy
5. Paste the data here.

cheers, Paul

Paul,

The only entry in problem devices.

USB Audio Device USB\VID_0D8C&PID_0014&MI_00\6&B4F499B&0&0000 The drivers for this device are not installed.

 

Reply | Quote

anonymous wrote:

Does the driver installation process complete when you cold boot with the device inserted into any USB port?

If this is a Cmedia sound chip then most of these have Windows 10 inbox drivers.

I’ve tried to ID the chip but no joy so far. It’s not mentioned in the Amazon page or on the Sabrent website. Sabrent tech support has not been helpful at all in resolving this. Best I got from them was “have you tried it in different USB ports?”. I asked for the chip ID but no reply yet.

Reply | Quote

You can try opening the device to see if there is a model number on the sound chip.

Reply | Quote

What a mess. Spent almost 2 days trying to claw my way out of this deepening Windows rabbit hole.

Removed ALL USB devices and hub except mouse and KB.

Ran Windows USB Troubleshooter – it returned “USB Controller in failed state or is not currently installed. USB controller must be installed or working for troubleshooter to run”. It gave NO other helpful details. Although except for this audio device everything USB was working. PLUS – In device manager’s listing for the Intel USB 3.0 Host Controller – 1.0 (Microsoft)  it says ‘working properly’ and NO errors are listed in its properties. Did a driver update search for the controller and Win says best drivers are installed. WTH? Troubleshooter says it’s broke but Device Manager says it’s not.

So, after that I did a SFC /SCANNOW. And the rabbit hole deepened… That failed. “Windows Resource Protection could not perform the requested operation.”

Did a quick search on that SFC error and got suggestions to run DISM’s  /Online /Cleanup-Image /RestoreHealth. Guess what? Yep, failed too. Got:

Error: 14098
The component store has been corrupted.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Searched that error and found guidance to ‘reset’ Windows Update stuff. I ran the “Reset Windows Update Tool” from wureset.com. Still no success. SFC and DISM still fail as before. Component store still corrupted.

From there I tried to cleanup the component store with

dism.exe /online /Cleanup-Image /StartComponentCleanup

but it fails with the same Error 14098 – Component Store corrupted.

That’s where I stopped. So, I have no clue if the USB issues are related to the component store stuff or not but guess I should try to fix it then see if the USB stuff clears up?

Please, how do I fix the component store???

 

Reply | Quote

To be fair, I don’t think it’s the fault of windows 10 at all.

Your amazon link is to a USB-A device (that has NO mention of being suitable for Windows 10)

Driverless for Windows 98SE/ME/2000/XP/Server 2003/Vista/7/8/Linux/Mac OSX.

with a non returnable policy.

However, the USB-C device is Windows 10 compatible (with a returns policy to Jan 2021)

Driverless for Windows XP/Server 2003/Vista/7/8/8.1/10/Linux/Mac OSX.

my bolding

source of link in #2302053

Windows - commercial by definition and now function...

1 user thanked author for this post.

WSkenh999

Reply | Quote

WSkenh999 wrote:

Error 14098 – Component Store corrupted.

That’s where I stopped. So, I have no clue if the USB issues are related to the component store stuff or not but guess I should try to fix it then see if the USB stuff clears up?

Please, how do I fix the component store???

Well. IF the USB issues and the Component Store error are directly related, I’d be worried about both being symptoms of a fault in the motherboard/processor/PCIe region. Not as the most probable cause, but as something close to the worst case (because of the potential to corrupt other data as well) that I’ve personally seen to cause this kind of thing…

In the absence of an actual hardware fault, there’s a few things that sometimes work and sometimes don’t.

There have been cases where an antivirus application has caused this error.

Sometimes it’s been possible to recover from this by running the same dism.exe commands in “safe boot” or other reduced-functionality state, or from external media (may require an install media of same Windows feature level, especially if booting without network…)

Another thing that sometimes may work is wiping certain parts of Windows Update information manually, so forcing a rebuild of that data.

And then there’s the reinstall method.

Yes, “component store corrupted” is one of the more annoying Windows 10 errors, exactly because it just seems so random…

Reply | Quote

Microfix wrote:

To be fair, I don’t think it’s the fault of windows 10 at all.

Your amazon link is to a USB-A device (that has NO mention of being suitable for Windows 10)

Driverless for Windows 98SE/ME/2000/XP/Server 2003/Vista/7/8/Linux/Mac OSX.

with a non returnable policy.

However, the USB-C device is Windows 10 compatible (with a returns policy to Jan 2021)

Driverless for Windows XP/Server 2003/Vista/7/8/8.1/10/Linux/Mac OSX.

my bolding

source of link in #2302053

Thanks for the good catch. Just ordered the USB-C model. I should have seen that but…

Reply | Quote

WSkenh999 wrote:

how do I fix the component store?

Reinstall Windows with the “retain my data” option.
If that doesn’t work you probably have to reinstall from scratch, or restore a backup.

It’s worth doing a disk check beforehand (Win R, cmd, chkdsk c:)

cheers, Paul

Reply | Quote

Paul T wrote:

WSkenh999 wrote:

how do I fix the component store?

Reinstall Windows with the “retain my data” option.
If that doesn’t work you probably have to reinstall from scratch, or restore a backup.

It’s worth doing a disk check beforehand (Win R, cmd, chkdsk c:)

cheers, Paul

I have a C: disk image from July. Any reason why not to try that first?

Perhaps the component store issue wasn’t present then.

Reply | Quote

I’d make a backup of the current broken Windows, then restore the July backup.

No downside AFAICS.

cheers, Paul

Reply | Quote

Paul T wrote:

I’d make a backup of the current broken Windows, then restore the July backup.

No downside AFAICS.

cheers, Paul

Yep, did that yesterday before I started running all that stuff. Mostly just the OS and programs on my C. I use an E partition and shared network drive for data storage. I’m saving the newer pgm settings/files and stuff not in the July image now.

Reply | Quote

Well, that was wishful thinking. Apparently the the component store issue has been around a while and didn’t know it. After restoring the July image still get the SFC and DISM errors. I reverted back to yesterday’s image. I’ll wait for the above mentioned USB-C USB Audio Device to arrive and see if it works and more fully prepare for a re-install, at some point soon. Everything’s (except USB issue) working for now so…

Thanks for everyone’s input.

Reply | Quote

WSkenh999 wrote:

Microfix wrote:

To be fair, I don’t think it’s the fault of windows 10 at all.

Your amazon link is to a USB-A device (that has NO mention of being suitable for Windows 10)

Driverless for Windows 98SE/ME/2000/XP/Server 2003/Vista/7/8/Linux/Mac OSX.

with a non returnable policy.

However, the USB-C device is Windows 10 compatible (with a returns policy to Jan 2021)

Driverless for Windows XP/Server 2003/Vista/7/8/8.1/10/Linux/Mac OSX.

my bolding

source of link in #2302053

Thanks for the good catch. Just ordered the USB-C model. I should have seen that but…

Well, I was to hasty in grasping at straws to get this working. Had I paid attention I would have realized I do NOT have USB-C jacks on my PC or anywhere else. *&^%$.

If anyone knows of a USB Audio Device that comes with its OWN DRIVERS please advise.

Reply | Quote

Startech has some models which have a full driver package.

Creative also has some adapters which has driver software.

Reply | Quote

Cross posted here.

Please advise when you cross post so we don’t duplicate effort – we are all volunteers.

cheers, Paul

2 users thanked author for this post.

WSkenh999, Microfix

Reply | Quote

Fixing Windows with the DISM command or reinstalling Windows seem the only options.

cheers, Paul

Reply | Quote

The Windows 10 build versions are different, could that be an important difference in this experience because Microsoft make so very many fully documented code changes between each build?

Reply | Quote