# Unplugging a Monitor Creates Error (API)

**URL:** <https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722>\
**Category:** FMOD Studio\
**Created:** [November 17, 2014, 8:09pm UTC](https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722 "2014-11-17T20:09:09Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![JGregg44](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@JGregg44](https://qa.fmod.com/u/JGregg44)\
**Post date:** [November 17, 2014, 8:09pm UTC](https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722/1 "2014-11-17T20:09:09Z")

</div>

We are using FMOD Studio API in our game for school and when you unplug a monitor it creates this error when running FMOD’s Update function:

“A Win32 COM related error occurred. COM failed to initialize or a QueryInterface failed meaning a Windows codec or driver was not installed properly.”

Currently my only guess is switching a sound source creates this issue. For example if using an HDMI cord and unplugging it would then cause the source to switch. However, when testing with a VGA cord this doesn’t happen.

Any ideas on how to fix this or possibly detect when a source switches and handle it accordingly.

Thanks in advance.

Using FMOD Studio Version 1.05.04

---

<div class="post-metadata">

**Author:** ![nick1](https://avatars.discourse-cdn.com/v4/letter/n/47e85d/32.png) [@nick1](https://qa.fmod.com/u/nick1)\
**Post date:** [November 17, 2014, 9:26pm UTC](https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722/2 "2014-11-17T21:26:29Z")

</div>

> [@](#):
>
> We are using FMOD Studio API in our game for school and when you unplug a monitor it creates this error when running FMOD’s Update function:
> 
> “A Win32 COM related error occurred. COM failed to initialize or a QueryInterface failed meaning a Windows codec or driver was not installed properly.”
> 
> Currently my only guess is switching a sound source creates this issue. For example if using an HDMI cord and unplugging it would then cause the source to switch. However, when testing with a VGA cord this doesn’t happen.
> 
> Any ideas on how to fix this or possibly detect when a source switches and handle it accordingly.
> 
> Thanks in advance.
> 
> Using FMOD Studio Version 1.05.04

What version of FMOD Studio are you using?

---

<div class="post-metadata">

**Author:** ![JGregg44](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@JGregg44](https://qa.fmod.com/u/JGregg44)\
**Post date:** [November 17, 2014, 11:09pm UTC](https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722/3 "2014-11-17T23:09:49Z")

</div>

FMOD Studio 1.05.04

---

<div class="post-metadata">

**Author:** ![nick1](https://avatars.discourse-cdn.com/v4/letter/n/47e85d/32.png) [@nick1](https://qa.fmod.com/u/nick1)\
**Post date:** [November 18, 2014, 12:04am UTC](https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722/4 "2014-11-18T00:04:32Z")

</div>

Sorry, I meant to ask which version of the API are you using?

---

<div class="post-metadata">

**Author:** ![JGregg44](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@JGregg44](https://qa.fmod.com/u/JGregg44)\
**Post date:** [November 18, 2014, 1:05am UTC](https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722/5 "2014-11-18T01:05:06Z")

</div>

FMOD Studio API for C++ downloaded with the same version we are using for FMOD Studio so 1.05.04. (I’m not using Low Level of fsbank if that’s what you mean?

---

<div class="post-metadata">

**Author:** ![nick1](https://avatars.discourse-cdn.com/v4/letter/n/47e85d/32.png) [@nick1](https://qa.fmod.com/u/nick1)\
**Post date:** [November 18, 2014, 2:20am UTC](https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722/6 "2014-11-18T02:20:09Z")

</div>

That error message corresponds to FMOD\_ERR\_COM, which was removed in 1.05.00. Can you make sure all the libs, DLLs and headers are from the 1.05.04.

---

<div class="post-metadata">

**Author:** ![JGregg44](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@JGregg44](https://qa.fmod.com/u/JGregg44)\
**Post date:** [November 18, 2014, 4:45am UTC](https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722/7 "2014-11-18T04:45:49Z")

</div>

That fixed it. I guess we were updating FMOD Studio but hadn’t been updating the API as well. Thanks.

---

<div class="post-metadata">

**Author:** ![AnalogInArse](https://avatars.discourse-cdn.com/v4/letter/a/e19b73/32.png) [@AnalogInArse](https://qa.fmod.com/u/AnalogInArse)\
**Post date:** [November 17, 2014, 11:30pm UTC](https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722/8 "2014-11-17T23:30:40Z")

</div>

Try messing around with sytem-\>getRecordNumDrivers, getDriver, getDriverInfo.

I use getRecordNumDrivers to detect the number of recording devices plugged in.

---

<div class="post-metadata">

**Author:** ![nick1](https://avatars.discourse-cdn.com/v4/letter/n/47e85d/32.png) [@nick1](https://qa.fmod.com/u/nick1)\
**Post date:** [November 18, 2014, 9:52pm UTC](https://qa.fmod.com/t/unplugging-a-monitor-creates-error-api/11722/9 "2014-11-18T21:52:26Z")

</div>

This sounds like a bug we fixed back in 1.04.08.