Windows 10 Remote Desktop Connects with Black Screen then DisconnectsRemote Desktop connection starts up,...
What is the difference between rolling more dice versus fewer dice?
How can I play a serial killer in a party of good PCs?
Macro expansion inside href
Saint abbreviation
Why don't key signatures indicate the tonic?
Why do we have to make "peinlich" start with a capital letter and also end with -s in this sentence?
A curious equality of integrals involving the prime counting function?
What will happen if Parliament votes "no" on each of the Brexit-related votes to be held on the 12th, 13th and 14th of March?
How do you funnel food off a cutting board?
How do you voice extended chords?
Is "the fire consumed everything on its way" correct?
Has Britain negotiated with any other countries outside the EU in preparation for the exit?
Play Zip, Zap, Zop
Why didn't Tom Riddle take the presence of Fawkes and the Sorting Hat as more of a threat?
Do "fields" always combine by addition?
How would an AI self awareness kill switch work?
Has any human ever had the choice to leave Earth permanently?
How to deal with possible delayed baggage?
After checking in online, how do I know whether I need to go show my passport at airport check-in?
What is the wife of a henpecked husband called?
Hilchos Shabbos English Sefer
Why do neural networks need so many training examples to perform?
How do I append a character to the end of every line in an excel cell?
TikZ graph edges not drawn nicely
Windows 10 Remote Desktop Connects with Black Screen then Disconnects
Remote Desktop connection starts up, screen draws, then goes blackRestore console session after remote desktop disconnects?Win 7: Black screen on boot up, before login screen?No sound after 5 minutesOdd disconnects with remote desktop connectionMouse lag/stutter when remote desktop client (mstsc) full-screen and multiple monitorsWindows remote desktop with software VPNLong black screen before Windows 7 starts loadingBlack screen with cursor after loginPC Desktop black screen upon booting
I've been having this issue since I updated (fresh install) to Windows 10 Professional. I used to connect to my computer via RDP through WAN and LAN with no issues.
After installing W10 and setting up everything correctly (ports, static IP etc) I still can connect, but during the day it randomly kicks me out and I can't successfully log in afterwards. It makes a secure connection and connects, but I get a black screen without a cursor and disconnects a few seconds after that without any errors.
It's an Intel i7 desktop with nVidia GPU with the latest drivers.
Things that I know/tried:
When issue occurs, I can replicate it on Windows, Mac, or iPads/iPhones over LAN or WAN.
Rebooting temporarily fixes the problem, until it starts happening again.
Disabling bitmap caching or changing resolution on RDP client doesn't fix it.
Pressing CTRL + ALT + END doesn't do anything.
Created a new account and tried logging on to that to test if it is account related, still didn't log in.
Did a
sfc /scannowto do a system scan and fix corrupt files, it came out with no errors.I checked the event log and apparently WINLOGON keeps crashing. It only says "the windows logon process has unexpectedly terminated"
I ran out of options to fix this, any help will be appreciated.
remote-desktop windows-10 connection black-screen-of-death
edited Sep 22 '15 at 5:24
Sami Kuhmonen
1,51211022
asked Sep 21 '15 at 22:51
asansalasansal
116113
|
show 3 more comments
I've been having this issue since I updated (fresh install) to Windows 10 Professional. I used to connect to my computer via RDP through WAN and LAN with no issues.
After installing W10 and setting up everything correctly (ports, static IP etc) I still can connect, but during the day it randomly kicks me out and I can't successfully log in afterwards. It makes a secure connection and connects, but I get a black screen without a cursor and disconnects a few seconds after that without any errors.
It's an Intel i7 desktop with nVidia GPU with the latest drivers.
Things that I know/tried:
When issue occurs, I can replicate it on Windows, Mac, or iPads/iPhones over LAN or WAN.
Rebooting temporarily fixes the problem, until it starts happening again.
Disabling bitmap caching or changing resolution on RDP client doesn't fix it.
Pressing CTRL + ALT + END doesn't do anything.
Created a new account and tried logging on to that to test if it is account related, still didn't log in.
Did a
sfc /scannowto do a system scan and fix corrupt files, it came out with no errors.I checked the event log and apparently WINLOGON keeps crashing. It only says "the windows logon process has unexpectedly terminated"
I ran out of options to fix this, any help will be appreciated.
remote-desktop windows-10 connection black-screen-of-death
edited Sep 22 '15 at 5:24
Sami Kuhmonen
1,51211022
asked Sep 21 '15 at 22:51
asansalasansal
116113
Is it the client or the server that you reboot that fixes the problem?
– cdavid
Sep 21 '15 at 23:22
Have you tried using a VPN and not exposing 3389 to the WAN?
– Linef4ult
Sep 22 '15 at 5:36
Me too. It's not this - tenforums.com/network-sharing/… because I have passwords on all the accounts, and it does the same thing regardless of local console connections status.
– nerdfever.com
Jan 9 '16 at 20:04
I have been experiencing this issue with server 2012 R2, and while the issue may not be related, the symptoms are very similar. Black screen and rebooting the server fixed it for a while. I don't have an answer, but I have it linked to TermService service crashing, despite not much in the logs indicating it. TermService is unusual since it can't be stopped via services.msc, but you can usetasklist /svc | findstr /C:TermServiceto identify the Process ID andtaskkill /F /PID [process_id]to end the process. Start TermService usingnet start TermService. I am still working on a solution.
– Johnny Keeton
Aug 24 '16 at 2:03
1
@Todilo See my answer below.
– Syntax Error
Mar 12 '18 at 22:39
|
show 3 more comments
I've been having this issue since I updated (fresh install) to Windows 10 Professional. I used to connect to my computer via RDP through WAN and LAN with no issues.
After installing W10 and setting up everything correctly (ports, static IP etc) I still can connect, but during the day it randomly kicks me out and I can't successfully log in afterwards. It makes a secure connection and connects, but I get a black screen without a cursor and disconnects a few seconds after that without any errors.
It's an Intel i7 desktop with nVidia GPU with the latest drivers.
Things that I know/tried:
When issue occurs, I can replicate it on Windows, Mac, or iPads/iPhones over LAN or WAN.
Rebooting temporarily fixes the problem, until it starts happening again.
Disabling bitmap caching or changing resolution on RDP client doesn't fix it.
Pressing CTRL + ALT + END doesn't do anything.
Created a new account and tried logging on to that to test if it is account related, still didn't log in.
Did a
sfc /scannowto do a system scan and fix corrupt files, it came out with no errors.I checked the event log and apparently WINLOGON keeps crashing. It only says "the windows logon process has unexpectedly terminated"
I ran out of options to fix this, any help will be appreciated.
remote-desktop windows-10 connection black-screen-of-death
edited Sep 22 '15 at 5:24
Sami Kuhmonen
1,51211022
asked Sep 21 '15 at 22:51
asansalasansal
116113
I've been having this issue since I updated (fresh install) to Windows 10 Professional. I used to connect to my computer via RDP through WAN and LAN with no issues.
After installing W10 and setting up everything correctly (ports, static IP etc) I still can connect, but during the day it randomly kicks me out and I can't successfully log in afterwards. It makes a secure connection and connects, but I get a black screen without a cursor and disconnects a few seconds after that without any errors.
It's an Intel i7 desktop with nVidia GPU with the latest drivers.
Things that I know/tried:
When issue occurs, I can replicate it on Windows, Mac, or iPads/iPhones over LAN or WAN.
Rebooting temporarily fixes the problem, until it starts happening again.
Disabling bitmap caching or changing resolution on RDP client doesn't fix it.
Pressing CTRL + ALT + END doesn't do anything.
Created a new account and tried logging on to that to test if it is account related, still didn't log in.
Did a
sfc /scannowto do a system scan and fix corrupt files, it came out with no errors.I checked the event log and apparently WINLOGON keeps crashing. It only says "the windows logon process has unexpectedly terminated"
I ran out of options to fix this, any help will be appreciated.
remote-desktop windows-10 connection black-screen-of-death
remote-desktop windows-10 connection black-screen-of-death
edited Sep 22 '15 at 5:24
Sami Kuhmonen
1,51211022
asked Sep 21 '15 at 22:51
asansalasansal
116113
edited Sep 22 '15 at 5:24
Sami Kuhmonen
1,51211022
asked Sep 21 '15 at 22:51
asansalasansal
116113
edited Sep 22 '15 at 5:24
Sami Kuhmonen
1,51211022
edited Sep 22 '15 at 5:24
Sami Kuhmonen
1,51211022
edited Sep 22 '15 at 5:24
Sami Kuhmonen
1,51211022
1,51211022
asked Sep 21 '15 at 22:51
asansalasansal
116113
asked Sep 21 '15 at 22:51
asansalasansal
116113
asked Sep 21 '15 at 22:51
asansalasansal
116113
116113
Is it the client or the server that you reboot that fixes the problem?
– cdavid
Sep 21 '15 at 23:22
Have you tried using a VPN and not exposing 3389 to the WAN?
– Linef4ult
Sep 22 '15 at 5:36
Me too. It's not this - tenforums.com/network-sharing/… because I have passwords on all the accounts, and it does the same thing regardless of local console connections status.
– nerdfever.com
Jan 9 '16 at 20:04
I have been experiencing this issue with server 2012 R2, and while the issue may not be related, the symptoms are very similar. Black screen and rebooting the server fixed it for a while. I don't have an answer, but I have it linked to TermService service crashing, despite not much in the logs indicating it. TermService is unusual since it can't be stopped via services.msc, but you can usetasklist /svc | findstr /C:TermServiceto identify the Process ID andtaskkill /F /PID [process_id]to end the process. Start TermService usingnet start TermService. I am still working on a solution.
– Johnny Keeton
Aug 24 '16 at 2:03
1
@Todilo See my answer below.
– Syntax Error
Mar 12 '18 at 22:39
|
show 3 more comments
Is it the client or the server that you reboot that fixes the problem?
– cdavid
Sep 21 '15 at 23:22
Have you tried using a VPN and not exposing 3389 to the WAN?
– Linef4ult
Sep 22 '15 at 5:36
Me too. It's not this - tenforums.com/network-sharing/… because I have passwords on all the accounts, and it does the same thing regardless of local console connections status.
– nerdfever.com
Jan 9 '16 at 20:04
I have been experiencing this issue with server 2012 R2, and while the issue may not be related, the symptoms are very similar. Black screen and rebooting the server fixed it for a while. I don't have an answer, but I have it linked to TermService service crashing, despite not much in the logs indicating it. TermService is unusual since it can't be stopped via services.msc, but you can usetasklist /svc | findstr /C:TermServiceto identify the Process ID andtaskkill /F /PID [process_id]to end the process. Start TermService usingnet start TermService. I am still working on a solution.
– Johnny Keeton
Aug 24 '16 at 2:03
1
@Todilo See my answer below.
– Syntax Error
Mar 12 '18 at 22:39
Is it the client or the server that you reboot that fixes the problem?
– cdavid
Sep 21 '15 at 23:22
Is it the client or the server that you reboot that fixes the problem?
– cdavid
Sep 21 '15 at 23:22
Have you tried using a VPN and not exposing 3389 to the WAN?
– Linef4ult
Sep 22 '15 at 5:36
Have you tried using a VPN and not exposing 3389 to the WAN?
– Linef4ult
Sep 22 '15 at 5:36
Me too. It's not this - tenforums.com/network-sharing/… because I have passwords on all the accounts, and it does the same thing regardless of local console connections status.
– nerdfever.com
Jan 9 '16 at 20:04
Me too. It's not this - tenforums.com/network-sharing/… because I have passwords on all the accounts, and it does the same thing regardless of local console connections status.
– nerdfever.com
Jan 9 '16 at 20:04
I have been experiencing this issue with server 2012 R2, and while the issue may not be related, the symptoms are very similar. Black screen and rebooting the server fixed it for a while. I don't have an answer, but I have it linked to TermService service crashing, despite not much in the logs indicating it. TermService is unusual since it can't be stopped via services.msc, but you can use
tasklist /svc | findstr /C:TermService to identify the Process ID and taskkill /F /PID [process_id] to end the process. Start TermService using net start TermService. I am still working on a solution.– Johnny Keeton
Aug 24 '16 at 2:03
I have been experiencing this issue with server 2012 R2, and while the issue may not be related, the symptoms are very similar. Black screen and rebooting the server fixed it for a while. I don't have an answer, but I have it linked to TermService service crashing, despite not much in the logs indicating it. TermService is unusual since it can't be stopped via services.msc, but you can use
tasklist /svc | findstr /C:TermService to identify the Process ID and taskkill /F /PID [process_id] to end the process. Start TermService using net start TermService. I am still working on a solution.– Johnny Keeton
Aug 24 '16 at 2:03
1
1
@Todilo See my answer below.
– Syntax Error
Mar 12 '18 at 22:39
@Todilo See my answer below.
– Syntax Error
Mar 12 '18 at 22:39
|
show 3 more comments
4 Answers
4
active
oldest
votes
Remote Desktop – Black Screen Of Death
The Issue
Using Remote Desktop the remote screen turns black right after login and you have no control. The issue appears to be caused by Screen Caching and accessing a system with different display resolution or RDP window sizes.
The Solution(s)
- While logged in and stuck on the black screen of death
- Press CTRL+ALT+END, or CTRL+ALT+FN+END on laptops. This calls Task Manager and in most cases you’ll immediately see the Desktop.
- If only Task Manager but no Desktop appears try running Explorer from Task Manager:
File > New Task > Explorer.exe
- Try connecting at a different resolution.
- Access the remote computers Computer Management or Services MMC and cycle the Remote Desktop Services service.
- Update display drivers, both on the connecting machine and on the machine you are connecting too.
- Some users are experiencing this with Nvidia GPUs. The Geforce Experience program has a "Share" feature aka "shadow play"; when enabled some people experience the problem. Try to disable it, restart and see if it helps.
- Check the display settings at the remote host and see if there is a phantom monitor present. Might need to change which monitor is the primary one
- 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.
- Try turning off Fast Startup
- This feature only works when you do a SHUTDOWN and then Boot. It doesn't effect a RESTART.
- Go to Control panel, Power Options and select Choose What the Power Buttons Do on the left.
- Then select Change Settings That are Currently Unavailable near the top center of screen...
- Lower down on the window, uncheck Fast Startup.
Prevention
- Disable bitmap caching for your RDP connections
- Confirm RDP account has full administrative rights on remote system
- Access the remote computer using consistent resolution – Full screen may help
- Confirm both systems' video drivers are up to date
Resources
(Google it at Microsoft support sites; I have too low a reputation to post links)
- Disable Bitmap Caching
2012 - Hotfix for “Black screen during a Remote Assistance session in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2”
- The lock screen is black or blank and does not respond to keyboard or swipe actions in Windows 10 Technical Preview
edited Aug 29 '18 at 12:56
JonathanDavidArndt
78711228
answered Feb 2 '17 at 8:55
daddedadde
15116
add a comment |
I've had the same problem - switch from 32bit to 24bit colours and it will let you connect as normal. All other settings can be left on their defaults.
answered Mar 12 '18 at 22:39
Syntax ErrorSyntax Error
16212
add a comment |
This might not help but I solved it by turning down the resolution. The problem occured as the monitor I was connecting from was 2560x1440, and the remote computer wouldn't allow that. Turning it down to 1920x1080 worked fine and I am now connected with everything showing.
answered Oct 29 '18 at 12:30
UnknownUnknown
1
add a comment |
I had this issue since I was having different DPI. On my laptop I had DPI set to 125% while a computer I was connecting had 100%. Setting DPI to 100% on laptop solved the problem.
answered 11 mins ago
Stanislav BerkovStanislav Berkov
1012
New contributor
Stanislav Berkov is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f976290%2fwindows-10-remote-desktop-connects-with-black-screen-then-disconnects%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Remote Desktop – Black Screen Of Death
The Issue
Using Remote Desktop the remote screen turns black right after login and you have no control. The issue appears to be caused by Screen Caching and accessing a system with different display resolution or RDP window sizes.
The Solution(s)
- While logged in and stuck on the black screen of death
- Press CTRL+ALT+END, or CTRL+ALT+FN+END on laptops. This calls Task Manager and in most cases you’ll immediately see the Desktop.
- If only Task Manager but no Desktop appears try running Explorer from Task Manager:
File > New Task > Explorer.exe
- Try connecting at a different resolution.
- Access the remote computers Computer Management or Services MMC and cycle the Remote Desktop Services service.
- Update display drivers, both on the connecting machine and on the machine you are connecting too.
- Some users are experiencing this with Nvidia GPUs. The Geforce Experience program has a "Share" feature aka "shadow play"; when enabled some people experience the problem. Try to disable it, restart and see if it helps.
- Check the display settings at the remote host and see if there is a phantom monitor present. Might need to change which monitor is the primary one
- 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.
- Try turning off Fast Startup
- This feature only works when you do a SHUTDOWN and then Boot. It doesn't effect a RESTART.
- Go to Control panel, Power Options and select Choose What the Power Buttons Do on the left.
- Then select Change Settings That are Currently Unavailable near the top center of screen...
- Lower down on the window, uncheck Fast Startup.
Prevention
- Disable bitmap caching for your RDP connections
- Confirm RDP account has full administrative rights on remote system
- Access the remote computer using consistent resolution – Full screen may help
- Confirm both systems' video drivers are up to date
Resources
(Google it at Microsoft support sites; I have too low a reputation to post links)
- Disable Bitmap Caching
2012 - Hotfix for “Black screen during a Remote Assistance session in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2”
- The lock screen is black or blank and does not respond to keyboard or swipe actions in Windows 10 Technical Preview
edited Aug 29 '18 at 12:56
JonathanDavidArndt
78711228
answered Feb 2 '17 at 8:55
daddedadde
15116
add a comment |
Remote Desktop – Black Screen Of Death
The Issue
Using Remote Desktop the remote screen turns black right after login and you have no control. The issue appears to be caused by Screen Caching and accessing a system with different display resolution or RDP window sizes.
The Solution(s)
- While logged in and stuck on the black screen of death
- Press CTRL+ALT+END, or CTRL+ALT+FN+END on laptops. This calls Task Manager and in most cases you’ll immediately see the Desktop.
- If only Task Manager but no Desktop appears try running Explorer from Task Manager:
File > New Task > Explorer.exe
- Try connecting at a different resolution.
- Access the remote computers Computer Management or Services MMC and cycle the Remote Desktop Services service.
- Update display drivers, both on the connecting machine and on the machine you are connecting too.
- Some users are experiencing this with Nvidia GPUs. The Geforce Experience program has a "Share" feature aka "shadow play"; when enabled some people experience the problem. Try to disable it, restart and see if it helps.
- Check the display settings at the remote host and see if there is a phantom monitor present. Might need to change which monitor is the primary one
- 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.
- Try turning off Fast Startup
- This feature only works when you do a SHUTDOWN and then Boot. It doesn't effect a RESTART.
- Go to Control panel, Power Options and select Choose What the Power Buttons Do on the left.
- Then select Change Settings That are Currently Unavailable near the top center of screen...
- Lower down on the window, uncheck Fast Startup.
Prevention
- Disable bitmap caching for your RDP connections
- Confirm RDP account has full administrative rights on remote system
- Access the remote computer using consistent resolution – Full screen may help
- Confirm both systems' video drivers are up to date
Resources
(Google it at Microsoft support sites; I have too low a reputation to post links)
- Disable Bitmap Caching
2012 - Hotfix for “Black screen during a Remote Assistance session in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2”
- The lock screen is black or blank and does not respond to keyboard or swipe actions in Windows 10 Technical Preview
edited Aug 29 '18 at 12:56
JonathanDavidArndt
78711228
answered Feb 2 '17 at 8:55
daddedadde
15116
add a comment |
Remote Desktop – Black Screen Of Death
The Issue
Using Remote Desktop the remote screen turns black right after login and you have no control. The issue appears to be caused by Screen Caching and accessing a system with different display resolution or RDP window sizes.
The Solution(s)
- While logged in and stuck on the black screen of death
- Press CTRL+ALT+END, or CTRL+ALT+FN+END on laptops. This calls Task Manager and in most cases you’ll immediately see the Desktop.
- If only Task Manager but no Desktop appears try running Explorer from Task Manager:
File > New Task > Explorer.exe
- Try connecting at a different resolution.
- Access the remote computers Computer Management or Services MMC and cycle the Remote Desktop Services service.
- Update display drivers, both on the connecting machine and on the machine you are connecting too.
- Some users are experiencing this with Nvidia GPUs. The Geforce Experience program has a "Share" feature aka "shadow play"; when enabled some people experience the problem. Try to disable it, restart and see if it helps.
- Check the display settings at the remote host and see if there is a phantom monitor present. Might need to change which monitor is the primary one
- 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.
- Try turning off Fast Startup
- This feature only works when you do a SHUTDOWN and then Boot. It doesn't effect a RESTART.
- Go to Control panel, Power Options and select Choose What the Power Buttons Do on the left.
- Then select Change Settings That are Currently Unavailable near the top center of screen...
- Lower down on the window, uncheck Fast Startup.
Prevention
- Disable bitmap caching for your RDP connections
- Confirm RDP account has full administrative rights on remote system
- Access the remote computer using consistent resolution – Full screen may help
- Confirm both systems' video drivers are up to date
Resources
(Google it at Microsoft support sites; I have too low a reputation to post links)
- Disable Bitmap Caching
2012 - Hotfix for “Black screen during a Remote Assistance session in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2”
- The lock screen is black or blank and does not respond to keyboard or swipe actions in Windows 10 Technical Preview
edited Aug 29 '18 at 12:56
JonathanDavidArndt
78711228
answered Feb 2 '17 at 8:55
daddedadde
15116
Remote Desktop – Black Screen Of Death
The Issue
Using Remote Desktop the remote screen turns black right after login and you have no control. The issue appears to be caused by Screen Caching and accessing a system with different display resolution or RDP window sizes.
The Solution(s)
- While logged in and stuck on the black screen of death
- Press CTRL+ALT+END, or CTRL+ALT+FN+END on laptops. This calls Task Manager and in most cases you’ll immediately see the Desktop.
- If only Task Manager but no Desktop appears try running Explorer from Task Manager:
File > New Task > Explorer.exe
- Try connecting at a different resolution.
- Access the remote computers Computer Management or Services MMC and cycle the Remote Desktop Services service.
- Update display drivers, both on the connecting machine and on the machine you are connecting too.
- Some users are experiencing this with Nvidia GPUs. The Geforce Experience program has a "Share" feature aka "shadow play"; when enabled some people experience the problem. Try to disable it, restart and see if it helps.
- Check the display settings at the remote host and see if there is a phantom monitor present. Might need to change which monitor is the primary one
- 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.
- Try turning off Fast Startup
- This feature only works when you do a SHUTDOWN and then Boot. It doesn't effect a RESTART.
- Go to Control panel, Power Options and select Choose What the Power Buttons Do on the left.
- Then select Change Settings That are Currently Unavailable near the top center of screen...
- Lower down on the window, uncheck Fast Startup.
Prevention
- Disable bitmap caching for your RDP connections
- Confirm RDP account has full administrative rights on remote system
- Access the remote computer using consistent resolution – Full screen may help
- Confirm both systems' video drivers are up to date
Resources
(Google it at Microsoft support sites; I have too low a reputation to post links)
- Disable Bitmap Caching
2012 - Hotfix for “Black screen during a Remote Assistance session in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2”
- The lock screen is black or blank and does not respond to keyboard or swipe actions in Windows 10 Technical Preview
edited Aug 29 '18 at 12:56
JonathanDavidArndt
78711228
answered Feb 2 '17 at 8:55
daddedadde
15116
edited Aug 29 '18 at 12:56
JonathanDavidArndt
78711228
edited Aug 29 '18 at 12:56
JonathanDavidArndt
78711228
edited Aug 29 '18 at 12:56
JonathanDavidArndt
78711228
78711228
answered Feb 2 '17 at 8:55
daddedadde
15116
answered Feb 2 '17 at 8:55
daddedadde
15116
answered Feb 2 '17 at 8:55
daddedadde
15116
15116
add a comment |
add a comment |
I've had the same problem - switch from 32bit to 24bit colours and it will let you connect as normal. All other settings can be left on their defaults.
answered Mar 12 '18 at 22:39
Syntax ErrorSyntax Error
16212
add a comment |
I've had the same problem - switch from 32bit to 24bit colours and it will let you connect as normal. All other settings can be left on their defaults.
answered Mar 12 '18 at 22:39
Syntax ErrorSyntax Error
16212
add a comment |
I've had the same problem - switch from 32bit to 24bit colours and it will let you connect as normal. All other settings can be left on their defaults.
answered Mar 12 '18 at 22:39
Syntax ErrorSyntax Error
16212
I've had the same problem - switch from 32bit to 24bit colours and it will let you connect as normal. All other settings can be left on their defaults.
answered Mar 12 '18 at 22:39
Syntax ErrorSyntax Error
16212
answered Mar 12 '18 at 22:39
Syntax ErrorSyntax Error
16212
answered Mar 12 '18 at 22:39
Syntax ErrorSyntax Error
16212
answered Mar 12 '18 at 22:39
Syntax ErrorSyntax Error
16212
16212
add a comment |
add a comment |
This might not help but I solved it by turning down the resolution. The problem occured as the monitor I was connecting from was 2560x1440, and the remote computer wouldn't allow that. Turning it down to 1920x1080 worked fine and I am now connected with everything showing.
answered Oct 29 '18 at 12:30
UnknownUnknown
1
add a comment |
This might not help but I solved it by turning down the resolution. The problem occured as the monitor I was connecting from was 2560x1440, and the remote computer wouldn't allow that. Turning it down to 1920x1080 worked fine and I am now connected with everything showing.
answered Oct 29 '18 at 12:30
UnknownUnknown
1
add a comment |
This might not help but I solved it by turning down the resolution. The problem occured as the monitor I was connecting from was 2560x1440, and the remote computer wouldn't allow that. Turning it down to 1920x1080 worked fine and I am now connected with everything showing.
answered Oct 29 '18 at 12:30
UnknownUnknown
1
This might not help but I solved it by turning down the resolution. The problem occured as the monitor I was connecting from was 2560x1440, and the remote computer wouldn't allow that. Turning it down to 1920x1080 worked fine and I am now connected with everything showing.
answered Oct 29 '18 at 12:30
UnknownUnknown
1
answered Oct 29 '18 at 12:30
UnknownUnknown
1
answered Oct 29 '18 at 12:30
UnknownUnknown
1
answered Oct 29 '18 at 12:30
UnknownUnknown
1
1
add a comment |
add a comment |
I had this issue since I was having different DPI. On my laptop I had DPI set to 125% while a computer I was connecting had 100%. Setting DPI to 100% on laptop solved the problem.
answered 11 mins ago
Stanislav BerkovStanislav Berkov
1012
New contributor
Stanislav Berkov is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I had this issue since I was having different DPI. On my laptop I had DPI set to 125% while a computer I was connecting had 100%. Setting DPI to 100% on laptop solved the problem.
answered 11 mins ago
Stanislav BerkovStanislav Berkov
1012
New contributor
Stanislav Berkov is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I had this issue since I was having different DPI. On my laptop I had DPI set to 125% while a computer I was connecting had 100%. Setting DPI to 100% on laptop solved the problem.
answered 11 mins ago
Stanislav BerkovStanislav Berkov
1012
New contributor
Stanislav Berkov is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I had this issue since I was having different DPI. On my laptop I had DPI set to 125% while a computer I was connecting had 100%. Setting DPI to 100% on laptop solved the problem.
answered 11 mins ago
Stanislav BerkovStanislav Berkov
1012
New contributor
Stanislav Berkov is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 11 mins ago
Stanislav BerkovStanislav Berkov
1012
New contributor
Stanislav Berkov is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 11 mins ago
Stanislav BerkovStanislav Berkov
1012
answered 11 mins ago
Stanislav BerkovStanislav Berkov
1012
1012
New contributor
Stanislav Berkov is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Stanislav Berkov is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Stanislav Berkov is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f976290%2fwindows-10-remote-desktop-connects-with-black-screen-then-disconnects%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is it the client or the server that you reboot that fixes the problem?
– cdavid
Sep 21 '15 at 23:22
Have you tried using a VPN and not exposing 3389 to the WAN?
– Linef4ult
Sep 22 '15 at 5:36
Me too. It's not this - tenforums.com/network-sharing/… because I have passwords on all the accounts, and it does the same thing regardless of local console connections status.
– nerdfever.com
Jan 9 '16 at 20:04
I have been experiencing this issue with server 2012 R2, and while the issue may not be related, the symptoms are very similar. Black screen and rebooting the server fixed it for a while. I don't have an answer, but I have it linked to TermService service crashing, despite not much in the logs indicating it. TermService is unusual since it can't be stopped via services.msc, but you can use
tasklist /svc | findstr /C:TermServiceto identify the Process ID andtaskkill /F /PID [process_id]to end the process. Start TermService usingnet start TermService. I am still working on a solution.– Johnny Keeton
Aug 24 '16 at 2:03
1
@Todilo See my answer below.
– Syntax Error
Mar 12 '18 at 22:39