Fix: Event ID 4768 Kerberos Authentication Ticket Requested

Learn more about the event ID 4768 and how to easily solve it

Reading time icon 3 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Key notes

  • In Windows Event Viewer logs, you may find event ID 4768 listed in the critical events.
  • Usually, when the system fails to verify a user credential using the Kerberos authentication method, Windows logs this event.
  • Though updating Microsoft Windows can come in handy, you still may need to follow other methods from this article to solve this problem.
how to fix Event ID 4768: Kerberos Authentication Ticket Requested

If you have found the event ID 4768, it means there was a failed attempt to validate a credential of an account. This article will help you to fix this problem.

Windows Event Viewer can store a lot of event information, including some very important security events. It helps a lot to troubleshoot various problems. A lot of users have been seeing the event ID 4768 with the message Kerberos Authentication Ticket Requested.

To solve this issue, you can follow some specific tricks. But knowing the reasons should be your first priority as it will help a lot in the troubleshooting steps.

What causes the event ID 4768?

Before going through the solution, you should know about the reasons. Usually, this problem occurs due to the following things:

  • A problem with Microsoft Windows: Sometimes, the Windows server may have a known bug that may prevent some users from authenticating using the Kerberos database, and that creates the event ID 4768.
  • Misconfiguration: Any misconfiguration on the Windows server also may trigger this problem.
  • Problematic update: If you start seeing that event ID after installing an update, it is most likely that the update was problematic.

How can you solve event ID 4768?

Before trying to troubleshoot this problem, we suggest you do the following things to avoid any unwanted hassles:

After that, follow these methods to get rid of event ID 4768: Kerberos authentication ticket requested.

1. Install the required patch manually

  1. Go to the Microsoft Update Catalog.
  2. Search for the update KB5015019.
  3. Download the update.downloading KB5015019 update from catalog
  4. Install it on Windows.
  5. Restart the Windows Server/PC.

In recent days, people have been facing the event ID 4768 with a message Kerberos authentication ticket (TGT) was requested. Installing that specific patch should fix the problem. However, if not, search for the news if there are any other updates like KB5016693 that may help.

For example, in the past, we saw the updates KB4015547 and KB4015550 fixed a lot of issues.

We also saw that last November, Microsoft released an update that solved Windows Kerberos issues. So, these updates are important.

2. Uninstall problematic update

  1. Open the Start Menu, type the control panel, and hit Enter.
  2. Go to Uninstall a program.
  3. Click on View installed updates.clicking view installed updates uninstall or change a program control panel
  4. Uninstall the problematic update.

This method helps when you start facing this problem after installing an update.

3. Use a Firewall

  1. In Control Panel, go to System and Security.going system and security control panel
  2. Then, go to Windows Defender Firewall.
  3. Go to Advanced settings.going windows defender firewall advanced settings
  4. Configure inbound and outbound rules.

If you are using anything else to prevent unwanted inbound requests, we strongly suggest you use the firewall instead. You can easily apply inbound and outbound rules on a Windows server. For specific users, it has fixed the event ID 4768. It also may work for you as well.

4. Enable VPN

You also can consider configuring a VPN connection for other users in your system. So, when they try to access your system, they must use a VPN to access the local network first.

In this case, Kerberos authentication can be able to verify the credentials without any other problems, and no event ID 4768 will be stored. However, this method applies to specific situations only.

If you are interested, learn about the best browsers that support Kerberos Authentication.

This article has explained how you can solve the event ID 4768 critical security error on Windows and Windows servers. If you have any other ideas that may help others, feel free to let us know in the comment box.

More about the topics: windows server