View attachment 45043
The dialog box that everyone is receiving is NOT the "Trusted software" confirmation box. The box is an ERROR in the FSD installed functionality of that FSX guage and the modification of the Fdav.dll. The "Trusted Software" dialog has never shown itself with multiple installs of this product using the FSD installer. The fact that it hasn't applies directly to the installer NOT the application.
Flight Simulator does that AFTER you are asked to choose it as "trusted" or not. IF I had ignored that message, it would not have applied it into the FSX.cfg as I listed.
The DLL may be digitally signed, however that does not forgoe the corruption of the file, which I assure you IS the ONLY cause of this issue.
This is not an installer issue. The files were all installed on your system, and as you indicated, it worked for you after you installed the software. The installation program does not make the edits to your fsx.cfg file that you listed, such as:
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Gauges\FDav.dll.twzaruuqulcqrhohokotoeelcnautoow wrhiwbbh=1
Flight Simulator does that.
1) It worked fine PRIOR to using the "guage" file that is fouled
2)Flight Simulator does that AFTER it's acknowledged as "trusted" So now your below statement about ignoring the dialog becomes false.
The dialog box you are seeing is Flight Simulator is asking you to confirm that you want to use the gauge that is used in conjunction with the cockpit.
That is Incorrect. That is not the dialog. The issue is an error with your installed files.
Until you select Yes, as trusted software or if you had previously ignored or canceled this dialog box, you will keep getting this message every time you load the aircraft. That is how Flight Simulator works.
I am aware of how FS works, and this box was not ignored, hence the additions to the fsx.cfg that were listed in the prior post
If you are confirming addon drivers as trusted and still keep getting this message it has nothing to do with any of your addon software. Flight Simulator is controlling this, and if that problem persist you will need to reinstall the sim.
My FS install is correctly done and this issue resides with your installer. Please notate the previous post.
This dll file is digitally signed, so there will also be an option to always trust the company that signed the software. If you select Yes, as trusted, you will not be prompted with this message every time you install a new aircraft or addon from that company. If a driver is not digitally signed you do not have this option. Many developers sign their software as we do, and some do not.
The digital signature does not correct the ERROR that the FSXGuage and the FDav.dll are creating
As far as any issues with writing to the dll.xml file, this is a Windows permissions issue that is local to your computer.
This is INCORRECT. That is NOT a windows permissions issue, as other installers are able to write to the xml.dll without error. ORBX,FSRecorder,Captain Sim, PMDG, FeelThere. YOur installer has CORRUPTED this file with the FSXGuage:
<LAUNCH.ADDON>
Code:
<LAUNCH.ADDON><LAUNCH.ADDON>
<NAME>FDav</NAME>
<DISABLED>False</DISABLED>
<MANUALLOAD>False</MANUALLOAD>
Gauges\FDav.dll</PATH>
<DLLSTARTNAME>module_init</DLLSTARTNAME>
<DLLSTOPNAME>module_deinit</DLLSTOPNAME>
</LAUNCH.ADDON>
Therefore, there is no "patch" that will correct this. If Windows denies permissions to access this file there is really nothing the installer can do about this. Permissions errors like this are usually caused by one of the following:
Again, this is INCORRECT! If there was a permissions error, it would not write to the xml.dll file as listed above. This is NOT a permissions error, there is NO UAC involvement,so the following is a mute solution. The INSTALLER is the issue sir.
1.Running the installer from across the Internet instead of downloading it to your hard drive.
2.Downloading the installer and running it on your hard drive in a location that has restricted Windows permissions. An example of this would be an external hard drive, or if you are running 64 bit Windows, from within your Program Files(x86) directory structure. And this, of course, depends on how your Windows environment is setup. Particularly with Windows Vista and Windows 7, there are a lot of variations here.
3.In Windows 7 or Vista (you don't say what you are using) you may have an issue with User Account Control (UAC). Here is some useful information on that:
http://technet.microsoft.com/en-us/l...91(WS.10).aspx
4.You may have security software, such as anti-virus or firewall software, that is restricting Windows access.
We have nearly 2,000 installs, reinstalls each month on the numerous software titles we have released. This is a problem which comes up very, very rarely. But when it does happen it almost always comes down to where/how the software was downloaded. Best results are always obtained by downloading the installer to the Downloads folder Windows setup, on the same drive and partition where Windows is installed. In some rare instances problems occur when the simulator is installed on a different drive and partition, but again, this depends on how the Windows environment is setup.
Now I'm beginning to get emotionally aggravated at your response. I have provided you ALL the pertinent information that you should require to fix this issue and you have responded with the "problem is your computer, piracy(in previous instances of this issue) or user error". This is unacceptable. This is NOT user error, or UAC, piracy or OS type/version. This is an INSTALLER error that YOUR installer and it's files have created.
Even AFTER the manunal uninstall, and AFTER going through pages of registry data and all the files that your installer touched, the ERROR now persists. Which means we all have to manually remove the Fdav.dll and hope like hell nothing else uses it. And now you're going to have to provide the corrected file to EVERYONE who this has affected.
DO NOT assume it is a "user" error. You have a long list of problems with this EXACT issue, and have yet to resolve it using the tools available to you. This is not MY problem this is YOUR problem. This is NOT our systems, this is YOUR installer and YOUR files!
I'm very sorry to become frustrated and crass, but FIX THE INSTALLER and fix the included files! NEVER assume your customer has made the mistake, ALWAYS assume you have.
YOU have not delivered a properly functioning installer, and have attempted to make it your customers problem. It doesn't matter that KCFlight Shop created this product. FSD is responsible to this customer as well because it is FSD's software that has created a problem!
I apologize for my frustration, but that type of customer solution is canned and irresponsible. I gave you technical data citing the EXACT issue and you throw "UAC" and "Permissions" theory at me. Also, heads up. Do NOT apply that this is a common installer problem.
I own almost every payware aircraft from every creator for fsx. This has never occurred prior to this install. This is not a common "installer" issue other than an FSD installer issue unless it's the guage that has fouled, which I doubt, because it's calling your "digitally signed" dll which is good for tracking the culprit.
