I have an .msi that contains several embedded, supported language transforms. I test on an English OS using the following command line...
msiexec /i c:\My\Path\Test.msi TRANSFORMS=:1031
On the English OS I do see the install dialogs in German. I can summon the other language displays in a similar manner by substituting the locale id (1040, 1034, etc).
Now if I try to use the same mechanism on a German OS, it fails with the following message...
"Error in the application of transforms. Make sure that the specificed transformation paths are valid." -- (translated from German).
If I simply execute the .msi without passing the transform, on the German OS, the correct dialog language is displayed, in this case German.
Even if I try to launch the .msi on the German OS, passing 1031 as the embedded transform, it still fails. Why can I not call the embedded transform from the command line on the German OS?
We do have some installation packages that are wrapped in a setup.exe with a language selection dialog, but this problem deals with .msi packages that must be delivered that way.
We have an update mechanism that has a language setting. I'm thinking this will be broken or won't work as well because that is also called using TRANSFORMS=:####. We may need to show installations in different languages on any OS. For example we have some users that run English OSs, but the installations run in French using the transform parameter. Why the difference with testing this stuff on English vs German OS. Again, passing the transform argument works on English OS, but not German.
I believe this is also a problem on an Italian OS as well.
Any help appreciated!
Edited by Superfreak3, 29 November 2016 - 23:00.