Yes, it looks like that was coincidence. We had the same problem again yesterday even though no menu edits had been performed. We had seven or eight users with Evo (old) open via Terminal Services and five or six using DBA. The Evo users all experienced codebase errors and were ejected from the program.
We captured the error messages that we received when trying to log in again and will post images after the IT department meeting this morning. Unfortunately, I was in a meeting when the crash occurred and my own session/crash screen was not available because my computer was at the BSOD
[Made me wonder if Evo crashing was related to my computer crashing, since the problem cleared up on its own shortly after I rebooted.]