High CPU usage caused by WinGet COM Server can significantly impact system performance on Windows 10 and Windows 11. In most cases, the issue is related to outdated App Installer components, corrupted cache files, damaged system files, or Windows update conflicts.
In this guide, I have mentioned some very simple steps to resolve these issues!
Fix WinGet COM Server High CPU Usage on Windows 10/11
If WinGet COM Server is causing high CPU usage on Windows 10 or Windows 11, follow these steps:
- Restart the WinGet-related processes through Task Manager.
- Update the App Installer application from the Microsoft Store.
- Repair or reset the App Installer package.
- Clear temporary package manager cache files.
- Run System File Checker and DISM scans.
- Update Windows to the latest version.
- Reinstall the App Installer application if necessary.
These solutions help eliminate corrupted files, outdated components, and package manager issues that commonly cause excessive CPU consumption.
Step 1: End the WinGet COM Server Process and Restart Windows
The first thing you should try is restarting the affected process. Temporary glitches can sometimes force the WinGet service into an endless loop, causing excessive CPU consumption.
Go to Taskbar > Right-click Start Button > Task Manager. Then click Processes and look for WinGet COM Server, Windows Package Manager, or any related App Installer process.
Select the process and click End Task.
After ending the process, save your work and restart your computer. Once Windows boots back up, open Task Manager again and monitor CPU usage for a few minutes.
If the CPU usage returns to normal levels, the issue was likely caused by a temporary software glitch. If the problem persists, continue with the next solution.
Step 2: Update the App Installer Application
Since WinGet relies heavily on the App Installer application, running an outdated version can lead to compatibility issues and excessive CPU activity.
Go to Start Menu > Microsoft Store. Then click your Profile Icon and select Downloads and Updates. Next, choose Get Updates to check for available updates.
Allow Microsoft Store to update all pending applications, especially App Installer.
Once the update finishes, restart your computer and observe the CPU usage again.
Microsoft frequently releases fixes for package management components, so updating App Installer often resolves WinGet-related performance issues.
Step 3: Repair the App Installer Package
If the App Installer files become damaged, the WinGet COM Server may repeatedly attempt to access corrupted components, increasing processor usage.
- Go to Start Menu > Settings > Apps > Installed Apps.
- Then locate App Installer in the application list.
- Click the Three-Dot Menu beside App Installer and select Advanced Options.
- Scroll down until you find the Repair option.
- Click Repair and allow Windows to complete the process. This action fixes application files without removing any data.
After the repair is complete, restart your computer and check whether CPU usage has improved.
Step 4: Reset the App Installer Application
If repairing the application does not solve the issue, resetting it may help remove damaged configuration settings.
Go to Settings > Apps > Installed Apps > App Installer > Advanced Options.
Then scroll down and click Reset.
Windows will restore the application to its default state and rebuild configuration files that may have become corrupted.
Once the reset process finishes, restart the system and monitor CPU activity.
Many users find that resetting App Installer eliminates persistent WinGet COM Server resource usage problems.
Step 5: Clear WinGet and Microsoft Store Cache
Corrupted cache files can cause WinGet to repeatedly process the same information, leading to unusually high CPU consumption.
- Go to Start Menu > Search Box and type wsreset.exe.
- Then click Run as Administrator.
- A Command Prompt window will appear briefly while Windows clears the Microsoft Store cache.
- Wait until the Store automatically opens.
- Next, restart your computer and check if the CPU usage has decreased.
Clearing cache files removes outdated package information and forces Windows to create fresh data structures.
Step 6: Run the System File Checker Scan
Damaged Windows system files can affect package management services and trigger performance issues.
- Go to Start Menu > Search > Command Prompt.
- Then select Run as Administrator.
- Type the following command: sfc /scannow
- Press Enter and allow the scan to complete.
The System File Checker will examine protected Windows files and automatically repair damaged components.
The process may take some time depending on your system specifications.
After completion, restart your PC and verify whether WinGet COM Server is still consuming high CPU resources.
Step 7: Repair Windows Image Files Using DISM
If the SFC scan cannot fully repair Windows components, the Deployment Image Servicing and Management tool can help restore system integrity.
Go to Start Menu > Search > Command Prompt > Run as Administrator. Then enter the following command:
DISM /Online /Cleanup-Image /RestoreHealth
Press Enter and wait for the process to finish.
DISM downloads healthy system files from Windows Update and replaces damaged components in the operating system image.
Once the scan is complete, restart your computer and review CPU performance.
This method is especially effective when WinGet issues are caused by deeper operating system corruption.
Step 8: Install the Latest Windows Updates
Microsoft regularly releases fixes that improve Windows Package Manager stability and performance.
Go to Settings > Windows Update. Then click Check for Updates. Download and install all available updates.
After installation, restart your computer and allow Windows to finish configuring updates.
Keeping Windows fully updated ensures that WinGet, App Installer, and related services work with the latest bug fixes and security improvements.
Step 9: Reinstall the App Installer Application
If none of the previous methods work, reinstalling App Installer can completely replace damaged WinGet components.
Go to Start Menu > Windows PowerShell > Run as Administrator.
Then enter the following command:
Get-AppxPackage Microsoft.DesktopAppInstaller | Remove-AppxPackage
Press Enter and wait for the removal process to finish. Next, open the Microsoft Store and search for App Installer.
Install the application again and restart your computer.
A fresh installation often resolves stubborn WinGet COM Server issues caused by corrupted package manager files.
Step 10: Perform a Clean Boot
Third-party applications can sometimes interfere with WinGet operations and create abnormal CPU usage.
Go to Start Menu > Search > System Configuration. Then open System Configuration and select the Services tab. Check Hide All Microsoft Services and click Disable All. Next, open the Startup tab and select Open Task Manager. Disable all startup applications.
Restart the computer and monitor CPU usage.
If the issue disappears, a third-party program is likely causing the conflict. You can then re-enable services gradually to identify the problematic application.
FAQs
Is WinGet COM Server safe?
Yes. WinGet COM Server is a legitimate Windows component associated with the Windows Package Manager. It is developed by Microsoft and is generally safe to run.
Why is WinGet COM Server using 100% CPU?
This usually happens because of corrupted App Installer files, damaged cache data, incomplete updates, or system file corruption.
Can I disable WinGet COM Server?
While you can stop the process temporarily, permanently disabling it is not recommended because it supports application installation and update functions.
Does updating Windows fix WinGet COM Server issues?
Yes. Installing the latest Windows updates often resolves compatibility bugs and package manager problems that contribute to high CPU usage.
Will reinstalling App Installer remove my applications?
No. Reinstalling App Installer only replaces package management components and does not uninstall your installed applications.