3
1
I am investigating a crash in an application (as a developer of the application). One of the things that happens at the time of the crash is that the Application Experience service starts.
I am wondering whether Windows loads this service once it detects a problem with an application in order for it to see whether there is a solution to recommend to the user; or whether the Application Experience service is a potential culprit.
The information that I've found (http://support.microsoft.com/kb/902196) suggests that the Application Experience service applies updates to applications in the background. If this is what it is doing, then I would say that it's a potential culprit.
Can anyone tell me whether this service is started in response to existing problems?
There's a good explanation of what this service does on ServerFault: Windows Application Experience Service. From that post: "There is a huge database of compatibility shims for thousands of permutations of applications ... Microsoft might notice, based on their vast amount of collected telemetry data, that a million people are suffering from an application crash ... and Microsoft may develop an update or a new compatibility shim based on that info."
– jrh – 2017-02-21T19:24:30.217... based on that I would say that the service starting is in response to (not the cause of) the crash. – jrh – 2017-02-21T19:25:12.347