<div>
I've tried it with w but this is related to the process directory , not the executable.<br />
The installer still gets copied on system32<br />
thank you<br />

</div>


I've tried it with w but this is related to the process directory , not the executable.
The installer still gets copied on system32
thank you


<div>
You may need to batch for this but try to put the syswow64 folder into the path statement before the system32 entry.<br />
<br />
try set PATH=%systemroot%\SysWOW64<wbr />;%PATH%<br />
this will be temporary
</div>


You may need to batch for this but try to put the syswow64 folder into the path statement before the system32 entry.

try set PATH=%systemroot%\SysWOW64;%PATH%
this will be temporary

<div>
It's working great.<br />
thank you.<br />

</div>


<div>
<div class="content wysiwyg-content">
Dear All,<br />
Lately I've been using PsExec. I use it to copy some NSIS exe installers to remote machines and execute them. The default remote path of these installers seems to be %windir%\system32. Is there a parameter available to change this to something else?<br />
<br />
I ask because on 64bit Windows systems you can't execute NSIS installers from the system32 directory, it will throw an error. <br />
<br />
Any advice would be greatly appreciated! Thanks a bunch.<br />

</div>
</div>


Dear All,
Lately I've been using PsExec. I use it to copy some NSIS exe installers to remote machines and execute them. The default remote path of these installers seems to be %windir%\system32. Is there a parameter available to change this to something else?

I ask because on 64bit Windows systems you can't execute NSIS installers from the system32 directory, it will throw an error. 

Any advice would be greatly appreciated! Thanks a bunch.


psexec problem on 64bit target systems

A scripting language is a programming language that supports scripts, programs written for a special run-time environment that automate the execution of tasks that could alternatively be executed one-by-one by a human operator. Scripting languages are often interpreted (rather than compiled). Primitives are usually the elementary tasks or API calls, and the language allows them to be combined into more complex programs. Environments that can be automated through scripting include software applications, web pages within a web browser, the shells of operating systems (OS), embedded systems, as well as numerous games. A scripting language can be viewed as a domain-specific language for a particular environment; in the case of scripting an application, this is also known as an extension language.

Scripting Languages

Batch files are text files containing a script of commands that are executed by the command interpreter on DOS, OS/2 and Windows systems. Most commonly, they are used to perform a series of functions that are repeated -- copying a set of files created daily with one step, for example.

Windows Batch

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.