Windows 10: Windows 10 TAPI intialize fails!

I am having the issues with TAPI and my search shows that all users face the same.

It seems the windows 10 TAPI fails to initialize! I can not believe how Microsoft could release like that and not fix it yet.

Here is how to reproduce it - download sample code from here. And run the program and see tapi.Initialize() fails to return (forever loop).

Windows 8 TAPI 3 in C# - Get Lines and make a call, see calls incomming sample in C# for Visual Studio 2010

Would appreciate a response from anyone if they have a work around. I need to for a high priority customer issue. Thanks!

:)

 

TAPI stopped working after Windows Creator's edition update

I have a program, which I developed in .net and sell as shareware. This program uses Microsoft's Telephony Application Programming Interface (TAPI) to access tapi complaint devices such as the Hiro H50113 modem or the Way2Call Hi-Phone Desktop Pro.

Unfortunately, immediately following the Windows 10 Creators’ update (Version 1703 – OS Build 15063.138) tapi no longer seems to be available on my machine.

That is to say, while my program can access devices directly (by using AT commands) it can not access them via tapi.

I’ve checked other machines and following the Windows Creator's edition update they are working ok with my program. So the problem seems to be localized to my machine.

Also, I checked Microsoft’s own fax and scan program – which also uses tapi – and it too does not recognize tapi devices following the Windows 10 Creators’ update my machine.

Additionally, from the windows Control Panel the ‘Phone and Modems’ option does not open up – it just hangs on my machine.

Working thru this post:

Small issue after upgrading to creator's update Solved - Windows 10 Forums

none of the ideas presented helped.

In the MS Event Log there is a 7000 error for Service Control Manager, its details read:

The CldFlt service failed to start due to the following error:

The request is not supported.

I’ve searched for that too, but no luck.

This was not a problem prior to the Windows 10 Creators’ update.

I really really really want to avoid a reinstall of the OS.

Any help would be appreciated.

 

Modem Wave Driver Issue

The same issue occurs with CallClerk in Windows 10 Nov update. This appears to be a Windows issue. Is anyone at Microsoft working on the issue? TAPI voice modems are no longer supported.