Kerberos RC4 Failures After Windows Updates? The Proven Fix

By Ahmet Tolga KAYA 7 min read
Kerberos RC4 Failures After Windows Updates? The Proven Fix

Kerberos RC4 failures are showing up on domain controllers patched since April 2026: a NAS stops accepting logins, a Linux box with a keytab cannot get tickets, or a legacy service account suddenly fails with an encryption error. The cause is not a broken domain. Microsoft changed what Active Directory assumes when an account has no encryption type configured, and the fix is almost always at the account level, not a registry rollback.

Why Kerberos RC4 Failures Started After the Updates

Microsoft tracks the change as CVE-2026-20833 and documents it in KB5073381. The Kerberos RC4 hardening 2026 rollout has three phases. Phase 1 began with the updates released on January 13, 2026 and only added audit events. Phase 2 began with the April 2026 updates, when domain controllers started assuming AES only for accounts without an explicit setting. Phase 3 began with the July 2026 updates, which, according to the Microsoft Tech Community post, removed audit-only mode and stopped reading the temporary RC4DefaultDisablementPhase rollback value.

In practice, the KDC now treats an empty msDS-SupportedEncryptionTypes attribute as 0x18, which means AES128 and AES256 only. Any account that relies on RC4 by default, and any client that only advertises RC4, no longer gets a ticket. It will most likely show up as an authentication failure at the target service rather than a clear KDC message, which is why Kerberos RC4 failures are hard to spot at first.

Kerberos RC4 failures can hit any environment where Microsoft says the change applies to domain controllers on Windows Server 2012 (ESU) through 2025, although the blog notes it has only validated behavior on systems released before 2025. Note that RC4 is not removed from Windows entirely. Only the ability to default to RC4 is gone, and an administrator can still configure it explicitly per account.

Symptoms: How to Recognize Kerberos RC4 Failures

  • A client or appliance reports that the encryption type is not supported; klist get returns 0xc00002fd with the text “The encryption type requested is not supported by the KDC.”
  • Security event 4769 on the DC shows a failure code of 0xE (KDC_ERR_ETYPE_NOTSUPP) in Microsoft’s Learn example, with a ticket encryption type of 0x17 (RC4) in successful older requests.
  • A Kdcsvc event 203, 204, 208 or 209 in the System log (source Kdcsvc) is an error where the KDC blocked cipher use. Events 201, 202, 206 and 207 were the earlier warnings.
  • Linux, NAS, printer, or vendor appliance sign-ins break while Windows clients keep working.

One caveat: the KB places events 201-209 in the System log, while the blog’s prerequisites section mentions the Security log. Check both. The Learn page uses the Security log events 4768 and 4769 as the RC4 indicators.

Kerberos RC4 failures illustration: Kdcsvc event 203 and klist encryption type not supported error

Step 1: Find Which Accounts Cause the Kerberos RC4 Failures

Start on a domain controller with an elevated PowerShell. List the Kdcsvc events first:

Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Kdcsvc'; Id=201,202,203,204,206,207,208,209} -MaxEvents 100 |
    Select-Object TimeCreated, Id, Message | Format-ListCode language: JavaScript (javascript)

Then look for service tickets still issued with RC4 in the Security log (ticket encryption type 0x17):

Get-WinEvent -LogName Security -FilterXPath "*[System[EventID=4769] and EventData[Data[@Name='TicketEncryptionType']='0x17']]" -MaxEvents 100 |
    Select-Object TimeCreated, Id, MessageCode language: JavaScript (javascript)

Microsoft also publishes helper scripts in the Kerberos-Crypto repository. The Learn page names List-AccountKeys.ps1 and Get-KerbEncryptionUsage.ps1, for example .\Get-KerbEncryptionUsage.ps1 -Encryption RC4, to enumerate RC4 usage across the domain.

Step 2: Check the Account’s msDS-SupportedEncryptionTypes

Use the query from Microsoft Learn to see what a service or computer account is configured for. Replace the name with your account:

$accountName = "nas01$"
$parameters = @{
    Filter     = "Name -eq '$($accountName)' -and (ObjectClass -eq 'Computer' -or ObjectClass -eq 'User')"
    Properties = "msDS-SupportedEncryptionTypes"
}
Get-ADObject @parameters | FL "DistinguishedName","msDS-SupportedEncryptionTypes","Name","ObjectClass"Code language: PHP (php)

An empty value follows the domain default, which is now AES only. The values you will meet are 24 (0x18, AES128 and AES256), 56 (0x38, adds AES256 session keys) and 28 (0x1C, RC4 plus AES). Note that 0x24 is not AES-only. It is RC4 plus an AES256 session key.

Step 3: Fix the Kerberos RC4 Failures at the Account Level

Match the event to the remedy. Microsoft’s guidance maps them like this:

  • Events 202, 204, 207, 209 (the service account has no AES keys): reset the account password so Active Directory generates AES keys. Microsoft’s Learn page states that changing the password generates these keys.
  • Events 201, 203, 206, 208 (the client only supports RC4): update the client, its krb5.conf, keytab or Kerberos library so it advertises AES.
  • If the device truly cannot do AES, Microsoft’s blog says to set msDS-SupportedEncryptionTypes on that one account to 0x1C. That is a per-account exception, and Microsoft calls it not recommended.

Reset the password of a service account like this, and then update whatever uses it:

Set-ADAccountPassword -Identity svc-nas01 -Reset -NewPassword (Read-Host -AsSecureString "New password")Code language: JavaScript (javascript)

A practical note from my own checklist, not from the Microsoft pages: because a reset changes the account keys, regenerate any Linux keytab that was created for that account. For a managed service account, the password rotates on its own, so you only need to check the client side.

If you must make the per-account exception, this sets 28 (RC4 plus AES) on a user account:

Set-ADUser -Identity svc-legacy -Replace @{'msDS-SupportedEncryptionTypes'=28}Code language: JavaScript (javascript)

For computer objects use Set-ADComputer the same way. Per the Learn page, a machine updates its own attribute after a restart, so reboot it after changing related settings.

Flowchart to fix Kerberos RC4 failures: find events, identify account, reset password, verify

Why You Should Not Roll Back the Whole Domain

You may find advice to set DefaultDomainSupportedEncTypes to allow RC4 for everyone. On Windows Server 2016 to 2022 the value lives under HKLM\System\CurrentControlSet\Services\KDC, and the blog gives a different path under ...\Policies\System\Kerberos\Parameters for Windows Server 2025. Microsoft says it honors explicit administrator configuration, and event 205 is logged at each KDC service start when the value includes anything other than AES-SHA1.

I would still avoid it. It reopens the exposure that CVE-2026-20833 closes for every account in the domain, and the RC4DefaultDisablementPhase switch that used to give a clean rollback is no longer read after the July 2026 updates. Fixing the Kerberos RC4 failures one account at a time is slower on day one and far safer afterwards.

Step 4: Verify the Kerberos RC4 Failures Are Gone

klist purge
klist get cifs/nas01.contoso.com

Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Kdcsvc'; Id=203,204,208,209} -MaxEvents 5Code language: JavaScript (javascript)

You want the ticket retrieved successfully, proof that the Kerberos RC4 failures are fixed, and no new error events after the change. Then look at event 4769 again: the ticket encryption type should read 0x12 (AES256) instead of 0x17. Watch for a full business cycle, because month-end jobs and weekly scripts often use rarely touched service accounts.

Kerberos RC4 failures resolved illustration: klist get succeeds and no Kdcsvc 203 events

Prevent the Next Round of Kerberos RC4 Failures

  • Inventory every service account and appliance with the Microsoft scripts, then reset old service account passwords so they hold AES keys.
  • Set msDS-SupportedEncryptionTypes explicitly on accounts you manage, instead of relying on the domain default.
  • Alert on Kdcsvc 203, 204, 208 and 209 so a failing integration reaches you before users do.
  • Retire devices that cannot do AES. Microsoft asks owners of third-party devices with no AES-SHA1 support to contact [email protected].

If a failure looks like a broken secure channel instead of an encryption issue, our guide on the trust relationship failed error between a workstation and the domain covers that path.

Read more: Trust Relationship Failed Between Workstation and Domain: 5 Proven Fixes

Read more: How To Windows Server 2016 Metadata Cleanup Best Way

Read more: Remove old BitLocker Recovery Passwords from Active Directory

Why do I see Kerberos RC4 failures after the April 2026 update?

From April 2026, updated domain controllers assume AES only (0x18) for accounts without an explicit msDS-SupportedEncryptionTypes value, so RC4-only clients and keys are denied.

Can I still roll back with RC4DefaultDisablementPhase?

No. Microsoft says the updates released in or after July 2026 stop reading that registry value, so the domain-wide audit rollback no longer works.

How do I generate AES keys for an old service account?

Reset the account password. Microsoft Learn states that changing the password generates the AES keys the KDC needs.

Which events point to Kerberos RC4 failures?

Kdcsvc events 203, 204, 208 and 209 are the enforcement errors, and Security events 4768 and 4769 show the encryption types used. Check both the System and Security logs.

Is msDS-SupportedEncryptionTypes 0x24 AES only?

No. 0x24 is RC4 plus an AES256 session key. AES only is 0x18, or 0x38 if you also want AES session keys.

References

Microsoft Support: KB5073381 – How to manage Kerberos KDC usage of RC4 for service account ticket issuance changes related to CVE-2026-20833

Microsoft Learn: Detect and remediate RC4 usage in Kerberos

Microsoft Tech Community: What changed in RC4 with the January 2026 Windows update and why

Microsoft Tech Community: How to manage RC4 hardening – definitive guide

Ahmet Tolga KAYA

Systems Engineer and Technical Writer focused on Windows, Microsoft technologies, infrastructure, cybersecurity, automation, and platform reliability.