SCNotification.exe High Memory or CPU Usage [Fix]

SCNotification or System Center Notification is a notification engine and a part of SCCM (System Center Configuration Manager). The System Center Configuration Manager lets users manage a large group of computers remotely. If SCNotification shows high memory or CPU usage on your Windows system, the solutions in this article may help resolve the issue.

Fix SCNotification.exe High Memory or CPU Usage in Windows

As described above, SCNotification is part of System Center Configuration Manager; high memory or CPU usage may occur if your system is incompatible with SCCM. Below are some fixes that may help you resolve this problem.

Restart the SCNotification
Restart SMS Agent Host Service
Check hardware requirements for SCCM
Change the WSUS port
Install Hotfix by Microsoft.

1] Restart the SCNotification

Before you proceed,end and restart the SCNotification process using Task Manager and see if it helps.

2] Restart SMS Agent Host Service

Open Windows Services Manager, locate and restart the SMS Agent Host Service and see if that works.

3] Check hardware requirements for SCCM

The first step is to check SCCM hardware requirements. If your system does not fulfill the minimum hardware requirements for SCCM, you may experience several issues with SCCM and other related components or applications.

To check this, you have to visit microsoft.com. You are experiencing high memory usage issue with SCNotification. One possible cause is insufficient memory to run SCCM. If your system has less memory or RAM than System Center Configuration Manager requires, increase the physical memory to fix the issue.

4] Change the WSUS port

Some users have found that the problem occurred because of WSUS (Windows Server Update Services). When they changed their WSUS port to 8080, the problem was fixed. You can also try this. If changing the WSUS port to 8080 does not fix the problem, revert the changes you made.

To check which port is configured for WSUS, follow the steps written below:

Log in to your WSUS server.
Open IIS Manager.
Right-click on the site that is running on WSUS and then select the Edit Binding option.
You will see the WSUS port. Select the HTTP or HTTPS port and click Edit.
Change the port and save.

5] Install Hotfix by Microsoft

Microsoft developed the hotfix to resolve high CPU consumption or high memory usage by SCCM. This Hotfix is for users who have System Center Configuration Manager 2007 Service Pack 2. If you have a management point installed on the site server in Microsoft SCCM 2007 Service Pack 2 and you are experiencing high memory or CPU consumption, you can use this Hotfix to fix the issue.

Close the System Center Configuration Manager Administration Console before applying this Hotfix. You do not need to restart your computer after applying this Hotfix. You will find this Hotfix on microsoft.com. If the Hotfix is not there, contact Microsoft support to get it.

It would be a good idea to update your Windows and the SCCM software.

Hope this helps.

Read: Fix vmmem.exe high memory usage.

How to fix SCNotification has stopped working error

The SCNotification has stopped working error occurs due to corrupted Microsoft .NET Framework or permission issues with the machine.config file. The machine.config file is a machine-level configuration file installed automatically when you install Microsoft .NET Framework.

You can fix the SCNotification has stopped working error by changing the permissions of the machine.config file. If this does not help, repair or reinstall the Microsoft .NET Framework.

Read: How to fix Performance issues in Windows

How to fix high memory usage on Windows 11

There are multiple causes of high memory usage on Windows devices. Usually, an app or software uses high memory or CPU when you perform tasks in that app or software. However, if CPU or memory usage stays high for long periods, you need to take action. You can try some general fixes to resolve this issue, like running chkdsk, SFC, and DISM scans, updating your device drivers, running the Performance Troubleshooter, etc.