Neurogami,
I have not had this issue with windows 10 64bit machines, you are correct on the
%SystemRoot%\system32\cmd.exe path.
However Windows 7 64 bit seemed to call the x86 directory when executing .bat files...I can only assume that it was related to WMI association that system32 was and should be looked on as a x86 program.
really, the trick was to use the x86 folder to store your .bat files, then you could use (Powershell or a cmd .bat call to the x86 short cut) which can be located anywhere on your PC.
You could use Windows Sysinternals PsEexec. to upload the .bat files to the x86 location and script the up load if it was needing to be deployed on a number of computers.'
PsExec download:
https://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
The below link to one of my PowerPoints might assist you to get your .bat functioning in the method and with the level of access your looking for, I created the PowerPoint located on my One Drive for some tech a few years ago,
as there was a need to leverage the NT Authority subsystem for WBEM.exe usage which was failing and needed the to be ran as the NT Authority permissions. Along with some other crazy security stuff we were doing on the servers.
- However, I never ran any (.bat) cmdlet's with this level of permission as most were pushed with PS exec to x86 folder and the short cuts were added to the Admin$ folder for tech to leverage during remote support. was the easiest
way to not have them know the administrative password on the Servers.
- Note, this issue with the inability to run .bat files on 64 bit machines does not affect me on
Windows 10 & I have been using the Windows 10 for many months now as a MSFT Previewer & employee.
CMD access to Net User (NT Authority\System)http://1drv.ms/1U51N5e
R/
sbryson