File Associations Reset After Windows Update? Fix It Here
After a Windows update, your PDFs open in Notepad and JPGs in Paint. Here's how to fix it fast.
Why This Happens
Windows updates—especially feature updates like 22H2 or 23H2—sometimes nuke your file associations. It's not a bug, it's a feature: Microsoft likes to "refresh" defaults during big updates. I had a client last month whose entire print queue died because of this, but that's another story. Here, you're looking at PDFs opening in Notepad or JPGs opening in Paint. Annoying, but fixable.
Fix 1: The 30-Second Fix — Use the Right-Click Menu
This works for one file type at a time. If you only have a couple broken associations, start here.
- Right-click the file (say, a .pdf) and select Open with.
- Choose the app you want (like Adobe Reader or Edge).
- Check the box that says Always use this app to open .pdf files.
- Click OK.
That's it. Repeat for each file type. For .jpg, right-click a JPEG, pick Photos, check the box. Done.
When this works: Only a handful of file types got reset. If every single file type is broken, skip to Fix 2.
Fix 2: The 5-Minute Fix — Reset Default Apps via Settings
If you've got a dozen broken types, use the Settings app. This is the built-in way Microsoft wants you to do it.
- Open Settings (Win + I).
- Go to Apps > Default apps.
- Search for the app you want to set as default, like Photos.
- Click the app, then scroll through the list of file types it can handle. Click each one that's wrong and pick the correct app.
Real-world tip: This is tedious if you have 20+ file types. But it's reliable. I had a client whose entire Office file set got reset—Word docs opened in Notepad. We did this for .docx, .xlsx, .pptx, plus .pdf, .jpg, .png. Took about 4 minutes.
If this doesn't work: The update might have corrupted the default apps database. Move to Fix 3.
Fix 3: The 15+ Minute Fix — Reset Default Apps Database via Registry
This is for when Windows stubbornly refuses to save your choices. You set an app as default, it reverts immediately. Happens after a botched update.
Back up your registry first. I've seen people skip this and regret it. Press Win + R, type regedit, hit Enter. In Registry Editor, click File > Export, save a full backup.
- Navigate to
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts. - Delete the .pdf subkey (or any extension that's broken). Right-click it, choose Delete.
- Close Registry Editor.
- Open a Command Prompt as Administrator (right-click Start, choose Command Prompt (Admin) or Windows Terminal (Admin)).
- Run this command:
assoc .pdf=AcroExch.Document.DC(replaceAcroExch.Document.DCwith the correct ProgID for your app).
Finding the right ProgID: For Adobe Reader, it's AcroExch.Document.DC. For Microsoft Edge, it's AppXq0fevzme2z5y9n5p2k0h4k7h4k7h (long string, look it up online or in another machine's registry). For Photos app, it's Microsoft.Photos plus a CLSID. Honestly, it's easier to just delete the subkey and then go back to Fix 2.
Another registry path to check: HKEY_CLASSES_ROOT\.pdf — sometimes the update sets the default value to something generic like txtfile. Change it back to the correct ProgID.
If you're uncomfortable with registry, try the official Microsoft tool: Microsoft Fix It for file associations (download from their site). It runs a script that resets the default apps database. Used it on a Windows 10 machine that had the problem after 22H2—worked like a charm.
Prevent This from Happening Again
After you fix it, you can prevent future resets. But honestly, there's no guaranteed way. Microsoft updates are unpredictable. I tell clients to take a screenshot of their default apps settings before a feature update. Then if it breaks, you've got a reference.
Another trick: Use a third-party tool like Default Programs Editor or FileTypesMan from NirSoft. These let you export and import your file associations as a backup. Takes 2 minutes to create a restore point for your settings.
When to Give Up and Reinstall
If none of this works—and I've seen it happen—your Windows profile might be corrupted. Create a new local user account, log into it, see if the associations stick. If they do, migrate your data. It's a pain, but it's faster than chasing ghosts in the registry.
Had a client last week whose associations reset every single boot. Tried all three fixes. Ended up creating a new profile. Problem solved in 30 minutes.
Was this solution helpful?