# FMOD.System.getDriver is unreliable after the default device is changed on Windows

**URL:** https://qa.fmod.com/t/fmod-system-getdriver-is-unreliable-after-the-default-device-is-changed-on-windows/17294
**Category:** FMOD Engine
**Tags:** csharp, unity
**Created:** [June 4, 2021, 9:49am UTC](https://qa.fmod.com/t/fmod-system-getdriver-is-unreliable-after-the-default-device-is-changed-on-windows/17294 "2021-06-04T09:49:51Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)
#### Post date: [July 26, 2022, 4:42am UTC](https://qa.fmod.com/t/fmod-system-getdriver-is-unreliable-after-the-default-device-is-changed-on-windows/17294/6 "2022-07-26T04:42:29Z")

</div>

This behavior is a result of registering for the `FMOD_SYSTEM_CALLBACK_DEVICELISTCHANGED` callback, which overrides the default behavior.

The value returned from `System::getDriver` is only updated when calling `System::setDriver` and by overriding the `FMOD_SYSTEM_CALLBACK_DEVICELISTCHANGED` callback, FMOD no longer does this automatically, you will need to handle this in your callback.

---

_[View the full topic](https://qa.fmod.com/t/fmod-system-getdriver-is-unreliable-after-the-default-device-is-changed-on-windows/17294)._