Windows 10: After RDP connection, the system cannot enter and only solved by rebooting

Discus and support After RDP connection, the system cannot enter and only solved by rebooting in Windows 10 Software and Apps to solve the problem; After closing the RDP connection, the connected system breakdown, and can only use after rebooting.... Discussion in 'Windows 10 Software and Apps' started by HaoJING1, Aug 9, 2022.

  1. HaoJING1 Win User

    After RDP connection, the system cannot enter and only solved by rebooting


    After closing the RDP connection, the connected system breakdown, and can only use after rebooting.

    :)
     
    HaoJING1, Aug 9, 2022
    #1
  2. JLJones Win User

    Solved

    Solved! or fixed! or whatever! I was able to absorb the extra space in a 3-step process:

    1. resize the System Reserved partition to use the space after it
    2. reboot
    3. stretch the M: data partition to absorb the space after it using the EXTEND -- not RESIZE -- command
    System rebooted and working normally. THX all.
     
    JLJones, Aug 9, 2022
    #2
  3. Arctucas Win User
    mobo/case connection

    Type LIST DISK

    press Enter

    (There are going to be several steps, so let me know when you do them, OK?)
     
    Arctucas, Aug 9, 2022
    #3
  4. Billzden Win User

    After RDP connection, the system cannot enter and only solved by rebooting

    RDP and Network Connection Drops While on Ethernet

    I have the following setup:

    2 x windows 10 and 1 X windows 7 computers connected to the same router through cable having 192.168.0.1 as the router gateway.

    win7-box: 192.168.0.38
    win10-box1: 192.168.0.211
    win10-box2: 192.168.0.24

    I am connecting from win7-box, which I'm using as the main machine, through RDP to the other 2 win10 machines.

    The connection to 192.168.0.211 runs smoothly but when I connect to 192.168.0.24, the connection gets interrupted after 30-60 seconds and I get the "This computer can't connect to the remote computer" error:


    After RDP connection, the system cannot enter and only solved by rebooting [​IMG]


    While ping 192.168.0.24 -t from 192.168.0.38 was running I got this:


    After RDP connection, the system cannot enter and only solved by rebooting [​IMG]


    Even if after the The connection has been lost error that corresponds to the Request timed out ping error - the connection seems to be restored (as ping is up again), if I try to RDP again I get the "Destination host unreachable" error.


    After RDP connection, the system cannot enter and only solved by rebooting [​IMG]


    Now I cannot RDP to 192.168.0.24 anymore until I manually log into this host by physically using its keyboard.

    I also did a ping 192.168.0.1 -t on 192.168.0.24 and noticed the General Failure error that corresponds to the Request timed out from the win7-box

    enter image description here

    I also noticed that I get the General Failure error intermittently, even if don't try a RDP connection on this win10-box2 machine.

    What I did:

    I tried a Network Reset from the Network&Internet settings:

    After RDP connection, the system cannot enter and only solved by rebooting [​IMG]


    • Tried switching the cable itself and the cable port on the router
    • Tried using a different static ip, other than 192.168.0.24
    • Tried using the wireless connection to the same router and noticed that even if do get some isolated Request timed out error when continuously pinging win10-box's ip, no issues are found and RDP connection is stable.

    I assume this has to be something wrong in my current win10-box2 configuration as the router seems to be working fine on other devices.

    The network configuration on win10-box2 is as follows:


    After RDP connection, the system cannot enter and only solved by rebooting [​IMG]


    The question would be - what else should I try/check in order to solve this issue?
     
    Billzden, Aug 9, 2022
    #4
Thema:

After RDP connection, the system cannot enter and only solved by rebooting

Loading...
  1. After RDP connection, the system cannot enter and only solved by rebooting - Similar Threads - RDP connection system

  2. RDP connection Problem. Only Domain computers don't connect.

    in Windows 10 Gaming
    RDP connection Problem. Only Domain computers don't connect.: Windows 10 Pro, 22H2. This is a RDP problem.I can connect to another computer in a different state using RDP. However, once this same computer joins the company Domain it will not connect.I get the message that the credentials don't work. It didn't help removing the computer...
  3. RDP connection Problem. Only Domain computers don't connect.

    in Windows 10 Software and Apps
    RDP connection Problem. Only Domain computers don't connect.: Windows 10 Pro, 22H2. This is a RDP problem.I can connect to another computer in a different state using RDP. However, once this same computer joins the company Domain it will not connect.I get the message that the credentials don't work. It didn't help removing the computer...
  4. RDP connection Problem. Only Domain computers don't connect.

    in Windows 10 Network and Sharing
    RDP connection Problem. Only Domain computers don't connect.: Windows 10 Pro, 22H2. This is a RDP problem.I can connect to another computer in a different state using RDP. However, once this same computer joins the company Domain it will not connect.I get the message that the credentials don't work. It didn't help removing the computer...
  5. After RDP connection, the system cannot enter and only solved by rebooting

    in Windows 10 Gaming
    After RDP connection, the system cannot enter and only solved by rebooting: After closing the RDP connection, the connected system breakdown, and can only use after rebooting. https://answers.microsoft.com/en-us/windows/forum/all/after-rdp-connection-the-system-cannot-enter-and/6d85766e-c0f3-4336-a111-bd492efdcfbf
  6. WSL Ubuntu-20.04: RDP Connection terminates after entering user credentials

    in Windows 10 Gaming
    WSL Ubuntu-20.04: RDP Connection terminates after entering user credentials: Hi,I'm using WSL with distribution Ubuntu-20.04 and need RDP access to the ubuntu desktop from my windows 10 enterprise, Build 19043.$ sudo /etc/init.d/xrdp status * xrdp-sesman is running * xrdp is running After establishing a RDP Connection from Windows 10 "Remote Desktop"...
  7. WSL Ubuntu-20.04: RDP Connection terminates after entering user credentials

    in Windows 10 Software and Apps
    WSL Ubuntu-20.04: RDP Connection terminates after entering user credentials: Hi,I'm using WSL with distribution Ubuntu-20.04 and need RDP access to the ubuntu desktop from my windows 10 enterprise, Build 19043.$ sudo /etc/init.d/xrdp status * xrdp-sesman is running * xrdp is running After establishing a RDP Connection from Windows 10 "Remote Desktop"...
  8. WSL Ubuntu-20.04: RDP Connection terminates after entering user credentials

    in Windows 10 Customization
    WSL Ubuntu-20.04: RDP Connection terminates after entering user credentials: Hi,I'm using WSL with distribution Ubuntu-20.04 and need RDP access to the ubuntu desktop from my windows 10 enterprise, Build 19043.$ sudo /etc/init.d/xrdp status * xrdp-sesman is running * xrdp is running After establishing a RDP Connection from Windows 10 "Remote Desktop"...
  9. Internet will only connect after reboot

    in Windows 10 Network and Sharing
    Internet will only connect after reboot: For the last few weeks I have had a strange problem. As long as the computer boots, it won't connect to the Internet whatever I do, but when I restart the computer, the Internet connection is fine. I am confused why this is happening and it is quite annoying. I am using an...
  10. Cannot connect via RDP to VM after kb4512508

    in Windows 10 BSOD Crashes and Debugging
    Cannot connect via RDP to VM after kb4512508: Hello, Recently I installed kb4512508 on a Windows 10 Pro. This machine is virtual machine on Hyper-V. After installing the update the machine has frozen. Connecting through RDP or console via Hyper-V was not possible anymore. I turned off the VM and restarted it through...