winget — the Windows Package Manager — is one of the best tools Microsoft has added in recent years. It lets us install apps, upgrade software, and manage packages straight from the command line. But sometimes, Windows throws an annoying error: ‘winget’ is not recognized as an internal or external command
This happens when Windows can’t locate the winget executable or the package manager isn’t properly installed. The good news? It’s easy to fix.
In this guide, we’ll walk you through all the reasons why this error appears — and all the ways to fix it step by step.
1. Update or Reinstall the App Installer Package (Most Common Fix)
Winget is part of the App Installer package. If App Installer is outdated or corrupted, winget won’t work.
1. Update from Microsoft Store
- Open the Microsoft Store.
- Click Library in the bottom-left corner.
- Click Get updates.
- Make sure App Installer gets updated.
2. Reinstall App Installer (If Update Doesn’t Fix It)
- Open this link:
ms-windows-store://pdp/?productid=9NBLGGH4NNS1 - Click Get to reinstall the package.
After installing, reopen Command Prompt or PowerShell and run:
winget
If App Installer was the problem, winget should now work perfectly.
2. Make Sure You Are on Windows 10/11 Version That Supports Winget
Winget works only on:
- Windows 10 version 1809 or later
- Windows 11 (all versions)
To check your Windows version:
- Press Win + R, type winver, and hit Enter.
If you’re on an older build, simply updating Windows will add winget.
Update Windows
- Press Win + I to open Settings.
- Go to Windows Update.
- Click Check for updates.
When Windows installs the latest build, winget becomes available automatically.
3. Make Sure Winget Is Added to PATH
If winget exists on your system but Windows can’t find it, your PATH environment variable may be missing the location.
Winget is stored here:
C:\Users\<YourUserName>\AppData\Local\Microsoft\WindowsApps
Check PATH:
- Press Win + I → System → About.
- Click Advanced system settings.
- Click Environment Variables.
- Under User variables, select Path and click Edit.
- Make sure this path exists:
C:\Users\<YourUserName>\AppData\Local\Microsoft\WindowsApps
If it’s missing, click New and paste it in.
Restart Command Prompt and try again:
winget
4. Sign Out and Sign Back In (Winget Activation Fix)
Sometimes winget won’t register until you refresh your user session.
- Click the Start Menu.
- Choose your profile icon.
- Click Sign out.
- Log back in and retry the command.
This simple step often fixes PATH and App Installer activation issues.
5. Enable the Microsoft Store Background Services
If your Store services are disabled, Windows won’t load the winget package.
Check the services:
- Press Win + R, type services.msc, and press Enter.
- Find these services:
- Microsoft Store Install Service
- Windows Update
- Background Intelligent Transfer Service (BITS)
- Make sure all of them are Running and Set to Automatic.
Restart winget after enabling these services.
6. Reset or Repair the App Installer Package
If App Installer is corrupted, repairing may fix the issue.
Repair App Installer
- Press Win + I to open Settings.
- Go to Apps > Installed apps.
- Search for App Installer.
- Click the three dots → Advanced options.
- Click Repair.
If that doesn’t help:
6. Click Reset.
After this, test winget again.
7. Use PowerShell to Reinstall Winget Manually (Advanced Fix)
If nothing works, you can reinstall Winget using PowerShell and the GitHub package files.
Download the latest Winget bundle
- Visit the official Windows Package Manager GitHub releases:
https://github.com/microsoft/winget-cli/releases - Download the latest .msixbundle for App Installer.
Install it
- Right-click the downloaded
.msixbundle. - Select Install.
Alternatively, use PowerShell:
Add-AppxPackage -Path "C:\Path\To\AppInstaller.msixbundle"
Winget will now be restored.
8. Verify Winget Installation
To confirm everything is working, run:
winget --version
If you see something like:
v1.7.10871
— then winget is installed correctly.
Why “winget is not recognized” Happens
To summarize, the error usually appears because:
- App Installer is outdated or missing
- PATH variable is broken
- Windows is outdated
- User session hasn’t refreshed
- Winget package failed to install
- Store background services are disabled
The steps above fix all of these issues.
Wrapping Up
Winget is one of the most useful Windows tools, and it can be frustrating when Windows says it isn’t recognized. Fortunately, the fix is usually simple — updating App Installer, repairing the package, or restoring the correct PATH entry.
Once winget is working, you can quickly install apps, upgrade software, or automate your Windows setup with just a few commands.
