We have a Chained installation package that installs a few apps and language packs that support quite a variety of properties and therefore we created a transform .mst to apply all the different properties. We have done this many times and have never had an issue with applying the transforms on the cmd line, but now we are having a strange issue.
We are testing on Windows 10 and if we run the cmd line install with TRANSFORMS=test.mst on Win 10, 64 bit the install works as expected, but if we run the exact same cmd on Win 10, 32 bit the install looks okay, but the transform did not get applied at all.
The only thing that I find in the log of the Win 10, 32 bit machine, where 64 bit mentions the transform file name, is: Transforms are not secure.
So why would the 32 bit OS not apply the transform and mention that the transforms are not secure?
Does anyone know why this happens and what could be done to allow the tranforms to be accepted on a 32 bit, Win 10 OS?
Thanks for any help.
We are testing on Windows 10 and if we run the cmd line install with TRANSFORMS=test.mst on Win 10, 64 bit the install works as expected, but if we run the exact same cmd on Win 10, 32 bit the install looks okay, but the transform did not get applied at all.
The only thing that I find in the log of the Win 10, 32 bit machine, where 64 bit mentions the transform file name, is: Transforms are not secure.
So why would the 32 bit OS not apply the transform and mention that the transforms are not secure?
Does anyone know why this happens and what could be done to allow the tranforms to be accepted on a 32 bit, Win 10 OS?
Thanks for any help.