Uninstalled and reloaded Flowbotics Studio, over three times, then went to a second computer. Same problem.
Went to second computer and the problem was there too. Then it started up long enough for me to work on a project and then I closed the app and on relaunch the problem is back. It shows up instantly upon launching the app. Then after waiting a while it started working again. Had to close the program for something else and it would not launch. Tried many times to launch, it seems like it crashes after two to three seconds of the spinning Windows timer, after clicking to launch. Then I unplugged my Wi-Fi usb adapter and it launched. But then broke again. The first computer does not have wifi.
The intermittent nature of the issue you describes seems to indicate something else is causing interference with FBS (FlowBotics Studio) that is running on your computers. This further seems to be the case since the software can and does run at times properly.
As you may be able to imagine it would be quite difficult to determine what interactions are causing this issue without any other data. This is especially true if we cannot reproduce the issue (we can’t). I have a strong feeling it is tied to something else that is happening on both of your computers. Could be as simple as a security suite/software doing something funky or a spyware or virus causing this problem. Or really any other software doing something that causes FBS to crash.
Unfortunately those are only data dumps for Microsoft and not exactly useful for us.
What may be useful would be a dump from FBS of the state of the software when the error happen.
You can find error dumps in the folder %AppData%\FlowBotics. Simply go there and look for dump (.dmp) and error log (.txt) files. You can then compress those files (ZIP?) and attach them here.
This being said, it is unusual that you did not receive an error pop-up from the software itself to send an error report (from FBS, not Windows/Microsoft). This would indicate the failing completely stopped the app (including error handling) instead of the app actually crashing.
