Documentation

Select a product for setup, deployment, and command reference.

DEFAULT APPLICATIONS

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.

Built for IT administrators, MSPs, and education IT who deploy Windows 10 and 11 desktops, Remote Desktop / Citrix / AVD session hosts, and FSLogix profiles, and need defaults like PDF reader, browser, or mail client set reliably at scale.
ROLLOUT

How a deployment typically works

  1. Write one config fileList the associations, optionally per AD or local group.
  2. Check it onceValidate it, then try it for a test user:SetUserFTA.exe config.txt -checkSetUserFTA.exe config.txt -plan
  3. Run SilentFTA at every logonFrom a logon script, GPO, scheduled task, or RMM tool. It shows no window.SilentFTA.exe config.txt
  4. 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.
OVERVIEW

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.

REFERENCE

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.

CommandWhat it doesExample
<extension> <ProgId> [group]Set an association.SetUserFTA.exe .pdf AcroExch.Document.DC
del <extension> [group]Remove the user’s choice, so Windows falls back to its default.SetUserFTA.exe del .pdf
replace <ext> <old> <new>Change it only where it is currently <old>.SetUserFTA.exe replace .htm ChromeHTML MSEdgeHTM
hklm / 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.txt
get [filter]List the user’s associations, optionally filtered.SetUserFTA.exe get .pdf,.docx
browserList installed browsers and the current default browser.SetUserFTA.exe browser
query <ext>Show the ProgId an extension or protocol resolves to.SetUserFTA.exe query mailto
info <ext>Show the user, legacy, and machine association, and whether Windows enforces the type.SetUserFTA.exe info .pdf
find <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,https
run <ext>Start the application associated with an extension.SetUserFTA.exe run .pdf
refreshTell Explorer that associations changed.SetUserFTA.exe refresh

Run SetUserFTA.exe without arguments to see the license details and a short usage summary.

CONFIGURATION

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 -check validates 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 -plan shows 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.
  • -strict applies 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.

ENFORCEMENT

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.

Deployment tip. Start SilentFTA without waiting for its child processes. A launcher that waits for the whole process tree (for example PowerShell Start-Process -Wait) would also wait for the watcher.
REQUIREMENTS

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.
SWITCHES

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.
BUILT FOR SCRIPTS

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

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.

Licenses and free trial You can include a trial with your SetUserFTA quote request. Request a quote and trial
RELEASE 3.0

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.
NETWORK PRINTERS

MapUserPrinters

Describe in one text file which printers go to which AD groups, OUs, AD attributes, locations, networks, computers, or tags. At logon, MapUserPrinters reads the file, maps what applies, removes what no longer applies, sets the default printer, and writes a log. It is built for logon scripts and Group Policy, and also works where Intune or another management tool handles deployment.

  • No runtime, no administrator rights, no internet access
  • No service and no installation on the clients
  • Single executables for x64, x86, and ARM64
  • User interface and log in English and German
ProgramForPurpose
MapUserPrinters.exeEvery user, at logonMaps and removes printers and sets the default printer. Runs silently and never shows a window.
MapUserPrintersConfig.exeAdministratorsEdits the configuration, previews the result, reads logs, and signs configurations.

Plan your rollout

Assign printers by rule

Use AD groups, sites, networks, computers, or policy tags. Set a default printer and remove outdated connections with cleanup rules.

Deploy on Windows

Deploy the executable, configuration, and license at user logon through Group Policy, Intune, or an existing script. Builds are available for x64, x86, and ARM64.

Keep using covered versions

The license is checked offline. Versions released during your maintenance term keep working. Renew maintenance for newer versions.

Request a trialRequest pricing

Check changes before rollout

Run WhatIf in the configuration editor to preview printer assignments for the current user and flag missing drivers without changing any connections.

Read about the configuration editor
Example WhatIf result for a user on Floor 1
  • PRT_01Connect and set as default
  • PRT_02Connect once
  • PRT_OLDRemove old connection
PERFORMANCE

How a logon run works

Every run checks the license and, when required, the configuration’s signature before it touches a single printer. It stays fast by avoiding the slow parts of typical scripts:

  1. Group membership from the logon tokenWindows has already resolved all nested groups at logon, so no LDAP queries are needed — even with thousands of configured printers.
  2. Local factsIP addresses, AD site, and session details come from local Windows caches and are read only when a line needs them.
  3. Parallel connectionsSeveral printers connect at once (4 by default). A print server that does not answer is skipped for its remaining printers instead of waiting for each timeout.
  4. Only changesExisting connections are read once; printers that are already mapped are left alone.
CONFIGURATION

The configuration file

One readable text file, MapUserPrinters.ini (or .txt), holds all printers and settings — one line per printer, with groups and options after a |.

[Printers]
\\PRINT1SV\PRT_01     | G_PRT_PRT_01; G_Floor1 | default
\\PRINT1SV\PRT_02     | *                      | once, ip=10.20.0.0/16
DEL \\PRTSV\*          | *

Groups

A line applies when the user is a member of any listed group, nested groups included. * means everybody.

default

Makes the printer the default printer; the first matching line wins.

mandatory / once

Mandatory printers are restored at every logon if the user removed them. Once printers are mapped the first time only; afterwards the user may remove them.

DEL rules

Delete printer connections, with wildcards — for example to retire an old print server. A printer the user is still assigned to is never deleted.

Comments

Lines starting with #. Prefix a printer line with # to disable it without losing it.

The file can be UTF-8, UTF-16, or ANSI, so group names with umlauts work.

SettingDefaultMeaning
ModemandatoryDefault for lines without once or mandatory.
RemoveUnassignednoRemove listed printers the user is no longer entitled to.
DisableWindowsManagedDefaultnoTurn off “Let Windows manage my default printer”.
Attempts, RetryDelay3, 2 sConnection attempts per printer.
Parallel4Printers connected at the same time.
ValidateGroupsnoAlso look up every configured group and log groups that do not exist.
LogFile, LogMaxSizeKB%APPDATA%\MapUserPrinters, 1024Log location and rotation size.
LanguageautoLanguage of the log: auto, en, or de.
TARGETING

Conditions: where and for whom

Besides groups, a line can require conditions on location, network, computer, session, tags, OU, or any AD attribute. Groups and all conditions must match. Within a condition, ; means or and ! means not — for example computer=LAB-*;!LAB-KIOSK*.

ConditionMatchesExample
ip= (subnet=)Any IP address of the computer10.20.0.0/16, 10.1.3.10-10.1.3.50, IPv6
network=A connected network: domain, private, public, or its namedomain, CorpWiFi
computer=Computer name, with wildcardsPC-BER-*
site=The computer’s AD siteBerlin
client=RDS/Citrix: the device the user sits atTHIN-BER-*
clientip=RDS/Citrix: that device’s address10.1.2.0/24
session=Kind of sessionconsole, remote, rdp, citrix
tag=Tags set by policy for the computer or userFinance; !Kiosk
userou=, computerou=OU of the user or computer object, sub-OUs includedSites/Berlin
user.<attribute>=, computer.<attribute>=Any AD attribute of the user or computer objectuser.department=Finance

Tags let Group Policy, Intune, or any other tool decide who gets a printer without AD groups: write tags such as Berlin or Floor 3 to the Tags policy value and target tag=Berlin in the configuration. Users cannot change them.

OU and attribute conditions read the user and computer objects once per logon with one signed and encrypted LDAP query each. Without a domain controller — on a laptop at home, for example — they don’t match and the log says why; network=domain makes such lines explicit.

Safe by default. Each fact is read once per logon and only when a line needs it. An invalid condition stops the run instead of silently widening who gets a printer, and /verbose logs which condition excluded a line.
ADMIN TOOL

The configuration editor

MapUserPrintersConfig.exe lets you build and check the configuration without editing text by hand. The file stays readable and can still be edited in Notepad.

Printer list

With check boxes to enable or disable lines, columns for action, groups, options, conditions, and comments, plus reordering.

Add from print server

Lists all shared printers of a server, derives group names from a template such as G_PRT_{share} or uses fixed groups, and adds conditions to all selected printers at once.

Printer dialog

Map or DEL rule, AD group picker, once or mandatory, default printer, one field per condition, AD attributes, and a comment.

Check groups

Looks up every configured group in AD and selects the printers whose groups do not exist.

Preview (WhatIf)

Runs the mapper for the current user without changing anything and shows what would be mapped, removed, or set as default — including missing drivers.

Log viewer

Opens your own log or a user’s log on another computer through the admin share, filters by run, level, and text, and refreshes automatically.

Signing and licensing

Sign configurations and install license files from the editor; /sign and /verify do the same from a script.

Convenience

Drag and drop of configuration files, light and dark mode that follows Windows, English and German switchable while running, and keyboard shortcuts for every command.

SECURITY

Security and central control

A changed configuration cannot send users to a foreign print server, and users never see or influence the configuration.

Signed configurations

The editor signs the configuration with your own key (ECDSA P-256, SHA-256) as a comment block at the end of the file. With the Require signed configurations policy, the mapper refuses unsigned, changed, or untrusted configurations and changes nothing. Re-saving in Notepad keeps the signature valid; any real change breaks it.

Allowed print servers

Limit mapping to listed servers by name, full name, or wildcard. Deleting old connections still works for every server.

Policies instead of files

All central settings live in HKLM or HKCU\Software\Policies\MapUserPrinters, which users cannot change.

Runs as the user

No elevation, no service, no installation on the clients.

Never shows anything

No message box or window, even for errors — everything goes to the log.

PolicyScopeEffect
Require signed configurationsComputerRun only configurations signed with a trusted key.
Trusted configuration signing keysComputerPublic keys whose signatures are accepted.
Allowed print serversComputerServers printers may be mapped from.
Tags for printer conditionsComputer and userTags for the tag= condition.
License fileComputerPath of the license file.

ADMX templates in English and German cover all five policies, for the Group Policy central store or Intune’s ADMX import. Any other tool can set the registry values directly.

LICENSING

Licensing

MapUserPrinters uses a signed license file that is checked offline. Without a valid license it logs the reason and changes nothing.

License file

MapUserPrinters.lic is readable text with licensee, edition, users, scope, and maintenance date. It is digitally signed, so any change invalidates it.

Scope

Bound to your Active Directory domain (including child domains) or your Microsoft Entra tenant, read locally from the computer — no internet access or online activation.

Maintenance

A license covers every version released up to its maintenance date and never stops working for those versions. Newer versions need a renewal. Only trial licenses expire.

Where it is found

The /license: parameter, the License file policy, next to the configuration, or next to the executable. The editor shows the status under Help › License.

Want to try it first? Request a time-limited trial license for your own environment. Request a trial →
ROLLOUT

Deployment and operation

Deployment is three files on a share and one line in a logon script or GPO: MapUserPrinters.exe, the configuration, and the license — for example in \\<domain>\NETLOGON\MapUserPrinters.

Logon

Add the executable as a GPO logon script or call it from an existing batch file. Parameters are optional.

Log

%APPDATA%\MapUserPrinters\MapUserPrinters.log in UTF-8, rotated at 1 MB, one marked block per run, readable with the editor’s log viewer.

Missing drivers

A failed mapping names the driver that is not installed, and /whatif checks drivers in advance.

Command line

/config:<file>Use a specific configuration file.
/log:<file>Write the log to a specific location.
/whatifDry run: show what would change, including missing drivers.
/verboseLog details, including which condition excluded a line.
/resetonceReset once printers so they are mapped again.
/lang:<en|de>Language of the log.
/license:<file>Use a specific license file.

Exit codes

0Everything done.
1At least one printer could not be mapped or removed.
2Configuration or setup error.
3No valid license.
4Signed configuration required, but missing or not accepted.
⊞ START MENU

Pin2StartMenu

Start menu layouts for Windows 11, deployed. Windows gives administrators almost no supported way to say “Finance gets these six apps, IT gets those, everyone else gets the standard set.” Pin2StartMenu does exactly that — and it also works one app at a time from the console.

Pin and arrange

  • Pin and unpin apps by name, app ID, program path, or shortcut — or by position.
  • Pin straight to a position, move a pin, or swap two.
  • Create folders on the Start menu and give them a name — something Windows itself offers no tool for.
  • Remove everything, or hand the Start menu back to the Windows default set.

Deploy a standard layout

  • Export a reference machine you have arranged by hand: the layout file is written for you.
  • Replace makes the Start menu exactly the file; import changes only what the file names (an app is pinned, is not pinned, or sits at a given position) and leaves the user’s own pins alone.
  • Rules by group: one rules file maps Active Directory or local groups to layouts. Apply a layout once (users may change it afterwards) or make it mandatory at every logon.
  • Apps that are not installed on a machine are skipped and reported; the rest is applied.

Safe to run

Dry run

-test works on every command that changes something — it shows what would happen and changes nothing.

Automatic backups

A backup is taken before every change; the last five are kept, and restore puts one back in a single command.

Verified

Changes are read back and checked before they are reported as done.

Cleanup

cleanup removes pins whose app has been uninstalled.

Log and diagnose

An optional log file for logon scripts, and a diagnose command for support.

Command reference

Quick start

Pin2StartMenu.exe apps
Pin2StartMenu.exe export start.txt
Pin2StartMenu.exe import start.txt -test
Pin2StartMenu.exe apply rules.txt -log

Layout file example

Microsoft.WindowsTerminal_8wekyb3d8bbwe!App
Microsoft.Windows.Explorer

folder Office
> Microsoft.Office.OUTLOOK.EXE.15
pin <app>Pin an app by name, path, shortcut, Store ID, or list number.
unpin <app>Remove a pinned item by name or position.
export <file>Save the current Start menu layout.
import <file>Add the differences from a layout file.
import <file> -overwriteReplace the current layout completely.
apply <rules>Choose and apply a layout by group membership.
showList the complete current layout, including folders.
apps [text]List pinnable installed apps, optionally filtered.
cleanupRemove pins for apps or shortcuts that no longer exist.
move <from> <to>Move one entry to another position.
swap <a> <b>Exchange two entries.
reset / restoreReturn to Windows defaults or restore a backup.

Common options

-testDescribe every change and write nothing.
-backupSave the current layout before writing.
-logWrite a detailed log in the user profile.
-forceWrite even when nothing appears to have changed.

At a glance

ManagesWindows 11 Start menu pins
Pin, unpin, check, list✓
Pin at a position, move, swap✓
FoldersCreate and name Start menu folders
Export / replace / import layouts✓
Rules by group, once or mandatory✓
Dry run, backups, restore✓
Clean up pins of removed apps✓
Back to Windows defaultsreset
WindowsWindows 11 24H2 and 25H2, Windows Server 2025
InstallationNone — one .exe
ROLLOUT

Deployment

A deployment is three steps and one line in your logon script. No agent, no service, no scheduled task, no policy template.

  1. Build the layoutArrange one machine by hand and export it, or write the list of apps yourself. One file per group.
  2. Write the rulesOne line per group, naming the layout it gets. Put the files on a share.
  3. Call it at logonIn a Group Policy logon script, this picks the user’s layout by group membership, applies it, and exits:Pin2StartMenu apply \\server\share\startmenu\rules.txt

A rules file

Rules are read from top to bottom. Put the fallback layout after the group-specific layout rules. Use once to preserve later user changes or mandatory to reapply the layout at every logon.

# group           = file          [once|mandatory]  [replace|import]
CONTOSO\Kiosk     = kiosk.txt     mandatory
CONTOSO\IT        = it.txt        once
*                 = default.txt   once              replace
*                 = remove-sap.txt once             import

A layout file

One app per line, top to bottom. For the Start menu, a folder line opens a folder and the > lines below it go inside:

Microsoft.WindowsTerminal_8wekyb3d8bbwe!App
Notepad
folder Office
> Microsoft.Office.OUTLOOK.EXE.15

Works with your tools

Group Policy logon scripts, a scheduled task at logon, or Intune and SCCM. The license can be installed for every user of a machine from Intune or SCCM running as SYSTEM.

Per user

Pins belong to each user, so the tools run in the signed-in user’s session. Pin2StartMenu can also be started as SYSTEM and hands over to the signed-in user.

Examples included

Ready-made example sets — a rules file, four layouts, and two import files — come with both tools.

BUILT FOR SCRIPTS

Exit codes

Every command answers through an exit code, and both tools use the same table — one error-handling block covers both.

0Done.
1Error.
2Not pinned (check).
3App or position not found.
4Not available on this machine (license or Windows version).
5The name matches several apps.
6Written, but did not take effect.
7Not running in the signed-in user’s session.
8Partly done, for example apps not installed here.
9Wrong command line.
REQUIREMENTS

Requirements

Both tools need only Windows x64 and a signed-in user.

Tested onWindows 11 24H2 and 25H2, Windows Server 2025
Also runs on—
Runs asThe signed-in user, in their session
InstallNone: copy one .exe and the license
Changes only the right profile. Pins belong to each user, so the tools change the layout of the user who runs them — not of other users, and not as SYSTEM. A run in the wrong account is refused with a clear message instead of changing the wrong profile. A major Windows update can change how Windows stores pins; on a Windows version the tool does not recognize, it stops before changing anything.
LICENSING

Licensing and free trial

Both tools are licensed by subscription, per number of users, with a free trial. Each license is a small signed file that is valid until a set date.

  • Keep the license file next to the .exe, or install it once with license install — for one user, or for every user of the machine (-machine, also from Intune or SCCM).
  • license shows who the tool is licensed to, the license type, and the last valid day.
  • One license number covers a customer who buys both tools; each tool gets its own license file.
  • Free trial: a demo package with the tool, a trial license, example files, and a short admin guide.
Try it in your environment. Request the free demo package or a quote for your number of users. Request a trial or quote →
⊞ TASKBAR

Pin2Taskbar

The taskbar your users need, the same on every machine. Windows has no public way to pin apps to the taskbar from a script. Pin2Taskbar pins, unpins, and orders taskbar apps from the command line and keeps a standard taskbar in place at every logon.

Pin and arrange

  • Pin and unpin apps by name, program (mstsc.exe), shortcut, app ID, or a number from the list of installed apps.
  • Pin straight to a position, move a pin, or swap two.
  • check answers “is Outlook pinned?” through the exit code, ready for a script to branch on.

Deploy a standard layout

  • Export the taskbar of a reference machine to a layout file.
  • Replace makes the taskbar match the file exactly; import adds what is missing, removes what must go, places apps at fixed positions, and leaves everything else as the user has it.
  • Rules by group with once or mandatory, exactly as in Pin2StartMenu. All matching rules are combined and the taskbar is written once.
  • Only what is different is changed, and nothing happens when the taskbar already matches — quick enough for every logon.
  • Keep the current order and only match the set of apps, if you prefer (-noorder).

Safe to run

Dry run and undo

-test for a dry run, a backup before every change, and restore to undo.

Cleanup

cleanup finds pins of uninstalled apps and leftover shortcut files; cleanup -check reports them first without removing anything.

Log file

Optional, with the result and timing of every run.

Command reference

Quick start

Pin2Taskbar.exe apps
Pin2Taskbar.exe export taskbar.txt
Pin2Taskbar.exe replace taskbar.txt -test
Pin2Taskbar.exe apply rules.txt -log

Layout file example

# One app per line, in taskbar order
Microsoft.Windows.Explorer
Microsoft.WindowsTerminal_8wekyb3d8bbwe!App
C:\Program Files\Company\App.exe
pin <app> [pos]Pin an app, optionally at an exact position.
unpin <app>Remove a taskbar pin.
export <file>Save the current taskbar layout.
import <file>Add what is missing, remove what must go, and leave the rest as the user has it.
replace <file>Match the taskbar to the layout exactly.
apply <rules>Choose and apply a layout by group membership.
show / check <app>List pins or test whether an app is pinned (answered by the exit code).
apps [text]List installed applications available to pin.
cleanup [-check]Remove pins of uninstalled apps and leftover shortcut files; -check only reports them.
move <from> <to>Move one pin to an exact position.
swap <a> <b>Exchange two taskbar pins.
diagnosePrint a read-only environment report.

Common options

-testDescribe every change and write nothing.
-backupSave the current layout before writing.
-logWrite a detailed log in the user profile.
-forceWrite even when nothing appears to have changed.

At a glance

ManagesTaskbar pins
Pin, unpin, check, list✓
Pin at a position, move, swap✓
Folders—
Export / replace / import layouts✓
Rules by group, once or mandatory✓
Dry run, backups, restore✓
Clean up pins of removed appsYes, plus leftover shortcut files
Back to Windows defaults—
WindowsWindows 11 24H2 or later and Windows Server (tested); runs on Windows 10 and Server 2016 or later
InstallationNone — one .exe
ROLLOUT

Deployment

A deployment is three steps and one line in your logon script. No agent, no service, no scheduled task, no policy template.

  1. Build the layoutArrange one machine by hand and export it, or write the list of apps yourself. One file per group.
  2. Write the rulesOne line per group, naming the layout it gets. Put the files on a share.
  3. Call it at logonIn a Group Policy logon script, this picks the user’s layout by group membership, applies it, and exits:Pin2Taskbar apply \\server\share\taskbar\rules.txt

A rules file

Rules are read from top to bottom. Put the fallback layout after the group-specific layout rules. Use once to preserve later user changes or mandatory to reapply the layout at every logon.

# group           = file          [once|mandatory]  [replace|import]
CONTOSO\Kiosk     = kiosk.txt     mandatory
CONTOSO\IT        = it.txt        once
*                 = default.txt   once              replace
*                 = remove-sap.txt once             import

Works with your tools

Group Policy logon scripts, a scheduled task at logon, or Intune and SCCM. The license can be installed for every user of a machine from Intune or SCCM running as SYSTEM.

Per user

Pins belong to each user, so the tools run in the signed-in user’s session.

Examples included

Ready-made example sets — a rules file, four layouts, and two import files — come with both tools.

BUILT FOR SCRIPTS

Exit codes

Every command answers through an exit code, and both tools use the same table — one error-handling block covers both.

0Done.
1Error.
2Not pinned (check).
3App or position not found.
4Not available on this machine (license or Windows version).
5The name matches several apps.
6Written, but did not take effect.
7Not running in the signed-in user’s session.
8Partly done, for example apps not installed here.
9Wrong command line.
REQUIREMENTS

Requirements

Both tools need only Windows x64 and a signed-in user.

Tested onWindows 11 24H2 or later, Windows Server
Also runs onWindows 10 and Windows Server 2016 or later (not tested)
Runs asThe signed-in user, in their session
InstallNone: copy one .exe and the license
Changes only the right profile. Pins belong to each user, so the tools change the layout of the user who runs them — not of other users, and not as SYSTEM. A run in the wrong account is refused with a clear message instead of changing the wrong profile. A major Windows update can change how Windows stores pins; on a Windows version the tool does not recognize, it stops before changing anything.
LICENSING

Licensing and free trial

Both tools are licensed by subscription, per number of users, with a free trial. Each license is a small signed file that is valid until a set date.

  • Keep the license file next to the .exe, or install it once with license install — for one user, or for every user of the machine (-machine, also from Intune or SCCM).
  • license shows who the tool is licensed to, the license type, and the last valid day.
  • One license number covers a customer who buys both tools; each tool gets its own license file.
  • Free trial: a demo package with the tool, a trial license, example files, and a short admin guide.
Try it in your environment. Request the free demo package or a quote for your number of users. Request a trial or quote →