Topic: WDM Driver not showing up as a playback device (Read 4028 times)

munkey · « **on:** December 03, 2019, 11:38:36 pm »

When I enable the WDM Driver and restart MC, nothing happens and the driver does not install.

When I check my sound properties, JRiver is not listed as one of the available Playback Devices.

I have ensured that all virus/windows defender stuff is turned off and I have run MC as an administrator and still not having any luck.

Any suggestions would be greatly appreciated.

Thanks!

JimH · « **Reply #1 on:** December 04, 2019, 07:13:47 am »

Did you reboot?

munkey · « **Reply #2 on:** December 04, 2019, 02:06:39 pm »

Yup, rebooted several times. Unchecked and rechecked the WDM checkbox several times as well. Still nothing showing up.

munkey · « **Reply #3 on:** December 04, 2019, 03:46:50 pm »

I got it to show up in Device Manager, but I'm getting a driver signing issue:

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)

Any ideas?

munkey · « **Reply #4 on:** December 04, 2019, 04:22:24 pm »

If I boot the computer without driver signing, then it works perfectly. So it's something to do with driver signing I guess?

JimH · « **Reply #5 on:** December 04, 2019, 04:34:01 pm »

What version of MC are you using?

munkey · « **Reply #6 on:** December 05, 2019, 06:50:49 pm »

25.0.114 (most recent one I believe)

RoderickGI · « **Reply #7 on:** December 05, 2019, 08:42:19 pm »

Try turning off the WDM Driver in Features.
Then reinstall MC25.0.114 over the top of the existing installation. Nothing will be lost. Backup the Library first if you are concerned.
Turn on the WDM Driver in Features again.
Restart MC.

Working?

If not, repeat but with the WDM Driver Feature enabled when you reinstall.

The above can force the driver to be registered properly, if it didn't for any reason in the past. The WDM Driver in MC25.0.114 is properly signed, I believe. A search of the forum would probably find discussion to confirm that.

madbrain · « **Reply #8 on:** December 08, 2019, 05:24:17 am »

Quote from: RoderickGI on December 05, 2019, 08:42:19 pm

Try turning off the WDM Driver in Features.
Then reinstall MC25.0.114 over the top of the existing installation. Nothing will be lost. Backup the Library first if you are concerned.
Turn on the WDM Driver in Features again.
Restart MC.

Working?

If not, repeat but with the WDM Driver Feature enabled when you reinstall.

I am having the same problem. Came here from a google search. The above didn't work for me. I think there might be an issue with the driver.

I also disabled driver signing with "BCDEDIT /SET TESTSIGNING OFF" + reboot.
No amount of checking / unchecking the WDM box gets the driver in MC25 installed. This might not have anything to do with the signature check. Pretty sure it used to work with MC24, though, but I had deleted it recently. Time for a reinstall.

Edit: reinstalled MC24.0.75 .
The JRiver WDM driver works fine, though it shows up in the GUI as "JRiver Media Center 23" . I only have MC24 and MC25 installed, no MC 23.

FYI, both MC24 and MC25 versions installed are 32-bit . I can't use the 64-bit versions due to some incompatibility with the ASIO drivers for my soundcard.

Looks like this is a regression from MC24 to MC25 in the 32-bit version.

Hendrik · « **Reply #9 on:** December 08, 2019, 07:30:38 am »

I've fixed the issue in MediaCenter. It was only broken quite recently, which is why it didn't really show up before.
You can use MC 25.0.107, for example, to install it, only after that version it was broken.

PS:
Note that the version number in the driver can sometimes be off since Windows caches the name of the device. Devices are not meant to "rename", since hardware typically doesn't do that, so even if you install a new driver, it might still show an old name.

RoderickGI · « **Reply #10 on:** December 08, 2019, 02:12:22 pm »

Same problem over here: https://yabb.jriver.com/interact/index.php/topic,119925.msg853899.html#msg853899

Hendrik, are you going to put the fix into a version of MC25? i.e. MC25.0.115?

munkey · « **Reply #11 on:** December 08, 2019, 04:05:12 pm »

Quote from: Hendrik on December 08, 2019, 07:30:38 am

I've fixed the issue in MediaCenter. It was only broken quite recently, which is why it didn't really show up before.
You can use MC 25.0.107, for example, to install it, only after that version it was broken.

PS:
Note that the version number in the driver can sometimes be off since Windows caches the name of the device. Devices are not meant to "rename", since hardware typically doesn't do that, so even if you install a new driver, it might still show an old name.

Thanks for the suggestions - looked for 107, but can't find it anywhere. Can you point me in the right direction please?

Thanks!

Hendrik · « **Reply #12 on:** December 08, 2019, 04:12:23 pm »

The closest we released publicly was apparently 104
https://yabb.jriver.com/interact/index.php/topic,122336.0.html

JimH · « **Reply #13 on:** December 08, 2019, 05:09:32 pm »

Quote from: RoderickGI on December 08, 2019, 02:12:22 pm

Same problem over here: https://yabb.jriver.com/interact/index.php/topic,119925.msg853899.html#msg853899

Hendrik, are you going to put the fix into a version of MC25? i.e. MC25.0.115?

Yes

madbrain · « **Reply #14 on:** December 08, 2019, 07:16:28 pm »

Quote from: Hendrik on December 08, 2019, 07:30:38 am

I've fixed the issue in MediaCenter. It was only broken quite recently, which is why it didn't really show up before.
You can use MC 25.0.107, for example, to install it, only after that version it was broken.

Thanks. Can you please provide a download link for MC 25.0.107 ?

Quote

Note that the version number in the driver can sometimes be off since Windows caches the name of the device. Devices are not meant to "rename", since hardware typically doesn't do that, so even if you install a new driver, it might still show an old name.

Yes, I noticed that after a few install/uninstall of MC24. The driver now says it's JRiver Media Center 24 as intended.
Good to know it's just a cosmetic issue. It was a bit disconcerting.

Hendrik · « **Reply #15 on:** December 09, 2019, 01:20:14 am »

Quote from: madbrain on December 08, 2019, 07:16:28 pm

Thanks. Can you please provide a download link for MC 25.0.107 ?

Just use 104 that I linked above, the driver is no different in that version.
After the driver is installed, you can upgrade to 114 and everything will be fine.

munkey · « **Reply #16 on:** December 09, 2019, 12:01:04 pm »

Still getting the same error

Awesome Donkey · « **Reply #17 on:** December 09, 2019, 02:33:27 pm »

With MC25 closed, you might try uninstalling the WDM driver from Windows' Device Manager, then try reinstalling it from 25.0.104.

Hendrik · « **Reply #18 on:** December 09, 2019, 03:03:04 pm »

Also when uninstalling, make sure to tick the box to remove all driver files, just to be sure.

munkey · « **Reply #19 on:** December 10, 2019, 09:56:07 am »

Well I'll be - that fixed it! Thanks for your help

Awesome Donkey · « **Reply #20 on:** December 10, 2019, 10:03:16 am »

Also 25.0.115 is out with a fix for the WDM driver too.

https://yabb.jriver.com/interact/index.php/topic,123295.0.html

INTERACT FORUM

Author Topic: WDM Driver not showing up as a playback device (Read 4028 times)