Author Topic: [P3D]GSX/ Addon manager installation error  (Read 6582 times)

ca177

  • Newbie
  • *
  • Posts: 20
[P3D]GSX/ Addon manager installation error
« on: July 06, 2012, 10:42:44 am »
Error when installing GSX. After that P3D says couatl engine error. Please see attached file for error log and screenshot. Re-installing or running the stand-alone addon manager installer does not solve the problem.
Thank you.
« Last Edit: July 06, 2012, 01:08:42 pm by ca177 »

ca177

  • Newbie
  • *
  • Posts: 20
Re: [P3D]GSX/ Addon manager installation error
« Reply #1 on: July 06, 2012, 11:27:43 am »
Installed only the KLAX, but still that message.
See attached screenshot.

ca177

  • Newbie
  • *
  • Posts: 20
Re: [P3D]GSX/ Addon manager installation error
« Reply #2 on: July 06, 2012, 01:03:51 pm »
Tried all FSDT products in FSX. Same error messge. Any idea?

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51452
    • VIRTUALI Sagl
Re: [P3D]GSX/ Addon manager installation error
« Reply #3 on: July 06, 2012, 06:24:07 pm »
Are you using the most current version of GSX ? If not sure, download it and install it again.

And, the message says to check the couatl.err file for details, could you post its content ?

ca177

  • Newbie
  • *
  • Posts: 20
Re: [P3D]GSX/ Addon manager installation error
« Reply #4 on: July 06, 2012, 06:29:08 pm »
After downloading the latest installer, problem continues with couatl.exe. It starts for a few seconds and crashes, so all FSDT products are not working. GSX installer also says cannot create "vehicles_airport" restoring to back up. Error log is as follows
===========================


couatl v2.0 (build 2315)
panic log started on Fri Jul 06 16:14:07 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 16:14:44 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 16:15:17 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 16:15:51 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 16:16:24 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 16:16:58 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 16:33:58 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 16:34:33 2012
Executable integrity compromised

couatl v2.0 (build 2309)
panic log started on Fri Jul 06 17:20:21 2012
Executable integrity compromised

couatl v2.0 (build 2309)
panic log started on Fri Jul 06 17:20:55 2012
Executable integrity compromised

couatl v2.0 (build 2309)
panic log started on Fri Jul 06 17:21:28 2012
Executable integrity compromised

couatl v2.0 (build 2309)
panic log started on Fri Jul 06 17:22:02 2012
Executable integrity compromised

couatl v2.0 (build 2309)
panic log started on Fri Jul 06 17:22:36 2012
Executable integrity compromised

couatl v2.0 (build 2309)
panic log started on Fri Jul 06 17:23:25 2012
Executable integrity compromised

couatl v2.0 (build 2309)
panic log started on Fri Jul 06 17:23:59 2012
Executable integrity compromised

couatl v2.0 (build 2309)
panic log started on Fri Jul 06 17:24:32 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 17:55:21 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 17:55:54 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 17:56:28 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 17:57:01 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 17:57:35 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 17:58:09 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 17:58:42 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:15:31 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:16:04 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:16:38 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:17:12 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:17:45 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:27:28 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:28:02 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:28:35 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:29:09 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:29:42 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:30:16 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:30:49 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:31:23 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:31:56 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:32:30 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:33:03 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:35:03 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:35:37 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:36:10 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:36:44 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:37:17 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:57:06 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:57:40 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:58:13 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 18:58:47 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 20:42:59 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 20:43:32 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 20:44:06 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 20:44:39 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 20:45:13 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 20:45:46 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 20:46:20 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:01:53 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:02:28 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:03:03 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:03:37 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:04:12 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:04:46 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:05:41 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:06:32 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:07:07 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:12:18 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:12:52 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:13:29 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 22:14:02 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 23:50:38 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 23:51:13 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 23:51:47 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 23:52:22 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 23:52:57 2012
Executable integrity compromised

couatl v2.0 (build 2315)
panic log started on Fri Jul 06 23:53:31 2012
Executable integrity compromised
« Last Edit: July 06, 2012, 06:31:55 pm by ca177 »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51452
    • VIRTUALI Sagl
Re: [P3D]GSX/ Addon manager installation error
« Reply #5 on: July 06, 2012, 06:31:34 pm »
the "Executable integrity compromised" has been discussed several times already, and it's caused by another product which is attaching itself to all executables, for example:

- The freeware ATI Tray Tools utility

- A similarly invasive system utility

- A real virus

ca177

  • Newbie
  • *
  • Posts: 20
Re: [P3D]GSX/ Addon manager installation error
« Reply #6 on: July 06, 2012, 06:33:36 pm »
Well, actually this is a freshly-installed P3D. Does Integrity problem means Prepar3d.exe is "infected" or couatl.exe is "infected"?

ca177

  • Newbie
  • *
  • Posts: 20
Re: [P3D]GSX/ Addon manager installation error
« Reply #7 on: July 07, 2012, 05:48:46 am »
The "Integrity compromised" problem is caused by "Lenovo One Key Theater". After disabling it, the couatl engine works fine now.
But the GSX installation error message still exists.
Please see attached screenshot.