Environment variables passed to launched apps
Published on July 31, 2018 By Chris TH In Stardock Software

Hi Dockers

Just discovered a little issue with the environment variables that are passed to the launched apps. It was discovered when attempting to launch the Windows Subsystem for Linux (WSL) from a CMD windows that was, in-turn, launched from OD+. The WSL won't start up (by typing 'wsl' at the command prompt), but if I start a CMD session from the windows start menu it's fine.

This is a Windows 10 Pro Ver 1803, build 17134.191 system.

To diagnose, I captured the environment vars from each session and discovered the following differences:

OD+ Environment

CommonProgramFiles=C:\Program Files (x86)\Common Files

PROCESSOR_ARCHITECTURE=x86
PROCESSOR_ARCHITEW6432=AMD64

ProgramFiles=C:\Program Files (x86)
ProgramFiles(x86)=C:\Program Files (x86)

Default (windows) Environment

CommonProgramFiles=C:\Program Files\Common Files

PROCESSOR_ARCHITECTURE=AMD64

ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)

I think maybe the issue is with the 'Program Files' var in the OD+ environment which would seem to point everything to the "Program Files (x86)" ?

Any way of changing these vars in the OD+ settings?

Cheers,

Chris.


Comments
on Jul 31, 2018

Hello,

Sorry to hear you are having issues. But, its known that OD+ is not supported in Windows 10.

Basj,

Stardock Community Assistant.

on Jul 31, 2018

Well that's a shame.

It's just kept working for me from the OS/2 version right through all the Windows incarnations since then - the utility of it is still there for me even in Win 10  .

Thanks for the reply.