title: Custom Action running as 64-bit on 32-bit install
body: <p>This application is a plugin for a larger application. To complete our installation, we need to run a batch script provided by the main application. The batch script errors saying that a certain registry key doesn't exist, but it exists in the WOW6432 part of the registry. It appears that the custom action is being ran as 64-bit, attempting to fetch the registry without the WOW6432. I have no access or control of the batch file, so I can't change that to check both parts of the registry.</p>
  
  <p>How can I make sure the custom action is ran as 32-bit?</p>
  
  <p>The cmd process is running in 64-bit mode when the batch file is ran.</p>
  
  <p><strong>Edit</strong>: To check if it is running 64 vs 32, I created a seperate batch script which checks looks for a registry key in HKLM/Software/SomeKey. The key is actually located in HKLM/Software/Wow6432/SomeKey. Manually running it with %windir%\SysWow64\cmd.exe (task manager flags this process as *32) works fine. Running it with the regular cmd.exe it cannot find the registry key. Putting this same batch file as a custom action in wix results in the non-*32 cmd to open and the regkey search failure.</p>
  
  <p>I set this batch in Wix like this: </p>
  
  <pre><code>&lt;CustomAction Id="batchCA" Property="BATCHFILE" ExeCommand="" Execute="deferred" /&gt;
  </code></pre>
  
  <p>Where BATCHFILE is a property set the the batchfile path. i.e "C:\temp\batch.cmd". It seems to run fine, but am I doing this wrong?</p>