Skip to main content

Windows Taskbar Policy

Updated this week

The Windows Taskbar Policy allows administrators to define a consistent, centrally managed set of applications that appear pinned to the Windows taskbar on every managed device.
This ensures a standardized user experience across your organization and helps users quickly access required apps.

This policy supports both Desktop Applications (Win32/EXE) and Universal Windows Apps (UWP).


How the Taskbar Policy Works

You can pin two types of applications:

App Type

Field Name

Example Identifier

How to Identify

Desktop Apps (EXE, non-UWP)

Desktop Application IDs

openvpn-gui.exe or full path

Get-StartApps PowerShell command

UWP Apps (Microsoft Store apps)

App User Model IDs

Microsoft.WindowsCalculator_8wekyb3d8bbwe!App

Value always ends with !App

Each entry you add becomes a pinned shortcut on the Windows taskbar.


Requirements

  • Windows Pro 10+

  • Windows Enterprise 10+

  • Windows Education 10+

  • Windows SE 10+

  • IoT Enterprise / IoT Enterprise LTSC 10+


Finding App Identifiers

Windows exposes app IDs through PowerShell.
Run the following command:

Get-StartApps

This returns a list of all installed applications and their identifiers.

How to tell whether an app is UWP or Desktop:

  • If the ID contains !App, it is a UWP (Universal Windows App)
    Example:
    ​Microsoft.WindowsCalculator_8wekyb3d8bbwe!App

  • If the ID does NOT contain !App, it is a Desktop/Win32 app
    Example:
    ​OpenVPN Technologies, Inc. OpenVPN GUI


1. Desktop Application IDs

Use this field to pin non-UWP applications, such as .exe programs installed through traditional installers.

You can enter:

  • Executable name
    e.g., openvpn-gui.exe

  • Full path (recommended)
    e.g.,

    {6D809377-6AF0-444B-8957-A3773F02200E}\OpenVPN\bin\openvpn-gui.exe

Examples

{6D809377-6AF0-444B-8957-A3773F02200E}\OpenVPN\bin\openvpn-gui.exe Anysphere.Cursor

How to locate full paths

You can manually browse your system or use PowerShell tools such as:

Get-StartApps | Where-Object { $_.Name -like "*appname*" }

2. App User Model IDs (UWP)

Use this field for apps installed through the Microsoft Store or apps packaged as UWP.

These always include:

  • A package name

  • _8wekyb3d8bbwe or similar publisher ID

  • !App at the end

Examples

Microsoft.WindowsCalculator_8wekyb3d8bbwe!App Microsoft.WindowsCamera_8wekyb3d8bbwe!App

Tip

If the identifier contains !App, it is definitely a UWP application.


Best Practices

Prefer full paths for Desktop Applications

Executable names may not be unique across systems.


Confirm identifiers using PowerShell

Always verify App IDs using:

Get-StartApps

Keep entries minimal and essential

Avoid overloading users with too many taskbar items.


Result on the Device

After the policy is pushed:

  • Desktop Application IDs β†’ pinned directly to taskbar

  • App User Model IDs β†’ pinned as UWP shortcuts

  • Existing user taskbar pins remain unless you apply additional cleanup policies


Summary

Field

Purpose

Desktop Application IDs

Pins EXE/Win32 apps installed via standard installers

App User Model IDs

Pins UWP / Microsoft Store apps

With accurate App IDs, Swif ensures that users get consistent and compliant taskbar layouts across every managed Windows device.

Did this answer your question?