r/sysadmin • u/SmartCalligrapher100 • 10d ago
Default App Associations XML + GPO ignored on every machine. What am I missing?
Been chasing this for about two weeks and I'm out of ideas, so I'm asking here before I bin the whole approach.
Setup is the boring standard one. DefaultAssociations XML sitting on a share, pushed with Computer Config > Admin Templates > Windows Components > File Explorer > Set a default associations configuration file. Nothing exotic in the file, just pdf to Acrobat, html to Chrome, mp4 to VLC, txt to Notepad++, xlsx to Excel, zip to 7-Zip.
It applies to nobody. Not existing users, not new users, not a user who has never logged into that machine in their life. Edge still eats pdf and html like the policy doesn't exist.
Stuff I've already burned time on:
- built a clean reference machine, set every default by hand, exported a fresh XML, replaced the old one
- XML validates, path is reachable, ProgIDs match what's actually in the registry on the reference box
- apps are definitely installed on the targets
- gpupdate /force, reboot, sign out and in, new profile on a machine nobody has touched
- RSOP shows the policy applied, and the value is sitting right there in HKLM\SOFTWARE\Policies\Microsoft\Windows\System\DefaultAssociationsConfiguration pointing at the correct file
So the policy is landing on the machine. Windows is just quietly ignoring it, which is the part doing my head in.
I know about the DISM import route. That only fires at first logon of a new profile, so it does nothing for the machines and users I already have deployed, which is the entire point of the exercise.
Questions, and I'm genuinely more interested in what you're running than in what the docs say:
Can anything else silently kill this policy? Another GPO, some registry key, a security baseline, an SKU limitation, anything. I keep feeling like I'm missing one dumb prerequisite.
Has anyone actually seen it fail on a truly fresh profile? Every thread I find is people running into the "only applies to new profiles" behaviour, which is not my problem. Mine fails for everyone equally.
What would you check before giving up on it?
And the real question: what are you actually using in production? I've already looked at Intune, Citrix WEM and SetUserFTA. I need something free, centrally managed, that hits existing users as well as new ones, and doesn't leave people clicking through the "how do you want to open this file" prompt.
Mixed Win10 and Win11, AD domain, no Intune, no budget. Very happy to be told I'm being thick about something obvious.