General Category > General Discussion
Every FSX startup: couatl.exe load Yes/No ? **SOLVED**
whiggy:
There are no VIRTUALI s.a.s certificates.
virtuali:
Then I'm sorry, but I think I'm out of explanations: when everything works correctly, the normal behavior is that, when you remove a line from a [trusted] section for a module, and the software author is not in the certificates list, you should see BOTH trust questions, the Windows one and the the FSX one.
Since, according to your description, you are seeing only the FSX one, and there's no certificate in the trusted (or not trusted) authors, something is not working correctly in your system or there might be a setting in Windows somewhere that is affecting this.
I'm afraid we don't have a solution: this specific problem has never been reported by anyone else before so, it's clearly something new that is affecting the normal Trust mechanism in Windows, which is unique to your system. Do you have another PC with FSX installed you can try it on ? Just as a test.
whiggy:
No sorry I don't have an another PC with FSX.
I downloaded and installed the scenery new, but I don't get any certificate in the list.
The only one thing:
I had 2 versions of FlightSimulator (FS9+FSX) on the same machine.
Few weeks ago, I uninstalled FS9 with all FSDreamteam scenerys and today I only use FSX.
What has surprised me is that I no had to enter a license number after installing the scenerys for FSX.
All scenerys were correct licensed.
virtuali:
--- Quote from: whiggy on February 05, 2011, 11:31:37 am ---No sorry I don't have an another PC with FSX. I downloaded and installed the scenery new, but I don't get any certificate in the list.
--- End quote ---
Maybe I'll explain it better: this is ok, you will have a certificate there only in one of these two cases:
1) You decided to Trust anything signed by us (it's one of the possible options on the *Windows* trust request screen), so you would see a VIRTUALI certificate in the Trusted Authors list, so that would explain why you wouldn't see any more Windows request screen.
OR
2) You decided NOT to Trust anything by VIRTUALI, this would also explain why you wouldn't get Windows trust requests anymore, but then FSX should never allow the module to run, not even once.
--- Quote ---What has surprised me is that I no had to enter a license number after installing the scenerys for FSX.All scenerys were correct licensed.
--- End quote ---
That's exactly what is supposed to happen, the activation of the sceneries is stored on Windows NOT on Flight sim, which means, as long as you don't reinstall Windows, you'll never lose it. And, as explained on every Info page of any product (JFK, for example)
http://www.fsdreamteam.com/products_jfk.html
--- Quote ---The product is sold as 2 Products in One. This means, by buying one version, you will automatically get the other for free, since activation and serial codes are shared between FSX and FS9.
--- End quote ---
Which is of course the best and easier way: if you use both FS9 and FSX on the same PC, you don't need to register in both sims, it's enough you register in one and, as long you don't reinstall Windows, the scenery will be active in the other sim as well.
In any case, your activation is fine and it's working as expected, and your problem doesn't have anything to do with activation, because you also see the scenery (and if you lost your activation for any reason, it would *not* disappear, it would revert back in Trial mode).
Your problem is that the fact you Trusted the Couatl program seems to not be saved correctly between FSX sessions, which is also interesting because, we have two modules, the Addon Manager and Couatl, it's strange you see repeated trusting questions about Couatl and not the Addon Manager, considering they have exactly the same digital signature.
Sorry, but I really can't explain it, it's really the first time it happens.
Last check, you please open REGEDIT, and check the value of the following key ?
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing
the default value is 0x23c00 (23c00 hexadecimal). If you see any other value, try to change it to back 0x23c00.
Xeno:
Hi,
I ve faced the same issue. My system is german. FSXSave.exe and couatl.exe both requested permission on FSX startup. With the solutions given here, I couldn't solve it.
I finally made it. What you hav to look for, is the path of couatl.exe in the EXE.xml. I figured there are 2 different issues: In case of FSXSave.exe, please take a note about the difference between german and english paths. It has to be german! Mine was english. So I switched the following part of my path from "\Program Files (x86)\" to "\Programme (x86)\". No more permission requests afterwards.
About GSX: the path was missing the drive letter and first folders. And again, i wrote it in german. Now, also couatl.exe is always trusted.
I've had a similar problem a few weeks ago, and i know that it never appeared before with the nearly same configuration. So i guess there might be a possible bug inside net.framework. Windows usually
translates different path languages automatically, as far as I know.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version