# Winlogbeat 9.2.1 Fails to Ingest Specific Windows Application Event (Winlogon Event ID 6000)

**URL:** <https://discuss.elastic.co/t/winlogbeat-9-2-1-fails-to-ingest-specific-windows-application-event-winlogon-event-id-6000/383593>\
**Category:** Beats\
**Tags:** winlogbeat\
**Created:** [November 21, 2025, 4:00pm UTC](https://discuss.elastic.co/t/winlogbeat-9-2-1-fails-to-ingest-specific-windows-application-event-winlogon-event-id-6000/383593 "2025-11-21T16:00:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![banksmt](https://avatars.discourse-cdn.com/v4/letter/b/bbce88/32.png) [@banksmt](https://discuss.elastic.co/u/banksmt)\
**Post date:** [November 21, 2025, 4:00pm UTC](https://discuss.elastic.co/t/winlogbeat-9-2-1-fails-to-ingest-specific-windows-application-event-winlogon-event-id-6000/383593/1 "2025-11-21T16:00:37Z")

</div>

**We are experiencing an issue where Winlogbeat successfully ingests all Windows log channels (Application/System/Security/Sysmon) except for one very specific event type:**

**Microsoft-Windows-Winlogon — Event ID 6000 ("The winlogon notification subscriber was unavailable to handle a notification event")**

**This event appears normally in the Windows Event Viewer under Application, but Winlogbeat never forwards it to Graylog**

---

<div class="post-metadata">

**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\
**Post date:** [November 22, 2025, 8:37am UTC](https://discuss.elastic.co/t/winlogbeat-9-2-1-fails-to-ingest-specific-windows-application-event-winlogon-event-id-6000/383593/2 "2025-11-22T08:37:15Z")

</div>

Hello @banksmt

Welcome to the community!!

I see that using the default System integration this information was captured :

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/8/e83613b3b33a9c84f269e502b45f012a8ed47028.png)

Thanks!!