After updating Microsoft Windows 10 to release version 1903, you find that your voice modem disabled. Applications that use TAPI voice functionality are no longer functioning. Audio playback and recording to the voice modem no longer work.
Symptoms:
Software is not detecting the modem as a compatible voice modem (voice modem disabled, no wave device found) and no audio playback/recording functionality. Some non-voice functionality of the modem may continue to work (outgoing and incoming calls, caller ID detection, etc.)
Some affected TAPI voice applications include: Win-911 V7 & Win-911 Standard, CallStation, VTScada, VZEnhanced56K and Phone Eve.
NOTE: This problem does not apply to software that uses “TAPI passthrough mode” to communicate with the voice modem. FaxTalk uses pass through mode for voice functionality and is not affected by this issue.
To continue using the software, third party vendors are suggesting you roll back to the previous version of Windows 10.
Workaround Solution
This solution is provided by our friends at http://www.t38faxvoip.com/ and is provided as-is, with no warranty or liability. This is for version 1903 of Windows 10 only and allows you to continue using your voice modem in Windows 10 version 1903. Please only follow these instructions if you are comfortable editing the Windows registry.
This workaround involves adding a missing driver related registry entry, and requires rebooting your computer. You do not need to uninstall or remove your voice modem drivers.
- To verify that your voice modem audio device has been detected in Windows 10:
From your Windows device manager, locate the “Sound, Video and Game Controllers” section. In this section, locate the “Unimodem Full Duplex Audio Device“, “Modem Audio Device” or “Unimodem Half Duplex Audio Device“.
NOTE: Click on “View, Show Hidden Devices” to display devices that are installed, but not currently active on the system.
2. Double-click the Unimodem Audio Device entry and verify that the location of this audio device is your voice/fax modem. If you have multiple modems, you may see more than one Modem Audio device listed.
3. Using regedit, locate the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32
In the Drivers32 key, locate all keys listed with “Wave#”.
For example, “Wave”, “Wave1” , “Wave2” etc. Determine the last “Wave#” key value that exists. If you only have “Wave” listed here, then create a new string value named “Wave2” with the string data “serwvdrv.dll“. If you have multiple keys that exist such as “Wave”, “Wave1”, “Wave2”, then add the the next available new string value. For example, “Wave3” with the string data “serwvdrv.dll“
4. If you are using a 64-bit Windows 10 – version 1903, you must repeat step 3 for using the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32
Note: If the Drivers32 key doesn’t exist in WOW6432Node\Microsoft\Windows NT\CurrentVersion, then you are using a 32-bit version of Windows 10. Skip this step and go to Step 5.
5. Restart Windows.
The voice/fax modem will now work for recording and playback, using any compatible TAPI application.
Acknowledgments:
Thanks to T38FaxVoip.com for troubleshooting and finding a solution and Eric Kutcher for his additional help.
Additional links, resources, notes:
The post Voice modem disabled with Windows 10 version 1903 appeared first on GetFaxing.com.