Thanks Pete. Microsoft really did make a complete pig's ear of FSX didn't they? :( Let's hope Watcher (and anyone else with this problem) can use this guidance to resolve the problem.It's such a pity that there isn't a utility that can relocate FSX for you. Not just for situations like this but when a new PC is purchased and the user wants to get FSX transferred with the minimum of fuss.

It is primarily the operating system causing the security related access problems, not FSX itself.There is a free utility to change the registry entry for the FSX or FS9 path for utilities that use the registry. Download this registry tool from here:http://www.flight1.com/view.asp?page=libraryFSX/FS9 Registry Repair Tool (36KB) and of course run it with admin privileges as an administrator :)Otherwise each application needs to have their access paths reset. There are some shareware tools available for moving applications around as well. I can't recall right now.

Thanks Pete. Microsoft really did make a complete pig's ear of FSX didn't they? :( Let's hope Watcher (and anyone else with this problem) can use this guidance to resolve the problem.It's such a pity that there isn't a utility that can relocate FSX for you. Not just for situations like this but when a new PC is purchased and the user wants to get FSX transferred with the minimum of fuss.

It is primarily the operating system causing the security related access problems, not FSX itself.

Yes, that is true.But the mess called SimConnect involves both parties. Microsoft's operating system team for devising a system for having multiple library versions available side-by-side in such a complex and convoluted way that it is impossible to resolve once it goes wrong (which, agreed, it shouldn't), and the FS team for an uninstaller which fails to uninstall SimConnect properly so preventing a correct reinstall.I've got good reason to want to be able to resolve this mess. My own main development system, on which I do all my testing, has somehow got into a state where SimConnect Base and SP1 versions don't work and cannot be either uninstalled nor reinstalled. SP2/Acceleration is fine (else I would be in a real mess), but it stops me running tests with, for example, GoFlight's FSX driver, which won't work with SP2's SimConnect, and so on.I've been trying to hack through registry entries, GUIDs and other assorted nightmares in the hope I'd be able to build a program which could sort this out -- make a clean sheet ready for a normal SimConnect.msi execution and install. But I've failed miserably. It is too complex and I've not the faintest idea how the various parts relate to each other, nor why it is all different (different GUIDs etc) on each PC.

There is a free utility to change the registry entry for the FSX or FS9 path for utilities that use the registry. Download this registry tool from here:

Yes, that's the one I provide a link to on my Support Forum too.RegardsPete

Hi all. Watcher is back. Please do not take my silence as having lost interest. Much to the contrary. I have been busy running various tests to try to sort out what needs to be done on my system to resolve the 75 error. What I have so far found after having run various tests is that several things need to be done when running Norton Internet Security, which includes antivirus and realtime protection. First I had to write specific rules to ensure that the locahost connection was not interfered wih. Then I had to set exclusions from realtime protection. This is sort of like a trust. I found that excluding just the RC executable was not enough. It was only after I excluded both RC directories that I had any success. So far I have managed to complete one flight from EGNT to EGLL without a 75 error. Will do more testing to make sure that it is not a fluke. I suspect that the communications are being stacked in one of these directories, requiring a write into a temporary file or stack located there. Please correct me if I am wrong in this assumption. In the midst of all this the USB hub on which my MPanel is located finally died so that delayed me considerably.

Hi all. Watcher is back. Please do not take my silence as having lost interest. Much to the contrary. I have been busy running various tests to try to sort out what needs to be done on my system to resolve the 75 error. What I have so far found after having run various tests is that several things need to be done when running Norton Internet Security, which includes antivirus and realtime protection. First I had to write specific rules to ensure that the locahost connection was not interfered wih. Then I had to set exclusions from realtime protection. This is sort of like a trust. I found that excluding just the RC executable was not enough. It was only after I excluded both RC directories that I had any success. So far I have managed to complete one flight from EGNT to EGLL without a 75 error. Will do more testing to make sure that it is not a fluke. I suspect that the communications are being stacked in one of these directories, requiring a write into a temporary file or stack located there. Please correct me if I am wrong in this assumption. In the midst of all this the USB hub on which my MPanel is located finally died so that delayed me considerably.

rc needs to be able to write to it's root directory to store the options. it also needs to be able to read/write to \rcv4\winwood - where it write the .wav file to be played by the controller, pilot and chatter pilot. this is what antivirus programs see as virus like, and abrubtly terminate access with a run time error 75 after a while.i hope your analysis would help other norton AV users. this doesn't seem to be an issue with use MSE users, and on top of that, MSE is free :-)jd