Blue Yeti mic stops functioning after update

[hippyeconomist]

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

28.0.1

OBS Studio Version (Other)

22.9.8.69

OBS Studio Log URL

https://obsproject.com/logs/CNx4jPvWUhf8QrrI

OBS Studio Crash Log URL

No response

Expected Behavior

Expected Blue Yeti microphone to continue working after the update to v28.

Current Behavior

Microphone stopped functioning with OBS after update.

Steps to Reproduce

1. Have a functioning version of OBS
2. Use the OTA update
3. No more audio from microphone

Anything else we should know?

Mic still works fine with StreamLabs/Audacity.

[hippyeconomist]

Running OBS Studio as Administrator produced no change in behavior.

[RytoEX]

This is due to how OBS enumerates and tracks devices (by their device ID). If the device ID that we have stored does not match a current valid ID for any reason (e.g., the device was unplugged and plugged back in, the device was uninstalled/reinstalled), then OBS will fail to load that device, as seen in the log:

12:45:11.082: [win-wasapi: '(Active) Yeti Mic'] update settings:
12:45:11.082:   device id: {0.0.1.00000000}.{8753614a-b7e0-4563-93e6-98cff5acc669}
12:45:11.082:   use device timing: 0
12:45:11.082: [WASAPISource::TryInitialize]:[{0.0.1.00000000}.{8753614a-b7e0-4563-93e6-98cff5acc669}] Failed to enumerate device: 80070490
12:45:11.082: WASAPI: Device '{0.0.1.00000000}.{8753614a-b7e0-4563-93e6-98cff5acc669}' failed to start (source: (Active) Yeti Mic)

Error 80070490 is "E_NOTFOUND", indicating that a device matching the specified device ID cannot be found. This can also occur in OBS Studio 27, and probably all versions of OBS Studio, as the code for this hasn't really changed much.

To fix this in your scene collection:

1. Swap each Yeti source to another device temporarily.
2. Save and close the source settings.
3. Swap the sources you changed in Step 1 back to the Yeti.

If that does not fix it, I would repeat the above but also restart OBS between Steps 2 and 3, or removing the sources completely and re-adding them. If that still does not fix it, I encourage you to visit our Discord server's #windows-support channel.