Fix: WaasMedic.exe High CPU Usage on Windows 11/10

WassMedic.exe represents the Windows Update Medic service. It is a part of the Windows operating system. This service runs in the background to take care of the Windows update components. Sometimes this service may consume a lot of system resources. Therefore, In this guide, we will show you how to fix WaasMedic.exe high CPU Usage on Windows 10 or Windows 11.

Microsoft introduced this service called Windows Update Medic (WaasMedic.exe) in Windows 10. The main purpose of this service is to take care of the Windows Update components so that you can continue receiving future Windows updates without any interruption. If any damage happens to the Windows Update components, this service work as a remedy for update components.
WassMedic.exe starts automatically in the background when any Windows update is being installed. This process ends itself when its work gets finished, but if this service is consuming CPU very intensively, you can walk through some solutions below.

WaasMedic.exe High CPU Usage on Windows 11/10

We can try to troubleshoot this error in the following ways.

  1. Run system file checker
  2. Disable Antivirus Program
  3. Stop Windows Updates for few days
  4. Disable WaasMedic.exe service temporarily

1. Run System File Checker

System File Checker checks the corrupted system files and fixes them. If any such file that is related to the WaasMedic.exe process is missing or corrupted, this may cause the WassMedic.exe high CPU usage.
Open the Command Prompt Admin, and at the Command Prompt, type the following command, and then press the Enter button.

command: sfc /scannow

This command will scan all the system files, if it finds any corrupted file, it will replace that file with a cached copy of the file that is located in a compressed folder at %WinDir%System32dllcache.
Wait for a while until you see “Verification 100% complete“.

2. Disable Antivirus Program

Antivirus may be one of the reasons for the WaasMedic.exe high CPU issue. If Antivirus finds any suspicious activity on the computer, it immediately blocks that to secure your computer.
You can disable or uninstall your Antivirus if it conflicts with Windows Update. First, you should disable the Antivirus, then check if this solves the issue, if you find Antivirus is not the reason, you may enable your Antivirus again.
Related articles:

3. Stop Windows Updates for few days

If Windows updates are not important for you, you can pause the Windows updates for few days. By doing this, the WaasMedic.exe service will be automatically closed in the background.
To pause the Windows updates, simply open Windows settings and go to the Update & Securities, then under the Windows Update section, click the Pause updates option. Windows updates will be paused for the next 7 days.
If you want to pause the updates for more than a week, then click the Advanced options. This option enabled you to pause the updates for a maximum of 35 days.

4. Disbale WaasMedic.exe temporarily

If none of the above troubleshooting methods are working, you should temporarily disable the WassMedia.exe service to get rid of the WaasMedic.exe High CPU issue.
If you try to disable this service through Service Manager, this will show you Access Denied prompt. It would be better if you follow the below steps to disable the WaasMedic.exe service temporarily.
Through the Registry editor, we will edit the database key of the Windows Update Medic service. By doing this, we can temporarily disable the WaasMedic.exe service.

  1. Press the Windows Logo + R key to open the Run Box.
  2. In the Run Box, type the regedit, and then click the OK.
  3. This will open the Registey Editor.
  4. Naviagte to the following directory.
  1. Inside the WaaSMedicSvc directory, you get key called “Start“.
  1. Double click the “Start” to edit its DWORD  (32-bit) Value.
  2. Change the value data from 3 to 4.
  1. Click the OK, then edit the Registry Editor.

Once you have complete this, Restart the computer. The Windows Update Medic Service or WaasMedic.exe is now disabled.