Inno Setup is a Windows installer builder. It uses the [Setup] DefaultGroupName value as the Start Menu program group name, then writes shortcuts into that folder unless you let the user change it on the Program Group page. Get this wrong and you can create duplicate groups, orphaned shortcuts, or a separate folder for every upgrade. This guide shows how DefaultGroupName, GroupDescription, DisableProgramGroupPage, and shortcut destinations affect the exact Start Menu folder users see for single apps and suites.

What the Start Menu folder means

What the Start Menu folder means
Installer settings screen showing Start Menu folder shortcut options

The Start Menu folder is the visible program group name users see in the Start menu. In Inno Setup, that visible name is separate from the shortcut target, which is the executable or document the shortcut opens. Keep those two ideas apart, because the name affects where the shortcut appears and the target affects what happens when it is clicked.

In practice, Inno Setup creates shortcuts in a folder such as {group} for the selected program group, {userprograms} for the current user’s Programs area, or {commonprograms} for the all-users Programs area. Those are shell-folder constants, so they resolve to real Windows locations during install.

Program group name versus shortcut target

DefaultGroupName sets the group name. A shortcut line sets the target. For example, this creates a shortcut named after the group and points it at the main EXE:

Name: "{group}\My App"; Filename: "{app}\MyApp.exe"

If the group name is wrong, the shortcut can still point to the right file. If the filename is wrong, the folder can look right while the shortcut fails.

How shell-folder constants map to visible folders

{group} follows the group name chosen on the Program Group page or in DefaultGroupName. {userprograms} lands in the current user’s Start Menu area. {commonprograms} lands in the shared Start Menu area for all users, which only works when the install scope and privileges allow it.

Say a suite has three apps and one uninstaller. A single Start Menu folder such as Acme Suite keeps those shortcuts together. A single-app install often works better with one shortcut and no extra folder at all.

What you'll need

  • An Inno Setup 7 script.
  • A main executable path in [Files].
  • One [Icons] entry per shortcut you want.
  • Optional [Tasks] entries for desktop or extra shortcuts.
  • Optional [Components] entries if shortcut sets depend on selected features.
  • A decision about current-user or all-users scope before you choose {userprograms} or {commonprograms}.

How Inno Setup chooses the folder

How Inno Setup chooses the folder
Installer settings screen showing application folder options

Inno Setup chooses the Start Menu folder from DefaultGroupName, then resolves shortcut destinations through the active shell-folder constant. The wizard’s Program Group page can let the user change the group name, but newer setups may disable that page by default through DisableProgramGroupPage. In the New Script Wizard, the common Start Menu Programs option is enabled by default, and Microsoft recommends that option for a single application rather than a suite.

DefaultGroupName and {group}

Use DefaultGroupName for the visible folder name and {group} in [Icons] to place shortcuts there. This keeps one folder name in one place and makes upgrades predictable.

[Setup]
DefaultGroupName=My App

[Icons]
Name: "{group}\My App"; Filename: "{app}\MyApp.exe"

Current-user and common shell folders

Use {userprograms} for a per-user install, and {commonprograms} for an all-users install when the installer runs with the needed administrative rights. Inno Setup supports both administrative and non administrative installations, so the same script can behave differently based on scope and privilege.

A common first-timer mistake is writing every shortcut to {commonprograms} and then running a non-admin install. The result is often a missing shortcut, because the installer cannot place items in the shared Programs area without the right scope.

What the Program Group page changes

The Program Group page controls whether the user can accept or change the Start Menu folder during setup. If you want one fixed folder, disable that page and keep the group name in the script. If you want the user to choose, leave the page available and make sure the shortcuts still point to {group} so the destination follows the chosen name.

Start Menu folder decision table

Scenario Recommended script pattern Expected visible result One failure mode to test
Single app DefaultGroupName=My App; one [Icons] entry to {app}\MyApp.exe One Start Menu folder with one app shortcut Duplicate folder name after upgrade
App suite DefaultGroupName=Acme Suite; several {group}\... shortcuts One shared program group with multiple shortcuts One shortcut lands outside the suite folder
Per-user install Name: "{userprograms}\My App"; Filename: "{app}\MyApp.exe" Shortcut appears only for the current user Another user cannot see the shortcut
All-users install Name: "{commonprograms}\My App"; Filename: "{app}\MyApp.exe" Shortcut appears for all users Install runs without rights and the shortcut is missing
Optional desktop shortcut [Tasks] task plus Check: IsTaskSelected('desktopicon'); Name: "{userdesktop}\My App" Desktop shortcut only when the task is chosen Desktop icon appears even when the task is off
No Start Menu entry No [Icons] line for {group}; keep only file install entries No Start Menu folder is created Installer still creates an empty group
Custom program group name DefaultGroupName=Vendor Tools\My App; shortcuts use {group} Visible folder uses the custom group name A stale folder remains after a rename
Uninstall cleanup checks Remove shortcuts from {group} and confirm the folder is empty before deletion Shortcut disappears and empty group is removed when nothing else uses it Shared folder stays behind after uninstall

How do you set the folder and shortcuts?

How do you set the folder and shortcuts?
An installer dialog shows application folder settings and checkboxes
  1. Set the group name. Put the visible folder name in DefaultGroupName. Use a plain product name for a single app and a suite name for multiple shortcuts, because the same name is what users see in the Start menu.
  2. Choose the shortcut scope. Use {userprograms} for current-user installs and {commonprograms} for all-users installs. Match that choice to the install scope so the shortcut lands where the installer has permission to write.
  3. Point shortcuts at the executable. Use the main app file in Filename:, then place the shortcut in {group}, {userprograms}, or {commonprograms} as needed. The folder choice controls location; the filename controls launch behavior.
  4. Gate optional entries. Tie desktop shortcuts to [Tasks] and feature-specific shortcuts to [Components]. That keeps optional items from appearing when the user does not choose the matching task or component.
  5. Disable the page if needed. Add DisableProgramGroupPage=yes when you want a fixed folder name with no user change. Leave it available when your install policy expects the user to pick a different group name.
  6. Clean up on uninstall. Remove only the shortcuts you created, then confirm the group is empty before expecting the folder to disappear. Shared folders should not be deleted if another product still uses them.

Common mistakes

Wrong folder name. This usually comes from changing DefaultGroupName but leaving old shortcuts behind. Test an upgrade path and check that only one visible program group remains.

Empty folder left behind. This happens when uninstall removes shortcuts but leaves an empty group. Confirm the uninstall removes every shortcut in the folder before expecting the folder itself to disappear.

Missing shortcut. A common cause is using {commonprograms} in a non-admin install or using the wrong task or component condition. Check scope first, then the condition on the shortcut entry.

Say a suite has a main app, a helper tool, and a PDF manual. If all three shortcuts use {group} under Acme Suite, users see one folder. If the manual shortcut accidentally uses {userprograms}, the suite splits across two places.

If that didn't work

Start by checking the exact [Icons] lines, then verify the chosen shell-folder constant. If the shortcut still lands in the wrong place, compare install scope to privileges and confirm the Program Group page is either enabled intentionally or disabled on purpose.

Keep reading

Frequently asked questions

How do I change the Start Menu folder in Inno Setup?

Change DefaultGroupName in [Setup], then keep shortcut entries pointed at {group}. If you want the user to choose the name, leave the Program Group page enabled. If you want one fixed folder, disable that page and keep the group name in the script.

What is the difference between a Start Menu folder and Start menu Programs folder in Inno Setup?

The Start Menu folder is the visible group name, while the Programs location is the shell folder that receives the shortcut. In script terms, DefaultGroupName names the group and {group}, {userprograms}, or {commonprograms} chooses where it lives.

How do I stop Inno Setup from creating a Start Menu folder?

Do not add any [Icons] entry that writes to {group}, {userprograms}, or {commonprograms}. If you only install files, no Start Menu group is created. Also check that no optional task or component still inserts a shortcut.

How do I create a Start Menu shortcut in Inno Setup?

Add an [Icons] entry with a Name: that points to the folder and a Filename: that points to the executable. A basic line looks like Name: "{group}\My App"; Filename: "{app}\MyApp.exe". The target is the app file, not the folder.

How do I install shortcuts for all users versus the current user?

Use {commonprograms} for all users and {userprograms} for the current user. Then match that choice to administrative or non administrative installation so the installer can write to the selected shell folder.

Why is Inno Setup creating the wrong program group name?

The usual cause is an unexpected DefaultGroupName value or a user choice on the Program Group page. Check the script for the exact group name, then confirm whether the wizard page is enabled or disabled. If upgrades are involved, also check for an old folder left from a previous name.

How do I create only a desktop shortcut and no Start Menu folder?

Create a desktop task and skip any Start Menu [Icons] entry. Use a desktop path such as {userdesktop} or the common desktop equivalent, and do not write anything to {group} or the Programs folders. That keeps the Start Menu clear.

What does the Program Group page do in the Inno Setup wizard?

It lets the user accept or change the Start Menu group name during setup. In newer builds it may be disabled by default, which makes the script’s DefaultGroupName control the visible folder name instead. Use it when you want user choice; disable it when you want one fixed group.