Share via

Event 6004

jamie younkin 320 Reputation points
2026-03-10T17:34:54.79+00:00

Today I got this in the event viewer and I don't know what this is for?

The winlogon notification subscriber <TrustedInstaller> failed a critical notification event.

Windows for home | Windows 11 | Performance and system failures
0 comments No comments

2 answers

Sort by: Most helpful
  1. DaveM121 876.9K Reputation points Independent Advisor
    2026-03-10T18:10:18.78+00:00

    That specific error trace in the event viewer usually indicates the Windows Modules Installer Service, responsible for updates, failed to respond during login and that event can usually be safely ignored.

    Apart from seeing that error in the event viewer, are you experiencing any problems with Windows on your PC?

    Was this answer helpful?

    0 comments No comments

  2. Q&A Assist
    2026-03-10T17:35:05.4633333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Event 6004 with the message:

    The winlogon notification subscriber <TrustedInstaller> failed a critical notification event.

    means that a Winlogon notification callback associated with the TrustedInstaller component did not complete correctly during a logon-related event (such as logon, logoff, lock, unlock, or shutdown).

    Key points:

    • Winlogon uses notification packages (DLLs) that receive callbacks for logon-related events.
    • These packages are registered in the registry under: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify
    • When an event occurs (for example, user logon), Winlogon calls the registered notification handlers. If one of these subscribers (here, <TrustedInstaller>) fails to process the event, Winlogon logs an event like the one seen.
    • The message itself does not necessarily mean immediate system damage; it indicates that the TrustedInstaller-related notification handler did not successfully handle a Winlogon event.

    For a home Windows 11 system, if this appears only occasionally and there are no visible problems (logon works, updates install, no repeated crashes), it can typically be treated as informational or transient. If it recurs frequently together with other symptoms (failed updates, repeated logon issues, or system instability), then further investigation would focus on:

    1. Checking for repeated related errors around the same time in Event Viewer (Application and System logs).
    2. Ensuring Windows is fully updated.
    3. Running system health checks such as sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated command prompt.

    The event itself is about a Winlogon notification subscriber failing its callback; it is not, by itself, a definitive sign of corruption or malware.


    References:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.