Access is denied. This initial program cannot be started. C:\Windows\System32\mstsc.exe

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Access is denied. This initial program cannot be started. C:\Windows\System32\mstsc.exe

L3 Networker

Hey,

 

On few servers, we can get RDP working. it is able to connect to and login, while on few, RDP is not working and it gives below error message. Our PSM servers do not have any DUO installed.

It logs in to PSM, from there, target machine login screen appears, credentials are entered but as soon as machine starts, below error is seen

Access is denied. This initial program cannot be started. C:\Windows\System32\mstsc.exe

1 accepted solution

Accepted Solutions

L3 Networker

Upon investigation, we found that this issue is only limited to servers which are having Remote desktop session host role installed. We have managed to resolve this by making below changes on target server:

Open Server Manager>Remote Desktop Services>Collections>Remote App Programs>Publish Remote App Programs>Add Remote Desktop Connection and add explorer.exe>Publish both.

View solution in original post

8 REPLIES 8

L7 Applicator

This looks like an OS level error - so that's where I'd recommend you look. Why is your user being denied access to MSTSC?

 

Can you RDP from the PSM server to the target outside Cyberark with this user successfully?

 

Are you connecting and opening a secondary connection? or is it just a basic RDP connection?

 

-Matt

Hello @Matt Jennison​ 

 

  1. We are manually able to RDP to target from PSM servers.
  2. It is just a basic RDP connection and not secondary one
  3. Also, we have noticed that when we tried for 4-5 times, it started to work on one of the servers but for few other, it doesn't work even after 7-8 re-tries.

if it works after a few tries, perhaps it's a timeout issue? Still weird it's an access denied situation, though.

 

Based on my research this generally occurs when rdp is trying to open a secondary connection, like ADUC or something like that. Have you checked the target machine event logs to see if there are any further details on why the user is being denied access to mstsc?

 

-Matt

L4 Transporter

This seems to be issue on target for me. Is there start program configure on the target server you are accessing? And also check the target user AD properties.

 

Thank you!

L4 Transporter

This seems to be issue on target for me. Is there start program configure on the target server you are accessing? And also check the target user AD properties.

 

Thank you!

Hi @Ankit Kumar​ 

 

It seems that account you are tying to use to login to those servers doesn’t have permissions start RDP.

 

Also please verify that the mstsc.exe file and its associated files in the C:\Windows\System32 directory have the correct permissions for the user account. You may need to adjust file system permissions using the Security tab in the file properties.

 

In addition please check whether the Firewall or Antivirus is not restricting the RDP.

 

Hope it helps

 

L3 Networker

Upon investigation, we found that this issue is only limited to servers which are having Remote desktop session host role installed. We have managed to resolve this by making below changes on target server:

Open Server Manager>Remote Desktop Services>Collections>Remote App Programs>Publish Remote App Programs>Add Remote Desktop Connection and add explorer.exe>Publish both.

Upon investigation, we found that this issue is only limited to servers which are having Remote desktop session host role installed. We have managed to resolve this by making below changes on target server:

Open Server Manager>Remote Desktop Services>Collections>Remote App Programs>Publish Remote App Programs>Add Remote Desktop Connection and add explorer.exe>Publish both.

  • 1 accepted solution
  • 817 Views
  • 8 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!