I am working on automating a program to run from a network drive, but I am having problems getting it to run. This program has a .sys file that it uses for something, it is a filter driver. If I run the program from a c:\test with that file in there, it works fine. Due to the sensitive nature of this program, I'd rather have it run from the network drive so that it won't accidently be left on a completed system. In previous efforts I've accomplished this by copying support files to either the script directory, or into SysWoW64/System32. Unfortunately, this program does not use search paths to find the file. In my testing: - ProcMon does not show the EXE looking for the .SYS file. - Depends does not show the .SYS file in the list. - PE Explorer shows that it looks for the .SYS in the same folder as the .EXE is located. So I am wondering if there is a way to configure Windows temporarily using Symbolic Links or an Environment variable or something else to help this EXE find its support file? A worst case scenario is that I'll just copy it to the HDD temporarily to run the program, but I'd rather not take this step if I don't have to. OS using here is Windows 8 Pro x64 which hopefully won't matter.