Skip to content

Commit 2e3cd6a

Browse files
v-tappelgatev-tappelgate
authored
Merge pull request #10112 from v-tappelgate/AB#7124-event-id-5719
AB#7124: Event ID 5719 when NetLogon restarts on WS2025 member server
2 parents 28ca2ce + 221160a commit 2e3cd6a

File tree

2 files changed

+160
-0
lines changed

2 files changed

+160
-0
lines changed

‎support/windows-server/toc.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3074,6 +3074,8 @@ items:
30743074
href: ./windows-security/client-device-has-newer-password-value-than-active-directory.md
30753075
- name: DCs can't be located and high-rate outbound sessions
30763076
href: user-profiles-and-logon/dcs-cannot-be-located-high-rate-outbound-sessions.md
3077+
- name: Event ID 5719 (STATUS_INTERNAL_ERROR) occurs when the NetLogon service restarts
3078+
href: ./windows-security/event-id-5719-when-netlogon-service-restarts.md
30773079
- name: Gather information for secure channel issues
30783080
href: ./windows-security/data-collection-for-troubleshooting-secure-channel-issues.md
30793081
- name: Troubleshoot domain controller location issues

‎support/windows-server/windows-security/event-id-5719-when-netlogon-service-restarts.md‎

Lines changed: 158 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,158 @@
1+
---
2+
title: Event ID 5719 - STATUS_INTERNAL_ERROR Occurs When the NetLogon Service Restarts
3+
description: Helps you diagnose Event ID 5719 when it includes the STATUS_INTERNAL_ERROR code. Windows might log this event when the NetLogon service restarts on Windows Server 2025.
4+
ms.date: 11/06/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, herbertm, raviks, arrenc, v-appelgatet
9+
ms.custom:
10+
- sap:windows security\NetLogon, secure channel, dc locator
11+
- pcy:WinComm Directory Services
12+
appliesto:
13+
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
14+
---
15+
# Event ID 5719 (STATUS_INTERNAL_ERROR) occurs when the NetLogon service restarts
16+
17+
This article helps you diagnose and understand the NetLogon service Event ID 5719, when the event includes the `0xC00000E5 (STATUS_INTERNAL_ERROR)` error code. Windows logs this event when the NetLogon service restarts on Windows Server systems. The event typically appears when Windows Server 2025-based member servers interact with domain controllers (DCs) that run earlier Windows Server versions.
18+
19+
## Symptoms
20+
21+
Each time the NetLogon service restarts on a Windows Server 2025 system, Windows logs Event ID 5719 (STATUS_INTERNAL_ERROR) in the System event log. The event text resembles the following excerpt:
22+
23+
> This computer was not able to set up a secure session with a DC in domain [domain name] due to the following: An internal error occurred.
24+
25+
The event text includes the `0xC00000E5 (STATUS_INTERNAL_ERROR)` code.
26+
27+
The event doesn't persist. Windows establishes the secure channel to the DC. Then, normal domain operations resume.
28+
29+
The event occurs even though you didn't make any recent configuration, update, or software changes. Typically, you only see this behavior in particular environments:
30+
31+
| Member server | Authenticating DC | Event and code |
32+
| - | - | - |
33+
| Windows Server 2025 | Windows Server 2025 | No Event ID 5719 |
34+
| Windows Server 2025 | Windows Server 2022 | Event ID 5719, `0xC00000E5 (STATUS_INTERNAL_ERROR)` |
35+
| Windows Server 2025 | Windows Server 2019 | Event ID 5719, `0xC00000E5 (STATUS_INTERNAL_ERROR)` |
36+
37+
## Cause
38+
39+
When the NetLogon service restarts in mixed Windows Server environments (Windows Server 2025 member servers and Windows Server 2022 or Windows Server 2019 DCs), Windows generates Event ID 5719 (STATUS_INTERNAL_ERROR). As long as the secure channel is established, this event is expected and harmless.
40+
41+
The error occurs because of protocol differences in Kerberos authentication support. The error doesn't indicate a functional problem unless it keeps occurring in circumstances other than the circumstances that this article discusses.
42+
43+
When a Windows Server 2025 member server tries to establish a secure channel to a DC that runs Windows Server 2022 or an earlier version, it starts the connection by using the new Kerberos authentication method. Older DCs don't support this new authentication Remote Procedure Call (RPC) call. Because of this lack of support, authentication fails and Windows logs Event ID 5719 (STATUS_INTERNAL_ERROR). In this situation, the system automatically falls back to the legacy NetLogon method to successfully establish the secure channel.
44+
45+
This sequence causes a single, harmless error event. You can safely ignore this event unless you also see ongoing authentication or connectivity problems.
46+
47+
## Resolution
48+
49+
Event ID 5719 (STATUS_INTERNAL_ERROR) might occur only one time when NetLogon restarts and the secure channel is established (domain operations proceed without any issues). In this case, the event is harmless. Don't try remediation unless you see other persistent authentication or secure channel issues.
50+
51+
Microsoft recognizes this event as expected in mixed-version environments. Microsoft might suppress or clarify this event in future updates or documentation.
52+
53+
> [!IMPORTANT]
54+
> If the error recurs outside of NetLogon restarts, or it coincides with domain trust or authentication failures, investigate further. Collect the log data, as described in [Collecting log data](#collecting-log-data), and then contact Microsoft Support.
55+
56+
### Workaround (optional)
57+
58+
[!INCLUDE [Registry important alert](../../../includes/registry-important-alert.md)]
59+
60+
As part of the transition to Windows Server 2025 or newer DCs that support Kerberos for secure channel setup, temporarily configure the following registry setting. Configure this setting on Kerberos-capable member computers that also run NetLogon.
61+
62+
This change suppresses the logging of Event ID 5719 (STATUS_INTERNAL_ERROR). After you deploy enough Windows Server 2025 or newer Kerberos-capable DCs in the domain to ensure reliable Kerberos-based secure channel establishment, remove the registry setting.
63+
64+
- **Registry subkey**: `HKLM\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters`
65+
66+
- **Registry entry details**:
67+
68+
- Name: `UseKerberosForSecureChannels`
69+
- Type: `REG_DWORD`
70+
- Value: `0`
71+
72+
To use a Windows command-line prompt to apply this change, run the following command:
73+
74+
```console
75+
reg add "HKLM\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters" /v UseKerberosForSecureChannels /t REG_DWORD /d 0 /f
76+
```
77+
78+
To use a Windows PowerShell prompt to apply this fix, run the following command:
79+
80+
```powershell
81+
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters" -Name "UseKerberosForSecureChannels" -Value 0 -Type DWord
82+
```
83+
84+
Apply this configuration only temporarily. After the domain environment is adequately updated, remove the registry change.
85+
86+
## Collecting log data
87+
88+
Collect the following logs:
89+
90+
- **System event logs**. Focus on entries for Event ID 5719 (Source: NetLogon).
91+
92+
- **NetLogon service logs**. If you need deeper analysis, turn on NetLogon debugging.
93+
94+
### Collecting system event logs
95+
96+
```console
97+
wevtutil qe System "/q:*[System[(EventID=5719)]]" /f:text /c:50
98+
```
99+
100+
### Enabling NetLogon debug logging
101+
102+
```console
103+
nltest /dbflag:0x2080ffff
104+
```
105+
106+
Windows writes these log entries to %systemroot%\debug\NetLogon.log.
107+
108+
To turn off logging, run the `nltest /dbflag:0x0` command.
109+
110+
## More information
111+
112+
The event is specific to Windows Server 2025 member servers that authenticate by using DCs that run earlier versions of Windows. In the same scenario, Windows Server 2019 and Windows Server 2022 member servers don't log Event ID 5719 (STATUS_INTERNAL_ERROR).
113+
114+
Windows Server 2025 systems that authenticate by using Windows Server 2025 DCs don't log Event ID 5719 (STATUS_INTERNAL_ERROR).
115+
116+
### Log entries in NetLogon.log that trace the secure channel process
117+
118+
When Windows initially tries to establish the secure channel, it uses Kerberos. Windows logs an entry that resembles the following excerpt:
119+
120+
```output
121+
[INIT] [10664] UseKerberosForSecureChannels = TRUE
122+
```
123+
124+
The DC refuses this first attempt. On the member server, Windows receives an error message that resembles the following log excerpt:
125+
126+
```output
127+
[SESSION] [3036] CONTOSO: NlDiscoverDc: Found DC \\CONTOSODC.CONTOSO.com
128+
[SESSION] [3036] CONTOSO: NlSessionSetup: Denied access as we could not authenticate with Kerberos 0xC002002E
129+
[CRITICAL] [3036] Assertion failed: ClientSession->CsState == CS_IDLE (Source File: onecore\ds\netapi\svcdlls\logonsrv\server\lsrvutil.c, line 3963)
130+
[SESSION] [3036] CONTOSO: NlSessionSetup: Denied access as we could not authenticate with Kerberos (translated status) 0xC00000E5
131+
[SESSION] [3036] CONTOSO: NlSetStatusClientSession: Set connection status to c00000e5
132+
[SESSION] [3036] CONTOSO: NlSetStatusClientSession: Unbind from server \\CONTOSODC.CONTOSO.com (TCP) 0.
133+
[MISC] [3036] Eventlog: 5719 (1) "CONTOSO" 0xc00000e5 3dc54378 84808124 847d677c e2aadc59 xC.=$...|g}.Y...
134+
[SESSION] [3036] CONTOSO: NlSetStatusClientSession: Set connection status to c000005e
135+
[SESSION] [3036] CONTOSO: NlSessionSetup: Session setup Failed[AC3]
136+
```
137+
138+
Windows tries again to create the secure channel. This time, it works. Windows logs entries that resemble the following excerpt:
139+
140+
```output
141+
[SESSION] [10664] CONTOSO: NlSessionSetup: Try Session setup
142+
[SESSION] [10664] CONTOSO: NlDiscoverDc: Start Synchronous Discovery
143+
[MISC] [10664] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c3fffff1
144+
[MAILSLOT] [10664] NetpDcPingListIp: CONTOSO.COM.: Sending UDP ping to 10.32.51.12 ...
145+
…
146+
[MISC] [10664] NetpDcAllocateCacheEntry: new entry 0x0000020544B6E450 -> DC:CONTOSODC DnsDomName:CONTOSO.COM Flags:0x3f1fd
147+
[MISC] [10664] NetpDcGetName: NetpDcGetNameIp for CONTOSO.COM. returned 0
148+
```
149+
150+
Windows also records the Security-NetLogon Event ID 9005 in the Applications and Service Logs\Microsoft\Windows\Security-NetLogon\Operational event log. The log entry resembles the following excerpt:
151+
152+
```output
153+
Source: Security-NetLogon
154+
Event ID 9005
155+
Task Category: Secure channel setup
156+
Secure channel setup has failed with Kerberos: An internal error occurred.
157+
Falling back to NetLogon.
158+
```

0 commit comments

Comments
 (0)