SETP usually fails with a 32 bit process

[vefatica]

SETP with 32-bit processes usually fails. 4572 in devenv.exe (32-bit);

d:\tc25> setp 4572 temp
TCC: Not in environment "temp"

It does work occasionally.

v:\> setp 4572 temp
temp=z:\

Most of the time I can get it to work by first using SETP on a 64-bit process.

v:\> setp 4572 temp
TCC: Not in environment "temp"

v:\> setp 4572 temp
TCC: Not in environment "temp"

v:\> setp 4572 temp
TCC: Not in environment "temp"

v:\> setp 4572 temp
TCC: Not in environment "temp"

v:\> setp %_pid temp <===================== 64-bit process
temp=z:\

v:\> setp 4572 temp
temp=z:\

v:\> setp 4572 temp
temp=z:\

v:\> setp 4572 temp
temp=z:\

 

[vefatica]

Most of the time I can get it to work by first using SETP on a 64-bit process.

In fact that's pretty reliable behavior ... SETP on a 32-bit process doesn't work until SETP has been used on a 64-bit process. Here are 4 newly-started instances of TCC.

 

[vefatica]

There's something else going on here. After SETP on a 64-bit process, SETP on a 32-bit process seems to work, but apparently gives the wrong answer.

Now, devenv (32-bit) is PID 6784. In a new TCC, as in a previous post,

v:\> setp 6784 temp
TCC: Not in environment "temp"

v:\> setp %_pid temp
temp=z:\

v:\> setp 6784 temp
temp=z:\

But I believe that's wrong because

1. My PSET32.EXE gives

v:\> pset32 6784 temp
C:\Users\vefatica\AppData\Local\Temp

2. devenv is writing its temp files to C:\Users\vefatica\AppData\Local\Temp (confirmed with FOLDERMONITOR)

3. devenv was started by PowerPro.exe whose TEMP is C:\Users\vefatica\AppData\Local\Temp

Here's another test; it seems to show the same thing.

v:\> set junk=foo

v:\> setp 6784 junk
TCC: Not in environment "junk"

v:\> setp %_pid junk
junk=foo

v:\> setp 6784 junk
junk=foo

v:\> set junk=bar

v:\> setp %_pid junk
junk=bar

v:\> setp 6784 junk
junk=bar

 

[rconn]

It's a Windows API bug; MS apparently munged it at some point in Win 10. (A quick Google search turned up a number of reports.)

 

[vefatica]

It's a Windows API bug; MS apparently munged it at some point in Win 10. (A quick Google search turned up a number of reports.)

Which API?