Blue Yeti Microphone / No driver found ?

[NexusFred]

Hello, I have an issue with a brand new Bleu Yeti Mic.

This one is detected by Win7 as you can see on the file attach, but Windows can't find a driver for it.

I tried this mic on another computer with the same hardware (motherboard, etc.) and the same operating system (installation + driver) and it works fine.

I updated all my drivers with Driver Booster but it doesn't change anything.

The mic still detected but no driver is found. I tried to uninstall it to force detection, without more success...

I think the driver needed for the microphone is not missing but corrupted. Does anyone know which driver(s) I need to remove and reinstall?

Or better is someone know how to solve this issue ?

Thanks

Nexus

 

[file3456]

You can try what is written in this article or use Driver Store Explorer on the computer with the driver. You'd export that one and only driver for the Yeti. Then import on the computer that doesn't have the driver.

In Driver Store Explorer you need to navigate to the driver folder and copy all those files (including the inf) to a USB drive or what ever. Then use the "update driver" option shown in the howtogeek article. To do that, right click the missing driver shown in Device Manager.

Reason for the problem may be due to a missing driver that Windows had in the driver store.


https://alternativeto.net/software/drivermax/ YMMV

If you do ID the driver, list it here along with the hardware ID if you can. Thanks.

- - - Updated - - -

I'm curios if you have the dlls and sys files on the computer. Download and install the program everything.exe from here (Don't use the lite version).


Now in Everything go above to Bookmarks | Organize Bookmarks | and import the audio_drivers.csv CSV file attached here in a Zip file.

Do you see what I have in this screenshot?



View attachment audio_drivers.zip






- - - Updated - - -

These are the drivers for my USB microphone - a Tonor Q9. Like the Yeti, my microphone was just plug 'n play. So I'm assuming the same files will be used.

Now, even IF those dlls and sys files are on your computer, the driver file its self for the Mic has to create the link to make the Mic work with those dlls and sys files.

 

[NexusFred]

You can try what is written in this article or use Driver Store Explorer on the computer with the driver. You'd export that one and only driver for the Yeti. Then import on the computer that doesn't have the driver. .... with those dlls and sys files.

Thanks for the tips. I think all drivers dlls and sys files are well installed


I try the Drivermax solution without any success.
I made a backup from my other Win7 of the "Yeti Stereo Microphone" drivers and restore them on my computer then reboot.

It doesn't change anything. The microphone is still detected but no driver is found for it.

The backup made with Drivermax
Yeti Stereo Microphone
_innodesc.xml
USBAUDIO.sys
wdma_usb.inf

_innodesc.xml :

<?xml version="1.0" encoding="utf-8" ?>
  <Description>
    <InfFile>
      wdma_usb.inf
    </InfFile>
    <Architecture>
      AMD64
    </Architecture>
    <DeviceDesc>
      <DDS_0>
        Périphérique audio USB
      </DDS_0>
    </DeviceDesc>
    <FriendlyName>
      Yeti Stereo Microphone
    </FriendlyName>
    <ClassDev>
      MEDIA
    </ClassDev>
    <ClassDesc>
      Contrôleurs audio, vidéo et jeu
    </ClassDesc>
    <Mfg>
      (USB Audio générique)
    </Mfg>
    <Provider>
      Microsoft
    </Provider>
    <ClassGUID>
      {4d36e96c-e325-11ce-bfc1-08002be10318}
    </ClassGUID>
    <WindowsVersion>
      6.1.7601
    </WindowsVersion>
    <HardwareID>
      <HID_0>
        USB\VID_046D&PID_0AB7&REV_0020&MI_00
      </HID_0>
      <HID_1>
        USB\VID_046D&PID_0AB7&MI_00
      </HID_1>
    </HardwareID>
    <HardwareCompatibleIDs>
      <CID_0>
        USB\Class_01&SubClass_01&Prot_00
      </CID_0>
      <CID_1>
        USB\Class_01&SubClass_01
      </CID_1>
      <CID_2>
        USB\Class_01
      </CID_2>
    </HardwareCompatibleIDs>
    <DriverCompatibleIDs>
      <DID_0>
        USB\CLASS_01
      </DID_0>
    </DriverCompatibleIDs>
    <DriverCompatibleIDsNames>
      <DIM_0>
        USB Audio Device
      </DIM_0>
    </DriverCompatibleIDsNames>
    <DriverDate>
      2013-07-12
    </DriverDate>
    <DriverVersion>
      6.1.7601.18208
    </DriverVersion>
    <MatchingDeviceID>
      <MID_0>
        usb\class_01
      </MID_0>
    </MatchingDeviceID>
    <DigitallySigned>
      0
    </DigitallySigned>
    <WindowsDefaultDriver>
      1
    </WindowsDefaultDriver>
  </Description>

I also tried to update all the drivers but apart from making Win7 slow and unstable it did not change anything concerning the microphone.

I thought it might be a hardware issue, but when I connected the Blue Yeti to my VMware Windows 10 machine, it worked fine

.... to continue ...

 

[file3456]

Okay, it looks like the exported XML file is showing a vendor ID for your working Yeti on the working computer as a Logitech device which it is not. Thus, if you try to import that exported XML and driver, the driver still probably won't work because the vendor ID and product ID is wrong. It appears you do have the dlls and sys files and what not. I checked their sizes you show there against mine. I think this may be a chip issue in how certain OS environments ID the USB chip. If I had a Yeti I'd tear it open and see what chip it uses. How to identify computer chips or integrated circuits on circuit boards | How To Wiki | Fandom

USB\VID_046D - Logitech, Inc. | Device Hunt

This is the correct vendor ID according to the Device Hunt website. USB\VID_B58E - Blue Microphones | Device Hunt

We might be able to modify that XML file with the correct information to import, but I don't think the PID (Product ID) would be correct, thus we'd have to see if your unknown device shows that correctly in Device Manager.




In the mean time, let's try this. In the Everything program search for wdma_usb.inf. Do you see that file in the path of C:\Windows\System32\DriverStore\FileRepository\xxxx? It should probably be 89KB in size (at least mine is). If found, we want to direct the microphone to this INF file in the "update software" option via Device Manager. To do that, go into Device Manager, right click the unknown device for the Yeti and chose "Update Driver Software" in the right click context menu. Now select "Browse my computer for driver software." Navigate to where the wdma_usb.inf is located in the DriverStore folder previously found in the Everything program. Does it install anything? Any errors?

Prior to doing this you may want to unplug most all other USB devices if they are drawing a lot of power. The maximum amount of Amps allowed per USB hub is 500 mA (half an Amp). In Windows XP you could see how much power each hub was using, but it doesn't appear to have that option in Device Manger for those hubs in Windows 7.

Doing some basic research I see others may have this exact same issue and it seems to me it might be all in how the chip IDs its self to Windows for proper USB driver installation. At least that's my hypothesis. I see in your Device Manager under Other (autres) peripherals the Yeti is identified and gives its name. It's just not able to install the right driver automatically for functionality like it should. Thus my speculation on proper hardware ID detection. And that could be the chip in the microphone and how it interact with certain setups and computer configurations.

If you go to the unknown device, double click and chose properties | Driver | Details | Hardware Ids from the drop down, what does it say? You can right click the values and copy/paste. A vendor ID will be four characters.


Also, go to command prompt and enter dxdiag Click through each tab noting any problems. Below is dxdiag there is also an option for 64 bit. Select that and once again go to each tab noting any problems. Preferably the sound tab for both 32 and 64 bit versions of drivers.

Are you using HDMI for audio delivery? That could potentially mess things up. To uninstall that component you'd go into your Nvidea control panel or equivalent.

- - - Updated - - -

Yeah, very interesting VMware passed the USB hardware though to the guest and Win 10 IDed the peripheral and installed the correct driver. So we know it's not hardware related, it's proper driver ID related. Finding the reason as to why Windows is having a coughing fit is the obvious solution.

 

[NexusFred]

Hello, thank you very much for taking the time to help me solve this problem.

Okay, it looks like the exported XML file is showing a vendor ID for your working Yeti on the working computer as a Logitech device which it is not. Thus,...

Blue Microphone has been owned by Logitech since 2018, maybe that's why. :sarc:

In the mean time, let's try this. In the Everything .... Does it install anything? Any errors?

When I do that I have this error (I translate it):Windows found driver software for your device but encountered an error while attempting install itUSB Composite DeviceThe specified path is invalid.

If you go to the unknown device, double click and chose properties | Driver | Details | Hardware Ids from the drop down, what does it say? You can right click the values and copy/paste. A vendor ID will be four characters.

The ID Vendor is :USB\VID_046D&PID_0AB7&REV_0020USB\VID_046D&PID_0AB7

Also, go to command prompt and enter dxdiag ...

No errors is detected on 64-bit or 32-bit

[FONT=&quot]Are you using HDMI for audio delivery? [/FONT]

I'm not using HDMI for sound or video.... To continue ...

 

[file3456]

Manually install a driver for the unknown device again except this time try the USB.inf file. Navigate to C:\Windows\System32\DriverStore\FileRepository or C:\Windows\inf. Also try the path of C:\Windows\inf and install wdma_usb.inf from there instead of the store folder. Though, the needed sys file would have to be in the same folder I'm sure. That's true for the DriverStore folder.

Do you have any other audio drivers installed? Other audio hardware?


Path not found would be exactly that. You pointed the Yeti hardware to the driver file path found in the Everything program? Is Windows on C drive? You don't have a unique install of some sort?

I'd like to see what Event Viewer says and the current running drivers. I'm thinking there's a driver conflict.

Run the attached batch file on the desktop to grab the last 100 events. You'll see two created files; application_log.txt and system_log.txt. Zip those and attach here.

View attachment Event_viewer_Application_and_System.bat

Next to see your drivers and whatnot. For that run Autoruns. Under File save the arn file after the scan has completed and Zip the arn file and upload here.

Autoruns for Windows - Windows Sysinternals | Microsoft Docs


The path not found is a very interesting one. It seems like your Yeti just can't access that driver file.

You can try running USBDeview and deleting all USB devices that are not being used. View any installed/connected USB device on your system You can organize by clicking the tabs above...

 

[NexusFred]

Manually install a driver for the unknown device again except this time try the USB.inf file. Navigate to C:\Windows\System32\DriverStore\FileRepository or C:\Windows\inf.

No change > Driver not found

Next to see your drivers and whatnot. For that run Autoruns. Under File save ...

I can't send this file here, it contains too much information about my operating system.I can't find a way to save only the Driver panel.

Path not found would be exactly that. You pointed the Yeti hardware to the driver file path found in the Everything program? Is Windows on C drive? You don't have a unique install of some sort?

All the drivers are stored on the C drive. The issue here is that the Yeti do not need any specific driver, just the standard USB MIC Driver. I have no other USB Mic installed.

Run the attached batch file on the desktop to grab the last 100 events. You'll see two created files; application_log.txt and system_log.txt. Zip those and attach here.

View attachment NexusFred_Yeti_Issue_Report_2022-06-29.zip

Next to see your drivers and whatnot. For that run Autoruns. Under File save the arn file after the scan has completed and Zip the arn file and upload here.

I can't send this file here, it contains too much information about my operating system. I can't find a way to save only the Driver panel.

You can try running USBDeview and deleting all USB devices ...

That do not change anything, no driver is found.The drivers file in use on my other Win7 and where the Yeti Mic works seems to be : usbccgp.sys

Windows 7 where the Yeti USB Mic work

==================================================
Device Name       : Blue Microphones
Description       : Périphérique USB composite
Device Type       : Unknown
Connected         : Yes 
Safe To Unplug    : Yes 
Disabled          : No
USB Hub           : No
Drive Letter      : 
Serial Number     : LT_211210025354AD020213_111000
Registry Time 1   : 25/06/2022 22:52:46
Registry Time 2   : 29/06/2022 12:44:33
VendorID          : 046d
ProductID         : 0ab7
Firmware Revision : 0.20
WCID              : 
USB Class         : 00
USB SubClass      : 00
USB Protocol      : 00
Hub / Port        : 
Computer Name     : BUGGY
Vendor Name       : 
Product Name      : 
ParentId Prefix   : 7&3aa66c5e&0
Service Name      : usbccgp
Service Description: Pilote parent générique USB Microsoft
Driver Filename   : usbccgp.sys
Device Class      : USB
Device Mfg        : (Contrôleur hôte USB standard)
Friendly Name     : 
Power             : 100 mA
USB Version       : 2.00
Driver Description: Périphérique USB composite
Driver Version    : 6.1.7601.18328
Driver InfSection : Composite.Dev
Driver InfPath    : usb.inf
Instance ID       : USB\VID_046D&PID_0AB7\LT_211210025354AD020213_111000
Capabilities      : Removable, UniqueID, SurpriseRemovalOK
Install Time      : 21/06/2022 17:34:31
First Install Time: 21/06/2022 17:34:31
Connect Time      : 
Disconnect Time   : 
==================================================

I tried installing it manually, targeting the winsxs folder where the usbccgp.sys file is also present, but I get this windows warning


How do I know which driver it is?

When I compare the 2 results obtained with USBDeview, I noticed that my microphone is marked as "not connected" even is in fact this one is connected?
Windows 7 where the Yeti USB Mic does not work

==================================================
Device Name       : Port_#0002.Hub_#0001
Description       : Blue Microphones
Device Type       : Unknown
Connected         : No
Safe To Unplug    : No
Disabled          : No
USB Hub           : No
Drive Letter      : 
Serial Number     : LT_211210025354AD020213_111000
Created Date      : 29/06/2022 14:10:22
Last Plug/Unplug Date: 29/06/2022 14:10:46
VendorID          : 046d
ProductID         : 0ab7
Firmware Revision : 0.20
USB Class         : 00
USB SubClass      : 00
USB Protocol      : 00
Hub / Port        : 
Computer Name     : WIN7-1
Vendor Name       :
Product Name      :
ParentId Prefix   : 
Service Name      : 
Service Description: 
Driver Filename   : 
Device Class      : USB
Device Mfg        : 
Friendly Name     : 
Power             : 100 mA
USB Version       : 2.00
Driver Description: 
Driver Version    : 
Driver InfSection : 
Driver InfPath    : 
Instance ID       : USB\VID_046D&PID_0AB7\LT_211210025354AD020213_111000
Capabilities      : Removable, UniqueID
==================================================

--- To continue ----

 

[NexusFred]

Does anyone have any other idea what I could do to fix this problem?

 

[file3456]

I recommended you use USBDeView to uninstall everything except keyboard/mouse and what have you to rule out a driver conflict somewhere. It's certainly possible the Yeti can't work due to another installed driver.

I really don't know what's going on here without sitting in front of your computer.

I'll look at your error log later.

PS:

It's "not connected" because Windows has no diver to say it is connected... We see it is drawing power at least, so we know the USB port/header is working unless its a deeper problem which I doubt since VMware picks up on the connected HID.

 

[file3456]

Okay, went over your logs and learned some French along the way.

Some issues that stand out that you may want to look into.

1) Looks like you have or had a software called something like Virtual USB MultiKey. Try completely uninstalling this once. Use RevoUninstaller.

2) There's a kind of driver called Sentinel64. Its use is for a USB dongle and software licensing. Try uninstalling that as well. Read here or use the aforementioned RevoUninstaller.

3) It looks like you have a DCOM permission issue. This may or may not be an issue with the Yeti, but I thought I'd mention it.

From the system log:

Event[14]:
  Log Name: System
  Source: Microsoft-Windows-DistributedCOM
  Date: 2022-06-29T15:22:44.000
  Event ID: 10016
  Task: N/A
  Level: Erreur
  Opcode: N/A
  Keyword: Classique
  User: S-1-5-19
  User Name: AUTORITE NT\SERVICE LOCAL
  Computer: Win7-1
  Description: 
Les paramètres d’autorisation par défaut de l’ordinateur n’accordent pas d’autorisation Local Activation pour l’application serveur COM avec le CLSID 
{BC50CF2A-E12C-4F18-90CE-714CC8600CEE}
 et l’APPID 
{BC50CF2A-E12C-4F18-90CE-714CC8600CEE}
 au SID AUTORITE NT\SERVICE LOCAL de l’utilisateur (S-1-5-19) depuis l’adresse LocalHost (utilisation de LRPC). Cette autorisation de sécurité peut être modifiée à l’aide de l’outil d’administration Services de composants.

Use the CLSID and APPID's mentioned in the above cited log entry with these instructions if you chose to try and fix it.

Event ID 10016: The machine-default permission settings do not grant Local Activation permission for the COM Server | Kunal Chowdhury

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID - Microsoft Q&A


Anti-virus software can play hell with things as well. Worst case, just temp uninstall Avast.

 

[NexusFred]

Thanks a lot for all your advices

I recommended you use USBDeView to uninstall everything except keyboard/mouse...

Done and Reboot > No change

Okay, went over your logs and learned some French along the way...

Sorry about that.

1) Looks like you have or had a software called something like Virtual USB MultiKey...

Done and Reboot > No change

2) There's a kind of driver called Sentinel64...

Can't find any item of Sentinel64 :
C:\Windows\System32\rnbosent > Do not exist
rnbosent > Do not exist
SETUPX86.EXE > Do not exist
Sentstrt.exe > Do not exist
Sentw95.dll > Do not exist
Sentw95.exe > Do not exist

3) It looks like you have a DCOM permission issue...

{BC50CF2A-E12C-4F18-90CE-714CC8600CEE} It's a software who only work if AI Suite 3 is running, and this one is not enabled on my OS.

Worst case, just temp uninstall Avast...

Avast Uninstalled
Comodo Firewall Uninstalled
Reboot > No change

When I uninstall the Blue Yeti Mic with USBDeView and then reconnect it, a small window appears:


Blue Microphones ... Looking on Windows Update in progress.
Then


Blue Microphones ... No driver has been found.


... To Continue --- Or Format C: /All /Quiet /Force :devil:...

 

[file3456]

Your system error log says the following:

Le service Sentinel64 n’a pas pu démarrer en raison de l’erreur :
Le périphérique spécifié est introuvable.

Is that service installed or some software for it to exist?

At this point I'm guessing something striped that driver from your driver store or something. Or something else is interfering. You didn't strip down your Windows install with something like NTLite, did you?

- - - Updated - - -

Do you have the Pro version? The driver is at the bottom of the page here. Otherwise they keep saying its completely plug 'n play.

 

[NexusFred]

Is that service installed or some software for it to exist?

I solve this issue by deleting Sentinel HASP (Aladdin HASP SRM) and reinstall the driver Sentinel System Driver Installer 7.5.7
Now I no longer get the error "The Sentinel64 service failed to start due to the error:" But that doesn't change anything :-(

At this point I'm guessing something striped that driver from your driver store or something. Or something else is interfering. You didn't strip down your Windows install with something like NTLite, did you?

I do not.

Do you have the Pro version?

Sadly no.

Otherwise they keep saying its completely plug 'n play.

Yes, but with your Windows instead of the microphone lol

Is there a way to manually reinstall the standard USB Mic driver?
Maybe the file is just corrupted.

 

[file3456]

You would have to try do an SFC /scannow as admin in the command prompt or conduct a repair install. https://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

For testing, I'd completely remove Sentinel HASP and see if the Yeti works. I feel like a driver or some software messed something up. Just a guess though.