It appears no one on the FSD development team tested on Vista 64

We appreciate your frustration, but to allege our software was never tested in Vista 64 is not correct. Some Vista 64 users (as in your particular case, it seems) have problems specifically with Vista 64's firewall particularly where any security/firewall addon has been installed as it has in your case if I recall correctly. Few users (less than 1% if you really want to be precise) have any problems installing our software in Vista 64 and it's very unfortunate that you fall in that very small group. This inconvenient and frustrating firewall problem, which it appears is what is likely the root cause in your case, is something that Microsoft themselves acknowledge and in only the last few days they have suggested a couple of new avenues for us to explore regards installation routines.It is important to explain that our software was indeed extensively tested in Vista 64, and explain that neither our own in-house Vista 64 machines our beta team's Vista 64 machines displayed the sort of problem you have. Still, we continue to look into the problems Vista can create where it comes to software installation. Actually we are currently testing a couple of their latest recommendations right now and should anything eventuate from this we will get in contact with you, or you can get back to us, whatever you prefer.Again, we really do appreciate your frustration but I can't see that it's either fair or in any way helpful to go around making comments that are simply inaccurate. Given your position as an Avsim staffer, such comments have the probability of misleading others and I very much regret having to correct them.

We appreciate your frustration, but to allege our software was never tested in Vista 64 is not correct and I'm afraid that I can't let that comment stand uncorrected.Some Vista 64 users (as in your particular case, it seems) have problems specifically with Vista 64's firewall particularly where any security/firewall addon has been installed as it has in your case if I recall correctly. Few users (less than 1% if you really want to be precise) have any problems installing our software in Vista 64 and it's very unfortunate that you fall in that very small group. This inconvenient and frustrating firewall problem, which it appears is what is likely happening in your case, is something that Microsoft themselves acknowledge and in only the last few days they have suggested a couple of new avenues for us to explore regards installation routines.It is important to state, for the record, that your allegation above is not correct and to also explain that our software was extensively tested in Vista 64. Neither any of our own in-house Vista 64 machines our beta team's Vista 64 machines displayed the sort of problem you have had but we continue to look into the problems Vista can create where it comes to software installation and activation. Actually, we are currently testing a couple of their latest recommendations.Again, we do appreciate your frustration but I don't think it's especially helpful to go around making comments that are inaccurate and which therefore may mislead others - especially given your position as an Avsim staffer.

Thank you Steve for your correction and explanation. I see Tim recently updated on the FSD forum and there is an entry to check for in the dll.xml file. In addition I recently ran the SP2 update for Vista 64. I was originally running the default Microsoft firewall with NOD32 antivirus but my earlier purchase from Eset was for their Smart Security product and Eset would no longer allow me to just run the AV product and I did have to upgrade my installation to the purchased product which was the Smart Security which disables the Microsoft firewall and places their own firewall in place. I will continue working with this and watching what support can provide for rectifying. My reason for posting here was to get some confirmation that others with Vista64 had successfully installed and if so potentially talk with them over specific settings.

Thank you Steve for your correction and explanation.

You are welcome.

I too just bought the FSD Commander this past weekend. My Garmin 480 turns on OK and shows the initiating screen but seems to get stuck there. Hitting, ENT, CLR, FPL, etc does not seem to get it past the initial screen. - Anyone else had this problem?- Anyone willing to venture a guess as to how to solve?I bought the Commander specifically to use the 480 and I hope all ends up OK. I've flown and enjoyed FSD Saratoga for the past year and hope to end up as pleased with the Commander as I am with the Saratoga.Thanks

Just a followup to report that this problem has been fixed. First time it was solved by switching to VC view (I normally fly 2d panel) and switching the 480 past the initiating screen by hitting CLR. After that, the 480 worked in all views. Now it seems to work fine in all views w/o switching to VC first. I hope this helps if anyone else has a similar issue.

I bought the new Commander for FSX when it first came out (pre-SP) and it caused immediate CTDs.I am religious about protecting my FSX install and have no other add-ons in FSX that cause this these days (Wilco non-FSX natives were the last culprits - they're long gone!).Unistalled the FSX Commander, very disappointed. :( May look again if the SP fixes it - then again, FSD have a pain in the backside on-line install if I remember corrently, so I probably won't bother.

I installed the Commander on Vista 64 without problems. UAC and DEP are off since day one (which obviously prevents some serious headache).