I'm using a program called InstallForge to generate installers that will place a batch file into the system32 folder.
When it runs and tries to put it in C:\windows\system32\ it is redirected to C:\windows\sysWOW64\ as the installer is a 32 bit application. When this happened in the past, I knew to use the override path C:\windows\sysnative\, however now when I am attempting to do this it reports "Windows can not find the path "C:\WINDOWS\sysnative".
Why might this 32 bit program not be able to access the sysnative folder? If it is 64 bit, why is system32 being redirected to sysWOW64?
1 Answer
It looks to be a bug with InstallForge.
Once the installer is built, InstallForge offers to run the installer immediately, and launches the installer if you selected "yes."
However, when InstallForge runs it, as apposed to the user running it, it does not properly handle the sysnative path. This is likely because it is not being run as an administrator, but I am still unsure exactly why InstallForge does this.
With sloppy testing, I initially missed the cause of the issue.
