Fix: Windows Still Thinks an App Is Installed After You Deleted It
Why Windows Still Thinks Your App Is Installed
We've all been there. You were younger, maybe not yet familiar with how Windows handles software, and you did what seemed perfectly logical , the program's folder was right there in C:\Program Files, so you selected it all and hit Delete. Gone. Done. Or so you thought.
Here's the thing: Windows doesn't actually track whether a program is installed by watching its folder. It tracks installations through a completely separate system , the Windows Registry and the Windows Installer database. When you used a proper installer to put that program on your machine, it wrote dozens (sometimes hundreds) of entries into the registry, recorded itself in the Programs and Features list, scattered files into %AppData%, %LocalAppData%, and %ProgramData%, and possibly even registered itself as a Windows service or shell extension. Deleting the main program folder removes maybe 60–70% of the footprint. The rest is still there, scattered across the system.
So now when you try to reinstall that program, one of a few things happens. The installer throws an error like "Another version of this product is already installed" or "This product is already installed" and refuses to continue. Or the installer appears to run fine but the program behaves strangely because it's picking up old, corrupt configuration data from your AppData folders. Or you open Settings → Apps → Installed Apps and the program still appears in the list, clicking "Uninstall" gives you an error because the uninstall executable no longer exists at the path Windows is pointing to.
I've seen this exact scenario on dozens of machines, sometimes from users doing what you did, sometimes from botched corporate deployment scripts or antivirus tools that delete files without going through the proper uninstall chain. The root causes always come down to the same three things:
- Orphaned registry keys under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\that still tell Windows the program is present - Windows Installer product records, if the original installer used MSI technology, a separate installer database entry remains in the Windows Installer service
- Leftover user data folders in AppData or ProgramData that a new installer detects and treats as a pre-existing installation
The good news: every single one of these is fixable without reinstalling Windows, without any paid tools, and without losing other programs or data. The process requires a bit of registry editing, which sounds scary, but I'll walk you through it step by step with exact paths and screenshots so nothing goes wrong. Browse all Microsoft fix guides →
Before we get into manual steps, though, let's try the easiest path first, Microsoft actually ships a dedicated troubleshooter for exactly this problem.
The Quick Fix, Try This First
Microsoft quietly maintains a tool called the Program Install and Uninstall Troubleshooter. It's not built into Windows Settings, you have to download it separately, but it's an official Microsoft tool and it's legitimately the fastest way to clear a stuck Windows app entry without touching the registry yourself.
Here's what to do. Open your browser and go to Microsoft's Program Install and Uninstall Troubleshooter page. Scroll down until you see the blue "Download troubleshooter" button and click it. The file that downloads is called MicrosoftProgram_Install_and_Uninstall.meta.diagcab, double-click it to run.
The troubleshooter opens with two choices: Installing or Uninstalling. Pick Uninstalling. On the next screen, it will scan your system and show you a list of all programs it detects, including orphaned entries where the files are already gone. Find the program you manually deleted in the list. If it appears there, select it and click Next. The tool will then ask if you want to remove the traces of this program. Choose "Yes, try to uninstall".
In most cases, especially for programs that originally used a standard MSI installer, this clears everything in about 30 seconds. The entry disappears from Apps & Features, the registry keys are removed, and you can proceed directly to reinstalling. Try your reinstall immediately after the troubleshooter finishes.
If the program doesn't appear in the troubleshooter's list, or the reinstall still fails afterward, don't worry, that just means the program used a non-MSI installer (many games and creative apps do this) and you'll need to clean things up manually. The steps below cover that completely.
This is the core of the whole problem. Windows keeps its list of installed programs, the same list you see in Settings → Apps, in the registry, and that's exactly where we need to go to remove the stuck entry. Don't let "registry editor" intimidate you; we're doing a targeted removal of one specific key, not a general cleanup.
Press Win + R, type regedit, and press Enter. If User Account Control prompts you, click Yes. Registry Editor opens. Now press Ctrl + F to open the Find dialog. Type the name of the program (or part of it, the first distinctive word is fine) and make sure Keys, Values, and Data are all checked. Click Find Next.
The main place to look manually is this path, navigate here using the left-hand tree:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallIf you're on a 64-bit version of Windows (almost certainly yes if you're running Windows 10 or 11), also check here for 32-bit programs:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\UninstallAnd for per-user installs (some apps install just for one user account):
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallUnder the Uninstall key you'll see a long list of subkeys, each one represents an installed program. Some have human-readable names like VLC media player. Others show a GUID like {90150000-0115-0409-0000-0000000FF1CE}, that's how MSI-based installs identify themselves. Click through them until you find the one matching your deleted program. Look at the DisplayName value on the right side, that's the friendly name shown in Apps & Features. When you find it, leave this window open and move to Step 2 before deleting anything.
If the search finds nothing in these paths, that's actually good news, it means the registry is already clean and your reinstall issue is coming from leftover AppData files, which we handle in Step 4.
Before you delete anything from the registry, take 60 seconds to export the key. This gives you a complete safety net, if something goes wrong, you can restore the entry by double-clicking the backup file.
Right-click on the subkey for your program in the left pane and select Export. In the Save dialog, choose a location you'll remember (Desktop is fine) and give the file a name like AppName-uninstall-backup.reg. Click Save. That's your insurance policy. Now right-click the same key again and select Delete. Windows will ask you to confirm, click Yes.
After deleting, open Settings → Apps → Installed Apps (on Windows 11) or Control Panel → Programs → Programs and Features (on Windows 10 or if you prefer the classic view). Refresh the list, the program should be gone. If it's still there, that means there's a second registry entry under one of the other Uninstall paths mentioned in Step 1. Go back and check all three locations.
One thing I want to be clear about: you are only deleting the uninstall record for this specific program. You are not touching anything that belongs to Windows itself or any other software. As long as you identified the correct subkey in Step 1, this operation is completely safe. If you're ever uncertain, look at the InstallLocation value in the right pane, it will show the original install path like C:\Program Files\ProgramName\, which makes it easy to confirm you have the right key.
Once the entry is removed from Apps & Features, try launching your installer again. If it still complains about an existing installation, continue to Step 3, there may be a Windows Installer product record that needs separate handling.
Programs installed with MSI technology, which includes most software from large vendors, virtually all Microsoft products, and many enterprise applications, register themselves not just in the Uninstall key but also in the Windows Installer's own product database. Simply deleting the Uninstall key doesn't touch this second record, and it can cause new installers to refuse to proceed.
First, find out if your program has a product code. In Registry Editor, navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\ProductsThis shows every MSI product ever registered on this machine for the system account. You can also check:
HKEY_CLASSES_ROOT\Installer\ProductsSearch (Ctrl+F) for the program name in the Data column. When you find the matching subkey, note the alphanumeric string that is its key name, that's the packed GUID for the product.
Alternatively, if you can find the original MSI file or the installer still runs, you can pull the product GUID more easily. Open PowerShell as Administrator (right-click Start → Windows PowerShell (Admin) or Terminal (Admin)) and run:
Get-WmiObject -Class Win32_Product | Select-Object Name, IdentifyingNumber | Sort-Object NameThis lists all MSI-registered products with their GUIDs (in standard {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} format). If your program appears here, copy the IdentifyingNumber. Then run:
msiexec /x {PASTE-YOUR-GUID-HERE} /qnThe /x flag tells Windows Installer to uninstall by product code, and /qn runs it silently. Even though the files are already deleted, Windows Installer can still clear its own product record. After this command completes, the entry should be fully gone. A successful run produces no output, it just returns you to the prompt. If it errors with Error 1605 ("This action is only valid for products that are currently installed"), the Windows Installer database is already clean and your issue is coming from somewhere else.
Even with the registry fully cleaned, many installers will detect leftover configuration folders from the previous installation and either refuse to install or enter a broken state where settings from the old install bleed into the new one. This is especially common with games, Adobe products, JetBrains IDEs, and any software that stores license data in AppData.
Open File Explorer and paste each of these paths into the address bar one at a time, pressing Enter to navigate there:
%APPDATA%%LOCALAPPDATA%%PROGRAMDATA%In each location, look for a folder named after the program or its publisher and delete it if present. For example, if you deleted Adobe Premiere Pro, you might find Adobe folders in all three locations. If it was a game from Steam or Epic, look for both the game's name and the publisher's name as separate folders.
A few things to keep in mind. First, %APPDATA% expands to C:\Users\YourUsername\AppData\Roaming, this is where most programs store settings that should "roam" with a user account. Second, %LOCALAPPDATA% is C:\Users\YourUsername\AppData\Local, this is where programs typically store cache data, crash logs, and local-only configuration. Third, %PROGRAMDATA% is C:\ProgramData and is shared across all user accounts on the machine, this is where system-wide program data lives, including license files.
If you want to be thorough, also check for any remaining files in the Windows Installer cache folder:
C:\Windows\InstallerThis folder holds the cached MSI packages and patches. Don't delete anything from here randomly, it contains installer data for all your other programs too. But if you see a file that clearly belongs to the program you removed (you can right-click any .msi file → Properties → Details to see the product name), you can safely delete it.
After clearing the AppData folders, your system should now have no memory whatsoever of the old installation. Move on to Step 5 to verify and reinstall.
Before running the installer, do a final check to make sure everything is actually clean. Open PowerShell as Administrator and run this to confirm no registry entries remain:
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* |
Where-Object { $_.DisplayName -like "*YourProgramName*" } |
Select-Object DisplayName, InstallLocationReplace YourProgramName with the actual name (or a distinctive part of it). If no results come back, the registry is clean. Also run it against the WOW6432Node path:
Get-ItemProperty "HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" |
Where-Object { $_.DisplayName -like "*YourProgramName*" } |
Select-Object DisplayName, InstallLocationClean results on both? Good. Now restart your computer. I know I already mentioned this, but it genuinely matters, Windows Installer caches product state information in memory, and a reboot flushes that cache completely. You want a totally clean start for the installer to work against.
After the reboot, run your installer as Administrator, right-click the installer executable and choose Run as administrator, even if you're already logged in as an admin. This gives the installer the elevated token it needs to write to Program Files and the registry without any permission-related failures.
The installer should now proceed without any "already installed" errors. If it still fails, check the installer's own log file, most installers write a log to %TEMP% (navigate there with Win+R, type %TEMP%). Look for a file with a name like ProgramName_install.log or a file with today's date. The log will usually tell you exactly what it found that caused the failure, which points you to the exact cleanup still needed.
Advanced Troubleshooting
If the steps above haven't solved it, the problem is almost certainly one of a few deeper issues. Let me walk you through what to check.
Reading Event Viewer for Installer Errors
When an installer fails, Windows almost always logs why. Press Win + R, type eventvwr.msc, and press Enter. Navigate to Windows Logs → Application. Look for events with Source = MsiInstaller. The key event IDs to focus on are:
- Event ID 11708, Installation operation failed. The Data field contains the product name and the specific error code.
- Event ID 1033, Windows Installer started an install. Useful for confirming the installer is actually running.
- Event ID 11719, Windows Installer removed an outdated installer service. Means the installer database had stale entries that Windows already cleaned up.
The error description in Event ID 11708 is often the Rosetta Stone for what's still blocking you. Error code 1603 means a fatal installation error, usually a file permission problem. Error code 1619 means the installer package itself can't be opened. Error code 1638 is the one that specifically means "another version is already installed", if you're still seeing 1638 after all the above steps, there's a registry key somewhere you haven't found yet.
Group Policy and Enterprise Environments
If you're on a domain-joined machine, a computer managed by your employer or school's IT department, Group Policy may be actively controlling which applications can be installed. Even if you clean up the registry perfectly, a Group Policy Object (GPO) can prevent certain installers from running at all, or it might push the application back down to your machine automatically. Check with your IT department before spending hours troubleshooting what might be a policy decision, not a local software conflict.
You can see what policies are applied to your machine by running this in an elevated command prompt:
gpresult /h C:\gpreport.htmlOpen C:\gpreport.html in a browser and look under Computer Configuration → Software Settings for any software installation policies related to your program.
Checking for Residual Services and Scheduled Tasks
Some programs, particularly VPNs, antivirus tools, backup software, and system utilities, install Windows Services and Scheduled Tasks that survive file deletion. These can interfere with reinstallation. Open Services (Win+R → services.msc) and look for any service referencing your program's name. If you find one, right-click → Properties → set Startup type to Disabled, then try the reinstall. Similarly, open Task Scheduler (Win+R → taskschd.msc) and check the Task Scheduler Library for any tasks referencing the old program.
Using Sysinternals Autoruns
Microsoft's free Sysinternals Autoruns tool (available from Microsoft's official Sysinternals suite page) is the most thorough way to find every single place a program embedded itself into Windows startup, registry run keys, scheduled tasks, services, browser extensions, shell extensions, and more. Run it with Administrator privileges, press Ctrl+F to search for the program name, and it will highlight every remaining reference. You can right-click any entry and choose Delete to remove it.
msiexec /unregister and msiexec /regserver repair sequence against the Installer service itself, which resets the entire database. It's not something I'd recommend doing blindly without support, because it affects every MSI-installed program on your machine.
Prevention & Best Practices
Now that you've gone through the work of cleaning this up manually, let's make sure you never have to do it again. The core lesson is that Windows applications are not self-contained, they spread themselves across multiple locations on your system during installation, and undoing that spread requires going through proper channels. Here's how to handle this right going forward.
Always use the official uninstaller first. Every program that installs via an installer writes its uninstall path into the registry. You can find it in Settings → Apps → Installed Apps (Windows 11) or Control Panel → Programs and Features (Windows 10). Click the three-dot menu next to the program and choose Uninstall. Windows will call the program's own uninstaller, which knows exactly where it put everything. This is always the right first step, even before any third-party tool.
Use a dedicated uninstaller utility for stubborn removals. Tools like Revo Uninstaller (free tier is fine for most uses) run the program's own uninstaller first, then scan for leftover registry entries and files and let you review them before deleting. This covers the gap between what the official uninstaller removes and what it leaves behind. It's not necessary for every uninstall, but it's invaluable when dealing with software that has a reputation for leaving junk behind, game launchers, creative suites, security software.
Know what you're deleting before you delete it. If you encounter a program folder in C:\Program Files that you want to remove, first check whether it shows up in Apps & Features. If it does, uninstall it through the proper channel. If it doesn't appear there, the files might have been left behind by a previous (and already logged) uninstall, at that point, manual deletion of just that folder is usually fine.
Create a System Restore point before major software changes. Press Win+R, type SystemPropertiesProtection, and click Create on the System Protection tab. This gives you a one-click rollback if something goes sideways during an install or uninstall sequence. It takes about 90 seconds and has saved me countless hours over the years.
- Always uninstall through Settings → Apps or Control Panel, never by deleting folders directly
- Run Revo Uninstaller or similar after removing programs with messy reputations (game launchers, Adobe CC, etc.)
- Create a System Restore point before installing any major software so you have a clean rollback option
- If an uninstaller fails mid-run, use Microsoft's Program Install and Uninstall Troubleshooter immediately, before trying anything else
Frequently Asked Questions
Why does Windows still show a program in Apps & Features after I deleted all the files?
Windows doesn't track installed programs by watching their folders, it tracks them through registry entries written during installation, specifically under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\. When you deleted the files manually, those registry entries were untouched, so Windows still "sees" the program as installed. The entry in Apps & Features is just Windows reading those registry keys and displaying them, remove the keys and the entry disappears. That's exactly what Steps 1 and 2 in this guide walk you through.
Is it safe to edit the registry? What if I accidentally delete the wrong key?
Editing the registry is safe when you're making targeted, specific changes, and completely within your ability to do correctly by following the steps in this guide. The risk comes from random or broad deletions. That's why Step 2 has you export a backup of the key before deleting it: if you realize you deleted the wrong thing, just double-click the .reg backup file you exported and Windows will restore it instantly. The uninstall registry keys we're targeting only control the Apps & Features list, removing one does not affect any other program on your machine, and it absolutely does not affect Windows itself.
My reinstaller says "Another version of this product is already installed" even after I cleaned the registry. What's left?
That specific error message, which corresponds to Windows Installer error code 1638, means the Windows Installer service still has a product record for the program, separate from the standard Uninstall registry key. This is the Windows Installer database, not the regular registry. The fix is to run msiexec /x {PRODUCT-GUID} /qn from an elevated PowerShell window, where the GUID comes from Get-WmiObject -Class Win32_Product. Step 3 in this guide covers this exact scenario in detail. If the GUID doesn't appear in Win32_Product, try Microsoft's Program Install and Uninstall Troubleshooter, which can forcibly clear corrupt Installer database records.
Can I just use a third-party uninstaller like Revo or IObit instead of doing this manually?
Absolutely, and for most cases, a tool like Revo Uninstaller is actually the faster path. Revo's "Forced Uninstall" mode is specifically designed for situations where the original uninstaller is gone: it scans the registry for any entries containing the program's name, lets you review them, and removes them. The manual steps in this guide are here for people who want to understand what's happening or who need a no-cost, no-download approach. If you're comfortable installing Revo and trust it, the Forced Uninstall feature there will accomplish everything in Steps 1 through 4 in a single workflow. Just make sure you're downloading from the official Revo site, there are fake "Revo Uninstaller" pages that bundle adware.
Do I need to restart Windows after removing the registry entry?
Technically no, for most cases, removing the registry key and refreshing Apps & Features is enough to proceed. But I strongly recommend restarting before attempting the reinstall, not after the cleanup. Windows Installer holds an in-memory cache of product state information, and a reboot clears that cache completely. Without a reboot, there's a meaningful chance the installer checks cached state rather than the freshly cleaned registry, still finds the old product record in memory, and throws the same "already installed" error. The 90 seconds the reboot costs is worth it.
I found the registry key for my program but the Uninstall path inside it points to a file that no longer exists, can I just leave it there?
No, that's actually exactly the problem you need to fix. When an entry has an UninstallString pointing to a missing file, clicking "Uninstall" in Apps & Features will throw an error and nothing will happen. Windows won't automatically clean up that entry. More importantly, if you try to reinstall the program, the installer may detect this broken entry and refuse to install, it sees "this product is registered" without realizing the uninstaller is gone. You need to delete that registry subkey (following the backup-first approach in Step 2) to clear the path for a clean reinstall. A broken uninstall entry left in place will continue to cause problems.