Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, May 14, 2018 4:56 PM | 1 vote
Hello,
After we upgraded to Fall Creator Update, everyone in the workplace has issues remoting into their PCs. This happens when they locked their PCs, head to a conference room (or laptop and other devices), and then remote into their PCs.
The RDP connects but then goes to a black screen after authentication but before the unlocking of the session since CTRL + ALT + END does not work. What also happens is the host PC (work PC in the user perspective) is frozen and had to be manually restarted (or they close the rdp and wait for a while).
We tried disabling printer redirection, disabling bitmap caching, smart card, remote audio, and other options but these doesn't work.
Also tried setting it to TCP only but that didn't work as it is still happening.
We had to close the rdp and wait for a while to reconnect again (which then sometimes show Unlocking your session... in the rdp screen). This workaround isn't viable since it was working fine before the 1709 update.
Windows are up to date using the latest May cumulative update. We can't upgrade to 1803 due to application compatibility issues. Also, downgrading to 1703 is not an option due to management decisions.
Another thing to note is that there is no events in the event logs detailing this issue.
Will there be an actual cumulative update that will directly address this issue?
Sincerely,
Andy
All replies (20)
Monday, May 14, 2018 5:37 PM
Hi,
If you RDP (remote desktop) to a Windows C and see only a black screen the computers involved appear to be arguing over screen resolution.
The easy way to resolve it is to:
- Click on the black RDP windows (to select it) and press CTRL-ALT-END to bring up the Windows Security screen and select LOG OFF, then log back in
- Start a new RDP client on your desktop but BEFORE you click CONNECT, click the SHOW OPTIONS link, click the DISPLAY tab and set the DISPLAY CONFIGURATION to a low resolution like 640×480
To actually solve the problem in the future:
- Disable BitMap Caching in your RDP client (on the EXPERIENCE tab).
- You can use this process to reduce the RDP compression to none.
For more details see, this Microsoft KBase article or this blog.
Kind regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Monday, May 14, 2018 6:59 PM
Hello,
1. Tried that already as mentioned in the ticket. It doesn't respond to the CTRL + ALT + END since it doesn't show up the security screen.
2. Sometimes that doesn't work but that won't be a good workaround for the users (the not tech savvy users).
=================
1. Done that as mentioned in opening post.
2. Haven't tried rdp compression so I will try to sneak that in on a tech that rdp often.
Sincerely,
Andy
Monday, May 14, 2018 8:15 PM
Here's another forum with this issue:
https://superuser.com/questions/976290/windows-10-remote-desktop-connects-with-black-screen-then-disconnects
Kind regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, May 15, 2018 6:31 AM
Hi Andy,
Is that if you use RDP to connect host PC, it will show you black screen?
Please check if you could maximize the remote desktop session screen when it occur black screen.
If yes, please press Ctrl+Shift+Esc to see if it could open task manager.
If yes, please try to run a new task as following screenshot.
Please check if there is any event created in System and Application of Event Viewer on host PC.
Please also check if there is any RDP event created in Event Viewer (Computer Management -> Event Viewer\Applications and Services Logs\Microsoft\ Windows\ TerminalServices-LocalSessionManager\Operational)
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, May 15, 2018 4:43 PM
I tried Ctrl + Shift + Esc and it doesn't work.
I found these events in a PC that I had the black screen issue.
================================================================
Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Source: Microsoft-Windows-TerminalServices-LocalSessionManager
Date: 5/11/2018 1:35:06 PM
Event ID: 36
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: computer.ssa.domain
Description:
An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x800708CA)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-LocalSessionManager" Guid="{5D896912-022D-40AA-A3A8-4FA5515C76D7}" />
<EventID>36</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x1000000000000000</Keywords>
<TimeCreated SystemTime="2018-05-11T20:35:06.691646000Z" />
<EventRecordID>981</EventRecordID>
<Correlation ActivityID="{F42036AF-0DFB-4ECC-90F8-3CC2EB440000}" />
<Execution ProcessID="484" ThreadID="2464" />
<Channel>Microsoft-Windows-TerminalServices-LocalSessionManager/Operational</Channel>
<Computer>computer.ssa.domain</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionId">4</Data>
<Data Name="State">8</Data>
<Data Name="StateName">CsrConnected</Data>
<Data Name="Event">2</Data>
<Data Name="EventName">EvCsrInitialized</Data>
<Data Name="ErrorCode">0x800708ca</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Source: Microsoft-Windows-TerminalServices-LocalSessionManager
Date: 5/11/2018 1:35:06 PM
Event ID: 36
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: computer.ssa.domain
Description:
An error occurred when transitioning from DisconnectedLoggedOn in response to EvConnected. (ErrorCode 0x800708CA)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-LocalSessionManager" Guid="{5D896912-022D-40AA-A3A8-4FA5515C76D7}" />
<EventID>36</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x1000000000000000</Keywords>
<TimeCreated SystemTime="2018-05-11T20:35:06.641216600Z" />
<EventRecordID>980</EventRecordID>
<Correlation ActivityID="{F4201620-FBF8-4808-9075-699EF6450000}" />
<Execution ProcessID="484" ThreadID="6016" />
<Channel>Microsoft-Windows-TerminalServices-LocalSessionManager/Operational</Channel>
<Computer>computer.ssa.domain</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionId">1</Data>
<Data Name="State">4</Data>
<Data Name="StateName">DisconnectedLoggedOn</Data>
<Data Name="Event">3</Data>
<Data Name="EventName">EvConnected</Data>
<Data Name="ErrorCode">0x800708ca</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Source: Microsoft-Windows-TerminalServices-LocalSessionManager
Date: 5/11/2018 1:35:06 PM
Event ID: 36
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: computer.ssa.domain
Description:
An error occurred when transitioning from DisconnectedLoggedOn in response to EvDesktopUnlocked. (ErrorCode 0x8007139F)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-LocalSessionManager" Guid="{5D896912-022D-40AA-A3A8-4FA5515C76D7}" />
<EventID>36</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x1000000000000000</Keywords>
<TimeCreated SystemTime="2018-05-11T20:35:06.482154900Z" />
<EventRecordID>979</EventRecordID>
<Correlation ActivityID="{F4201620-FBF8-4808-9075-699EF6450000}" />
<Execution ProcessID="484" ThreadID="6384" />
<Channel>Microsoft-Windows-TerminalServices-LocalSessionManager/Operational</Channel>
<Computer>computer.ssa.domain</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionId">1</Data>
<Data Name="State">4</Data>
<Data Name="StateName">DisconnectedLoggedOn</Data>
<Data Name="Event">14</Data>
<Data Name="EventName">EvDesktopUnlocked</Data>
<Data Name="ErrorCode">0x8007139f</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Source: Microsoft-Windows-TerminalServices-LocalSessionManager
Date: 5/11/2018 1:35:05 PM
Event ID: 40
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: computer.ssa.domain
Description:
Session 3 has been disconnected, reason code 12
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-LocalSessionManager" Guid="{5D896912-022D-40AA-A3A8-4FA5515C76D7}" />
<EventID>40</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x1000000000000000</Keywords>
<TimeCreated SystemTime="2018-05-11T20:35:05.664982900Z" />
<EventRecordID>978</EventRecordID>
<Correlation ActivityID="{F420D8BB-EE8C-4DD0-B0F4-E4BB6C3F0000}" />
<Execution ProcessID="484" ThreadID="4592" />
<Channel>Microsoft-Windows-TerminalServices-LocalSessionManager/Operational</Channel>
<Computer>computer.ssa.domain</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<EventXML xmlns="Event_NS">
<Session>3</Session>
<Reason>12</Reason>
</EventXML>
</UserData>
</Event>
Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Source: Microsoft-Windows-TerminalServices-LocalSessionManager
Date: 5/11/2018 1:35:05 PM
Event ID: 36
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: computer.ssa.domain
Description:
An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x800708CA)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-LocalSessionManager" Guid="{5D896912-022D-40AA-A3A8-4FA5515C76D7}" />
<EventID>36</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x1000000000000000</Keywords>
<TimeCreated SystemTime="2018-05-11T20:35:05.652556000Z" />
<EventRecordID>977</EventRecordID>
<Correlation ActivityID="{F420D8BB-EE8C-4DD0-B0F4-E4BB6C3F0000}" />
<Execution ProcessID="484" ThreadID="4592" />
<Channel>Microsoft-Windows-TerminalServices-LocalSessionManager/Operational</Channel>
<Computer>computer.ssa.domain</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionId">3</Data>
<Data Name="State">8</Data>
<Data Name="StateName">CsrConnected</Data>
<Data Name="Event">2</Data>
<Data Name="EventName">EvCsrInitialized</Data>
<Data Name="ErrorCode">0x800708ca</Data>
</EventData>
</Event>
Tuesday, May 15, 2018 4:47 PM
Tried those steps and it didn't fixed the issue (focusing on prevention).
Bitmap caching was disabled - still happens
Can;t make users local admins since that is a security risk
It is always set to full screen on the rdp so that didn't work
Video drivers are up to date and it is still happening.
RDP worked fine in 1607 and 1703 so I don't know what changed that could be causing it in 1709
Friday, May 18, 2018 11:28 PM
The RDP compression did not work. Had someone that remotes from home sometimes test this.
Tuesday, May 22, 2018 4:15 PM
Any other suggestions? Hopefully, a cumulative update fixes this rather than relying on a workaround.
Not sure that KB4103714 fixes this since it is not in the notes. At least it fixes a RemoteApp issue we are noticing.
Wednesday, May 30, 2018 11:16 PM
Still having issues relating to this. It is annoying with the black screen since it forces a reboot when workaround doesn't work.
When will Microsoft address the black screen rdp issue? The issue causes a deadlock when trying to remote into a active session.
Thursday, May 31, 2018 11:06 PM
I made a feedback in the feedback hub. Not sure if that is going to help or not though.
Friday, November 2, 2018 1:45 PM
Still having issues relating to this. It is annoying with the black screen since it forces a reboot when workaround doesn't work.
When will Microsoft address the black screen rdp issue? The issue causes a deadlock when trying to remote into a active session.
I would definitely check to make sure you have License Installed. If you are connecting via rdp to your dedicated server and Black Screen is forced and the only thing you see is your cursor. then its 100% Licenses related issue. make sure you have windows license installed and paid for in your dedicated server control panel.
Good luck.
Tuesday, December 11, 2018 11:14 PM
Not sure that was helpful at all. I know this is not a licensing issue.
Thursday, March 14, 2019 4:12 PM
Also seeing the issue on v1809
Tried disabling bitmap cache, printers etc.
Disabled UDP and connection is TCP
After resizing the window and waiting the session comes back and the even log has explorer.exe error and restart
Faulting application name: Explorer.EXE, version: 10.0.17763.348, time stamp: 0x03d46193
Faulting module name: explorerframe.dll, version: 10.0.17763.1, time stamp: 0x4d895e00
Exception code: 0xc0000409
Fault offset: 0x0000000000094127
Faulting process id: 0x22a8
Faulting application start time: 0x01d4d9e45b624c49
Faulting application path: C:\WINDOWS\Explorer.EXE
Faulting module path: C:\WINDOWS\system32\explorerframe.dll
Report Id: 9914cb94-49bd-4003-be5c-ab92d168b478
Faulting package full name:
Faulting package-relative application ID:
Is there a workaround or fix for this?
Thursday, March 14, 2019 5:46 PM
Just an update, issue seems to be on client side connecting. Using 1709 based WIN 10 host to connect does not have this issue.
Monday, March 25, 2019 8:41 PM
We are also having this same issues since the 1809 version Remote Desktop from One PC to others in another location. It seems to happen after the login if you toggle between the host machine and the one you are remoting to.
Anyone have a good answer or is there a hotfix out there that helps with this?
Tried all of the things above and it does not work.
Wednesday, March 27, 2019 12:54 AM
I thought this was something with my configuration. It would be nice to see this resolved soon since it appears to be related to the latest update that was sent out.
Wednesday, March 27, 2019 7:00 PM
You can get the Remote Desktop app from Microsoft Store
Tuesday, April 23, 2019 3:10 PM
Running 1809 same issue. We remote heavily in our office so I see it at least once a day. Sometimes it even freezes the target computer to the point of needing a hard reboot. None of the suggestions in this thread or any other I've found have helped. I've been dealing with this since version 1703.
Thursday, April 25, 2019 3:10 PM
Did you try the Microsoft RDP from the Store. I have no black screens using the UWP app
Wednesday, September 11, 2019 7:57 PM
Still broken on some computers, it's got to be a setting somewhere... the RDP app gets black screen also.