I just get a black screen remoting (RDP) into Windows 8 box
When I remote into my Windows 8 desktop with Windows 7 it works fine but when try with Windows 8 I get an empty screen after it connects. Keyboard commands work despite the screen being black; I can open Explorer etc. using them and they persist when I reconnect with Windows 7.
Any ideas on what is wrong?
windows-8 remote-desktop
asked Dec 24 '12 at 18:50
MichaelMichael
2031315
add a comment |
When I remote into my Windows 8 desktop with Windows 7 it works fine but when try with Windows 8 I get an empty screen after it connects. Keyboard commands work despite the screen being black; I can open Explorer etc. using them and they persist when I reconnect with Windows 7.
Any ideas on what is wrong?
windows-8 remote-desktop
asked Dec 24 '12 at 18:50
MichaelMichael
2031315
Have you fully patched both computers including option updates? (RDP version 8.0 has come out several weeks ago on Windows 7 and maybe also on 8).
– harrymc
Jan 10 '13 at 15:06
In addition to @harrymc's suggestion, take a look at the source Win8 RDP settings. Also, are the source (Win7 and Win8) hosts on the same LAN as the target Win8, and the NIC and Comms port speeds verified OK? Lastly, try different NIC ports for the source hosts on your switch.
– Lizz
Jan 11 '13 at 6:35
Does changing the Windows 8 theme have any effect? On the Experience tab for Remote Desktop Connection, what happens if you connect choosing Modem (28.8 Kbps) and deselect Bitmap Caching?
– user314104
Jul 30 '13 at 1:13
add a comment |
When I remote into my Windows 8 desktop with Windows 7 it works fine but when try with Windows 8 I get an empty screen after it connects. Keyboard commands work despite the screen being black; I can open Explorer etc. using them and they persist when I reconnect with Windows 7.
Any ideas on what is wrong?
windows-8 remote-desktop
asked Dec 24 '12 at 18:50
MichaelMichael
2031315
When I remote into my Windows 8 desktop with Windows 7 it works fine but when try with Windows 8 I get an empty screen after it connects. Keyboard commands work despite the screen being black; I can open Explorer etc. using them and they persist when I reconnect with Windows 7.
Any ideas on what is wrong?
windows-8 remote-desktop
windows-8 remote-desktop
asked Dec 24 '12 at 18:50
MichaelMichael
2031315
asked Dec 24 '12 at 18:50
MichaelMichael
2031315
asked Dec 24 '12 at 18:50
MichaelMichael
2031315
asked Dec 24 '12 at 18:50
MichaelMichael
2031315
asked Dec 24 '12 at 18:50
MichaelMichael
2031315
2031315
Have you fully patched both computers including option updates? (RDP version 8.0 has come out several weeks ago on Windows 7 and maybe also on 8).
– harrymc
Jan 10 '13 at 15:06
In addition to @harrymc's suggestion, take a look at the source Win8 RDP settings. Also, are the source (Win7 and Win8) hosts on the same LAN as the target Win8, and the NIC and Comms port speeds verified OK? Lastly, try different NIC ports for the source hosts on your switch.
– Lizz
Jan 11 '13 at 6:35
Does changing the Windows 8 theme have any effect? On the Experience tab for Remote Desktop Connection, what happens if you connect choosing Modem (28.8 Kbps) and deselect Bitmap Caching?
– user314104
Jul 30 '13 at 1:13
add a comment |
Have you fully patched both computers including option updates? (RDP version 8.0 has come out several weeks ago on Windows 7 and maybe also on 8).
– harrymc
Jan 10 '13 at 15:06
In addition to @harrymc's suggestion, take a look at the source Win8 RDP settings. Also, are the source (Win7 and Win8) hosts on the same LAN as the target Win8, and the NIC and Comms port speeds verified OK? Lastly, try different NIC ports for the source hosts on your switch.
– Lizz
Jan 11 '13 at 6:35
Does changing the Windows 8 theme have any effect? On the Experience tab for Remote Desktop Connection, what happens if you connect choosing Modem (28.8 Kbps) and deselect Bitmap Caching?
– user314104
Jul 30 '13 at 1:13
Have you fully patched both computers including option updates? (RDP version 8.0 has come out several weeks ago on Windows 7 and maybe also on 8).
– harrymc
Jan 10 '13 at 15:06
Have you fully patched both computers including option updates? (RDP version 8.0 has come out several weeks ago on Windows 7 and maybe also on 8).
– harrymc
Jan 10 '13 at 15:06
In addition to @harrymc's suggestion, take a look at the source Win8 RDP settings. Also, are the source (Win7 and Win8) hosts on the same LAN as the target Win8, and the NIC and Comms port speeds verified OK? Lastly, try different NIC ports for the source hosts on your switch.
– Lizz
Jan 11 '13 at 6:35
In addition to @harrymc's suggestion, take a look at the source Win8 RDP settings. Also, are the source (Win7 and Win8) hosts on the same LAN as the target Win8, and the NIC and Comms port speeds verified OK? Lastly, try different NIC ports for the source hosts on your switch.
– Lizz
Jan 11 '13 at 6:35
Does changing the Windows 8 theme have any effect? On the Experience tab for Remote Desktop Connection, what happens if you connect choosing Modem (28.8 Kbps) and deselect Bitmap Caching?
– user314104
Jul 30 '13 at 1:13
Does changing the Windows 8 theme have any effect? On the Experience tab for Remote Desktop Connection, what happens if you connect choosing Modem (28.8 Kbps) and deselect Bitmap Caching?
– user314104
Jul 30 '13 at 1:13
add a comment |
3 Answers
3
active
oldest
votes
This Technet thread suggests:
- Type Ctrl + Alt + End
- Then cancel
- Then exiting and reconnecting
You could also try disabling bitmap caching using this KB article.
edited Jun 17 '15 at 12:28
Jeroen
89951743
answered Jan 12 '13 at 15:59
K.AK.A
5,41221132
Ctrl+Alt+End worked for me, it brought up the Options where I could start the Task Manager and then could tab to other windows. I found out that I had left Firefox in fullscreen mode, and it was not refreshing, causing the black screen.
– user1113270
Aug 20 '15 at 15:33
add a comment |
Open the Local Group Policy Editor on the machine you are running the Remote Desktop client.
Under Computer Configuration>Administrative Templates>Windows Components>Remote Desktop Services?Remote Desktop Connection Client
Enable the setting called Turn Off UDP On Client
Now I'm able to connect without issue... somehow UDP isn't making it through and this change fixes the problem!
Should anyone wish to change the setting from registry rather than through group policy, here's the place to do that:
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient
Createset fClientDisableUDP (REG_DWORD) to 1.
PS> Set-ItemProperty -Path 'HKLM:SOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient' -Name fClientDisableUDP -Value 1
edited Feb 9 at 0:18
Ƭᴇcʜιᴇ007
99.8k14158221
answered Jan 15 '14 at 14:01
MichaelMichael
2031315
add a comment |
I spent hours diagnosing this issue, "Turn Off UDP On Client" works around it for me also.
Turns out our office Draytek 2820 has a UDP flood DoS attack trigger which was set to 300 packets / second. Upping to 1000 packets per second resolves this for me.
answered Jul 10 '14 at 20:22
Andrew EdwardsAndrew Edwards
1
Yes it does. "Any idea what is wrong?" Yes. My router UDP flood attack was false triggering. Exactly the same symptoms and that fixed it. This answers the question.
– Andrew Edwards
Jul 13 '14 at 12:21
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%2f523808%2fi-just-get-a-black-screen-remoting-rdp-into-windows-8-box%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
This Technet thread suggests:
- Type Ctrl + Alt + End
- Then cancel
- Then exiting and reconnecting
You could also try disabling bitmap caching using this KB article.
edited Jun 17 '15 at 12:28
Jeroen
89951743
answered Jan 12 '13 at 15:59
K.AK.A
5,41221132
Ctrl+Alt+End worked for me, it brought up the Options where I could start the Task Manager and then could tab to other windows. I found out that I had left Firefox in fullscreen mode, and it was not refreshing, causing the black screen.
– user1113270
Aug 20 '15 at 15:33
add a comment |
This Technet thread suggests:
- Type Ctrl + Alt + End
- Then cancel
- Then exiting and reconnecting
You could also try disabling bitmap caching using this KB article.
edited Jun 17 '15 at 12:28
Jeroen
89951743
answered Jan 12 '13 at 15:59
K.AK.A
5,41221132
Ctrl+Alt+End worked for me, it brought up the Options where I could start the Task Manager and then could tab to other windows. I found out that I had left Firefox in fullscreen mode, and it was not refreshing, causing the black screen.
– user1113270
Aug 20 '15 at 15:33
add a comment |
This Technet thread suggests:
- Type Ctrl + Alt + End
- Then cancel
- Then exiting and reconnecting
You could also try disabling bitmap caching using this KB article.
edited Jun 17 '15 at 12:28
Jeroen
89951743
answered Jan 12 '13 at 15:59
K.AK.A
5,41221132
This Technet thread suggests:
- Type Ctrl + Alt + End
- Then cancel
- Then exiting and reconnecting
You could also try disabling bitmap caching using this KB article.
edited Jun 17 '15 at 12:28
Jeroen
89951743
answered Jan 12 '13 at 15:59
K.AK.A
5,41221132
edited Jun 17 '15 at 12:28
Jeroen
89951743
edited Jun 17 '15 at 12:28
Jeroen
89951743
edited Jun 17 '15 at 12:28
Jeroen
89951743
89951743
answered Jan 12 '13 at 15:59
K.AK.A
5,41221132
answered Jan 12 '13 at 15:59
K.AK.A
5,41221132
answered Jan 12 '13 at 15:59
K.AK.A
5,41221132
5,41221132
Ctrl+Alt+End worked for me, it brought up the Options where I could start the Task Manager and then could tab to other windows. I found out that I had left Firefox in fullscreen mode, and it was not refreshing, causing the black screen.
– user1113270
Aug 20 '15 at 15:33
add a comment |
Ctrl+Alt+End worked for me, it brought up the Options where I could start the Task Manager and then could tab to other windows. I found out that I had left Firefox in fullscreen mode, and it was not refreshing, causing the black screen.
– user1113270
Aug 20 '15 at 15:33
Ctrl+Alt+End worked for me, it brought up the Options where I could start the Task Manager and then could tab to other windows. I found out that I had left Firefox in fullscreen mode, and it was not refreshing, causing the black screen.
– user1113270
Aug 20 '15 at 15:33
Ctrl+Alt+End worked for me, it brought up the Options where I could start the Task Manager and then could tab to other windows. I found out that I had left Firefox in fullscreen mode, and it was not refreshing, causing the black screen.
– user1113270
Aug 20 '15 at 15:33
add a comment |
Open the Local Group Policy Editor on the machine you are running the Remote Desktop client.
Under Computer Configuration>Administrative Templates>Windows Components>Remote Desktop Services?Remote Desktop Connection Client
Enable the setting called Turn Off UDP On Client
Now I'm able to connect without issue... somehow UDP isn't making it through and this change fixes the problem!
Should anyone wish to change the setting from registry rather than through group policy, here's the place to do that:
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient
Createset fClientDisableUDP (REG_DWORD) to 1.
PS> Set-ItemProperty -Path 'HKLM:SOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient' -Name fClientDisableUDP -Value 1
edited Feb 9 at 0:18
Ƭᴇcʜιᴇ007
99.8k14158221
answered Jan 15 '14 at 14:01
MichaelMichael
2031315
add a comment |
Open the Local Group Policy Editor on the machine you are running the Remote Desktop client.
Under Computer Configuration>Administrative Templates>Windows Components>Remote Desktop Services?Remote Desktop Connection Client
Enable the setting called Turn Off UDP On Client
Now I'm able to connect without issue... somehow UDP isn't making it through and this change fixes the problem!
Should anyone wish to change the setting from registry rather than through group policy, here's the place to do that:
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient
Createset fClientDisableUDP (REG_DWORD) to 1.
PS> Set-ItemProperty -Path 'HKLM:SOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient' -Name fClientDisableUDP -Value 1
edited Feb 9 at 0:18
Ƭᴇcʜιᴇ007
99.8k14158221
answered Jan 15 '14 at 14:01
MichaelMichael
2031315
add a comment |
Open the Local Group Policy Editor on the machine you are running the Remote Desktop client.
Under Computer Configuration>Administrative Templates>Windows Components>Remote Desktop Services?Remote Desktop Connection Client
Enable the setting called Turn Off UDP On Client
Now I'm able to connect without issue... somehow UDP isn't making it through and this change fixes the problem!
Should anyone wish to change the setting from registry rather than through group policy, here's the place to do that:
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient
Createset fClientDisableUDP (REG_DWORD) to 1.
PS> Set-ItemProperty -Path 'HKLM:SOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient' -Name fClientDisableUDP -Value 1
edited Feb 9 at 0:18
Ƭᴇcʜιᴇ007
99.8k14158221
answered Jan 15 '14 at 14:01
MichaelMichael
2031315
Open the Local Group Policy Editor on the machine you are running the Remote Desktop client.
Under Computer Configuration>Administrative Templates>Windows Components>Remote Desktop Services?Remote Desktop Connection Client
Enable the setting called Turn Off UDP On Client
Now I'm able to connect without issue... somehow UDP isn't making it through and this change fixes the problem!
Should anyone wish to change the setting from registry rather than through group policy, here's the place to do that:
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient
Createset fClientDisableUDP (REG_DWORD) to 1.
PS> Set-ItemProperty -Path 'HKLM:SOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient' -Name fClientDisableUDP -Value 1
edited Feb 9 at 0:18
Ƭᴇcʜιᴇ007
99.8k14158221
answered Jan 15 '14 at 14:01
MichaelMichael
2031315
edited Feb 9 at 0:18
Ƭᴇcʜιᴇ007
99.8k14158221
edited Feb 9 at 0:18
Ƭᴇcʜιᴇ007
99.8k14158221
edited Feb 9 at 0:18
Ƭᴇcʜιᴇ007
99.8k14158221
99.8k14158221
answered Jan 15 '14 at 14:01
MichaelMichael
2031315
answered Jan 15 '14 at 14:01
MichaelMichael
2031315
answered Jan 15 '14 at 14:01
MichaelMichael
2031315
2031315
add a comment |
add a comment |
I spent hours diagnosing this issue, "Turn Off UDP On Client" works around it for me also.
Turns out our office Draytek 2820 has a UDP flood DoS attack trigger which was set to 300 packets / second. Upping to 1000 packets per second resolves this for me.
answered Jul 10 '14 at 20:22
Andrew EdwardsAndrew Edwards
1
Yes it does. "Any idea what is wrong?" Yes. My router UDP flood attack was false triggering. Exactly the same symptoms and that fixed it. This answers the question.
– Andrew Edwards
Jul 13 '14 at 12:21
add a comment |
I spent hours diagnosing this issue, "Turn Off UDP On Client" works around it for me also.
Turns out our office Draytek 2820 has a UDP flood DoS attack trigger which was set to 300 packets / second. Upping to 1000 packets per second resolves this for me.
answered Jul 10 '14 at 20:22
Andrew EdwardsAndrew Edwards
1
Yes it does. "Any idea what is wrong?" Yes. My router UDP flood attack was false triggering. Exactly the same symptoms and that fixed it. This answers the question.
– Andrew Edwards
Jul 13 '14 at 12:21
add a comment |
I spent hours diagnosing this issue, "Turn Off UDP On Client" works around it for me also.
Turns out our office Draytek 2820 has a UDP flood DoS attack trigger which was set to 300 packets / second. Upping to 1000 packets per second resolves this for me.
answered Jul 10 '14 at 20:22
Andrew EdwardsAndrew Edwards
1
I spent hours diagnosing this issue, "Turn Off UDP On Client" works around it for me also.
Turns out our office Draytek 2820 has a UDP flood DoS attack trigger which was set to 300 packets / second. Upping to 1000 packets per second resolves this for me.
answered Jul 10 '14 at 20:22
Andrew EdwardsAndrew Edwards
1
answered Jul 10 '14 at 20:22
Andrew EdwardsAndrew Edwards
1
answered Jul 10 '14 at 20:22
Andrew EdwardsAndrew Edwards
1
answered Jul 10 '14 at 20:22
Andrew EdwardsAndrew Edwards
1
1
Yes it does. "Any idea what is wrong?" Yes. My router UDP flood attack was false triggering. Exactly the same symptoms and that fixed it. This answers the question.
– Andrew Edwards
Jul 13 '14 at 12:21
add a comment |
Yes it does. "Any idea what is wrong?" Yes. My router UDP flood attack was false triggering. Exactly the same symptoms and that fixed it. This answers the question.
– Andrew Edwards
Jul 13 '14 at 12:21
Yes it does. "Any idea what is wrong?" Yes. My router UDP flood attack was false triggering. Exactly the same symptoms and that fixed it. This answers the question.
– Andrew Edwards
Jul 13 '14 at 12:21
Yes it does. "Any idea what is wrong?" Yes. My router UDP flood attack was false triggering. Exactly the same symptoms and that fixed it. This answers the question.
– Andrew Edwards
Jul 13 '14 at 12:21
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%2f523808%2fi-just-get-a-black-screen-remoting-rdp-into-windows-8-box%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
Have you fully patched both computers including option updates? (RDP version 8.0 has come out several weeks ago on Windows 7 and maybe also on 8).
– harrymc
Jan 10 '13 at 15:06
In addition to @harrymc's suggestion, take a look at the source Win8 RDP settings. Also, are the source (Win7 and Win8) hosts on the same LAN as the target Win8, and the NIC and Comms port speeds verified OK? Lastly, try different NIC ports for the source hosts on your switch.
– Lizz
Jan 11 '13 at 6:35
Does changing the Windows 8 theme have any effect? On the Experience tab for Remote Desktop Connection, what happens if you connect choosing Modem (28.8 Kbps) and deselect Bitmap Caching?
– user314104
Jul 30 '13 at 1:13