What Is WpnUserService (Windows Push Notifications User Service) and Why Is It Using So Much CPU?

A Service Host that lists WpnUserService is using too much CPU in Windows 11. The odd suffix is normal; it does not explain the CPU use. Start by identifying the current process and its listed services. Avoid disabling the service or editing its registry template as a first response: Microsoft warns that disabling per-user services can break dependent apps.

Quick Diagnosis

Fix #1: Identify the Busy Process and Its Services

Problem: Task Manager shows high CPU use by a Service Host that lists WpnUserService.

Why it happens: Windows Push Notifications User Service supports local and push notifications. Windows creates per-user services when you sign in and stops and deletes them when you sign out. The suffix identifies the user context; a service instance is not the same thing as a separate process. Microsoft explains this in its current per-user services documentation (reviewed October 16, 2026). The name alone does not identify a cause of high CPU use. Use the current process and service list below rather than assume that every Service Host groups services in the same way.

• Press Ctrl + Shift + Esc to open Task Manager. Microsoft documents that shortcut and resource monitoring in its Windows performance guidance.
• In Processes, identify the entry showing the high CPU reading. Note the displayed process name and CPU use. Do not end a Windows service process merely to make the number fall.

• Open Details and identify the currently busy process there, then note its PID (process ID). Several processes can have the same name, so a matching name alone is insufficient. If you cannot identify the process reliably, keep your CPU observations for support instead of choosing a PID by name. If your Task Manager opens in a compact view, expand More details first. Microsoft’s PID instructions explain the Details view and PID column; the layout can vary by Windows version.

Microsoft’s Task Manager PID instructions — public documentation captured October 16, 2026. Documentation view; no Windows procedure was performed for this article.

• For a documented list of services associated with a process, open Command Prompt and run this read-only query, replacing 1234 with the current PID you recorded:

tasklist /svc /fi "PID eq 1234"

Microsoft’s tasklist reference applies to Windows 11 and documents /svc plus the PID filter. The command lists process/service information; it does not stop services or change their configuration. Note whether WpnUserService appears and whether the same process lists other services. If the command fails or access is unavailable, record that result for support instead of guessing.

• Leave Task Manager open while the PC is idle for a few minutes. See whether CPU use stays high or drops after a short burst.

Verify: If several services are listed for that PID, the process-level CPU observation does not isolate an individual service. If usage changes, note the time and what you were doing. This gives support an observation, not a proven cause.

Fix #2: Restart Windows and Compare CPU Use Again

Problem: The Service Host stays busy after you close your apps.

Why it happens: Microsoft’s performance guidance recommends closing unused apps and restarting if performance does not improve. Per-user services are recreated at sign-in. A restart is a comparison step, not a promise to clear persistent settings, saved notification data, or an underlying fault.

• Save your work.
• Select Start > Power > Restart.
• Sign back in and wait a few minutes without opening your usual apps.
• Open Task Manager with Ctrl + Shift + Esc. Repeat Fix #1 to identify the current process and PID, then compare CPU use while idle. Do not reuse a PID from before the restart.

Verify: Record whether the spike returns and which apps you opened before it. If its timing coincides with alerts, Fix #4 is a controlled notification-setting comparison; that timing does not prove a cause. Signing out stops and deletes the per-user instance, and signing in creates one again, but this does not undo a changed service template.

Common Issues and Solutions

Fix #3: Install Applicable Windows 11 Updates

Problem: High CPU use returns after a restart, with no clear app trigger.

Why it happens: Microsoft says Windows updates often include fixes and performance improvements. That is general Windows maintenance guidance, not evidence of a WpnUserService-specific bug or a guaranteed CPU fix for your PC.

• Open Settings > Windows Update.
• Select Check for updates.

• Install any updates that apply and restart if Windows asks you to.
• Check CPU use again while the PC is idle.

Verify: Repeat Fix #1 after the update and any restart. Record whether the CPU behavior changed. Keep your Windows version details with the support notes described below.

Fix #4: Turn Off Notifications for One Suspected App

Problem: CPU use rises around frequent alerts from an app you recently installed, updated, or changed.

Why it happens: The timing makes that app worth checking. It doesn’t prove the app or WpnUserService caused the load. Change one app’s setting at a time so you can judge the result.

• Open Settings > System > Notifications.
• Select the suspected app under Notifications from apps and other senders, then turn its notifications off. Microsoft’s notification settings guidance documents the app controls. You will not receive that app’s alerts while they are off, so avoid disabling alerts you need.

Microsoft’s per-app notification guidance — public documentation captured October 16, 2026. Documentation view; no Windows procedure was performed for this article.

• Under comparable normal use, repeat Fix #1 and record the current process’s CPU reading. Keep other settings unchanged during this comparison.
• Turn the app’s notifications back on if CPU use doesn’t change.

Verify: Record whether the readings changed, then restore the app’s notifications unless you intentionally want them off. Microsoft’s performance guidance says reducing unnecessary notifications can provide small performance improvements; it does not establish that an app or WpnUserService caused your particular spike.

Fix #5: Check a Disabled Service Without Guessing Its Configuration

Problem: Notifications stopped after you disabled WpnUserService to lower CPU use.

Why it happens: WpnUserService supports notifications, and Microsoft warns that disabling per-user services can affect dependent apps. User-specific instances and their registry templates are different. The template is not shown in the Services console, and Microsoft lists WpnUserService among the services that cannot be managed with a security template.

• Press Win + R, type services.msc, and press Enter.
• Look for the suffixed Windows Push Notifications User Service entry for your signed-in account and record its displayed name and state. Microsoft documents viewing user-specific instances in this console. Do not assume the visible instance is the underlying service template.

Microsoft’s per-user service-instance guidance — public documentation captured October 16, 2026. Documentation view; no Windows procedure was performed for this article.

• If you changed a service or registry setting, keep a record of the exact change and ask Microsoft Support or your administrator which configuration should be restored. Do not guess a startup type or copy registry fixes for a different service.
• After any authorized configuration recovery, compare notification behavior again. Signing out and back in recreates the per-user instance, but a disabled template can recreate it in a disabled state.

Verify: Check an app whose alerts you normally receive and record the result. Use the documented per-app notification controls to quiet an app, rather than disabling WpnUserService as a CPU shortcut.

Fix #6: Use Windows Security When There Are Separate Warning Signs

Problem: Windows Security reports a threat, or you have another concrete reason to suspect malware alongside the performance problem.

Why it happens: Microsoft notes that malware can consume CPU and disk resources. That does not mean WpnUserService is malware or that its suffix identifies a threat. Follow security alerts separately from the process-name investigation.

• Follow any action Windows Security recommends for a detected threat. Do not delete a Windows service file solely because its name looks unfamiliar.
• For Microsoft’s documented performance-related malware check, open Start > Settings > Privacy & security > Windows Security > Virus & threat protection.

• Select Quick scan, as Microsoft’s Windows performance guidance describes. Follow the resulting Windows Security instructions if it detects a threat.

Verify: Record and act on the scan result. A clear scan is not a guarantee that every file is safe or an explanation of CPU use; continue the process investigation if the performance problem remains.

Error Messages and Labels

What you see	What it means	What to do
WpnUserService_ followed by characters	Windows has created a per-user service instance. The suffix is normal.	Use Fix #1 if you also see a symptom, such as high CPU use that lasts.
Service Host with WpnUserService listed	Check the actual current process/service association; the label alone does not identify a CPU cause.	Use the current PID and documented tasklist query in Fix #1.
Notifications stopped after a service change	A changed per-user-service configuration may affect dependent apps; the original CPU cause remains unproven.	Record the change and use Fix #5; do not guess a registry or startup setting.
High CPU in the Processes tab	The process is busy at that moment. A brief spike may pass.	Check CPU use while idle and note when the spike returns.

Settings to Check

For the one-app comparison, use Settings > System > Notifications and record the original setting. Change only the app you are checking and restore it afterward unless you want its alerts off. This is our comparison method, not a Microsoft-confirmed WpnUserService-specific fix.

These steps apply to Windows 11. Windows 10 also has per-user services, but its Settings layout differs.

Getting Help When CPU Use Stays High

If the same Service Host stays busy after a restart, updates, and the one-app test, gather these details for support:

• Open Settings > System > About and record the Windows details shown under Windows specifications. Microsoft’s device-information guidance documents that location. You can compare the version with its Windows 11 release information.

• Record the current process name, PID and observed CPU use, plus the service names returned by the read-only tasklist query.
• Note when the spike starts, how long it lasts, and which apps or alerts appear around that time.
• Include any specific error message Windows actually displayed. Do not infer a cause from timing alone.

Share those details with Microsoft Support or the Microsoft Community. A screenshot of the expanded Service Host and matching PID helps more than the suffixed name alone.

Prevention Tips

Follow the supported Windows update and notification controls above. Keep notes of changes so you can compare behavior under similar conditions. Avoid registry, notification-database or service-template edits without a supported recovery plan; the per-user-service documentation warns that configuration changes can affect dependent apps.

Wrapping Up

Start with Fix #1: identify the current process and its services, then record what happens after the supported restart, update or one-app comparison. These observations can help support investigate; they do not prove a WpnUserService-specific cause. If high CPU use persists, share the current PID, process/service list, Windows version and timing notes with support. The suffix itself is documented normal behavior.