v16 Windows App Not Updating

[jms]

Clients of one of my 3CX servers are experiencing failed Windows app updates.

The user opens 3CX.
The message appears: "The 3CX app requires the latest version of the 3CX phone system, version 16. Contact your admin to upgrade 3CX and launch the app."
The user clicks OK.
Nothing happens.

When a client of the other 3CX server gets the same message, they click OK and the app updates.

I've checked that I can get the app manually from the server by typing "http://svrcha16:5000/myphone/3cxforwindows.msi" into a web browser. The msi file downloads, and it's the correct size.

The clients are all on a different subnet to the server. There is a VPN to enable access to internal addresses. The firewall allows all traffic on the VPN, and SIP, RTP, Tunnel and 5000-5001 to the Internet.

What could be stopping the client app from updating?

 

[CentrexJ]

Is the failing one not running v16 sp5? New client needs sp5.

 

[jms]

Both are running 16.0.612. Neither has outstanding server updates.

 

[JohnS_3CX]

Hello,

Perhaps the user does not have sufficient rights on that machine for the app to autoupdate itself?

What if an administrator logs into the machine and launches the client, will it autoupdate?

What version is the client currently?

 

[jms]

In every case I have manually installed the update from the latest 3cx.com web site download.

I noted a while back that the client install was asking for a different C++ runtime, which users don't have rights to install. Previously I had deployed vcredist 2010 and vcredist 2015 by group policy as a 3CX prerequisite. The latest v16 client installs vcredist 2019 (which includes 2015 I believe).

I've added a GPO to install vcredist 2019 and I will see if this fixes it. One that I fixed yesterday had already installed the client but wouldn't work until I ran a repair install from appwiz.cpl. It didn't want to reinstall vcredist.

 

[jms]

I just had another instance of this and could spend time with the machine. JohnS probably has something in regard to rights.
User logs on, 3CX opens, says it needs an update. Version is 16.3.0.111.
User clicks OK, nothing happens.
I make the user a local admin.
User logs on, 3CX opens, says it needs an update. Version is 16.3.0.111.
User clicks OK, nothing happens.
I revoke admin privileges.
User logs on. 3CX opens, works fine, doesn't say it needs an update. Version is still 16.3.0.111.

 

[SteveITS]

I was just able to update to the new Windows client released today, running as a standard user.

Where are you looking at version numbers? The version in Settings/Apps in Windows isn't changed after an update: https://www.3cx.com/community/threads/windows-client-updater-doesnt-update-version-number.73377/

 

[jms]

There's an About screen in Settings, Advanced Settings in the Windows client. It has the same number as in appwiz.cpl.
The msi in "http://svrcha16:5000/myphone/3cxforwindows.msi" is the same size in both 3CX servers. Only one is experiencing the problem.

 

[SteveITS]

. It has the same number as in appwiz.cpl

Interesting, Windows still shows 16.0.1.81 for our PCs, while the software is newer.

 

[jms]

This issue recurred on a machine i'd previously "fixed" today.
I remembered that I noticed an App update came through yesterday on a 3CX server.
I updated the server in question with the app. Now it's all fixed and works as expected/remembered: user clicks OK, app closes, update runs, app opens, all is good.
Interestingly, the change log says v16.3.0.111, which I was using, is a BETA.
My mistake, probably. My policy is not to use BETA software.
So I'm on version 16.3.0.144 now and it appears to be fixed. If it comes up on any more machines I'll update this thread.

 

[SteveITS]

change log says v16.3.0.111, which I was using, is a BETA.
My mistake, probably

I noticed that also. That was the version from v16 update 5.

 

[JohnS_3CX]

The app version in Windows Add/Remove Programs will not change. This is normal, the updater will replace the files of the existing installation so goes without saying that you should check your version from within the app and not rely on the Windows registry entry.