If this were on my computer, I would examine the error using a tool like ProcDump. Various options are available, but I would recommend running something like this to start looking for the error:
> procdump -e 1 -f "" -w uistudio.exe
This will launch ProcDump such that it will wait for you to launch UI Path. As soon as you try to launch it, ProcDump will immediately attach to the process and start dumping all errors it captures.
Explanation of parameters:
- -e 1 = Capture all “first chance exceptions” (this will include “handled” exceptions).
- -f “” = Filter exceptions (and include all).
- -w uistudio.exe = Wait for this executable to load into memory (it will attach to the first one).
You will probably see a lot of exceptions. Only one of them will be the cause (usually the last one). Depending on how deep you want to get into the issue, you can use other options in ProcDump to generate a full memory dump, and start exploring stack traces, parameter values, etc. That requires memory debugging skills, but ProcDump can definitely generate what’s needed to investigate.