RDP to Windows 7 is stuck on Welcome screen after wake-on-lan from sleep
up vote
0
down vote
favorite
I am trying to set up wake-on-lan for my office desktop (Windows 7 Enterprise). I want it to sleep when I am not there, unless I wake it up remotely and use it in a remote desktop session. Things initially work ok out of the box (no changes in BIOS or network adapter): if the desktop sleeps, my RDP session wakes it up (it beeps), then I can enter my password. However at this moment the RDP session stays stuck on the welcome screen, forever:
This happens both for reconnecting to existing sessions or for logging in as a new session. Things only get unstuck and the RDP session wakes up completely when I move the mouse (the desktop's own physical mouse , not the mouse on the remote client - I am testing this from a laptop in the same room, so I have physical access to the desktop). Any idea what I should do to make the desktop wake up completely even when I have no physical access to it?
windows-7 remote-desktop sleep wake-on-lan hybrid-sleep
asked May 12 '14 at 14:09
A V
5115
add a comment |
up vote
0
down vote
favorite
I am trying to set up wake-on-lan for my office desktop (Windows 7 Enterprise). I want it to sleep when I am not there, unless I wake it up remotely and use it in a remote desktop session. Things initially work ok out of the box (no changes in BIOS or network adapter): if the desktop sleeps, my RDP session wakes it up (it beeps), then I can enter my password. However at this moment the RDP session stays stuck on the welcome screen, forever:
This happens both for reconnecting to existing sessions or for logging in as a new session. Things only get unstuck and the RDP session wakes up completely when I move the mouse (the desktop's own physical mouse , not the mouse on the remote client - I am testing this from a laptop in the same room, so I have physical access to the desktop). Any idea what I should do to make the desktop wake up completely even when I have no physical access to it?
windows-7 remote-desktop sleep wake-on-lan hybrid-sleep
asked May 12 '14 at 14:09
A V
5115
If nothing helps and even Restart-Computer powershell cmdlet not works, you can try to restart the computer using WMI in powershell: Invoke-WmiMethod -ComputerName COMPUTER_IP -Credential (Get-Credential) -Class Win32_Process -Name Create -ArgumentList "shutdown -r -f -t 0" . BTW, Jessica's solution didn't help in my situation (IDK what really happened with my computer), but forced reboot solved the problem.
– 2xMax
Jul 1 '14 at 22:24
This may be related to the USB suspend state of your USB devices or hubs...
– Kinnectus
Mar 11 '16 at 18:14
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am trying to set up wake-on-lan for my office desktop (Windows 7 Enterprise). I want it to sleep when I am not there, unless I wake it up remotely and use it in a remote desktop session. Things initially work ok out of the box (no changes in BIOS or network adapter): if the desktop sleeps, my RDP session wakes it up (it beeps), then I can enter my password. However at this moment the RDP session stays stuck on the welcome screen, forever:
This happens both for reconnecting to existing sessions or for logging in as a new session. Things only get unstuck and the RDP session wakes up completely when I move the mouse (the desktop's own physical mouse , not the mouse on the remote client - I am testing this from a laptop in the same room, so I have physical access to the desktop). Any idea what I should do to make the desktop wake up completely even when I have no physical access to it?
windows-7 remote-desktop sleep wake-on-lan hybrid-sleep
asked May 12 '14 at 14:09
A V
5115
I am trying to set up wake-on-lan for my office desktop (Windows 7 Enterprise). I want it to sleep when I am not there, unless I wake it up remotely and use it in a remote desktop session. Things initially work ok out of the box (no changes in BIOS or network adapter): if the desktop sleeps, my RDP session wakes it up (it beeps), then I can enter my password. However at this moment the RDP session stays stuck on the welcome screen, forever:
This happens both for reconnecting to existing sessions or for logging in as a new session. Things only get unstuck and the RDP session wakes up completely when I move the mouse (the desktop's own physical mouse , not the mouse on the remote client - I am testing this from a laptop in the same room, so I have physical access to the desktop). Any idea what I should do to make the desktop wake up completely even when I have no physical access to it?
windows-7 remote-desktop sleep wake-on-lan hybrid-sleep
windows-7 remote-desktop sleep wake-on-lan hybrid-sleep
asked May 12 '14 at 14:09
A V
5115
asked May 12 '14 at 14:09
A V
5115
asked May 12 '14 at 14:09
A V
5115
asked May 12 '14 at 14:09
A V
5115
asked May 12 '14 at 14:09
A V
5115
5115
If nothing helps and even Restart-Computer powershell cmdlet not works, you can try to restart the computer using WMI in powershell: Invoke-WmiMethod -ComputerName COMPUTER_IP -Credential (Get-Credential) -Class Win32_Process -Name Create -ArgumentList "shutdown -r -f -t 0" . BTW, Jessica's solution didn't help in my situation (IDK what really happened with my computer), but forced reboot solved the problem.
– 2xMax
Jul 1 '14 at 22:24
This may be related to the USB suspend state of your USB devices or hubs...
– Kinnectus
Mar 11 '16 at 18:14
add a comment |
If nothing helps and even Restart-Computer powershell cmdlet not works, you can try to restart the computer using WMI in powershell: Invoke-WmiMethod -ComputerName COMPUTER_IP -Credential (Get-Credential) -Class Win32_Process -Name Create -ArgumentList "shutdown -r -f -t 0" . BTW, Jessica's solution didn't help in my situation (IDK what really happened with my computer), but forced reboot solved the problem.
– 2xMax
Jul 1 '14 at 22:24
This may be related to the USB suspend state of your USB devices or hubs...
– Kinnectus
Mar 11 '16 at 18:14
If nothing helps and even Restart-Computer powershell cmdlet not works, you can try to restart the computer using WMI in powershell: Invoke-WmiMethod -ComputerName COMPUTER_IP -Credential (Get-Credential) -Class Win32_Process -Name Create -ArgumentList "shutdown -r -f -t 0" . BTW, Jessica's solution didn't help in my situation (IDK what really happened with my computer), but forced reboot solved the problem.
– 2xMax
Jul 1 '14 at 22:24
If nothing helps and even Restart-Computer powershell cmdlet not works, you can try to restart the computer using WMI in powershell: Invoke-WmiMethod -ComputerName COMPUTER_IP -Credential (Get-Credential) -Class Win32_Process -Name Create -ArgumentList "shutdown -r -f -t 0" . BTW, Jessica's solution didn't help in my situation (IDK what really happened with my computer), but forced reboot solved the problem.
– 2xMax
Jul 1 '14 at 22:24
This may be related to the USB suspend state of your USB devices or hubs...
– Kinnectus
Mar 11 '16 at 18:14
This may be related to the USB suspend state of your USB devices or hubs...
– Kinnectus
Mar 11 '16 at 18:14
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
I had this problem for years. After a lot of research and experimentation, I created the following script and it works for me and some of my colleagues...
Put the following in a text file and name it as .bat (like Release_RD.bat)
tasklist -s your_machine_name -fi "imagename eq mpnotify.exe"
set /p pid=Enter PID found above:
taskkill -s your_machine_name -pid %pid%
pause
If you aren't currently looking at the spinning Welcome screen, attempt to log in again so that your remote desktop client is actively on the Welcome screen
Double-click the .bat script and follow the directions in it. You might have to run the script twice if there are multiple mpnotify.exe processes.
If it works, the hung remote session will then proceed past the Welcome screen and you'll be logged in.
answered May 29 '14 at 0:45
Jessica
413
add a comment |
up vote
0
down vote
Would connecting as the console session help?
mstsc /admin
answered Mar 31 '17 at 1:24
KERR
25126
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',
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%2f752521%2frdp-to-windows-7-is-stuck-on-welcome-screen-after-wake-on-lan-from-sleep%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I had this problem for years. After a lot of research and experimentation, I created the following script and it works for me and some of my colleagues...
Put the following in a text file and name it as .bat (like Release_RD.bat)
tasklist -s your_machine_name -fi "imagename eq mpnotify.exe"
set /p pid=Enter PID found above:
taskkill -s your_machine_name -pid %pid%
pause
If you aren't currently looking at the spinning Welcome screen, attempt to log in again so that your remote desktop client is actively on the Welcome screen
Double-click the .bat script and follow the directions in it. You might have to run the script twice if there are multiple mpnotify.exe processes.
If it works, the hung remote session will then proceed past the Welcome screen and you'll be logged in.
answered May 29 '14 at 0:45
Jessica
413
add a comment |
up vote
0
down vote
I had this problem for years. After a lot of research and experimentation, I created the following script and it works for me and some of my colleagues...
Put the following in a text file and name it as .bat (like Release_RD.bat)
tasklist -s your_machine_name -fi "imagename eq mpnotify.exe"
set /p pid=Enter PID found above:
taskkill -s your_machine_name -pid %pid%
pause
If you aren't currently looking at the spinning Welcome screen, attempt to log in again so that your remote desktop client is actively on the Welcome screen
Double-click the .bat script and follow the directions in it. You might have to run the script twice if there are multiple mpnotify.exe processes.
If it works, the hung remote session will then proceed past the Welcome screen and you'll be logged in.
answered May 29 '14 at 0:45
Jessica
413
add a comment |
up vote
0
down vote
up vote
0
down vote
I had this problem for years. After a lot of research and experimentation, I created the following script and it works for me and some of my colleagues...
Put the following in a text file and name it as .bat (like Release_RD.bat)
tasklist -s your_machine_name -fi "imagename eq mpnotify.exe"
set /p pid=Enter PID found above:
taskkill -s your_machine_name -pid %pid%
pause
If you aren't currently looking at the spinning Welcome screen, attempt to log in again so that your remote desktop client is actively on the Welcome screen
Double-click the .bat script and follow the directions in it. You might have to run the script twice if there are multiple mpnotify.exe processes.
If it works, the hung remote session will then proceed past the Welcome screen and you'll be logged in.
answered May 29 '14 at 0:45
Jessica
413
I had this problem for years. After a lot of research and experimentation, I created the following script and it works for me and some of my colleagues...
Put the following in a text file and name it as .bat (like Release_RD.bat)
tasklist -s your_machine_name -fi "imagename eq mpnotify.exe"
set /p pid=Enter PID found above:
taskkill -s your_machine_name -pid %pid%
pause
If you aren't currently looking at the spinning Welcome screen, attempt to log in again so that your remote desktop client is actively on the Welcome screen
Double-click the .bat script and follow the directions in it. You might have to run the script twice if there are multiple mpnotify.exe processes.
If it works, the hung remote session will then proceed past the Welcome screen and you'll be logged in.
answered May 29 '14 at 0:45
Jessica
413
answered May 29 '14 at 0:45
Jessica
413
answered May 29 '14 at 0:45
Jessica
413
answered May 29 '14 at 0:45
Jessica
413
413
add a comment |
add a comment |
up vote
0
down vote
Would connecting as the console session help?
mstsc /admin
answered Mar 31 '17 at 1:24
KERR
25126
add a comment |
up vote
0
down vote
Would connecting as the console session help?
mstsc /admin
answered Mar 31 '17 at 1:24
KERR
25126
add a comment |
up vote
0
down vote
up vote
0
down vote
Would connecting as the console session help?
mstsc /admin
answered Mar 31 '17 at 1:24
KERR
25126
Would connecting as the console session help?
mstsc /admin
answered Mar 31 '17 at 1:24
KERR
25126
answered Mar 31 '17 at 1:24
KERR
25126
answered Mar 31 '17 at 1:24
KERR
25126
answered Mar 31 '17 at 1:24
KERR
25126
25126
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f752521%2frdp-to-windows-7-is-stuck-on-welcome-screen-after-wake-on-lan-from-sleep%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
If nothing helps and even Restart-Computer powershell cmdlet not works, you can try to restart the computer using WMI in powershell: Invoke-WmiMethod -ComputerName COMPUTER_IP -Credential (Get-Credential) -Class Win32_Process -Name Create -ArgumentList "shutdown -r -f -t 0" . BTW, Jessica's solution didn't help in my situation (IDK what really happened with my computer), but forced reboot solved the problem.
– 2xMax
Jul 1 '14 at 22:24
This may be related to the USB suspend state of your USB devices or hubs...
– Kinnectus
Mar 11 '16 at 18:14