I haven't bothered with updates since 5.0.0, as they all kept crashing immediately on startup. (Other posts on 5.0.1 and 5.0.2 detail this.) Our IT department mandates Sophos as the anti-evil software.
Installed 5.1.1 today (5.0.0 still installed) and it repeatedly crashed *instantly* on startup. I decided to open 5.0.0 - no problem. No models were open. (That was a problem with 5.0.1 and 5.0.2 crashing.)
Closed it and restarted 5.1.1 - it's open and hasn't crashed yet. (Mind you, I haven't done anything yet, but that's a lot better than where I was.) I loaded a random STL, closed and reopened 5.1.1. It opened without crashing and without the STL. Tools > Options > General > Restore workspace on startup was off. I enabled it, reloaded the same STL, and shut off 5.1.1.
OMG - it opened and loaded the model! Perhaps there was some startup junk from the past failed installs or 5.0.0 that got in the way of 5.1.1 that was cleared up somehow?
Regardless, hallelujah! We might be back on the road!
Re: 5.1.1 crashed instantly on startup, but... fixed?
*Moving this to the troubleshooting section so more users can find it*
You may have already seen this on the forum, but we have had other users confirm that Sophos was causing apps to crash and behave in weird ways on their computer. Multiple users were able to show that disabling Sophos immediately made all of those problems go away, so if you're running Sophos I would recommend trying to add an exception or temporarily disable the service to see if that suddenly resolves the issue.
Sophos interfering with another running program can certainly cause unintended side effects, so it's possible some of the files that S3D reads and writes could get corrupted in the process. If it ever happens again, I would recommend following the instructions here to see all of the files and settings the software may be trying to restore on startup:
https://www.simplify3d.com/resources/faq/#quest-6350
Deleting the savedState.factory file is sometimes all that is required.
You may have already seen this on the forum, but we have had other users confirm that Sophos was causing apps to crash and behave in weird ways on their computer. Multiple users were able to show that disabling Sophos immediately made all of those problems go away, so if you're running Sophos I would recommend trying to add an exception or temporarily disable the service to see if that suddenly resolves the issue.
Sophos interfering with another running program can certainly cause unintended side effects, so it's possible some of the files that S3D reads and writes could get corrupted in the process. If it ever happens again, I would recommend following the instructions here to see all of the files and settings the software may be trying to restore on startup:
https://www.simplify3d.com/resources/faq/#quest-6350
Deleting the savedState.factory file is sometimes all that is required.
