Brandon’s reply is helpful if the reason is generally, but from your reply it looks that’s not related with account reason etc.
The most direct solution is install a IDE for example VS or other to catch what’s the detail exception.
If your environment is not allowed to install IDE, you can add some code in the sample code, for example:
this.DispatcherUnhandledException += new System.Windows.Threading.DispatcherUnhandledExceptionEventHandler(App_DispatcherUnhandledException);
AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);
Then print the exception into a log file. You can also try to check system log to see whether any exception caught by windows.
If you think the logic loop in any function for example ExtractTiles, you can also dump some text in log file to trace what’s the status when it’s run.
Before that, you should want to find another machine, copy entire folder and run product center first, login your account, activate the product and try again, this is for make sure whether it’s a special environment problem.
In fact we found some new machines to test and it still works well.
Any news about your test please let us know.