3cx Client Updater ERROR

[Connexium Partner]

Hello,

We have encountered issues with the latest version of 3cx that triggers an update of the Windows Softphone:



Knowing how tech illiterate are some of our customers, this would likely be a logistical nightmare to manually (download and re-install) all Windows Softphones.

Any suggestions?
Thank you

 

[SteveITS]

FWIW I ran the Windows client as a standard user and it self-updated fine. Is it working on any PCs? Perhaps check file/folder permissions?

 

[JohnS_3CX]

Hi

As @SteveITS noted, standard users should also be able to auto-update.

However file permissions are still not granted in your case.

Perhaps that specific deployment environment has other security group policies that stop the client from self updating. You will have to look into that possibility and see what could be blocking file access (even antivirus suites may be stopping this).

 

[Connexium Partner]

Hello, I am glad it's working well for you. But I am still experiencing errors. The PC used in the OP has only microsoft anti-virus. Its Windows 10 PRO Build 17763. Nothing fancy.

I uninstalled the softphone and re-installed version 15 manually. Installation was ok. It did however asked me for permission by the UAC.

As for the upgrade, I was now able to download the upgrade package but another permission error gave me this message:


When trying to manually browse to that location (C:\ProgramData\3CXPhone for Windows\PhoneApp\temp\Notification) using the Windows File Explorer, I do get a permission error:


Lastly, I uninstalled the Softphone once again and deleted the folder C:\ProgramData\3CXPhone for Windows (because lots of stuff was still in that folder after uninstallation). Reinstalled Windows Client v15 to trigger self update and I was now able to have the built-in upgrader work without errors

Anyways, I wanted to share this with you because I may not be the only one who will get this error while upgrading.

 

[JohnS_3CX]

Thanks @Connexium Partner

It sounds like the permissions for the folder were messed up for some reason.

Deleting it altogether and then reinstalling was the key: It must have recreated the permissions according to what the windows user profile is allowed to inherit.

I cannot say for sure what the permissions were before, but if you do come across it again it would be good to compare the properties of the healthy folder VS the one that is problematic:

1. Permissions


2. And the Advanced window to see the Owner of the object

 

[Connexium Partner]

Excellent. Thank you for this information.
If I encounter this issue again, I will try to capture the folder permissions and update this post for reference. In the meantime, I hope this thread can help other users with a similar issue.