DanKH

"Please check the times of those entries" Ha Ha, I like the way you talk back to people Pete, always have and always will. You missed to quote one of my statements: "But as Emile wrote, I only had these errors in connection with a FSX crash. If I have a successful FSX-session with normal use, and closure, the event is not logged/fired only in the case of a FSX crash...." "It is absolutely nothing to do with any SDK -- the SDK isn't even provided to FSX users of the non-Deluxe version" Sorry my bad, I naively thought that simconnect only shipped with the Deluxe version as the SDK does, hence the question. But as you have most clearly pointed out, there's nothing wrong with FSUIPCapparently. So I just hope that time will show that you're right. I can't remember when you last started out a reply with a "really`, I'll take a look to see if there could be something wrong here..." Normally it take a few postings to convince you that something might need to be "adjusted"... well anyway. Thank you for your program, I continue to use it out of necessity. And of course always use your latest version. Hopefully I won't run into the same problem when I need to have it installed in the future.

Hi I got the exact same errors as Emile. Only getting when in connection with a FSX crash. In my case I had the sim standing untouched for a very long time (a couple of hours) when the computer suddenly rebooted (it has been setup to do so in the start up and recovery section of Computer management). But as Emile wrote, I only had these errors in connection with a FSX crash. If I have a successful FSX-session with normal use, and closure, the event is not logged/fired only in the case of a FSX crash.... As I currently do not have any applications running that relies on FSUIPC, I have it uninstalled for the time being. But I hope it won't be an issue once I get to the point where I need it.... On of the events in the log states that the referenced assembly couldn't be found, and another statement that simconnect isn't installed on your system. To me that indicates some non-efficient error-handling code, as I presume that (at least in my case) when having the SDK installed, FSUIPC should also be able to find it?..... But as I do not know the source code, I'll be reluctant to judge if it is FSUIPC that enforces the crash or not.... But I bet you (Peter) will try to explain why it couldn't be FSUIPC's fault that FSX crashes .. or? I hope that you will be able to either convince us that it isn't FSUIPCs fault, or if it is, that you will be able to solve it. ATB DanKH