A network shared RemoteApp won’t start on the remote computer

When starting a windows 2008 (R2) RemoteApp from or depends on a network mapped drive you get the error “The program did not start on the remote computer.”

Solution: The problem is caused because the program is hosted on or depends on a network mapped drive. When starting a RemoteApp the program doesn’t wait till the logon script script is finished but just start the program directly and cannot find the right drive or program.
Workarround is to map the network drive persistant so it’s available before the RemoteApp program starts or create a batch file as RemoteApp so you can first map the network drive and then start the program.

12 Responses to “A network shared RemoteApp won’t start on the remote computer”

  1. Caleb says:

    I have this exact issue however when I launch the published app from almost any other user it runs ok without any mapped drive, but when I launch it with a newly created account it fails. any idea?

    • Scott says:

      Caleb- I am having the same issue. Did you ever find a solution?

      • Chris says:

        The reason a first time login doesn’t work is because it still fails to launch the application the first time without waiting for the login script to initiate correctly. Try running it a second time and it shouldn’t fail. Also, this behavior will probably repeat if the the terminal server reboots from updates pertaining to any system files… Don’t ask me why…

        • Jay says:

          I get the same error and issue. Application runs from a mapped network drive. Trying to run it from RD web access or rdp. file i get the error above. Anyone know a fix or solution for this?

          • ronnypot says:

            did you try to create a persistant network mapping? or run the RemoteApp as a script where you first make the network mapping and then run the program?

  2. Lox says:


    I am having the same problem as well. The app has never had any issues with any other users except for one client. Has anyone figured out a solution for this?


    • ronnypot says:

      it could be that this users profile is corrupted and only loads a temporary profile. Try recreating this users user profile on the remoteapp RDS server.

  3. Katie says:

    We found that we were getting this error because the logon script was hanging for some users. Our logon script is supposed to map 3 drives for each user, but before mapping them it deletes any drives that are currently mapped to those drive letters. The problem was that for certain users it would hang & ask them to allow the deletion of these drives before the script could continue & when they are starting remote apps they do not see this pop up request, so we added a /Q behind the delete portion of our logon script to “quiet” the request, forcing it to continue & that seemed to fix the problem. EXAMPLE: net use s: /delete /Q

    Hope this helps!

  4. Steve McD says:

    Creating a bat file that mapped the drive and then launched the app worked for me. Thanks all!

  5. Rodel says:

    I know this is an old post. But here is the definitive solution.

    1. Go to the RemoteApp Manager
    2. In the RemoteApp Programs list, just change the path of the program to a proper UNC path. i.e. Instead of G:\ShareFolder\ProgramPath\hello.exe, change it to \\Servername\Sharedfolder\ProgramPath\hello.exe

    Hope this helps!

  6. Sokratis says:

    i have the same issue, mapped the drive persistent on the client, but still gettig the error. if i enter the credentials of domain admin, it works. please help.
    PS the domain user is able to login rdp session on the target sevrer

Leave a Reply

Sharing Buttons by Linksku