Issues after updating to M-Files Version 25.8.15085.11

Hi Harpreet.

Like we were able to determine, the root cause was Trend Micro antivirus not having MFStatus.exe in its exclusion list. Adding this also here, so others will check this if they have similar symptoms.

Have a nice day.

I can confirm that – we encountered the same issue with TrendMicro and MFStatus.exe yesterday at two other customer sites as well. :-)

Hi

Do we need to exclude "MFStatus.exe" explicitly, or is it already covered by excluding the entire path `C:\Program Files\M-Files`? Just want to confirm - are we overlooking anything here?

According to the customers’ IT staff or their IT service providers, the MFStatus.exe cannot be defined as an exception in TrendMicro using the path with the %mfilesversion% variable.
Adding MFStatus.exe as an exception without the path did not work either.
Only after adding the full path "C:\Program Files\M-Files\25.8.15085.11\Bin\x64" 
as an exception, everything worked properly again.

Sorry, I’m not familiar with TrendMicro myself – we are using Bitdefender, and there the use of variables in paths is not an issue.

According to the customers’ IT staff or their IT service providers, the MFStatus.exe cannot be defined as an exception in TrendMicro using the path with the %mfilesversion% variable.
Adding MFStatus.exe as an exception without the path did not work either.
Only after adding the full path "C:\Program Files\M-Files\25.8.15085.11\Bin\x64" 
as an exception, everything worked properly again.

Sorry, I’m not familiar with TrendMicro myself – we are using Bitdefender, and there the use of variables in paths is not an issue.

We saw a number of users running into problems with Desktop Settings configuring the server connection. The automatic update halted and did not complete the installation. This customer also used TrendMicro.
Funny thing was that only about 5 or 6 users out of 75 were affected. I am not sure whether all of their users are on Windows 11 yet. That was the case for the affected users but may not be the case for the rest of them.

We were able to reinstall the 25.6 version manually to solve the immediate problem, and their service provider confirmed that they could add the exception using %mfilesversion%. When that came in place they were able to update M-Files. 

I can't say for certain whether there were clients with the same setup who were not affected. As mentioned, I don't have access to the customer's TrendMicro configurations myself, so I can only pass on the information I received from them.

With my own Bitdefender setup, adding an exception using the %Mfilesversion% variable in the path doesn't cause any issues – it works without problems.