ContributionsMost RecentMost LikesSolutionsRe: Command prompt closes immediately on connecting It works for a little bit, then the next version breaks it, then they fix it again. We did set a GPO to disable the firewall (still set to Domain), since our AV has its own anyways, and we haven't had problems with this latest version. We had it disabled for over a year though and it didn't help with the last version, so it's hit or miss. Re: Black screen when using remote control on RDP connection to Windows Server 2016Come to find out, it seems to be a problem with the computer itself, somehow. The problem fixes itself when we open the lid of the laptop. When the lid is closed and we use LMI and RDP, the screen is blank for anything, no Run command or Control Panel, or anything. When we open the laptop, everything works just fine and the screen shows up just fine, even if the RDP was blank a second ago. As soon as we close the lid again, everything in the RDP stops again and I can’t click any icons or do any commands. Never had the problem on any other computers. We leave the computers in the office and the users LMI into them to run the programs, so we never needed to have the lids open. This one will have to be though.Re: Black screen when using remote control on RDP connection to Windows Server 2016 I have a client that just started doing the same. No fix yet. If I use LMI and start the RDP, the RDP is blank. If I RDP into the client and use the RDP on their machine to get to the server, then it's fine. Re: Command prompt closes immediately on connecting That's not a solution. Of course we can disturb the user and make them not able to work while we work on a problem. If we don't want to disturb the user and run in the background, we need the PowerShell remote to work. Re: Command prompt closes immediately on connecting I'm still getting this error. Fully updated Windows and LMI 14512. Start Command Prompt and it keeps closing and refreshing. Every computer I try, 20+ so far.