FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Phflies99 on July 11, 2017, 10:05:28 pm
-
Hello,
since a couple of days I get a Windows message asking me with witch app I "want to open this file" everytime I start my computer. The message appears approximately 15 seconds after booting Windows. When I choose an app such as "Editor" in order to open the file, there occurs the following text:
2017-06-03 11:51:37.037 Log opened. (Time zone: UTC+02:00)
2017-06-03 11:51:37.037 Setup version: Inno Setup version 5.5.9 (a)
2017-06-03 11:51:37.037 Original Setup EXE: E:\Programme (x86)\Addon Manager\Couatl_Updater.exe
2017-06-03 11:51:37.037 Setup command line: /SL5="$6092A,253199,169472,E:\Programme (x86)\Addon Manager\Couatl_Updater.exe" /product=GSX /silent /log=C:\Users\Philipp So\AppData\Roaming\Virtuali\UpdateCache\Couatl_Updater.LOG
2017-06-03 11:51:37.037 Windows version: 10.0.14393 (NT platform: Yes)
2017-06-03 11:51:37.037 64-bit Windows: Yes
2017-06-03 11:51:37.037 Processor architecture: x64
2017-06-03 11:51:37.037 User privileges: Administrative
2017-06-03 11:51:37.038 64-bit install mode: No
2017-06-03 11:51:37.040 Created temporary directory: C:\Users\PHILIP~1\AppData\Local\Temp\is-PMHE3.tmp
2017-06-03 11:51:37.043 Extracting temporary file: C:\Users\PHILIP~1\AppData\Local\Temp\is-PMHE3.tmp\idp.dll
2017-06-03 11:51:37.105 taskName Updating Live Update cache files
2017-06-03 11:51:37.330 taskName Updating Addon Manager files
2017-06-03 11:51:37.330 cacheFolder set to C:\Users\Philipp So\AppData\Roaming\virtuali\UpdateCache\
2017-06-03 11:51:37.330 cacheFile set to C:\Users\Philipp So\AppData\Roaming\virtuali\UpdateCache\fsdtroot.md5
2017-06-03 11:51:37.330 cacheFileName set to fsdtroot.md5
2017-06-03 11:51:37.330 File cache C:\Users\Philipp So\AppData\Roaming\virtuali\UpdateCache\fsdtroot.md5 loaded
2017-06-03 11:51:37.336 local file bglmanx_aerosoft.dat matches remote file, skipping update.
2017-06-03 11:51:37.338 local file bglmanx.dat matches remote file, skipping update.
2017-06-03 11:51:37.340 local file Couatl_Updater.exe missing or not matching, updating it...
2017-06-03 11:51:37.340 http://update.fsdreamteam.com/setup/fsdtroot/Couatl_Updater.exe E:\Programme (x86)\Addon Manager\Couatl_Updater.exe added.
2017-06-03 11:51:37.348 local file FSdt_install_guide.pdf matches remote file, skipping update.
2017-06-03 11:51:37.352 local file bglmanx_fbeam.dat matches remote file, skipping update.
2017-06-03 11:51:37.354 local file Couatl_Updater2.exe matches remote file, skipping update.
2017-06-03 11:51:37.359 local file bglmanx.dll matches remote file, skipping update.
2017-06-03 11:51:37.361 local file bglmanx_fsdt.dat matches remote file, skipping update.
2017-06-03 11:51:37.364 local file bglmanx64.dll matches remote file, skipping update.
2017-06-03 11:51:37.364 local file bglmanx_qwings.dat matches remote file, skipping update.
2017-06-03 11:51:37.401 Executing E:\Programme (x86)\Addon Manager\Couatl_Updater2.exe /product=GSX /silent /log=C:\Users\Philipp So\AppData\Roaming\Virtuali\UpdateCache\Couatl_Updater2.LOG
2017-06-03 11:51:44.117 Error 1 running E:\Programme (x86)\Addon Manager\Couatl_Updater2.exe which means Unzulässige Funktion
2017-06-03 11:51:44.117 Message box (OK):
Error 1 running E:\Programme (x86)\Addon Manager\Couatl_Updater2.exe which means Unzulässige Funktion
2017-06-03 11:51:47.700 User chose OK.
2017-06-03 11:51:47.700 Starting the installation process.
2017-06-03 11:51:47.701 Installation process succeeded.
2017-06-03 11:51:47.702 Need to restart Windows? No
2017-06-03 11:51:47.703 Deinitializing Setup.
2017-06-03 11:51:47.705 Log closed.
The only product I have installed at the moment is GSX.
I really don´t know what causes this problem and I appreciate every kind of help.
Best regards
Philipp
-
The problem doesn't have anything to do with Couatl or any of our software, which doesn't set anything to start with Windows. Some else in your system is trying to open an (old, because it's from June 3rd) FSDT Live Update log, and for some reason is asking that question at every Windows startup.
Either it's some kind of strange antivirus interference, or you must have placed something in the Windows startup, but I can't really see how this could happen.
Check the Windows Task Manager, under the "Startup" tab, you will see all the programs that are being started with Windows, and disable the ones that shouldn't be there. I assure you we haven't put anything there with our installer.
-
You are right, there was a misplaced file in my autostart-menu. I have no clue how it got there, but thank you very much for your help.
I am sorry for the inconvenience, as I could have thought of this myself.
Again thank you for your patience, your doing a really good job on supporting all these people!