the update could be failed, or windows is hanging before the restart and pending for an action..
Unfortunately there is no simple method to test this if you don't have a local access on the PC.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
i have a problem. I restarted a pc remotely because it had a windows feature update, from 1803 to 1809. RIght now it has been over 3 hours and yet i can't connect to the pc through rpd. For some reasons, i can ping it from console and i can connect to his shared folder //namepc.
WIth the covid19 problems, i can't go to the office and restart it so right now the person that should use it is blocked. Does anyone know of a method to restart again the pc or to restart at least the RDP service? This is really a huge problem.
Thank you.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
the update could be failed, or windows is hanging before the restart and pending for an action..
Unfortunately there is no simple method to test this if you don't have a local access on the PC.
Hello lexpert, my name is Farah and I'm an Independent Adviser. I can help you regarding this problem
is this machine a part of a domain environment?
if yes, open services from your device by typing "services.msc" in start menu and hit enter
you"ll see on the top left Services (local) right click on it and choose connect to another computer, enter the FQDN of the other PC "PC name" and try to open it.
Once yo have achieved the connection, try to restart RDP service.
I think though that it's not related to the rdp service. instead the security enhancements in the newer build has stopped the connection from none authorized pcs or users
Anyway please try this and give me a feedback
Cheers!
Farah
With the ip it gives to me the same error message. The other person on the pc has the domain account. He is trying to access through RDP. There is also a local account but both should not start. I was wondering if by any chance the pc is still restarting or something like that. But still at this point i think it has been more than 3 hours from the start of the feature update. From 1803 to 1809.
Hello again,
try connecting using the IP address,
once more to understand the issue.. does the other person, have local access to the PC were you installed the update? it could be that the device has not yet restarted..
Hi Farah,
yes the pc is in a domain enviroment. What is the FQDN name? I insertend "namepc.namedomain" that is the full name of the pc and it said to me "error1722 the rpc server is unavailable".
Also about the enanched security, the person still can't connect from his pc. He used this pc to connect to the pc in the domain. So i am not sure if this is the issue.