SetUserFTA
Since Windows 8, a user’s default apps are protected by a hash: an association written any other way is ignored or reset to the Windows default. Group Policy (the default associations XML) only applies at first logon or forces one setting on everyone — and from then on, users can no longer pick their own apps.
SetUserFTA writes the per-user choice exactly as the Settings app does, with the hash Windows expects. Associations take effect immediately, without a reboot or a new logon, and can be set per user, per group, once, or enforced for the whole session.
How a deployment typically works
- Write one config fileList the associations, optionally per AD or local group.
- Check it onceValidate it, then try it for a test user:
SetUserFTA.exe config.txt -checkSetUserFTA.exe config.txt -plan - Run SilentFTA at every logonFrom a logon script, GPO, scheduled task, or RMM tool. It shows no window.
SilentFTA.exe config.txt - Enforce or set onceLines marked MANDATORY stay enforced for the rest of the session; lines marked APPLYONCE are set once and then left to the user.
Features at a glance
Per-user associations with a valid hash
File types and protocols (.pdf, mailto, https …) set the way Windows accepts them, instantly, no reboot.
Default browser in one line
HKLM "Google Chrome" sets http, https, .htm, and .html from the browser’s own registration.
Config files
One file for the whole organization: set, delete, replace, and browser lines, comments, any common text encoding.
Group targeting
Apply a line only to members of an AD or local group, or to everyone except a group (!Group).
Last match wins
A user in several groups gets each extension written once, with the last matching line deciding.
MANDATORY
Keeps an association in place for the whole session; changes are reverted automatically.
APPLYONCE / -applyonce
Sets a default once and then respects the user’s own choice.
Dry run and validation
-plan shows what a config does for a user; -check validates it for everyone. Nothing is written.
-strict
All or nothing: a config with an error applies nothing.
SilentFTA
Windowless version for logon scripts and RMM tools: no console, no pop-ups.
UCPD support
Works with Microsoft’s User Choice Protection Driver on Windows 10 and 11.
FSLogix and RDS
Works in FSLogix profiles and on multi-user session hosts.
No “default app reset” pop-ups
Suppresses the Windows notifications that would otherwise follow a change.
Inspection
List, search, and verify associations; export them to a file.
Scripting-ready
Consistent exit codes and an optional log file for every run.
Commands
Every command accepts comma-separated lists without spaces (.txt,.log or http,https), and the set, delete, and browser commands take an optional group as the last argument.
<extension> <ProgId> [group]Set an association.SetUserFTA.exe .pdf AcroExch.Document.DCdel <extension> [group]Remove the user’s choice, so Windows falls back to its default.SetUserFTA.exe del .pdfreplace <ext> <old> <new>Change it only where it is currently <old>.SetUserFTA.exe replace .htm ChromeHTML MSEdgeHTMhklm / hkcu <browser> [group]Make a browser the default (http, https, .htm, .html).SetUserFTA.exe hklm "Google Chrome"<config file>Apply a config file.SetUserFTA.exe \\server\share\fta.txtget [filter]List the user’s associations, optionally filtered.SetUserFTA.exe get .pdf,.docxbrowserList installed browsers and the current default browser.SetUserFTA.exe browserquery <ext>Show the ProgId an extension or protocol resolves to.SetUserFTA.exe query mailtoinfo <ext>Show the user, legacy, and machine association, and whether Windows enforces the type.SetUserFTA.exe info .pdffind <ProgId>Find every extension and protocol that uses a ProgId (wildcards allowed).SetUserFTA.exe find Acro*verify <ext>Check that the stored association carries a valid hash (exit code 1 if not).SetUserFTA.exe verify .pdf,httpsrun <ext>Start the application associated with an extension.SetUserFTA.exe run .pdfrefreshTell Explorer that associations changed.SetUserFTA.exe refreshRun SetUserFTA.exe without arguments to see the license details and a short usage summary.
Config files
One text file describes the associations for the whole organization; SetUserFTA and SilentFTA read the same format.
# Everyone .pdf,AcroExch.Document.DC HKLM "Google Chrome" # Group targeting (AD or local groups), or everyone except a group .dwg,AutoCAD.Drawing,Engineering .pdf,FoxitReader.Document,!Finance # Remove a user choice, or replace one ProgId with another del .xyz replace .htm ChromeHTML MSEdgeHTM # Enforce for the session, or set only once MANDATORY mailto,Outlook.URL.mailto.15 APPLYONCE .txt,txtfile
How a file is applied. The whole file is read and resolved for the user before anything is written: group filters are evaluated, and when several lines set the same extension (a user in several groups), the last matching line wins. Each extension is then written once, which keeps logons fast.
Line keywords
MANDATORY
(set and browser lines): the association is applied on every run and kept in place for the session by SilentFTA.
APPLYONCE
(set, replace, and browser lines): the association is applied once. After that the user may change it, and later runs leave their choice alone. The -applyonce switch does this for every line of a file.
Check before you deploy
SetUserFTA.exe config.txt -checkvalidates the file for any user: syntax, extensions and ProgIds, and that every group exists. It lists extensions set by more than one line. A ProgId or browser not installed on the checking machine is only a warning.SetUserFTA.exe config.txt -planshows what the file does for the user running it: the final ProgId per extension, the line that decided it, the lines it overrode, and the current state. Run it as a test user.-strictapplies nothing if any line has an error. Without it, valid lines are applied and the run reports the error through its exit code.
Both -check and -plan write nothing.
File format. ANSI, UTF-8 (with or without BOM), and UTF-16 files are accepted. Lines starting with # are comments. Quotes around a field are optional, and trailing commas from spreadsheet exports are ignored. A config file on a network share that is unavailable at logon is reported as an error rather than silently skipped.
SilentFTA and MANDATORY enforcement
SilentFTA is the windowless edition for deployment: SilentFTA.exe \\server\share\fta.txt at logon applies the config without a console window or any pop-up, from a logon script, Group Policy, a scheduled task, or an RMM tool. It uses the same license and config format as SetUserFTA and supports the same switches, including -applyonce, -strict, and -log.
MANDATORY keeps associations in place. Some applications and updates reset defaults, and users can change them in Settings. When the applied config contains MANDATORY lines, SilentFTA starts a small background watcher for the rest of the session. It is notified the moment a mandatory association changes and puts it back about two seconds later.
Users cannot override it
A change made in Settings or through “Open with” is reverted every time.
No fighting loops
If another program keeps changing an association back, the watcher waits longer each time (10 seconds up to 60 minutes) instead of fighting it, and pauses after more than 60 such resets in an hour. Settings changes are still reverted during that pause.
Easy to see what happened
With -log, every change is logged together with the application that was in the foreground at that moment. For proof of which process wrote a value, the documentation describes how to turn on Windows registry auditing.
Lightweight lifecycle
One watcher per user session. The next logon run replaces it with the current config, a config without MANDATORY lines stops it, and it ends at logoff. SilentFTA.exe -stopwatch stops it on demand.
SetUserFTA can start the watcher too: when a config with MANDATORY lines is applied with SetUserFTA, it hands enforcement to SilentFTA.exe in the same folder.
Start-Process -Wait) would also wait for the watcher.Compatibility
WindowsWindows 10 and 11, Windows Server 2016 and later, 64-bit. Version 3.0 is 64-bit only; 32-bit systems stay on 2.7.3.Windows 11 hash rotationSupports the newer UserChoiceLatest scheme (AppDefaultHashRotation) automatically, alongside the classic UserChoice.UCPDDetects Microsoft’s User Choice Protection Driver and automatically uses a supported method for the protected types (.pdf, http, https, and others), including the newer UCPD feature flags. A specific method can be forced with -method0 … -method4.FSLogixDetects FSLogix. With the SetUserFTA FSLogix App Masking rule sets installed, the UCPD-protected types are written directly.Remote Desktop, Citrix, AVDEach user session is handled independently, so many users can log on at the same time. Within one session only one instance runs at a time.VerificationAfter every write, SetUserFTA asks Windows itself whether it accepts the new association.NotificationsSuppresses the “an app default was reset” and “how do you want to open” prompts that a change could otherwise trigger.User contextRuns in the user’s context.Options
Switches can go anywhere on the command line. Unknown or mistyped switches are rejected, so a typo never silently changes what a deployment does.
-applyonceApply each association only once; afterwards the user’s own choice is kept.-reapplyRewrite associations even if they are already set.-strictApply nothing if the config file has any error.-planDry run of a config file for the current user (SetUserFTA).-checkValidate a config file for any user (SetUserFTA).-validonlySkip associations whose application is not installed on this machine.-legacyAlso set the legacy per-user class association, for older applications.-skipaclLeave the association key writable instead of locking it against other programs.-noverifySkip the check after writing.-norefreshDo not notify Explorer of the change.-noappxHide Store (AppX) apps in listings.-cmdlineShow the program command line in listings.-nocheckDo not detect the Windows 11 hash rotation (use the classic scheme).-method0 … -method4Force a specific UCPD method.-log[:path]Write a detailed log file; the screen shows only the results.-export[:path]Save the output of get, query, find, and browser to a file.-verboseShow detailed output on screen.-vSilentFTA only: show errors in a message box (for troubleshooting).-stopwatchSilentFTA only: stop the session’s MANDATORY watcher.Scripting and troubleshooting
Both programs report the outcome through the exit code, so deployment tools and scripts can act on it.
0Success, including nothing to do (already set, nothing to delete, user not in the group).1Something failed: an association could not be written, verify found a broken association, the config file was not reachable, or no valid license.2Usage error: unknown switch or wrong number of arguments.Verify in scripts
SetUserFTA.exe verify .pdf,https returns 1 if an association is missing, broken, or was changed by another program.
Log files
-log writes the full detail to %APPDATA%\SetUserFTA\ or a path you choose, while the screen shows only the results. Logs can be read while a run is still writing them.
Export
-export:C:\Temp\assoc.txt saves a listing for inventory or support.
Diagnose a type
info .pdf shows every layer Windows considers for an extension and whether Windows enforces it.
Licensing
SetUserFTA 3.0 is licensed as a subscription: one license file covers SetUserFTA and SilentFTA and is valid until the date it shows. A free trial is available.
Where the license can live
As SetUserFTA.lic next to the program, or imported once into the registry for the machine or the user. If several are present, the first valid one is used, so a renewed license file works even while an expired one is still imported.
Check it
SetUserFTA.exe without arguments shows the licensee, license type, user count, and expiry date.
Renewal
After the expiry date, plus one day of grace, the tool stops and asks for a renewal; MANDATORY enforcement ends then too.
New in 3.0
MANDATORY enforcement
Keep chosen associations in place for the whole session, with built-in protection against fighting loops.
APPLYONCE per line
Set some defaults once and others on every logon, in the same file.
Smarter config processing
The file is resolved first and every extension written once, so users in many groups log on faster.
-plan, -check, and -strict
See what a config does, validate it before rollout, and make deployments all or nothing.
Apply-once that lasts
The “applied once” record now survives a user changing the default in Settings. Changing the config to a different ProgId applies the new one once, with no extra delete line.
Windows checks the result
Verification asks Windows itself, and apps that are not installed yet are handled correctly.
Newer UCPD versions
Supported, including the newer protection flags.
Safer by default
Typos and wrong argument counts are rejected instead of creating a wrong association; one instance per session.
verify command
Checks associations from scripts.
Easier troubleshooting
With -log, the details go to the file and the screen stays clean.
Subscription licensing
With clear expiry information.
Upgrading from 2.x
- With
-applyonce, the last matching line now wins (2.x applied the first). - 3.0 is 64-bit only.
- Existing apply-once records are taken over, so upgrading does not re-apply anything.
PowerPoint