Customize Windows 10 Start and taskbar with Group Policy

Applies to

In WindowsВ 10 Pro, Enterprise, and Education, you can use a Group Policy Object (GPO) to deploy a customized Start and taskbar layout to users in a domain. No reimaging is required, and the layout can be updated simply by overwriting the .xml file that contains the layout. This enables you to customize Start and taskbar layouts for different departments or organizations, with minimal management overhead.

This topic describes how to update Group Policy settings to display a customized Start and taskbar layout when the users sign in. By creating a domain-based GPO with these settings, you can deploy a customized Start and taskbar layout to users in a domain.

When a full Start layout is applied with this method, the users cannot pin, unpin, or uninstall apps from Start. Users can view and open all apps in the All Apps view, but they cannot pin any apps to Start. When a partial Start layout is applied, the contents of the specified tile groups cannot be changed, but users can move those groups, and can also create and customize their own groups. When you apply a taskbar layout, users will still be able to pin and unpin apps, and change the order of pinned apps.

Operating system requirements

In Windows 10, version 1607, Start and taskbar layout control using Group Policy is supported in WindowsВ 10 Enterprise and WindowsВ 10 Education. In Windows 10, version 1703, Start and taskbar layout control using Group Policy is also supported in WindowsВ 10 Pro.

The GPO can be configured from any computer on which the necessary ADMX and ADML files (StartMenu.admx and StartMenu.adml) for WindowsВ 10 are installed. In Group Policy, ADMX files are used to define Registry-based policy settings in the Administrative Templates category. To find out how to create a central store for Administrative Templates files, see article 929841, written for Windows Vista and still applicable in the Microsoft Knowledge Base.

How Start layout control works

Three features enable Start and taskbar layout control:

The Export-StartLayout cmdlet in Windows PowerShell exports a description of the current Start layout in .xml file format.

To import the layout of Start to a mounted Windows image, use the Import-StartLayout cmdlet.

You can modify the Start .xml file to include or create an .xml file just for the taskbar configuration.

In Group Policy, you use the Start Layout settings for the Start Menu and Taskbar administrative template to set a Start and taskbar layout from an .xml file when the policy is applied. The Group Policy object doesn’t support an empty tile layout, so the default tile layout for Windows is loaded in that case.

To learn how customize Start to include your line-of-business apps when you deploy WindowsВ 10, see Customize the Windows 10 Start layout.

Use Group Policy to apply a customized Start layout in a domain

To apply the Start and taskbar layout to users in a domain, use the Group Policy Management Console (GPMC) to configure a domain-based Group Policy Object (GPO) that sets Start Layout policy settings in the Start Menu and Taskbar administrative template for users in a domain.

The GPO applies the Start and taskbar layout at the next user sign-in. Each time the user signs in, the timestamp of the .xml file with the Start and taskbar layout is checked and if a newer version of the file is available, the settings in the latest version of the file are applied.

The GPO can be configured from any computer on which the necessary ADMX and ADML files (StartMenu.admx and StartMenu.adml) for WindowsВ 10 are installed.

The .xml file with the Start and taskbar layout must be located on shared network storage that is available to the users’ computers when they sign in and the users must have Read-only access to the file. If the file is not available when the first user signs in, Start and the taskbar are not customized during the session, but the user will be prevented from making changes to Start. On subsequent sign-ins, if the file is available at sign-in, the layout it contains will be applied to the user’s Start and taskbar.

For information about deploying GPOs in a domain, see Working with Group Policy Objects.

Use Group Policy to apply a customized Start layout on the local computer

You can use the Local Group Policy Editor to provide a customized Start and taskbar layout for any user who signs in on the local computer. To display the customized Start and taskbar layout for any user who signs in, configure Start Layout policy settings for the Start Menu and Taskbar administrative template. You can use the Start Menu and Taskbar administrative template in User Configuration or Computer Configuration.

This procedure applies the policy settings on the local computer only. For information about deploying the Start and taskbar layout to users in a domain, see Use Group Policy to deploy a customized Start layout in a domain.

This procedure creates a Local Group Policy that applies to all users on the computer. To configure Local Group Policy that applies to a specific user or group on the computer, see Step-by-Step Guide to Managing Multiple Local Group Policy Objects. The guide was written for WindowsВ Vista and the procedures still apply to WindowsВ 10.

This procedure adds the customized Start and taskbar layout to the user configuration, which overrides any Start layout settings in the local computer configuration when a user signs in on the computer.

To configure Start Layout policy settings in Local Group Policy Editor

On the test computer, press the Windows key, type gpedit, and then select Edit group policy (Control panel).

Go to User Configuration or Computer Configuration > Administrative Templates >Start Menu and Taskbar.

Right-click Start Layout in the right pane, and click Edit.

This opens the Start Layout policy settings.

Enter the following settings, and then click OK:

Select Enabled.

Under Options, specify the path to the .xml file that contains the Start and taskbar layout. For example, type C:\Users\Test01\StartScreenMarketing.xml.

Optionally, enter a comment to identify the Start and taskbar layout.

If you disable Start Layout policy settings that have been in effect and then re-enable the policy, users will not be able to make changes to Start, however the layout in the .xml file will not be reapplied unless the file has been updated. In Windows PowerShell, you can update the timestamp on a file by running the following command:

Update a customized Start layout

After you use Group Policy to apply a customized Start and taskbar layout on a computer or in a domain, you can update the layout simply by replacing the .xml file that is specified in the Start Layout policy settings with a file with a newer timestamp.

Manage Windows 10 Start and taskbar layout

Applies to

• WindowsВ 10, Windows Server 2016 with Desktop Experience, Windows Server 2019 with Desktop Experience

Organizations might want to deploy a customized Start and taskbar configuration to devices running WindowsВ 10 Pro, Enterprise, or Education. A standard, customized Start layout can be useful on devices that are common to multiple users and devices that are locked down for specialized purposes. Configuring the taskbar allows the organization to pin useful apps for their employees and to remove apps that are pinned by default.

Taskbar configuration is available starting in Windows 10, version 1607.

Start and taskbar configuration can be applied to devices running Windows 10 Pro, version 1703.

For information on using the layout modification XML to configure Start with roaming user profiles, see Deploy Roaming User Profiles.

Using CopyProfile for Start menu customization in Windows 10 isn’t supported. For more information Customize the Default User Profile by Using CopyProfile

Start options

Some areas of Start can be managed using Group Policy. The layout of Start tiles can be managed using either Group Policy or Mobile Device Management (MDM) policy.

The MDM policy settings in the table can also be configured in a provisioning package using Policies > Start. See the reference for Start settings in Windows Configuration Designer.

The following table lists the different parts of Start and any applicable policy settings or Settings options. Group Policy settings are in the User Configuration\Administrative Templates\Start Menu and Taskbar path except where a different path is listed in the table.

Start	Policy	Local setting
User tile	MDM: Start/HideUserTile Start/HideSwitchAccount Start/HideSignOut Start/HideLock Start/HideChangeAccountSettings Group Policy: Remove Logoff on the Start menu	none
Most used	MDM: Start/HideFrequentlyUsedApps Group Policy: Remove frequent programs from the Start menu	Settings > Personalization > Start > Show most used apps
Suggestions -and- Dynamically inserted app tile	MDM: Allow Windows Consumer Features Group Policy: Computer Configuration\Administrative Templates\Windows Components\Cloud Content\Turn off Microsoft consumer experiences Note: This policy also enables or disables notifications for a user’s Microsoft account and app tiles from Microsoft dynamically inserted in the default Start menu.	Settings > Personalization > Start > Occasionally show suggestions in Start
Recently added	MDM: Start/HideRecentlyAddedApps Group Policy: Computer configuration\Administrative Template\Start Menu and Taskbar\Remove «Recently Added» list from Start Menu (for Windows 10, version 1803)	Settings > Personalization > Start > Show recently added apps
Pinned folders	MDM: AllowPinnedFolder	Settings > Personalization > Start > Choose which folders appear on Start
Power	MDM: Start/HidePowerButton Start/HideHibernate Start/HideRestart Start/HideShutDown Start/HideSleep Group Policy: Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands	none
Start layout	MDM: Start layout ImportEdgeAssets Group Policy: Prevent users from customizing their Start screen Note: When a full Start screen layout is imported with Group Policy or MDM, the users cannot pin, unpin, or uninstall apps from the Start screen. Users can view and open all apps in the All Apps view, but they cannot pin any apps to the Start screen. When a partial Start screen layout is imported, users cannot change the tile groups applied by the partial layout, but can modify other tile groups and create their own. Start layout policy can be used to pin apps to the taskbar based on an XML File that you provide. Users will be able to change the order of pinned apps, unpin apps, and pin additional apps to the taskbar.	none
Jump lists	MDM: Start/HideRecentJumplists Group Policy: Do not keep history of recently opened documents	Settings > Personalization > Start > Show recently opened items in Jump Lists on Start or the taskbar
Start size	MDM: Force Start size Group Policy: Force Start to be either full screen size or menu size	Settings > Personalization > Start > Use Start full screen
App list	MDM: Start/HideAppList	Settings > Personalization > Start > Show app list in Start menu
All Settings	Group Policy: Prevent changes to Taskbar and Start Menu Settings	none
Taskbar	MDM: Start/NoPinningToTaskbar	none

In local Settings > Personalization > Start, there is an option to Show more tiles. The default tile layout for Start tiles is 3 columns of medium sized tiles. Show more tiles enables 4 columns. To configure the 4-column layout when you customize and export a Start layout, turn on the Show more tiles setting and then arrange your tiles.

Taskbar options

Starting in Windows 10, version 1607, you can pin additional apps to the taskbar and remove default pinned apps from the taskbar. You can specify different taskbar configurations based on device locale or region.

There are three categories of apps that might be pinned to a taskbar:

Apps pinned by the user

Default Windows apps, pinned during operating system installation (Microsoft Edge, File Explorer, Store)

Apps pinned by the enterprise, such as in an unattended Windows setup

We recommend using the layoutmodification.xml method to configure taskbar options, rather than the earlier method of using TaskbarLinks in an unattended Windows setup file.

The following example shows how apps will be pinned — Windows default apps to the left (blue circle), apps pinned by the user in the center (orange triangle), and apps that you pin using XML to the right (green square).

In operating systems configured to use a right-to-left language, the taskbar order will be reversed.

Whether you apply the taskbar configuration to a clean install or an update, users will still be able to:

• Pin additional apps
• Change the order of pinned apps
• Unpin any app

In Windows 10, version 1703, you can apply an MDM policy, Start/NoPinningToTaskbar , to prevents users from pinning and unpinning apps on the taskbar.

Taskbar configuration applied to clean install of Windows 10

In a clean install, if you apply a taskbar layout, only the apps that you specify and default apps that you do not remove will be pinned to the taskbar. Users can pin additional apps to the taskbar after the layout is applied.

Taskbar configuration applied to Windows 10 upgrades

When a device is upgraded to Windows 10, apps will be pinned to the taskbar already. Some apps may have been pinned to the taskbar by a user, and others may have been pinned to the taskbar through a customized base image or by using Windows Unattend setup.

The new taskbar layout for upgrades to Windows 10, version 1607 or later, will apply the following behavior:

• If the user pinned the app to the taskbar, those pinned apps remain and new apps will be added to the right.
• If the user didn’t pin the app (it was pinned during installation or by policy) and the app is not in updated layout file, the app will be unpinned.
• If the user didn’t pin the app and the app is in the updated layout file, the app will be pinned to the right.
• New apps specified in updated layout file are pinned to right of user’s pinned apps.

Start layout configuration errors

If your Start layout customization is not applied as expected, open Event Viewer and navigate to Applications and Services Log > Microsoft > Windows > ShellCommon-StartLayoutPopulation > Operational, and check for one of the following events:

• Event 22 is logged when the xml is malformed, meaning the specified file simply isn’t valid xml. This can occur if the file has extra spaces or unexpected characters, or if the file is not saved in the UTF8 format.
• Event 64 is logged when the xml is valid, but has unexpected values. This can happen when the desired configuration is not understood, elements are not in the required order, or source is not found, such as a missing or misspelled .lnk.