Adobe AIR installer has encountered a problem and needs to close

[Brylee]

Has anybody come across such issue. I had done the installation of AIR 1.5 previously and done successfully when suddenly some of my AIR applications stopped launching with this error message :

Adobe AIR Installer has encountered a problem and needs to close. We are sorry for the inconvenience.

I tried to launch it using another way and got it can be done and AIR application is running fine through the Flex Builder. Adobe, or somebody here can suggest me for some effective and helpful suggestion ..

[Beckett]

Hello guys ! I am running with the issues from the installation of adobe installer. Whenever, i launch the installer, the Adobe AIR installer i always come up with this window.(I have attached this in the attachment section).. I am using Windows XP SP3. It it occurred from the system incapability or is it from application. How do I fix this issue ? Thanks.

[Hockson]

I got the solution for this very issue. You have to make some modification in the windows registry, you have to follow steps suggested below :

1. Browse the Windows Registry editor, you can get the windows registry from the Start => Run and type regedit in the Open text box. Click on OK button to start the registry editor.
2. Move for the following registry location: HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Premiere\7.0\Help.
3. Make a right-click on the Help key and choose Permissions.
\4. In the Permissions For Help window, choose each Group or User name and configure the Permissions to Allow proper Control. Click on the apply button and then OK to save the changes and get exit from window.
5. Exit from the Registry Editor.

[Viceman]

This is the solution :

Check your mm.cfg file for the entry:

PreloadSwf=C:/Documents and
Settings/Administrator/workspace/.metadata/.plugins/com.adobe.flash.pr
ofiler/ProfilerAgent.swf?host=localhost&port=9999

And just destroy it out ! Leave all of the thing else intact, and check to find out if you are able to install the AIR application now . Oliver Goldman at Adobe is investigating later ... Does It contained something to do with the debug version of FlashPlayer or the Profiler associated within the Flex Builder?