CyberKit

Event IDs

Security event 4778

A session was reconnected to a Window Station

Channel: Security. Category: Logon/Logoff (Audit Other Logon/Logoff Events).

What it records

Generated when a user reconnects to an existing, disconnected Terminal Services (RDP) session, switches back to a desktop via Fast User Switching, or reconnects to a Hyper-V Enhanced Session. Records the Subject account, the Session Name the session reconnected to, and (for a network reconnect), the Client Name and Client Address it came from.

Why it matters

Distinguishes a session resuming from a dormant, disconnected state from a brand-new authentication (4624), since a disconnected RDP session stays logged on in memory without re-prompting for credentials. Paired with 4779, it lets an analyst bound exactly how long a given Window Station session was actively in use versus sitting idle-but-live across a shift or an investigation window. An unexpected reconnect (from an unfamiliar Client Address, outside normal hours, or to an account that shouldn't have a lingering session) is a signal an attacker regained a dormant foothold without needing a fresh logon.

What triggers it

Legitimately: a user reconnecting to their own disconnected RDP session from the same or a different client, or switching back to a locked desktop via Fast User Switching. Anomalously: an attacker reconnecting to a dormant RDP session left open by a prior logon, from an unexpected Client Address or outside the account's normal hours, to regain access without triggering a fresh 4624 logon or re-authentication prompt.

Fields that carry the answer

Key fields
FieldWhat it tells you
Account Name (Subject)Who reconnected: the identity to check against expected RDP/console usage patterns.
Session NameWhich session was resumed (RDP-Tcp#N for a typical RDP session, Console for Fast User Switching, or a GUID-style name for a Hyper-V Enhanced Session) confirms this was a reconnect to an existing session, not a fresh logon.
Client AddressSource IP of the reconnecting client: the primary pivot for tracing where the reconnect originated; shows 'LOCAL' for a console/Fast-User-Switching reconnect.
Logon IDCorrelates the reconnect back to the original 4624 logon that created the session being resumed.

In practice

Logged when CORP\jsmith reconnects to Session Name RDP-Tcp#6 from Client Address 198.51.100.42, resuming a Terminal Services session left disconnected rather than triggering a new interactive logon. Paired with a later 4779 disconnecting that same session, 4778 lets an analyst reconstruct exactly when the session was actively being used versus sitting disconnected-but-logged-on.

Sample record

A session was reconnected to 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

Sources

Paste a record into Event XML or open a log in EVTX Reader.