Errors related to Windows Push Notifications User Service on Windows Server 2022 Core

Ashok Kumar 20 Reputation points
2025-07-31T04:34:01.8+00:00

I installed Windows Server 2022 Core (not Desktop Experience) including the latest OS updates, and everything was fine (i.e. no significant, repeated errors had been logged). Later, I installed App Compatibility Features on Demand (FOD) so that I'd have some basic GUI tools available (e.g. Event Viewer, Task Scheduler, etc.).

Overall, FOD has been very helpful to ease administration of Windows Server Core as I transition away from Desktop Experience. However, after installing FOD I noticed that Event Viewer (System) is showing many recurring errors whenever I log in:

Information - Event ID 7036: The Windows Push Notifications User Service_2fb4a service entered the stopped state.

Error - Event ID 7023: The Windows Push Notifications User Service_2fb4a service terminated with the following error: CoInitialize has not been called.

Error - Event ID 7031: The Windows Push Notifications User Service_2fb4a service terminated unexpectedly. It has done this 5 time(s). The following corrective action will be taken in 16000 milliseconds: Restart the service.

I'm not sure why Windows Push Notification (WPN) services would be installed for Windows Server Core (even with FOD) because WPN is mostly used by desktop OS with GUI for updating live tiles, etc. I'm also not able to disable this service, because it seems that a variant of the service is created with each login. That variant is indicated by the "_2fb4a" as shown in the error messages above. Each time I log in, it is dynamically created with a different identifier.

Is there a way to fix this error? Or is this a bug in Windows Server Core with FOD installed?

Windows for business | Windows Server | Devices and deployment | Other
0 comments No comments
{count} votes

Accepted answer
  1. Oliver Nguyen 440 Reputation points Independent Advisor
    2025-08-01T16:45:31.36+00:00

    Hi Ashok Kumar,

    You can Ignore the errors because they’re harmless.

    Suppress log entries using filters or scripts.

    Uninstall FOD if GUI tools aren’t critical:

    Remove-WindowsCapability -Online -Name App.Support.Tools~~~~0.0.1.0

    ===========================================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

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