Overview
Pin2StartMenu and Pin2Taskbar are two small command-line tools for Windows administrators. Each is a single .exe with nothing to install: write a plain text file with the apps you want pinned, call the tool from a logon script, and the signed-in user gets that layout.
The two tools share one file format, one rules syntax, one set of exit codes, and one licensing model — what you learn for one works for the other.
One file format
Plain text, one app per line — for the Start menu and the taskbar alike.
One rules syntax
Map groups to layouts, once or mandatory, in one rules file.
One set of exit codes
One error-handling block in your script covers both tools.
One licensing model
One license number covers both tools; each gets its own license file.
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.
checkanswers “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.
At a glance
Both tools do the same jobs for their part of Windows; only the Windows versions and a few extras differ.
ManagesWindows 11 Start menu pinsTaskbar pinsPin, 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✓Yes, plus leftover shortcut filesBack to Windows defaultsreset—WindowsWindows 11 24H2 and 25H2, Windows Server 2025Windows 11 24H2 or later and Windows Server (tested); runs on Windows 10 and Server 2016 or laterInstallationNone — one .exeNone — one .exeDeployment
A deployment is three steps and one line in your logon script. No agent, no service, no scheduled task, no policy template.
- Build the layoutArrange one machine by hand and export it, or write the list of apps yourself. One file per group.
- Write the rulesOne line per group, naming the layout it gets. Put the files on a share.
- 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.
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
Both tools need only Windows x64 and a signed-in user.
Tested onWindows 11 24H2 and 25H2, Windows Server 2025Windows 11 24H2 or later, Windows ServerAlso runs on—Windows 10 and Windows Server 2016 or later (not tested)Runs asThe signed-in user, in their sessionThe signed-in user, in their sessionInstallNone: copy one .exe and the licenseNone: copy one .exe and the licenseLicensing 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). licenseshows 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.
Outlook
Teams
Word
Excel
PowerPoint