RunAs regedit.exe requires full path???

[ferbfletcher]

In the past, I could always do this successfully:

 

RunAs($user,$domain,$password,0, "regedit.exe /s someregscript.reg","",@SW_HIDE)

Now, however, regedit.exe will not run unless I specify the path to regedit.exe like this:

RunAs($user,$domain,$password,0, @WindowsDir & "\regedit.exe /s someregscript.reg","",@SW_HIDE)

Other commands still seem to work without a path.  "net.exe" still seems to work fine without a path.

Does the RunAs not use the system path values properly for regedit.exe ?

Edited July 14, 2015 by Melba23
Fixed formatting

[Melba23]

ferbfletcher,

The Help file does say you need to pass the full path - so I am not surprised that you have to do just that.

M23

[ferbfletcher]

ferbfletcher,

The Help file does say you need to pass the full path - so I am not surprised that you have to do just that.

M23

That's not entirely accurate.  In fact, the help file uses this as an example:
Run("notepad.exe")  without any path.  Directly from the help file.

Run("notepad.exe") works.

Run("regedit.exe") does not work.

Run("C:\windows\regedit.exe") works.

So, what is the difference?

[SadBunny]

Regedit works for me with or without a path. As long as I put "#RequireAdmin" on top of my script, that is. Which version of Windows are you using? Sure that your PATH environment variable is ok and that you are not actually running from non-standard directories or anything like that?

[Exit]

my two cents

ShellExecute("regedit.exe")

Or write for Lazy

ShellExecute("regedit")

Edited July 22, 2015 by Exit