The root of the problem is probably the people who had this problem did not allow the setup to launch MM because when it's launched by the setup it is launched with admin privileges so you have to manually launch it as admin one time because COM works only properly when it's at least launched one time with admin privileges, nasty MM bug causing me 4 hours headache.

Source: "MediaMonkey.exe"; DestDir: "{app}"; Flags: regserver

Actually I stand corrected. InnoSetup has a built in COM registration flag called regserver. For your Inno Setup it would be in the [Files] section something like this...

[code]Source: "MediaMonkey.exe"; DestDir: "{app}"; Flags: regserver[/code]

Filename: {sys}\regsvr32.exe; Parameters: "{app}\MediaMonkey.exe""; StatusMsg: Updating COM Object...; Flags: runhidden

I have noticed that when you install MM 3.2 it does not install the COM object with the Installer but instead you have to run MediaMonkey ONCE as Admin for the COM Object to get registered.

I know MM uses InnoSetup for it's installer and since that runs at Admin level it should be easy enough to add 1 line to the Installer to do the COM object registration.

[code]Filename: {sys}\regsvr32.exe; Parameters: "{app}\MediaMonkey.exe""; StatusMsg: Updating COM Object...; Flags: runhidden[/code]

If not my users are getting this strange error if they install MM 3.2 fresh and immediately try and use MonkeyTunes...

[url]http://www.mediamonkey.com/forum/viewtopic.php?f=19&t=45495[/url]