Windows 10 1903 Voice Modem stops working

After upgrading to 1903 my voicemaill system no longer works. I can't play outgoing messages to people who call nor can I record messages they want to leave. I'm using a USRobotics voice modem and everything has been working fine until this 1903 "upgrade".  I have checked the drivers and the unimodem drivers are there it's just not seeing my modem as a voice modem and installing it as a sound device to record calls and play outgoing messages.  After rolling my system back to the previous version everything is fine. I know that I'll be forced by Microsoft to eventually install 1903 and that sucks as I really need my voicemail system........ Any suggestions?
|

Was this discussion helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this discussion?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this discussion?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

I know no one has responded to you but I am impacted by the same issue on a voicemail system.  The same thing happened with 1511 and it took MS months to resolve.  Very frustrating.  If you already have a fix, please let me know that it was.

4 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I know no one has responded to you but I am impacted by the same issue on a voicemail system.  The same thing happened with 1511 and it took MS months to resolve.  Very frustrating.  If you already have a fix, please let me know that it was.

Yes it's so frustrating! I went back to Windows 10 1809 and set my Windows 10 Feature Update to delay version 1903 for a year. Hopefully they will fix the issue by then. If you hear of any fixes or if Version 1903 is fixed I would greatly appreciate it if you would let me know............ Thanks...........Greg

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Same issues here although I have a different brand of voice modem. 

Does anyone have a workaround yet? 

Have any vendors responded?

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello,

Same problem here, using Multi-Tech modem and it will not work 

on Windows 10 - 1903. 

Any fix yet?

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Received an alarm about this from our partners.

Tested our Virtual Fax-Voice Modems (TAPI compatible) with the good old CallStation application.

Can confirm the bug in Windows 10 1903.

The CallStation reports "Failed to get modem wave out ID" when trying to turn on the voice functions.

The restarting of the PC and re-installation of modems does not help.

This problem is not present in Windows 10 1809 and in Windows Server 2019.

The problem is similar to the one that caused heated debate several years ago:

http://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/56k-modem-missing-unimodem-audio-device-after/7a53af94-21fe-4352-80ec-b27fb3dc5886?page=1

(Then it was finally resolved on the Microsoft side.)

However, this time some other reasons.

The "Unimodem audio Device" associated with modem is installed and present in the Device Manager as required.

Have tried to find a workaround.

The replacing of modem.sys (from older Win version) does not help this time.

Tried also to replace the following system files: rootmdm.sys, ModemcSA.sys, ksthunk.sys, csamsp.dll (standard windows files on which voice modem drivers depend) - also without success. No ideas what is wrong.

As we noticed, vendors have already begun to give massive recommendations not to install 1903 (with pictures of how to roll back to the previous Windows version).

See example:

https://supportdesk.win911.com/support/solutions/articles/24000043298-windows-10-version-1903-tapi-incompatibility

It is clear that this is the wrong way.

The only right way, the problem should be fixed on Microsoft side, and the faster the better.

Can you please fix?

Thanks in advance.

9 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thank you,,,Hopefully this will be fixed soon!!!!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The problem is somewhere with winmm,dll

waveOut…

waveIn…

waveOutGetNumDevs/waveInGetNumDevs do not contain "modem" voice devices in the enumeration (like before), do not see!!!

https://docs.microsoft.com/en-us/windows/win32/api/mmeapi/nf-mmeapi-waveoutgetnumdevs

so waveOutOpen/waveInOpen (that TAPI app need) or any other will not work.

The replacement of winmm,dll etc. does not help

May be something wrong with registry, may be something corrupted in Windows audio subsystems.

No further ideas.

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Well, here is the manual fix and will work.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
"waveN"="serwvdrv.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32]
"waveN"="serwvdrv.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Userinstallable.drivers] //???
"waveN"="serwvdrv.dll"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96c-e325-11ce-bfc1-08002be10318}\000X\Drivers\wave\serwvdrv.dll]
"Driver"="serwvdrv.dll"
"Description"="Modem Wave Driver"
"Alias"="waveN"

For example, you have installed 2 voice modems.

1) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]

Find the last wave[N-1], say "wave1" exists and create 2 entries:

"wave2"="serwvdrv.dll"
"wave3"="serwvdrv.dll"
2) [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32]

Add the same as in (1)

"wave2"="serwvdrv.dll"
"wave3"="serwvdrv.dll"
3) Find your "unimodem" devices at this path:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96c-e325-11ce-bfc1-08002be10318}\ and add aliaces you have already added:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96c-e325-11ce-bfc1-08002be10318}\0003\Drivers\wave\serwvdrv.dll]
"Alias"="wave2"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96c-e325-11ce-bfc1-08002be10318}\0004\Drivers\wave\serwvdrv.dll]
"Alias"="wave3"
4) Restart the computer. Will work.

Normally, all these keys should be properly registered when installing the modem driver, but for some reason 1903 does not do this.

(assumption) Most likely again some kind of defective file, as it was with the modem.sys last time, presumably one of the above mentioned. Necessary to replace consistently and test. But the bottom line is that they must be replaced at the time of installation of the modem driver, and not when modem is already installed.

And naturally, Microsoft is simply obliged to deal with this, because writing such "fixes" on the vendor's side is at least a bad idea.

Thanks.

5 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Well, even easier, you need to add 1 entry into registry (and its 32-bit copy on x64).

1) Goto [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]

Find the last wave… parameter, say "wave" and "wave1" are exist and create 1 new entry wave(+1):

"wave2"="serwvdrv.dll"
2) Goto [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32]

Add the same as in (1)

"wave2"="serwvdrv.dll"

3) Restart the computer.

The already installed modems will work. The new modems that you will install later also will work (after installing a new modem, you must always restart the computer, otherwise TAPI does not see waveID).

No need to delve into the unimodem voice devices keys, especially since there is usually a mess of new and already deleted ones.

Well, in general, any vendor can add this fix ... although this is incorrect and should be fixed on the Microsoft side.

7 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thank you again. 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Discussion Info


Last updated October 13, 2020 Views 1,346 Applies to: