Scripting

I think you need to use msiexec /qb /x {APPGUID}

(try also /qn if you want really really quiet)

I tried /q /qn /qb+ with no better result.

Any idea?

Did you try the command line exactly as above?

The Microsoft says to use GUID to remove, not the MSI name itself. You don't specifically say that you tried this.

Yes...
Did you package that software?

Never even heard of it... but if it uses MSI it should take the regular command line options. What tool are you using? did you extract the GUID from the MSI? If all of the above doesn't work for you there may be a custom action which forces the uninstall to be verbose (not silent). Maybe you can look for that and REM it out. Can you actually edit the MSI or create a transform (better?). Can you cut and paste the command you're using here?

MsiExec.exe /X"Sources\FSCOMMAND\Contribute_Installer.msi" /qn /L*v "%temp%\Uninstal_%packagename%.log"

We took the commandline from the registry (ARP). And we had the same problem so we took the msi name instead.

In the MSI we found a custom action CA_askuserfordeleteuserconfig and delete it in our MST. So the problem is not reappearing. Very strange.

You really should read the Microsoft link I sent in a prevous post. There is an example of using a GUID with the /X switch and not the MSI name. I don't know if your way is even supported. I've never seen it done that way.

I am always using both (I mean with no difference). And there is no problem. I read the MS documentation and I don't see what you mean.

You should read your link better:
From the command window, type msiexec /x [package|ProductCode] and then press ENTER.
Where:

package is the name of the Windows Installer package file.

ProductCode is the globally unique identifier (GUID) of the Windows Installer package.



This is directly from the MS site and it say specifically it is possible to use the msi name or the GUID.

I am having a little trouble understanding some of your comments.

Deleting the custom action "CA_askuserfordeleteuserconfig" resolved the problem and allowed it to be silently removed?

Indeed, I did misread the MSFT web page.

We created a MST and in our MST, we just removed that custom actions.

We asked Macromedia about it and they said they are not supporting the unattended uninstall and they ask us to look to the newsgroup. LOL

Not a very competent answer.

Well, that's why people like us are needed - to support the unsupported! [;)]

True!
We discovered at the first installation the software is asking for a registrion number then it goes to Internet and store a registration to the HD (outside the file system) and in the registry. This registration is unique because it is base on the serial number and on the Hardware.

How will I support this!