How to Uninstall and Reinstall Chrome on Windows 11 Using Winget CMD

Google Chrome, the most popular browser on Windows, occasionally encounters performance issues that can hinder user experience. Problems such as corrupted profiles, extension conflicts, broken updates, and crashes can render the browser nearly unusable. While standard troubleshooting methods may suffice in some cases, a complete uninstall and reinstall often provides the quickest solution. Enter the Windows Package Manager, or Winget, which offers a command-line approach to streamline this process in mere seconds.

Quick Answer

To uninstall and reinstall Chrome on Windows 11 using Winget, start by opening Terminal as an administrator. Execute the command winget uninstall Google.Chrome to remove the browser. Once the uninstallation is complete, run winget install Google.Chrome to install a fresh copy. For a clean reinstall, ensure you delete the leftover Chrome user data folder located at %LocalAppData%GoogleChrome between the uninstall and reinstall steps.

Command Summary

Action	Command
Check installed version	winget list Google.Chrome
Uninstall Chrome	winget uninstall Google.Chrome
Verify removal	winget list Google.Chrome
Reinstall Chrome	winget install Google.Chrome
Silent install (no prompts)	winget install Google.Chrome –silent
Delete leftover data	rmdir /s /q “%LocalAppData%GoogleChrome”

Why Use Winget to Reinstall Chrome?

While it is possible to uninstall Chrome via the Settings app or Control Panel, Winget presents several advantages that can be particularly beneficial:

• Speed: Two commands can replace the lengthy process of multiple clicks and downloads, especially useful when Chrome is unresponsive.
• Scripting and automation: For those managing multiple PCs, Winget commands can be integrated into PowerShell scripts or deployment tools, facilitating repeatable installations.
• Remote management: When troubleshooting remotely, executing a command is far simpler than navigating unfamiliar interfaces.
• Consistent results: Winget ensures the latest stable version is downloaded directly from its curated repository, avoiding potential pitfalls of third-party downloads.
• Enterprise deployments: IT teams can seamlessly incorporate Chrome installation into existing scripts without the need for additional package managers.

However, it’s worth noting that Winget may not be the ideal choice for everyone. If command-line interfaces are daunting or if a quick fix is needed on a single machine, the graphical method through Settings remains effective.

Things You Should Check

Before executing any commands, consider the following:

• Winget availability: Ensure Winget is pre-installed on your Windows 11 version. If missing or outdated, install or update it from the Microsoft Store. Verify by running winget --version in Terminal.
• Administrator privileges: Uninstalling system-wide applications requires elevated permissions. Right-click the Terminal icon and select Run as administrator.
• Backup your data: If you wish to retain bookmarks, saved passwords, or extensions, ensure Chrome Sync is activated and synced to your Google account before proceeding. A standard Winget uninstall preserves profile data, but a clean reinstall will delete it.

Important: Close Chrome completely before running the uninstall command. Active Chrome processes may impede the uninstallation, leading to potential failures. Check Task Manager (Ctrl + Shift + Esc) to terminate any lingering processes.

Step 1: Check the Installed Chrome Version

Before proceeding with the uninstallation, confirm that Winget recognizes Chrome on your system. This step also reveals the currently installed version, which is useful for later verification.

Open Windows Terminal as administrator and execute:

winget list Google.Chrome

If Winget returns no results, Chrome may have been installed through a method not tracked by Winget, such as an enterprise MSI deployment. In such cases, broaden your search with:

winget list --name Chrome

This command will identify any package with “Chrome” in its name, including Chrome Beta or other Chromium-based browsers. Make note of the exact package ID for the next step.

Step 2: Uninstall Chrome Using Winget

With Chrome confirmed in Winget’s list, proceed to run the uninstall command:

winget uninstall Google.Chrome

Winget will locate Chrome’s native uninstaller and execute it, typically completing the process within 10 to 15 seconds. For a silent uninstall without prompts, use:

winget uninstall Google.Chrome --silent

Note that a standard uninstall retains your Chrome user data folder, which includes bookmarks, browsing history, saved passwords, and extension data stored at %LocalAppData%GoogleChromeUser Data. This design allows your profile to resume where it left off upon reinstallation.

Step 3: Verify Chrome Was Removed

To confirm the uninstallation was successful, run the list command again:

winget list Google.Chrome

If the uninstall was successful, Winget should return no results. You can also check the Start menu and the Apps section in Settings to ensure Chrome is no longer present.

If Chrome still appears in the list, it likely means the uninstall process was interrupted or Chrome processes were still running. Terminate any remaining processes and attempt the uninstall again:

taskkill /IM chrome.exe /F

winget uninstall Google.Chrome --force

Step 4: Reinstall Chrome Using Winget

Now, install a fresh copy of Chrome:

winget install Google.Chrome

Winget will download the latest stable release from the official source and run the installer, typically completing within 30 to 60 seconds, depending on your internet connection. Once finished, Chrome will be accessible from your Start menu and taskbar.

Launch Chrome and verify the version at chrome://settings/help to ensure you are running the latest build. If your Google account sync was active prior to the uninstall, signing in will automatically restore your bookmarks, passwords, extensions, and other synced data.

Optional: Silent Install Command

For scripting or unattended deployments, the silent flag suppresses all installer dialogs:

winget install Google.Chrome --silent

This command can be combined with additional parameters for enterprise scenarios:

winget install Google.Chrome --silent --accept-package-agreements --accept-source-agreements

This variant bypasses all confirmation prompts, making it suitable for batch scripts, deployment pipelines, or remote installations where user interaction is not feasible.

Clean Reinstall: Removing Leftover Chrome Data

A standard uninstall and reinstall retains existing profile data, which is generally desirable. However, if you are troubleshooting issues like a corrupted profile, persistent crashes, or malware-related problems, a clean reinstall is advisable.

What Gets Left Behind After a Standard Uninstall

Even after Winget removes Chrome, the following data remains on disk:

• Bookmarks, browsing history, and download records
• Saved passwords and autofill data
• Cookies and site permissions
• Extension files and their settings
• Cache files and service worker data
• Custom flags and experimental settings

All of this data resides in a single folder. Deleting it allows for a truly fresh start.

How to Perform a Clean Reinstall

1. After uninstalling Chrome using the Winget command mentioned earlier.
2. Open File Explorer and navigate to: %LocalAppData%GoogleChrome
3. Delete the entire Chrome folder.
4. Alternatively, run this from an elevated command prompt:

winget list --name Chrome

0

• Optionally, also remove the registry entries. Open Registry Editor and delete:

winget list --name Chrome

1

• Reinstall Chrome with: winget install Google.Chrome

Data loss warning: Deleting the Chrome user data folder will permanently remove all locally stored bookmarks, passwords, history, and extension data. Ensure Chrome Sync is enabled before proceeding, as this data will be unrecoverable if not.

In instances where a corrupted Preferences file or a broken extension database leads to Chrome crashing on launch, a clean reinstall often resolves the issue when other methods fail. If Chrome is crashing before you can access settings, this approach is worth considering.

---

Winget vs Control Panel: Uninstall Method Comparison

Both methods effectively achieve the desired outcome. The appropriate choice hinges on your specific situation and comfort level.

Feature	Winget (CLI)	Settings / Control Panel	Winner
Speed	~10 seconds per command	~1-2 minutes with clicks	Winget
Scriptable	Yes, fully automatable	No	Winget
Requires browser	No	Yes, to re-download	Winget
Ease of use	Requires CLI knowledge	Familiar GUI workflow	Settings
Remote management	Ideal for remote/SSH	Requires screen sharing	Winget
Enterprise deployment	Fits into existing pipelines	Manual per-machine process	Winget
Removes user data	No (same as GUI)	No (optional checkbox)	Tie
Available on all Windows 11	Yes, via App Installer	Yes, all versions	Tie

For single-machine, one-time fixes, either method suffices. However, for scenarios involving multiple machines, scripting, or remote troubleshooting, Winget clearly stands out as the superior tool.

Troubleshooting Winget Errors

While Winget is generally reliable, certain common issues may arise. Here’s how to address them:

“No installed package found matching input criteria”

This message typically indicates that Chrome was installed outside of Winget’s tracking, such as via a direct .exe download. To resolve this, try:

winget list --name Chrome

If it still does not appear, resort to the Settings app for uninstallation, then utilize Winget for the reinstall.

“The operation was blocked by Windows Installer”

This error may occur if another installer or Windows Update process is active. Wait a moment and retry. Alternatively, restart the Windows Installer service:

winget list --name Chrome

3

winget list --name Chrome

4

“Winget is not recognized as a command”

Your Windows build might be outdated, or the App Installer package could be missing. To rectify this:

1. Open the Microsoft Store.
2. Search for “App Installer” and install or update it.
3. Restart Terminal and run winget --version to confirm.

Uninstall Hangs or Chrome Processes Block Removal

Chrome may continue running background processes. To address this, force-close all instances:

taskkill /IM chrome.exe /F

Winget Source Errors or Stale Cache

If Winget cannot locate Chrome in its repository, reset the source:

winget list --name Chrome

6

This action refreshes the package index from Microsoft’s servers, resolving most repository-related issues.

Installation Fails with Access Denied

Ensure you are running Terminal as an administrator, as Winget requires elevated privileges for system-wide installations. Right-click Terminal and select “Run as administrator” before retrying.

Frequently Asked Questions

Does uninstalling Chrome with Winget delete my bookmarks and passwords? No. A standard Winget uninstall removes the Chrome application but retains your user data folder at %LocalAppData%GoogleChromeUser Data.

Can I use Winget to install a specific version of Chrome? Winget supports version-specific installs with the –version flag, though Google’s repository typically only contains the latest stable release.

Is Winget pre-installed on Windows 11? Yes. Winget comes pre-installed with all versions of Windows 11 as part of the App Installer package.

What is the difference between Winget uninstall and a clean reinstall? A standard Winget uninstall removes Chrome’s program files but preserves user data. A clean reinstall requires deleting the Chrome user data folder for a fresh start.

Can I use Winget to reinstall Chrome on multiple PCs at once? Yes. Winget commands can be included in a PowerShell script for deployment across multiple machines.

Will Chrome set itself as the default browser after reinstalling with Winget? No. Windows 11 does not permit applications to set themselves as the default browser during installation.

What happens if Winget fails to uninstall Chrome? If the Winget uninstall command fails, try force-closing all Chrome processes and rerun the command with the --force flag. If it still fails, use the Settings app for removal and then Winget for the reinstall.