Topic: WDM not working with MC24 (Read 3862 times)

JRU · « **on:** April 22, 2018, 11:30:12 am »

The WDM driver wasn't working when I installed MC24 but was working with MC23, I tried ticking/unticking, closing and reopening MC 23/24 and also restarted my computer but it just wouldnt show up in the control panel sound properties. The WDM in MC23 has also stopped working. Some help please.

JimH · « **Reply #1 on:** April 22, 2018, 12:01:31 pm »

The wiki has a topic on WDM Driver.

JRU · « **Reply #2 on:** April 22, 2018, 12:30:16 pm »

I have already read the wiki and it is not working, as I mentioned it was working but stopped working. I tried ticking and unticking the WDM driver box in features to install it but it isn't installing.

franklimalvorecer3 · « **Reply #3 on:** April 23, 2018, 06:34:20 am »

The same thing happened to me, I manage to solve this issue by desactivating e reactivating it again, go on: settings>general>features>, then unmark the wdm driver box, close the windows jriver will ask for confirmation, click yes, then you close jriver and open it again, now you comeback the same way, and mark the wdm driver box, close the windows and say yes again, now jriver will install the wdm drive, and it will appear on windows sound management.

JRU · « **Reply #4 on:** April 23, 2018, 12:49:20 pm »

I have already done what you described multiple times but it does not work, either in MC23 or 24. That is why I don't know what to do and came here asking for help.

Awesome Donkey · « **Reply #5 on:** April 23, 2018, 12:54:28 pm »

Secure Boot enabled?

JRU · « **Reply #6 on:** April 23, 2018, 01:20:39 pm »

Sorry I don't know what that is. I do know that I have made no changes to windows in a long time and this problem occurred when I installed MC24, MC23 was still installed and the WDM was still working but I thought it might be a conflict so I unchecked the WDM in MC23 and it did indeed uninstall but now that won't install either.

Awesome Donkey · « **Reply #7 on:** April 23, 2018, 01:43:34 pm »

Possibly this: https://yabb.jriver.com/interact/index.php/topic,114531.0.html

You can check by typing msinfo into the Windows 10 Cortana search bar and pressing Enter. If within the System Information window Secure Boot State says On, that's likely the issue. The WDM driver currently isn't compatible with the latest Windows 10 signing requirements so the WDM driver won't install/work if Secure Boot is enabled.

JRU · « **Reply #8 on:** April 23, 2018, 04:01:17 pm »

I am on Windows 7, how do I check for Secure Boot on Windows 7? Or is Secure Boot not an issue on Windows 7?

tyler69 · « **Reply #9 on:** April 23, 2018, 04:03:01 pm »

Correct me if I am wrong, but JRiver should rather look into fixing this issue (I haven't seen an official reply on fixing this issue) than (implicitly) asking their users to disable a security feature. A sticky or an updated Wiki that would explain the situation and the risk of disabling secure boot might be beneficial for all involved.

RD James · « **Reply #10 on:** April 24, 2018, 05:25:06 am »

Quote from: JRU on April 23, 2018, 04:01:17 pm

I am on Windows 7, how do I check for Secure Boot on Windows 7? Or is Secure Boot not an issue on Windows 7?

I think the Secure Boot feature was introduced with Windows 8, so Windows 7 shouldn't be affected by it.

JRU · « **Reply #11 on:** April 25, 2018, 01:25:10 pm »

Ah okay, thanks for letting me know. So then what is the issue? Why isn't the WDM installing?

JRU · « **Reply #12 on:** April 27, 2018, 07:40:02 am »

No one? Any help would be appreciated, I really need the WDM to work. If I can even get it to work on MC23, that would be fine too.

dtc · « **Reply #13 on:** April 27, 2018, 08:22:26 am »

If I understand correctly, Microsoft changed their signing procedure for drivers. Not sure this is an issue with Windows 7 or not.

Awesome Donkey · « **Reply #14 on:** April 27, 2018, 12:08:47 pm »

Quote from: dtc on April 27, 2018, 08:22:26 am

If I understand correctly, Microsoft changed their signing procedure for drivers. Not sure this is an issue with Windows 7 or not.

From what I can tell, just Windows 10. It *should* work with Windows 7 and 8.1.

JRU · « **Reply #15 on:** April 27, 2018, 12:34:16 pm »

Quote from: Awesome Donkey on April 27, 2018, 12:08:47 pm

From what I can tell, just Windows 10. It *should* work with Windows 7 and 8.1.

It was working just fine on MC23, it was only after I installed MC24 that it didn't work on MC24, I thought it might be a conflict with MC23 so I uninstalled it in MC23 but now it won't work on either. The WDM is a large part of the reason I use JRiver and it not working is a big issue for me

RD James · « **Reply #16 on:** April 27, 2018, 01:03:41 pm »

I know this is probably a stupid question, but are you sure that you're running Windows 7?
Hit WIN+R and run "winver".

What you describe here is exactly what happened to me on my Windows 10 system.
MC23 was working just fine, and updated to 23.0.104 without any issues.
I installed MC24 and the WDM driver would no longer run. Downgrading to 23.0.104 still prevented the WDM driver from running.
The only version where the WDM driver still works is 23.0.80, but that version of the driver is known to cause BSODs.

That change is only supposed to affect Windows 10 though, as it was the 2016 Anniversary Update to Windows 10 that started enforcing the new driver signing requirements (which had been in place since the launch of Windows 10).

JRU · « **Reply #17 on:** April 28, 2018, 05:37:39 am »

I am 100% certain I am running Windows 7, I did the test you described anyway and it said Windows 7.

JimH · « **Reply #18 on:** April 28, 2018, 05:50:31 am »

Quote from: JRU on April 22, 2018, 12:30:16 pm

I have already read the wiki and it is not working, as I mentioned it was working but stopped working.

Did you read the wiki about Windows Control Panel settings?

JRU · « **Reply #19 on:** April 28, 2018, 11:13:18 am »

Quote from: JimH on April 28, 2018, 05:50:31 am

Did you read the wiki about Windows Control Panel settings?

I read this page -

https://wiki.jriver.com/index.php/WDM_Driver

JRiver does not even show up in the Control Panel Sound properties. It only lists my sound card.

JRU · « **Reply #20 on:** May 06, 2018, 10:38:17 am »

Anyone? I'm completely stuck on this and can't get it to work, no matter how many times I install/uninstall JRiver or tick/untick the boxes or restart windows.

JRU · « **Reply #21 on:** May 08, 2018, 11:56:06 am »

I have been trying everything but it is not working, as a last resort I did a system restore and now the WDM in MC23 is working, I didn't try installing MC24 again least it get broken again. JRiver MC23/24 was showing up in device manager with an exclamation point indicating that it was not working before I did the system restore, it listed some issue with windows driver signatures, I don't remember the exact message but it was listed as Code 52. Hopefully someone will be able to point out why it was not working and hopefully correct the issue for future MC releases. I really hope so because if the WDM is not sorted I will not be upgrading to MC25 when it comes and stick to MC23 where the WDM works. Hopefully this message can help others who have this issue.

RD James · « **Reply #22 on:** May 08, 2018, 12:02:21 pm »

I'm pretty sure that Code 52 is the error that you get when the driver has been blocked due to it not meeting the system's driver signing requirements.
I'm really missing being able to use the WDM driver now that I've updated.

JRU · « **Reply #23 on:** May 08, 2018, 01:12:54 pm »

If it is a problem with driver signing requirements then shouldn't it have never worked on the system to begin with? It has been working fine on Windows 7 for years. Why would it suddenly have a problem?

RD James · « **Reply #24 on:** May 08, 2018, 01:57:25 pm »

Quote from: JRU on May 08, 2018, 01:12:54 pm

If it is a problem with driver signing requirements then shouldn't it have never worked on the system to begin with? It has been working fine on Windows 7 for years. Why would it suddenly have a problem?

I'm still not sure why your system is affected since it's on Windows 7, but the updated version of the WDM driver had to be signed with a new certificate.
The new certificate has a date past the cut-off that Microsoft has set to allow less-strict driver signing policies to be used (so that older devices would still work) and the updated WDM driver does not meet the new requirements.

JRU · « **Reply #25 on:** May 09, 2018, 10:06:01 am »

Thanks for the explanation, it does bring up the question why its a problem on Windows 7. Does that mean that the WDM does not work on Windows 10?

RD James · « **Reply #26 on:** May 09, 2018, 10:46:44 am »

Quote from: JRU on May 09, 2018, 10:06:01 am

Thanks for the explanation, it does bring up the question why its a problem on Windows 7. Does that mean that the WDM does not work on Windows 10?

Not without disabling security features.

Mark_Chat · « **Reply #27 on:** May 15, 2018, 03:43:43 pm »

Quote from: JRU on May 08, 2018, 11:56:06 am

I have been trying everything but it is not working, as a last resort I did a system restore and now the WDM in MC23 is working, I didn't try installing MC24 again least it get broken again. JRiver MC23/24 was showing up in device manager with an exclamation point indicating that it was not working before I did the system restore, it listed some issue with windows driver signatures, I don't remember the exact message but it was listed as Code 52. Hopefully someone will be able to point out why it was not working and hopefully correct the issue for future MC releases. I really hope so because if the WDM is not sorted I will not be upgrading to MC25 when it comes and stick to MC23 where the WDM works. Hopefully this message can help others who have this issue.

I have this exact same problem.
I run Windows 10 Home as an administrator on my HTPC.

WDM driver no longer shows up as a sound device in sound manager and in Windows Device Manager there is an exclamation mark and a problem with device driver signing and code 52.

Of note, JRiver Media Center updates never installed automatically on this PC - I always got the "unable to load JRTools.dll" message unless I downloaded the Media Centre installation .exe file, right clicked and "run as administrator"

Is it a related problem? IS this due to it being Windows 10 Home (No problems with updating Media Center automatically on my Windows 10 Professional PC)

RD James · « **Reply #28 on:** May 15, 2018, 05:15:52 pm »

Quote from: Mark_Chat on May 15, 2018, 03:43:43 pm

Of note, JRiver Media Center updates never installed automatically on this PC - I always got the "unable to load JRTools.dll" message unless I downloaded the Media Centre installation .exe file, right clicked and "run as administrator"

Do you have UAC disabled on your system? The installer should be requesting elevation automatically.

Mark_Chat · « **Reply #29 on:** May 15, 2018, 11:00:26 pm »

Yes, I have UAC disabled. The screen greying or annoying alerts just, well, annoy me.

I have it disabled on my other PC too, and no problems with it. Are you suggesting that disabling UAC is interfering with installation of software? I assumed it should be the other way around.

RD James · « **Reply #30 on:** May 16, 2018, 12:06:54 am »

Quote from: Mark_Chat on May 15, 2018, 11:00:26 pm

Yes, I have UAC disabled. The screen greying or annoying alerts just, well, annoy me.

I have it disabled on my other PC too, and no problems with it. Are you suggesting that disabling UAC is interfering with installation of software? I assumed it should be the other way around.

If you disable UAC, software cannot request elevated permissions any more.
I'd guess that one PC is signed in as an admin account while the other is signed in as a standard user.
You shouldn't ever disable or reduce the UAC setting below its maximum, or use an admin account as a user account.

Awesome Donkey · « **Reply #31 on:** May 16, 2018, 03:33:36 am »

IMO, disabling UAC on a system will only lead to issues. The alerts may be annoying, but they serve a purpose.

munkey · « **Reply #32 on:** June 05, 2018, 03:25:37 pm »

Is there any update on this? The WDM Driver is also not working for me because because of the outdated digital signature.

When will JRiver be updating their certificate? I should not have to disable security features on my computer in order to use this feature.

Thanks

Mark_Chat · « **Reply #33 on:** June 19, 2018, 02:26:45 am »

Quote from: munkey on June 05, 2018, 03:25:37 pm

Is there any update on this? The WDM Driver is also not working for me because because of the outdated digital signature.

When will JRiver be updating their certificate? I should not have to disable security features on my computer in order to use this feature.

Thanks

I second this.
Any update please JRiver?
Is it currently being worked on, even if you can't give an ETA?

AnubisPantera · « **Reply #34 on:** June 22, 2018, 06:04:39 am »

Im also struggeling with this, so went back to MC20.

RD James · « **Reply #35 on:** June 23, 2018, 12:52:09 am »

The driver from 23.0.80 works with MC24 until this is resolved, but you must disable exclusive mode in Windows' sound device settings, as it can BSOD your system with that version of the driver.

INTERACT FORUM

Author Topic: WDM not working with MC24 (Read 3862 times)