What is “WinGet COM Server” Process and How to Fix High CPU Usage Caused by it

Recently, several users have raised concerns about experiencing high CPU usage caused by the "WinGet COM Server" process after updating Windows, installing applications, or seemingly at random.

While WinGet COM Server is a legitimate process, it can sometimes cause high CPU usage due to a variety of reasons, such as installing or updating a large number of applications, downloading a large application, a conflict with other apps, or a problem with the winget installation.

What is WinGet COM Server Process?

WinGet COM Server is a process that is used by the Windows Package Manager (winget) to communicate with other applications. It is a legitimate process that is essential for winget to function properly.

Winget is a command-line tool and package manager that allows you to discover, install, upgrade, remove, and configure applications on Windows 10 and Windows 11 computers. It is a convenient way to install and manage your software, as it allows you to do so from a single location.

WinGet COM Server is responsible for handling a variety of tasks, including downloading, installing, uninstalling, and updating applications, as well as managing application dependencies.

Fixing WinGet COM Server High Usage issue

There are a few things you can do to try to fix high CPU usage caused by WinGet COM Server:

1. Perform a Full System Shutdown

If you're encountering issues with Winget or any other software, performing a full shutdown can be a good troubleshooting step.

This is because it essentially gives your computer a fresh start by fully resetting and reinitializing everything, including reloading all the core processes and drivers right from scratch.

Doing this can often resolve problems that stem from bad drivers or issues at the kernel level. Here's how to do it:

Press the Win + Rthe keys to open the Run dialog box. Type cmd and press Ctrl + Shift + Enter to open the Command Prompt with administrator privileges.
In the Command Prompt, enter the following command and press Enter:

shutdown /s /f /t 0

This command initiates a complete shutdown of your PC. It may take longer than a normal shutdown because Windows will close all running processes and services. After your system has fully powered down, turn it back on, and see if the WinGet COM Server process still using excessive CPU.

2. Update the App Installer

Winget (Windows Package Manager) has become a built-in feature in Windows 10 and 11, and it's controlled through the App Installer program on your computer. If you haven't kept your App Installer up to date, you might run into problems when using Winget to handle packages.

Method 1:

Open the Microsoft Store and navigate to the 'Library' section.

Look for any pending updates for the App Installer. If updates are available, manually search for and install them.

After updating the App Installer, check if the high CPU usage issue persists.

Method 2:

Another way to update winget is by downloading the installer from the official GitHub page:

Visit the official winget GitHub page.
On the left-side panel, click the latest release under 'Releases'.

On the Version page, scroll down to the 'Assets' section and click the .msixbundle file to download the file.

Run the downloaded file and click 'Update' or 'Re-install'.

Wait for the installation process to finish. The app may automatically install additional dependencies required for winget to work.

3. Disable Non-essential Winget Sources

If you have installed winget sources that you don't use, you can disable them to reduce the load on WinGet COM Server.

To list all the winget sources, run the below command in the Command Prompt:

winget sources list

To disable a winget source, open a PowerShell window and run the following command:

winget source disable <source name>

4. Re-register Winget

If the problem is related to Winget, re-registring the Windows Package Manager (Winget) might fix the problem. Re-registering Winget will restore its default settings without completely removing and reinstalling it.

Launch Windows PowerShell as administrator and paste the following command, and press Enter.

Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.Winget.Source_2021.718.1322.843_neutral__8wekyb3d8bbwe\AppXManifest.xml" -Verbose

After successfully executing the command, reboot your system.

5. Perform a Clean Boot

Performing a clean boot can often help diagnose and potentially resolve issues related to software conflicts or background processes that might be causing problems on your computer. It can help identify whether the high CPU usage issue related to the 'WinGet COM Server' is caused by a third-party service or startup program conflicting with it. Here's how:

Open the Run command, type msconfig , and press Enter to open the System Configuration window.

In the General tab, choose 'Selective startup' and uncheck the box that says 'Load startup items'.

Move to the 'Services' tab and check the box that reads 'Hide all Microsoft services'.

Click 'Disable all' to disable all non-Microsoft services.

Switch to the 'Startup' tab and click 'Open Task Manager'.

Inside the Task Manager, disable each startup application by right-clicking on them and selecting 'Disable'.

Close the Task Manager, and click 'Apply', followed by 'OK' in the System Configuration window.

Once it's done, restart your computer.

After your computer restarts, it will be in a clean boot state, meaning only essential Microsoft services and drivers will be running.

If the high CPU usage problem disappears after performing a clean boot, it means that a third-party service or startup program is likely the culprit. You can then gradually enable services and startup items one by one (or a few at a time) to identify which one is causing the issue.

Once you've identified the problematic software or service, you can try updating, repairing, or uninstalling the service.

To return your system to its normal startup configuration, go back to the System Configuration tool. Under the 'General' tab, select 'Normal startup' and click 'Apply', then 'OK'.

Then, restart your computer.

However, if you're still encountering the problem of high CPU usage even after performing a clean boot, it indicates that the issue might be tied to Windows itself or a critical system process, rather than being caused by a third-party appsor service. In such cases, you might have to consider other troubleshooting steps.

6. Repair Corrupted System Files

Corrupted system files can also lead to GPU not showing up in Task Manager. To scan and repair these faulty system files, you can run a combination of SFC and DISM. To do so:

Open Command Prompt with administrative privileges.
Type sfc /scannow and then press Enter.

After running the SFC scan, it's time to run the Deployment Image Servicing and Management (DISM) scan.

To run the Deployment Image Servicing and Management (DISM) scan, type the following commands one after the other and hit Enter after each:

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

7. Run the Windows Memory Diagnostic tool

This tool specifically checks your computer's Random Access Memory (RAM) and lets you know if it finds any errors. Here's how you can run it:

Open Windows Search, search for 'memory diagnostic', and select the 'Windows Memory Diagnostic' tool.

In the Windows Memory Diagnostic window, click on 'Restart now and check for problems (recommended)'. Once you click Restart now, your computer will automatically restart, run the Memory Diagnostic tool, and then restart again on its own.

After the system restarts, you will see a notification. If there's any problem with the memory, you will be notified. You can also review the Windows Memory Diagnostic tool results in the Event Viewer.

Here are some additional tips to help reduce high CPU usage: