Couatl error **SOLVED**

[DMdoc]

I keep getting an error message when loading P3Dv4.5:

couatl v3.2 (build 4325)
panic log started on Sun May  3 15:21:47 2020
problem raised by addon <unknown>
Traceback (most recent call last):
  File "<string>", line 52, in loadAddons
  File ".\python27\shlex.py", line 279, in split
  File ".\python27\shlex.py", line 269, in next
  File ".\python27\shlex.py", line 96, in get_token
  File ".\python27\shlex.py", line 172, in read_token
ValueError: No closing quotation
{}

Thus far, I have:
1) inactivated my virus scans (Windows Security & Malwarebytes)
2) removed all traces of GSX and the FSDreamTeam airports
3) downloaded gsx_p3d4_setup.exe and ran it.
4) The SAME MESSAGE is back to annoy me.

Any idea what I should try next?

[virtuali]

I cannot reproduce it and it's the first time I ever see that error and, it indicates something basically impossible: an error in the Python language *itself*. Since the Python interpreter is embedded in the Couatl.exe, the only possible reason I can think of, is your antivirus has corrupted it.

DO NOT "disable" the antivirus, we never suggested that but, instead, add the Addon Manager folder to the antivirus Exclusions. This because some antivirus still block files even if the "look" disabled, because the only way to really disable them is to uninstall them. That's why we never suggest to disable the antivirus, but to use the Exclusions.

- add the Addon Manager folder to the antivirus Exclusions.

 - Run the FSDT Live Update again

[DMdoc]

An update on the error described above...
1) I got the same error when using GSX in P3Dv5.
2) I gave up using GSX for a few weeks.
3) Yesterday, I saw a posting here that described where to find the Dreamteam stuff in the regedit file. I deleted that part of the regedit file, as well as everything on my computer from previous installs.
4) I then downloaded the most recent GSX stuff from your website, ran it, and EVERYTHING is working again.

Although I'm not sure, I'd guess my problem had been some glitch in the regedit file.