locked
ShellExecute doesn't return when opening file on network drive RRS feed

  • Question

  • Hi,

    my application creates a process by means of CreateProcessWithTokenW. The created process uses ShellExecute with parameter 'open' to start another application. This works fine as long as the started application is located on a local drive. If it is located on a network drive ShellExecute never returns.

    If ShellExecute is called directly by the process that actually calls CreateProcessWithTokenW it always works, for local and network files, and independent from whether the calling process is elevated or not.

    Why does ShellExecute not return in this special case? 

    Update: The problem occurs under Windows 7, but not under XP.
    • Edited by _More_ Wednesday, August 1, 2012 1:25 PM
    Wednesday, August 1, 2012 12:59 PM