No issue at all here.

Upgraded 10 hours ago and all is fine till now...

I hope it will stay like this for you. We updated 23:00 cet yesterday. First lock started at 11:30 today (so after 12h30 of uptime)

I'll have to stay around to kill the process if it happens again :/ and hope that having to kill the process will not corrupt any files like it used to do with for example json config and kind of db files...

Our update had no problem, we don't use MAPI.

We don't either. I hope this is a false alarm but as it already happened 3 times since the update, we're being cautionous here.

It might be some background procedure running after the update that gets stuck il a loop. Let's see if it happens again...

Hi Ron,

No OS reboot but : stop service, uninstall, launch installer. As we always do to try to keep the downtime as low as possible.

I probably try a full OS reboot if problem comes again.

Have you had any further issues Sebastien?

Hello echoDreamz,

Not since the latest service kill/restart. I'll update the thread if it happens again.

Would be good too if ST could indicate if a build is safe to downgrade back to the previous build in the changelog, just incase breaking issues do occur, we know if it is safe to rollback.

No issue today since the latest restart. Let's say that it was a temporary issue due to dunno what. So false alarm :)

Hello everyone, 48 hours have passed since the update and no issues reported yet. I tested the fixes for the issues that were the most critical for us (handling of message text encoding and the issue of attached files that contained accented characters) and everything seems fixed. On the other hand, our customers being mainly businesses, the ultimate test will be when they return to work on Monday morning. I keep my fingers crossed!

Yes FrankyBoy. Crossing fingers too, here they start working right now. It's the real test.

We updated 48 hour ago and never had issues