RunAs w/ Profile does not grant acess to user environment

[DaveF]

Using beta 3.2.11.0 on XP SP2:

In a child process spawned by the RunAs function with the proper flag to force the as-yet unloaded run-as user's profile to load, the child process's environment is that of the Default User rather than the run-as user's, though the other run-as elements of the run-as user's profile (such as the system registry) can be accessed as desired.

Code to reproduce:

; declare yourself
Dim $ourPID, $ourRead
; Run child task with option to load run-as user's profile
$ourPID = RunAs("is", @ComputerName, "smack", 1, @ComSpec & " /c set", @SystemDir, @SW_HIDE, 2)
; Read the child task's STDOUT output
While 1
  $ourRead &= StdoutRead($ourPID)
  If @error Then ExitLoop
WEnd
; Display result
MsgBox(0, "Debug", @AutoItVersion & " yields:" & @CRLF & $ourRead)

[Valik]

Ahhh hell, good catch, Dave. I see what the problem is.

Note to self: Document that the profile *must* be loaded in order to get environment variables specified in the profile, otherwise a bare-bones environment will be loaded.

[Valik]

Fixed in version: 3.2.11.11

[Valik]

Fixed in version: 3.2.11.12