![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 49%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERW%3C/text%3E%3C/svg%3E)
These errors can be ignored according to Microsoft:
Error 7 Kerberos Windows server 2025
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 80%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECT%3C/text%3E%3C/svg%3E)
Carlos Torrijos Martín
35
Reputation points
Hello. I've migrated to Windows Server 2025 and am seeing the following error in the Event Viewer:
The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. The account name was and lookup type 0x108.
Log Name: System
Source: Microsoft-Windows-Kerberos-Key-Distribution-Center
Event ID: 7
Task Category: None
Level: Error
Keywords: Classic
User: N/A
The computer that's causing it isn't showing up, and I don't know how to investigate. Can anyone give me any idea why this happens?
Windows for business | Windows Server | User experience | Other
Answer accepted by question author
2 additional answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 74%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIC%3C/text%3E%3C/svg%3E)
Ionut Condurache 0 Reputation points2025-06-19T10:52:28.0233333+00:00 Hello, we have the exact same error on newly Windows Server 2025 promoted DC!
-
Carlos Torrijos Martín 35 Reputation points
2025-06-19T11:03:54.35+00:00 Hello Inout
Any solution? I've seen in some technical notes that this error could be caused by computers running Windows 11 23h2, but I've already migrated everything to 24h2 and I'm still having the same problem. I think it could be servers with versions lower than Windows Server 2025 that are causing it. Do you have Microsoft support to open a case?
-
Ionut Condurache 0 Reputation points
2025-06-19T12:03:16.0766667+00:00 Hi Carlos,
No solution yet, I'm hopping someone from MS will jump in to clarify.
Checking online there are dozens of threads about this on different forums and people recommend to stick with Windows Server 2022.
Sign in to comment -
-
Carlos Torrijos Martín 35 Reputation points
2025-10-21T09:37:18.3766667+00:00 Thanks
René Wieldraaijer. I already knew the answer, but the contribution is appreciated. Best regards