🚀 go-pugleaf

Hi all, I've got a problem that's just appeared today.  Software system has 
been working fine for the last month so I assume MS have updated something.

I have a service that runs and monitors certain aspect of the users 
computer.  We have a system tray application that is used to relay 
information to and from the users desktop via an IPC conduit (since the 
system needs to work in vista and XP, and vista isolates services into 
session 0).

When the user double-clicks on the system tray app, an IPC message is sent 
to the service, which in turn launches a configuration application on the 
users desktop.  The code does this in the following stages:

1) WTSGetActiveConsoleSessionId();
2) WTSQueryUserToken();
3) DuplicateTokenEx();
4) CreateEnvironBlock();
5) CreateProcessAsUserW();

- until today, this code was working fine.  However, CreateProcessAsUser has 
started to return an error code, 123, The filename, directory name, or 
volume label syntax is incorrect.  The second parameter (lpApplicationName) 
to this call is created thus:

WideString wzAppName = (WideString)("\"" + Utils->getControlCentreExePath() 
+ "\"");

In the MSDN documentation, it states:

"If you are using a long file name that contains a space, use quoted strings 
to indicate where the file name ends and the arguments begin; otherwise, the 
file name is ambiguous. For example, consider the string "c:\program 
files\sub dir\program name". This string can be interpreted in a number of 
ways."

So to avoid the possibility of rouge program trying to imitate our config 
application, I use quotes around the path.  This seems to be causing the 
problem.  If I remove the double-quotes, the code works, but there is the 
potential of another application being placed in the root directory (with 
the same name) and being launched instead of ours.

Can anyone help me out there.  Does anyone know a work around or have any 
suggestions?

Many thanks in advance,

Mike