You can't. This is going to need to be fixed by FSDT. It looks like there is possibly a problem in the Addon Manager itself. I know they had a problem a long time ago with it. Heck, this might be whats causing all the .dll errors in the other threads people are reporting 
There's nothing to be fixed right now. You are confusing several issues:
- The original poster about the debugger problem is due to the fact he probably had an older version, the one that still didn't supported the >2GB patch together with the original MS CD protection. This has been fixed months ago: the current version is now compatible both with >2GB FS9.EXE AND with the MS CD protection. The only catch, if you "switch" between an standard FS9.EXE and a nocd one, you need to run the Addon Manager (or any of our scenery) installer again, so it will be able to detect the change of the EXE and install the right version.
- Other "DLL issues" people were having, weren't due to the Addon Manager. Instead, they were caused by a corrupted scenery.cfg file with thousand of random names instead of the (c) Copyright symbol in the title of some scenery areas. This was probably caused by *antother* product that act on the scenery.cfg, that can't deal with proper text encoding and saves back corrupted scenery.cfg files. This was always fixed by manually correcting the scenery.cfg. However, the *current* version of the Addon Manager that is online now and that everyone will automatically get the next time he'll launch any of our installers, is ALREADY fixed to DEFENDS itself from such corrupted scenery.cfg files.
- Remaining DLL problems are usually antivirus program faults (happens all the time, for example, with Flight1's wrapper as well), that usually gets fixed with the antivirus updates. Last week an AVG update mistakenly reported our DLL to be a virus, making it crashing. It was fixed by AVG in the next live update.