Unfortunately, the attempt to set the Telephony- service to „start automatically“ with the setup of version 4.3.141 turned out to be a misstep. Some users report that uninstalling 4.3.141 results in the Telephony- service no longer being visible in the Services- control panel. Version 4.3.142 is also affected.
The reason for this is that during the uninstallation process, the setup sets the value called Start in the registry under ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTapiSrv instead of resetting it to its default value 3 (= start manually). This value correlates with the setting that you have specified as the start mode in the Services- console:
1. recovery via Reg-File-Import
2. Manual recovery in RegEdit 1TP18Alternative to 1)
The Windows Installer Setup for TAPICall has been extended with the intention of ensuring that the telephony- service is set to „start automatically“" mode, as since Windows 10 the service is increasingly not yet ready when TAPICall is started and there are corresponding problems when connecting to TAPI. Although the service is started when required, this usually takes too long. The behaviour of older Windows - versions would be desirable, which start the service without delay when the system is started, so that it is already running when TAPICall needs it.
In the service management console, you can set the start mode of the service to „automatic„„. However, Windows 10 apparently always resets the value to "manual“. The idea was to use the Windows Installer to keep the value at "automatic“ and to bring systems into the correct state immediately when installing TAPICall.
TAPICall itself attempts to influence the control of the service via WMI, but is usually unable to do so successfully because the user context in which TAPICall is running as a process does not allow changes to the registry. This requires elevated rights, which require a UAC-Prompt. However, since we do not want to run TAPICall as an administrator and only a few users work as local administrators on their PCs, the automatic setting of the service by TAPICall itself is rarely successful. The next idea was to let the setup do this part, as it always runs in a context with elevated rights and practically full system access.
As it is not possible to address the Windows- service administration directly from an MSI- setup, we have instead directly addressed the registry- value that determines the start mode of the telephony- service (tapisrv).
Unfortunately, however, when a product is uninstalled, the Windows Installer cancels all the settings that came with the setup. Even if the Start- value already existed before the setup was executed, it is deleted during uninstallation, which does not correspond to the expected behaviour, but has unfortunately been observed on several systems.
Removing the Start-Who makes the Telephony- service inaccessible.
If you have updated from 4.3.141 to 4.3.142, which is basically an uninstallation of 4.3.141 followed by an installation of version 4.3.142, then its setup will have reinstalled the same ( component, i.e. the Start-value is retained with the value 2, but uninstalling version 4.3.142 would also unintentionally delete the value again.
To prevent this from happening again in future, the component in question has been removed from the setup.
PCs that had versions 4.3.141 or 4.3.142 installed are very likely to require the repair steps listed above, even if they are upgraded to a newer version (>= 4.3.143).
PCs that have updated from version 4.3.140 or older to 4.3.143 or newer do not need this repair, as both older setups and all setups from version 4.3.143 onwards leave the Telephony- service untouched.
We regret these circumstances and apologise for any inconvenience caused!
The reason for this is that during the uninstallation process, the setup sets the value called Start in the registry under ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTapiSrv instead of resetting it to its default value 3 (= start manually). This value correlates with the setting that you have specified as the start mode in the Services- console:
- 2 = start automatically - if the „Start automatically (delayed)„ mode has been selected, there is also a DWORD- value called "DelayedAutoStart“ with the value 0x00000001
- 3 = start manually
- 4 = deactivated
1. recovery via Reg-File-Import
- Download the attached ZIP and unzip it to any location on your PC
- The contained file tapisrv_manual.reg can be used if you want to restore the service in „manual start“ (Standard)" mode. The file tapisrv_auto.reg restores the service with the „start automatically“" mode.
Please import only one of these files, as only the last imported „gewinnt“. - To import the desired file, double-click on the file and then confirm the UAC-Prompt and the security prompt posed by the Windows Registry Editor (meaning: „Do you really want to import the settings from the file?“)
- RegEdit will confirm that the file has been imported.
- If the double-click does not work, e.g. because your antivirus-product prevents this, you can also start RegEdit manually (open the Start menu, enter „regedit“ and press Enter/Return). In the RegEdit-programme there is a menu item File the subitem Import..., where you can specify the desired file
- You can check the success of the import in RegEdit by going to the path ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTapiSrv and select the value displayed in the right half Start check. It should be of the type REG_DWORD and, depending on the selected file, either have the value 0x00000003 (3) or 0x00000002 (2).If the value is missing completely, the import may not have worked. Try again; if necessary, you can carry out the steps described below.
- Now restart the PC to apply the changed configuration. The Telephony- service should then be visible again in the administration console
- If the service is now visible again, you can skip the steps described below under 2.
2. Manual recovery in RegEdit 1TP18Alternative to 1)
- Start the Registry Editor by clicking on the Windows- logo (= Start menu) and entering regedit, followed by the Enter/Return-key. A UAC- prompt may need to be confirmed before the programme starts.
- Navigate to the path ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTapiSrv - Since Windows 10, this address can simply be entered in the address bar of RegEdit to jump directly there. With older Windows- versions, you have to find this folder step by step through the tree structure
- In the right-hand half of the window, there should be TapiSrv-folder, among other things, a value called Start find. If it is not present, the service cannot be displayed and managed. If the value is present and the service management console still does not display the Telephony- service, the PC may need to be restarted in order to process the changed Registry- data
- Assuming the value Start is missing, you can create it as follows:
[list] - select Edit -> New -> DWORD-Value (32-Bit) from the menu. Please ensure that you create the 32-Bit- value and not the 64-Bit- value
- In the next step, the value you have just created is named. Please enter the following name Start a
- To set the value, double-click on the line you have just created. In the dialogue, simply enter the number 2 or 3 as the value. 2 stands for „start automatically„ and 3 for "start manually“. Confirm the value with the OK-button.
- in the overview you should now see that the Start-Value was taken over with the previously specified number
- Now restart the PC to apply the changed configuration. The Telephony- service should then be visible again in the administration console
The Windows Installer Setup for TAPICall has been extended with the intention of ensuring that the telephony- service is set to „start automatically“" mode, as since Windows 10 the service is increasingly not yet ready when TAPICall is started and there are corresponding problems when connecting to TAPI. Although the service is started when required, this usually takes too long. The behaviour of older Windows - versions would be desirable, which start the service without delay when the system is started, so that it is already running when TAPICall needs it.
In the service management console, you can set the start mode of the service to „automatic„„. However, Windows 10 apparently always resets the value to "manual“. The idea was to use the Windows Installer to keep the value at "automatic“ and to bring systems into the correct state immediately when installing TAPICall.
TAPICall itself attempts to influence the control of the service via WMI, but is usually unable to do so successfully because the user context in which TAPICall is running as a process does not allow changes to the registry. This requires elevated rights, which require a UAC-Prompt. However, since we do not want to run TAPICall as an administrator and only a few users work as local administrators on their PCs, the automatic setting of the service by TAPICall itself is rarely successful. The next idea was to let the setup do this part, as it always runs in a context with elevated rights and practically full system access.
As it is not possible to address the Windows- service administration directly from an MSI- setup, we have instead directly addressed the registry- value that determines the start mode of the telephony- service (tapisrv).
Unfortunately, however, when a product is uninstalled, the Windows Installer cancels all the settings that came with the setup. Even if the Start- value already existed before the setup was executed, it is deleted during uninstallation, which does not correspond to the expected behaviour, but has unfortunately been observed on several systems.
Removing the Start-Who makes the Telephony- service inaccessible.
If you have updated from 4.3.141 to 4.3.142, which is basically an uninstallation of 4.3.141 followed by an installation of version 4.3.142, then its setup will have reinstalled the same ( component, i.e. the Start-value is retained with the value 2, but uninstalling version 4.3.142 would also unintentionally delete the value again.
To prevent this from happening again in future, the component in question has been removed from the setup.
PCs that had versions 4.3.141 or 4.3.142 installed are very likely to require the repair steps listed above, even if they are upgraded to a newer version (>= 4.3.143).
PCs that have updated from version 4.3.140 or older to 4.3.143 or newer do not need this repair, as both older setups and all setups from version 4.3.143 onwards leave the Telephony- service untouched.
We regret these circumstances and apologise for any inconvenience caused!
Answer #2
Summary of the solution:
Exit TAPICall and Outlook and install the latest version of TAPICall from this link simply "over it“, done.
In rare cases : If that doesn't work, run this ZIP- file tapisrv_auto.zip execute tapisrv_auto.bat as administrator and restart your computer.
Exit TAPICall and Outlook and install the latest version of TAPICall from this link simply "over it“, done.
In rare cases : If that doesn't work, run this ZIP- file tapisrv_auto.zip execute tapisrv_auto.bat as administrator and restart your computer.