Security event 4779
A session was disconnected from a Window Station
Channel: Security. Category: Logon/Logoff (Audit Other Logon/Logoff Events).
What it records
Generated when a user disconnects from an existing Terminal Services (RDP) session, leaving it running and logged on in the background rather than logging off, switches away from a desktop via Fast User Switching, or disconnects from a Hyper-V Enhanced Session. Records the Subject account, the Session Name that was disconnected, and (for a network session), the Client Name and Client Address it disconnected from.
Why it matters
Marks the start of a session's dormant-but-still-logged-on window: the counterpart to 4778's resume. Together the pair let an analyst bound exactly when an RDP session was actively in use versus sitting disconnected and reachable for later reconnection without re-authentication. A disconnect with no later 4778 reconnect, and no eventual 4634/4647 logoff closing it out, is worth tracking, since the underlying session and its credentials remain live in memory the whole time.
What triggers it
Legitimately: a user closing an RDP window or a network interruption dropping the connection without a full logoff, or switching to another desktop via Fast User Switching. Anomalously: an attacker deliberately leaving a session disconnected rather than logging off, to preserve a live, re-connectable foothold that survives without needing fresh credentials.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Account Name (Subject) | Who disconnected. The identity whose session remains logged on but unattended afterward. |
| Session Name | Which session was disconnected: the value to watch for in a later 4778 reconnect (or its prolonged absence). |
| Client Address | Source IP the session disconnected from: the last-known client location before the session went dormant. |
| Logon ID | Ties the disconnect back to the originating 4624 logon and forward to the session's eventual 4778 reconnect or 4634/4647 logoff. |
In practice
Logged when CORP\jsmith's RDP client at 198.51.100.42 drops the connection to Session Name RDP-Tcp#6 without a full logoff. The session stays authenticated and resident on the server. If that Session Name is never reconnected (4778) or formally logged off (4634/4647) for an extended period, the disconnected-but-live session is worth flagging as a standing foothold.
Sample record
A session was disconnected from a Window Station. Subject: Security ID: S-1-5-21-3623811015-3361044348-30300820-1104 Account Name: jsmith Account Domain: CORP Logon ID: 0x3E7F2A1 Session: Session Name: RDP-Tcp#6 Additional Information: Client Name: WKSTN-042 Client Address: 198.51.100.42
ATT&CK techniques
- T1021.001: T1021.001
Sources
Paste a record into Event XML or open a log in EVTX Reader.