Skip to main content

How to Reset a Stuck Remote Desktop Protocol (RDP) Session in Batch Script

Remote Desktop Protocol (RDP) sessions are generally stable, but occasionally they can freeze, hang on a black screen, or become unresponsive due to network glitches or application crashes. When this happens, simply disconnecting and reconnecting often doesn't solve the problem because the session state remains "stuck" on the server.

In this guide, we will learn how to forcefully reset a stuck RDP session using Batch Script commands. This method allows you to clear the problematic session without rebooting the entire server, saving time and preventing disruption for other users.

Understanding the Reset Command​

The primary command for resetting a session is rwinsta (Reset Window Station) or its alias reset session.

  • Disconnect (tsdiscon): Leaves programs running.
  • Logoff (logoff): Gracefully closes programs and signs out.
  • Reset (rwinsta): Forcefully terminates the session immediately. Any unsaved data in that session will be lost, similar to cutting power to a single computer.
danger

Warning: Resetting a session will cause the user to lose any unsaved work in that specific session. Use this only when the session is unresponsive and cannot be gracefully logged off.

Step 1: Identify the Stuck Session ID​

Before you can reset a session, you must know its Session ID. You can find this using the qwinsta (Query Window Station) or query session command.

Syntax:

qwinsta /server:<ServerName>

If you are running this on the server locally (or via a different admin RDP session on the same server), you don't need the /server switch.

Example Command:

qwinsta

Output:

 SESSIONNAME       USERNAME                 ID  STATE   TYPE        DEVICE
 services                                    0  Disc
 console                                     1  Conn
 rdp-tcp#0         bjones                    2  Active
 rdp-tcp#1         jsmith                    3  Active
 rdp-tcp                                 65536  Listen

In this case, if bjones (ID 2) is the stuck user, we need to remember the ID 2.

Step 2: Reset the Session​

Once you have the ID, use rwinsta to reset it.

Syntax:

rwinsta <SessionID> /server:<ServerName>

Example: To reset the session with ID 2 on the local server:

rwinsta 2

To reset session ID 4 on a remote server named FileServer01:

rwinsta 4 /server:FileServer01

Automating the Reset Process​

You can create a batch script to automate finding and resetting a user's session. This is useful for helpdesk scenarios where you want to quickly fix a specific user's frozen session.

Example Script: Reset by Username​

This script asks for a username and attempts to reset their session.

@echo off
setlocal EnableDelayedExpansion

:: Prompt for username
set /p "TargetUser=Enter username to reset: "

if "!TargetUser!"=="" (
    echo No username entered. Exiting.
    pause
    exit /b
)

echo Searching for sessions for user: !TargetUser! ...

:: Find the session ID for the user
:: qwinsta output columns: SESSIONNAME  USERNAME  ID  STATE
:: When SESSIONNAME is present (e.g., "rdp-tcp#1"), all columns are populated.
:: When SESSIONNAME is blank (e.g., disconnected sessions), columns shift left.
:: We grab enough tokens and test which one is the numeric Session ID.

set "FOUND="

for /f "skip=1 tokens=1-5" %%A in ('qwinsta 2^>nul ^| findstr /i "!TargetUser!"') do (
    set "SID="

    :: Test if token C (3rd column) is a number, normal case with SESSIONNAME present
    echo %%C | findstr /r "^[0-9][0-9]*$" >nul 2>&1
    if !errorlevel! equ 0 (
        set "SID=%%C"
    ) else (
        :: Test if token B (2nd column) is a number, shifted case without SESSIONNAME
        echo %%B | findstr /r "^[0-9][0-9]*$" >nul 2>&1
        if !errorlevel! equ 0 (
            set "SID=%%B"
        )
    )

    if defined SID (
        echo Found session ID: !SID! for user: !TargetUser!
        echo Resetting session ID !SID!...
        rwinsta !SID!

        if !errorlevel! equ 0 (
            echo Successfully reset session !SID!.
        ) else (
            echo Failed to reset session !SID!. Check permissions.
        )
        set "FOUND=1"
    )
)

if not defined FOUND (
    echo No session found for user: !TargetUser!
)

echo Done.
pause
tip

Run as Administrator: Finding and resetting other users' sessions requires administrative privileges. Make sure to run your batch file as Administrator.

Common Issues and Troubleshooting​

"Access is Denied"​

If you receive an "Access is Denied" error, it means the account running the script does not have permission to manage sessions on the target server. Ensure you are using an admin account.

"Session Not Found"​

If qwinsta returns nothing, double-check the username. Also, note that disconnected sessions (State: Disc) might not show up in simple lists if you filter incorrectly, though qwinsta usually lists everything.

Using reset session instead of rwinsta​

Windows provides reset session as a more readable alias for rwinsta. They perform the exact same function.

reset session 2

Summary​

Resetting a stuck RDP session is a straightforward process once you know the commands. By using qwinsta to identify the Session ID and rwinsta to clear it, you can resolve "black screen" login issues and frozen desktops quickly without affecting the rest of the server.

Table of Contents