Author Topic: Couatl crash, crashing P3Dv4  (Read 2142 times)

kconlon

  • Newbie
  • *
  • Posts: 16
Couatl crash, crashing P3Dv4
« on: September 18, 2018, 04:05:46 pm »
Since the GSX L2 upgrade I am seeing P3Dv4.30 CTD frequently.  When I look in the event viewer I am seeing Couatl.exe errors like this

Faulting application name: Couatl.exe, version: 3.2.0.4029, time stamp: 0x5b9159f7
Faulting module name: ucrtbase.dll, version: 10.0.17134.191, time stamp: 0xcb91c047
Exception code: 0xc0000409
Fault offset: 0x000a253b
Faulting process id: 0x13ac
Faulting application start time: 0x01d447d883006208
Faulting application path: D:\Users\Kevin\Documents\Prepar3D v4 Add-ons\Addon Manager\Couatl\Couatl.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 705575d6-35f4-4dc0-86f2-08c65db961c3
Faulting package full name:
Faulting package-relative application ID:

I last ran the FSDT Life update this morning (9/18) and still am seeing the error.
I am using W10 Defender and have the folder  D:\Users\Kevin\Documents\Prepar3D v4 Add-ons\Addon Manager\Couatl set as an exclusion area.

Most recently I was using  the new AS 320 sitting at FSDT KCLT (Gate B6) when the CTD happened (hadn't even evoked GSX yet).
Any thoughts?

Thanks
Kevin



virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: Couatl crash, crashing P3Dv4
« Reply #1 on: September 19, 2018, 11:54:19 pm »
Faulting application name: Couatl.exe, version: 3.2.0.4029

Quote
I last ran the FSDT Life update this morning (9/18) and still am seeing the error.

This is clearly the antivirus, since version 4029 is not the latest one, and it's not possible to get the old one (which is not online anymore) with Live Update, unless something is blocking the download.

Quote
I am using W10 Defender and have the folder  D:\Users\Kevin\Documents\Prepar3D v4 Add-ons\Addon Manager\Couatl set as an exclusion area.

As clearly explained in all forum posts about the antivirus, we NEVER said to "exclude Couatl". We always said to exclude the WHOLE Addon Manager folder because, if you don't do that, you cannot possibly be sure the *UPDATER* itself won't be blocked from doing his job.

Be sure you also don't have other software that might block the download, like a firewall, an anti-spyware, etc.