1 of 1 people found this helpful
If you launch FileMaker without attempting to open a file, do you get the same crash?
I would expect so given the above description, but let's be sure.
Since installing/updating an app can make a change to the registry, while I wouldn't list an update to Adobe Flash at the top of my list of suspects, you can't absolutely rule it out either.
Have you run any utilities such as chkdisk to see if your hard drive is healthy?
Try from a different windows user account or better yet, create a brand new user account and try launching FileMaker from the new/different user account.
I've seen damaged user acounts (and never did figure out what exactly damaged the account) that repeatedly crashed FileMaker and fixed them by creating a new user account.
This does appear to be a user profile related problem. I could use Filemaker as another user on the same machine. I deleted my network profile and the error has gone.