We have an application that we are trying to profile to persist in an instant clone environment and every time we try to use the application profiler it crashes.
I have tried both LTSB (our environment currently) as well as 1803 as a profile machine.
I load up the UEM Profiler, point it at the correct start menu item (I have also pointed directly to the exe that runs) and after 1-2 seconds it comes back and the application we are attempting to profile never starts.
Looking at windows application logs, the program in question when attempting to run under the profiler application is terminated due to System.OverflowException.
The application in question loads up fine on it's own without being profiled.
Any ideas or workarounds to finding where this program saves it's info?