topic Re: BIMcloud 2025.1 Not Showing 2025.3 Update in Teamwork & BIMcloud

BIMcloud 2025.1 Not Showing 2025.3 Update

vlahtinen — Fri, 14 Nov 2025 09:36:00 GMT

Hi everyone,

Our BIMcloud Server (version 2025.1) isn’t notifying us about the 2025.3 update. Check for updates is enabled in the BIMcloud Manager settings, but the update notification still doesn’t appear. In the past, we always got a notification when a new update was available.

Is this expected behavior, or are there any extra steps required before BIMcloud will detect the 2025.3 update? I haven't yet tried to run the installation package of the new version.

Thanks for any guidance!

Re: BIMcloud 2025.1 Not Showing 2025.3 Update

vlahtinen — Fri, 14 Nov 2025 09:40:04 GMT

The installation package seems to find the previous installations normally.

Re: BIMcloud 2025.1 Not Showing 2025.3 Update

Kornel Beleznai — Tue, 18 Nov 2025 21:29:45 GMT

Hello there,

I'm sorry to hear about your problem, and thanks for raising it here.

I tested this behavior on my side with the same BIMcloud version (2025.1), and it seemed to be working properly: the notification about the newer version appeared.

According to this, if the issue with the Check for Updates notification still happens on your side, please consider contacting your local support for further help.

Thank you for your understanding.

Cheers!

Re: BIMcloud 2025.1 Not Showing 2025.3 Update

vlahtinen — Tue, 18 Nov 2025 19:48:38 GMT

Thanks for checking and confirming it’s working on your end!

If there aren’t any known issues with proceeding manually, I’ll go ahead with the manual update rather than troubleshoot this further. If anything unexpected comes up, I’ll report back.

Re: BIMcloud 2025.1 Not Showing 2025.3 Update

Kornel Beleznai — Thu, 20 Nov 2025 15:57:51 GMT

Hi again,

I talked to the related Product Manager about this case, and they let me know that this is actually a known issue that was already registered in our database as DEF-25924. They intend to fix it in the next BIMcloud on-premises update, but the investigation and fix seem to be more difficult, so the timeline is not set for it yet.

Unfortunately, there are no known workarounds for this issue either at the moment. I'm sorry for the inconvenience.

Best regards!