Share via

User Profile Event trigger 1534

Anonymous
2025-01-02T07:26:31+00:00

We noticed a large number of warning events on our Windows Server 2022 with Event ID 1534 'User Profile Service,' starting on November 8, 2024. The event details are as follows: 'Profile notification of event Load for component {0A556D98-CFEE-4D84-82A7-00377F939198} failed, error code is See Tracelogging for error details.'

In our infrastructure, we were unable to find the TDL key using the path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileNotification. However, after deleting the CLSID {0A556D98-CFEE-4D84-82A7-00377F939198} from ProfileNotification\DefaultAssociationsProfileHandler, the issue was resolved when tested on one of the production servers.

Is it safe to delete the CLSID permanently, or do you have any other solution apart from relying on the TDL key?

Windows Server Identity and access User logon and profiles

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

9 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-01-06T13:11:06+00:00

    Thank you for your detailed response and for highlighting the potential consequences of modifying or deleting registry entries.

    We wanted to seek clarification regarding Event ID 1534. While we understand the potential risks of registry modifications, we have observed the following:

    1. The Event ID 1534 warnings have been generated consistently across all our servers since October 2024.
    2. Despite the warnings, we have not encountered any user-specific issues or noticeable impact on server functionality.
    3. Given our infrastructure's large event log size, these warnings contribute significantly to log clutter.

    In light of the above, could you confirm if it would be safe to ignore these Event ID 1534 warnings, provided no user-facing or system functionality issues have been observed?

    Your guidance will help us determine the appropriate course of action.

    0 comments
  2. Anonymous
    2025-01-07T09:35:50+00:00

    Hello

    Greetings!

    Please confirm what changes did you make then the Event ID 1534 generated consistently across all your servers since October 2024.

    I am sorry, after my research and search, Event ID 1534: Occurs mainly for DOMAIN joined User Profiles.

    It is unclear if there are side-effects. If you notice any, restore the backed up Registry keys again to resolve the issue.

    If you have any question or concern, please feel free to let us know.

    Best Regards,
    Daisy Zhou

    0 comments
  3. Anonymous
    2025-01-07T15:23:22+00:00

    Dear Microsoft Support Team,

    Thank you for your response.

    As per our support team, the 1534 event started appearing consistently on a few servers after the installation of security patches KB5044281 and KB5044414 in October 2024. However, in our infrastructure:

    1. We do not use domain-joined systems.
    2. End users access applications like Navigator using RDS RDP and AVD desktops only.
    3. We have not received any user requests or observed any issues related to domain joining, operating system behavior, application functionality, or data integrity.
    4. Our event logs have sufficient space due to an overwrite policy. Additionally, we store event logs in a separate Azure storage account, ensuring there is no impact on OS performance.

    Given the above, could you please confirm if it is safe to ignore the Event ID 1534 in our environment?

    We want to ensure there are no potential risks or overlooked issues before making a decision.

    Looking forward to your advice

    0 comments
  4. Anonymous
    2025-01-08T11:42:18+00:00

    Hello

    Good day!

    Given the above, could you please confirm if it is safe to ignore the Event ID 1534 in our environment?

    If it is warning and there is no any actual problem now, you can ignore it for now and keep monitoring.

    If you have any question or concern, please feel free to let us know.

    Best Regards,
    Daisy Zhou

    0 comments