The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Solved
Scripting Limitations/unable to run certain commands in C:\WINDOWS\System32
I have the following script that I am deploying to a LogMeIn session with private session mode (using link to download LogMeIn agent and not calling card). The LogMeIn technician console and the agen...
Hi 0000000000, welcome to the community.
I have been informed that the best practice is to check if path C:\Windows\Sysnative\msg.exe exists and then refer msg.exe this way in the shell, otherwise you may call simply msg.exe.
It is recommended to use the following code in a CMD file:
"
if exist C:\Windows\Sysnative\msg.exe (
C:\Windows\Sysnative\msg.exe blabla........
) else (
msg.exe blabbla...
)
"I hope this helps.
Hi 0000000000, welcome to the community.
I have been informed that the best practice is to check if path C:\Windows\Sysnative\msg.exe exists and then refer msg.exe this way in the shell, otherwise you may call simply msg.exe.
It is recommended to use the following code in a CMD file:
"
if exist C:\Windows\Sysnative\msg.exe (
C:\Windows\Sysnative\msg.exe blabla........
) else (
msg.exe blabbla...
)
"
I hope this helps.
- The OS I am running this on is Windows 11. What is weird is that running C:\Windows\Sysnative\msg.exe outside of LogMeIn shows that the file doesn't exist and trying to dir C:\Windows\Sysnative shows the directory doesn't exist.
Running it in LogMeIn works. I guess the LogMeIn applet is running as 32-bit process or running 32-bit command prompt and this folder is a virtual folder only accessible to 32 bit programs so they can run 64-bit programs if the virtual folder is specified in path if these resources are to be believed:
https://www.samlogic.net/articles/sysnative-folder-64-bit-windows.htm
https://learn.microsoft.com/en-us/windows/win32/winprog64/file-system-redirector
