Picture the scene: you install a Windows update on Tuesday night, and by Wednesday morning your PDFs are opening in Notepad as gray gibberish. Those .webp images you saved from a design site now launch in a text editor. And if you're really unlucky, a niche extension like .iwi from a game install throws up an endless "How do you want to open this file?" prompt. I've debugged this exact mess for clients for fifteen years, and almost everyone reaches for the same wrong fix: changing the default app in Settings. That's the trap. To truly remove Windows 10 file association for a file extension, you have to clear the recorded user choice — not reassign it to another program. Below are four methods that actually work, and what to do when an association refuses to stay gone.
Understanding Windows 10 File Associations: Change vs Remove
What Is a File Association?
Think of a file association as a phonebook entry. The file extension (.pdf, .txt, .jpg) is the name you look up; the app registered to handle it is the number you dial. When you double-click any file, Windows checks that entry, finds the handler, and passes the file to it.
Under the hood, the shell stores your personal entries in a specific registry area: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts. When you tick "Always use this app" in the Open With dialog, Windows writes a UserChoice value there that records your decision. This is why two accounts on the same PC can open .jpg files in completely different programs — the choice follows the user, not the machine.
A broken association usually announces itself in one of three ways: the wrong app launches, file icons turn blank white, or Windows asks you to pick a program every single time. Each symptom traces back to the same registry tree.
Change vs Remove vs Reset: What Actually Solves the Problem
These three actions get mixed together in forum threads constantly, but they solve different problems.
| Task | What It Does | When to Use | Difficulty |
|---|---|---|---|
| Change | Reassigns one file extension to another installed app | You know which app you want and it's installed | Easy |
| Remove | Deletes the user-chosen default so Windows asks again | An app hijacked the extension and Settings won't let go | Medium |
| Reset | Restores Microsoft's recommended defaults for most file types | Many associations broke at once after a feature update | Easy |
| Most people only need Change. But if you're reading this, you've probably discovered that Settings has no "Remove" button for a file type. You can swap the default around all day, yet the hijacking app keeps coming back. That's when Remove becomes the real answer — and Reset is the blunt instrument you try first when Windows Update wrecks a dozen associations overnight. |
How to Reset File Associations in Windows 10 Using Settings
Reset All File Associations to Microsoft Recommended Defaults
Start with the least invasive fix. Go to Settings > Apps > Default Apps, scroll all the way down, and under "Reset to the Microsoft recommended defaults," click the Reset button.
Here's the catch: this doesn't just fix your one broken extension. It resets your default browser, your default email client, your default music player, and roughly thirty other file type and protocol associations all at once. If you've customized your system over the years, you'll spend a while afterward re-applying preferences.
Before you click, take a screenshot of the Default Apps screen. I can't count how many users have hit Reset and then forgotten which PDF reader they had installed. A quick screenshot saves you twenty minutes of head-scratching later.
Set a Specific Default App by File Type after Reset
Once the reset finishes, you're working with a clean slate. To reapply a preference honestly, use the search box near the top of the Default Apps page — it accepts file types like .pdf or link types like HTTP. Type the exact extension, click the current default, and pick the app you actually want.
But notice what this interface does not offer you. There is no delete option. You can tell Windows "use this app," but you can't tell it "forget you ever saw this file type." For true removal, Settings is a dead end, and that's by design — Microsoft would rather you always have a default than none at all.
Windows 11 Settings Difference
Windows 11 reorganizes the same page so you search by app first, then choose which file types that app claims. The underlying data, however, lives in the same FileExts registry branches on both operating systems. If you master the Windows 10 registry steps in this guide, the skill carries straight over to Windows 11.
Remove Windows 10 File Association with Registry Editor
Back Up FileExts First
I'm going to sound like a broken record here, but export before you edit. Open Registry Editor (press Win + R, type regedit, hit Enter), navigate to the FileExts key, right-click it, and choose Export. Save the .reg file somewhere you'll actually find in a panic — not the Downloads folder.
That backup is your undo button. Registry Editor doesn't have a built-in one, and I remember a 2019 support call where a user deleted one level too high while trying to clean up a misbehaving .mkv association. The exported .reg file was the only thing that brought their shell configuration back. Take the two minutes.
Go to FileExts and Locate Your Extension Key
Copy and paste this path into Registry Editor's address bar, then press Enter:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
Under FileExts, you'll see folders named after every extension Windows has ever seen you open — .txt, .pdf, .zip, and a collection of obscure types you forgot existed. Find the folder matching your problem extension.
Inside each folder, three subkeys matter:
- UserChoice — stores the default app you picked. This overrides everything, including command-line settings.
- OpenWithList — stores apps that appear when you click Open With.
- OpenWithProgids — lists program identifiers that have historically handled this file type.
Delete UserChoice to Remove the Association
Right-click the UserChoice key under your target extension folder and choose Delete. That single action clears the user-level association Windows has been following.
If stale entries remain in the Open With menu — for instance, an app you uninstalled months ago still appears there — delete or clean the OpenWithList and OpenWithProgids subkeys too. For extensions that have been through multiple app changes, I sometimes delete the entire extension folder under FileExts. That wipes all association history for that file type in one clean sweep.
A word of caution: don't go wandering into HKEY_CLASSES_ROOT and delete the matching top-level key unless you're deliberately removing a system-registered file class. That's where users get themselves into serious trouble, because some of those classes are used by Windows components themselves.
Also worth knowing: Windows protects the UserChoice key with a hash-based integrity check, a mechanism it has used since introducing the value many versions ago. You can open the key in Registry Editor and type a different ProgID manually, but if the hash doesn't match, the operating system ignores you. Deleting the key is far more reliable than editing it.
What Happens after Removal
Sign out and sign back in (or restart Explorer if you're in a hurry). Now double-click a file of the type you just cleaned. Windows should hesitate, then ask: "How do you want to open this file?"
This is the moment that tells you the removal worked. Pick another app, tick "Always use this app to open .ext files," or leave the file unassociated. The choice is finally yours.
One honest caveat: extensions registered at the system level, such as .txt or .ini, may fall back to a built-in Microsoft handler even after you delete UserChoice. You'll see Notepad again instead of a prompt. That's expected behavior, not a failed fix.
Remove File Associations Using Command Line or PowerShell in Windows 10
Use assoc .ext= at an Elevated Command Prompt
The command-line route is older than most of the machines running it. Open Command Prompt as Administrator and run the assoc command with an equals sign and nothing after it:
assoc .7z=
This removes the mapping between .7z and the executable class registered for it. You can confirm the result with:
assoc .7z
If removal worked, Windows responds with a message along the lines of "File association not found for extension .7z."
The companion command, ftype, shows you the command line that runs when a registered file type is launched. It's useful when you want to see what an app actually executes behind the scenes.
Here's the limitation that trips people up: if a UserChoice value exists in the registry, that per-user default overrides whatever assoc changes. On a modern Windows 10 machine where you've already chosen a default app through the Open With dialog, assoc often edits the system-level mapping while your user-level choice still wins. Expect this and test with a real file.
PowerShell Equivalent for Automation
PowerShell still ships without a native Remove-FileAssociation cmdlet. If you're scripting this fix across several machines, you have two straightforward options.
First, invoke the classic command from inside PowerShell:
cmd /c assoc .7z=
Second, remove the registry key directly:
Remove-Item -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.7z\UserChoice"
The registry route is faster, but it's also less forgiving. There is no recycle bin for registry keys. Export first, run second.
How to Remove a File Association Without Registry: The Dummy App Trick
Create a Dummy Executable File
This is the workaround I've used more times than I can count, and it's the one volunteers and community experts keep recommending on Microsoft's own Q&A forum. The logic is beautifully simple: associate the stubborn extension with a program that doesn't actually work, then delete that program. Windows is left with a broken reference and no choice but to ask you again.
Start by enabling file name extensions. In File Explorer, click the View ribbon tab and tick File name extensions. Then create a new text file on your desktop and rename it from DummyRemover.txt to DummyRemover.exe. Click through the "you have to confirm the change" warning.
No, it's not a real executable. It doesn't need to be.
Associate Your File Type with the Dummy App
Right-click a file that uses the problem extension and choose Open With > Choose another app. Tick the box that says Always use this app to open .ext files — this step is critical. Scroll down, click More apps, then scroll again and pick Look for another app on this PC. Navigate to your desktop and select DummyRemover.exe.
The file will not open in any meaningful way. That's fine. You're not trying to view the file — you're trying to transfer ownership of the association to a program you control.
Delete the Dummy App and Restart
Delete DummyRemover.exe from your desktop. Now restart your PC — and I mean click Restart, not Shut down followed by pressing the power button. Windows 10's default shutdown behavior uses Fast Startup, a hybrid shutdown that doesn't fully end your session. A proper restart forces the shell to recognize the now-missing program.
After the reboot, double-click your file again. Windows will realize the association points to an executable that no longer exists and ask you what to use instead. That's the removal you were after.
Windows 10 File Association Fix After an Update: Why Defaults Keep Changing
Why Updates and New Apps Hijack File Associations
File association hijacking — when an app quietly reassigns file types to itself — usually follows a predictable pattern:
- An application installs or updates and re-registers its file handlers as part of the setup.
- A Windows feature update resets certain associations to Microsoft defaults while preserving others.
- A multi-user profile migration copies over associations but leaves behind orphaned registry entries.
I've noticed that the hardest cases almost always have one thing in common: an app updater running in the background. Some programs condition their setup to re-assert control over their file extensions on every launch or update, with no visible permission prompt. If you change the default and it reverts by the next reboot, check whether that app is truly closed before you blame Windows.
Cannot Remove Windows 10 File Association? Fix UserChoice and Permissions
| Symptom | Likely Cause | What to Try |
|---|---|---|
| UserChoice reappears after restart | An app updater is re-registering its handler | Remove the association again, then use the dummy app trick |
| Extension can't be changed in Settings | Group Policy or managed profile override | Check for a default associations configuration policy |
| Deleting UserChoice has no visible effect | File has a system-level class registration | Accept the fallback default, or use Reset for the file type |
| Association locked for all accounts | Enterprise management software | Contact your IT administrator; local changes won't stick |
If Windows rewrites UserChoice immediately after you delete it, you're likely dealing with a policy or an aggressive app updater rather than a corrupted registry. Check Group Policy by running gpedit.msc and navigating to Computer Configuration > Administrative Templates > Windows Components > File Explorer. If the policy "Set a default associations configuration file" is enabled, local user changes are fighting a losing battle. |
Prevent Future Default-App Hijacking
The single best habit: when you only want to open one file in a different program, use Open With > Choose another app but don't tick "Always use this app." That one-time override never writes a lasting UserChoice value.
For those managing fleets of machines, export your desired associations to an XML configuration and deploy it through Group Policy. This keeps every managed device aligned and reduces the number of tickets you get after feature updates. Review those policies after each Windows version update, because a new feature update can quietly change how Windows applies them.
Windows 10 File Association Repair Tools vs Manual Fixes: Which Method Is Safer?
When a Free File Association Repair Tool Can Help
Registry editing isn't everyone's idea of a relaxing afternoon. If the Settings reset failed and you want help inspecting your associations, a specialized utility is a reasonable next step.
Two tools I trust in this space are FileTypesMan from NirSoft and Default Programs Editor. FileTypesMan gives you a flat, searchable table of every file type registered on your system, with export and edit options. Default Programs Editor is older and hasn't seen active development in years, so use it with care on recent Windows 10 builds.
Whichever you choose, download it only from the author's official website. Many third-party download portals bundle unwanted software alongside these tiny utilities, and the last thing you need after a file association headache is a toolbar nobody asked for.
Manual Fixes You Can Try First
The practical rule I give every client: export the registry key, make one change, and test with a single sample file before touching the rest.
If the test breaks, restore the exported
.regand reassess. If it works, repeat for the next extension.
No tool can make smart decisions about which app should own a file type. You have to supply that judgment. Manual fixes force you to be deliberate, which is precisely why they're safer for people who are comfortable reading a warning dialog before clicking OK.
Quick Comparison: 5 Ways to Remove a Windows 10 File Association
| Method | Difficulty | Removes One Association | Best For |
|---|---|---|---|
| Settings reset | Easy | No | After a major Windows update breaks many types at once |
| Registry Editor | Medium | Yes | One stubborn extension that keeps reverting |
| Dummy app trick | Easy | Yes | Removing a file type without registry experience |
| Command line / PowerShell | Medium | Partially | Scripting the fix across several machines |
| Third-party repair tool | Low to Medium | Yes | Getting a visual overview before making changes |
FAQ
How do I remove a file association in Windows 10?
Back up the FileExts registry key first. Then open Registry Editor and paste HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts into the address bar. Open the folder matching your extension (like .pdf), right-click the UserChoice key, and select Delete. Sign out and sign back in. If the file still opens in a fallback app, you're dealing with a system-level registration, which the Settings reset is better equipped to handle.
How do I reset all file associations to default in Windows 10?
Open Settings > Apps > Default Apps, scroll to the bottom, and click Reset under "Reset to the Microsoft recommended defaults." This restores Microsoft's standard defaults for most file types and link types at once. Note that it may not clear old entries from your Open With menu — those live in separate OpenWithList subkeys.
Why can't I change file associations in Windows 10?
Most cases come down to one of four causes: an application update re-registers its handlers faster than you can change them, a Group Policy object overrides local user choices, the protected UserChoice key has been manually edited and Windows now ignores it, or the association is managed by a different user profile. Work through those in order and you'll usually find the culprit.
Can I delete a file association from the Windows 10 registry?
Yes. Export the FileExts key first, then delete the UserChoice subkey under the extension you want to clean. If Windows recreates the key after a reboot, investigate whether an app updater or a managed policy is rewriting it. The dummy app trick works well in those resistant cases.
How do I restore file associations after a Windows 10 update?
Run Settings > Apps > Default Apps and click Reset. Then reapply your important defaults by file type using the search box at the top of the page. If associations keep resetting after every update, clean out the FileExts subkeys for the affected extensions, then use the dummy app trick to create a clean slate.
Which Method Is Right for You?
Removing a Windows 10 file association is ultimately about removing a user choice — not just shuffling defaults around. Start with the Settings reset when Windows Update caused widespread chaos. Turn to Registry Editor when one specific extension keeps landing in the wrong app. And when the registry fight feels futile, remember the dummy app trick: sometimes the most reliable tool is a file named DummyRemover.exe that does absolutely nothing.
Always export before you edit. Always test with a real file. And if your associations keep changing after every update, combine the dummy app removal with the Settings reset, then take a hard look at which applications you've allowed to run and update in the background.
Which Windows 10 file association were you trying to remove? Tell us in the comments — and include your Windows build number (press Win + R, type winver) if you want a more targeted fix.