Thanks Matt.1. Update for current radios to support FSX, or not necessary?Yup.. done that. But it is a beta version and I have contacted Flight link and they have promised me that they will look into it. So that effort is going on in parallel.2. Running latest FSUIPCCheck.3. Windows XP SP2, fully updated?Check.4. Any chance you can try same setup, on a different computer just to test?Could do that. Its a bit of an effort to move some stuff. That other PC with FSX does not have a sound card.5. Reinstall .net 1.1 and 2.0?Hmm... I could try that.6. If you run the setup, right now, using FS9, no problems? Or do you now encounter sameNo problems with FS9. for 1. Flight link does not use .net and Vox ATC uses .Net 1.1 for FS9. So there is no conflict.6.b. problem in FS9 AND FSX? Or is it JUST FSX? (IE, you have voxatc for FS9 and it works, or same issue)Problem only with FSX VoxAtc and FSX Flight link. Both talk to FSUIPC/FSX via .net 2.0 version. Hencey they are stepping on each other. Don't know who the culprit/offender is. The problem happens as soon after the Vox ATC does the test and the display for the ATIS frequency shows up. Just after than..the popups galore with the exception 23 starts.7. DO you have VoxATC AND VoxATCX installed? I know that when I installed VoxATCX it hosed my FS9 version, although, that was on the old sim rig which had problems to being with (Spyware running as I found out later) and I ultimately ended up building a new rig. But have you tried spybot/adware just to check for any other possible software issues that COULD cause something funky to go on here... just a thought.I don't believe its advirus or anything cause I run those checks regulalry and PC is clean. I have installed them both VOX. FS9 version and the FSX version.But I really would like to purchase the FSX version of Voxatc rather than the FS9 version.Manny

Thanks Bruce.