mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Update Start and Taskbar configuration
This commit is contained in:
Paolo Matarazzo
parent
434a663caa
commit
41de122e56
@ -1,14 +1,16 @@
|
|||||||
---
|
---
|
||||||
title: Configure the Start menu
|
title: Customize and export the Start layout
|
||||||
description: Learn about the available options to configure the Windows Start menu and how to configure them via Configuration Service Providers (CSP) or group policy (GPO).
|
description: Learn how to customize the Windows Start layout and export the configuration to apply to other devices.
|
||||||
ms.topic: how-to
|
ms.topic: how-to
|
||||||
ms.date: 03/15/2024
|
ms.date: 03/04/2024
|
||||||
appliesto:
|
|
||||||
zone_pivot_groups: windows-versions-11-10
|
zone_pivot_groups: windows-versions-11-10
|
||||||
|
appliesto:
|
||||||
|
ms.collection:
|
||||||
|
- tier1
|
||||||
---
|
---
|
||||||
|
|
||||||
# Configure the Start menu
|
|
||||||
|
|
||||||
|
<!-->
|
||||||
To configure the Start menu, you can use one of the following options:
|
To configure the Start menu, you can use one of the following options:
|
||||||
|
|
||||||
- Configuration Service Provider (CSP): this option is commonly used for devices managed by a Mobile Device Management (MDM) solution, like Microsoft Intune. The [Start Policy CSP][WIN-1] is used to configure the Start menu.
|
- Configuration Service Provider (CSP): this option is commonly used for devices managed by a Mobile Device Management (MDM) solution, like Microsoft Intune. The [Start Policy CSP][WIN-1] is used to configure the Start menu.
|
||||||
@ -17,177 +19,404 @@ To configure the Start menu, you can use one of the following options:
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> While many of the Start menu policy settings can be configured using both CSP and GPO, there are some settings that are only available using the Start Policy CSP.
|
> While many of the Start menu policy settings can be configured using both CSP and GPO, there are some settings that are only available using the Start Policy CSP.
|
||||||
|
|
||||||
## Policy settings
|
To learn about the available policy settings to configure the Start menu via configuration service provider (CSP) and group policy (GPO), see [Start menu policy settings](policy-settings.md).
|
||||||
|
|
||||||
This section describes the policy settings to configure the Start menu via configuration service provider (CSP) and group policy (GPO).
|
Use a standard, customized Start layout on devices that are common to multiple users, and devices that are locked down.
|
||||||
|
|
||||||
:::row:::
|
-->
|
||||||
:::column span="2":::
|
|
||||||
The list of settings is sorted alphabetically and organized in four categories:
|
|
||||||
|
|
||||||
1. **Start layout**: settings to control the Start menu layout
|
# Customize and export the Start layout
|
||||||
1. **User options**: settings to control the options exposed when selecting the user icon
|
|
||||||
1. **Pinned folders**: settings to control the folders pinned for quick access
|
|
||||||
1. **Power options**: settings to control the options exposed when selecting the power icon
|
|
||||||
|
|
||||||
:::column-end:::
|
This article describes how to customize the Windows Start menu, export its configuration, and deploy the customization to other devices. The article is intended for IT professionals who manage devices in a business or educational environment.\
|
||||||
:::column span="2":::
|
If you are looking for OEM information, see the article [Customize the Start layout](/windows-hardware/customize/desktop/customize-the-windows-11-start-menu)
|
||||||
::: zone pivot="windows-10"
|
|
||||||
:::image type="content" source="./images/windows-10-settings.png" alt-text="Sample start menu layout with its components highlighted." border="false" lightbox="./images/windows-10-settings.png":::
|
|
||||||
::: zone-end
|
|
||||||
|
|
||||||
::: zone pivot="windows-11"
|
::: zone pivot="windows-11"
|
||||||
:::image type="content" source="./images/windows-11-settings.png" alt-text="Sample start menu layout with its components highlighted." border="false" lightbox="./images/windows-11-settings.png":::
|
|
||||||
::: zone-end
|
|
||||||
|
|
||||||
|
Your organization can deploy a customized Start layout to your Windows 11 devices. Customizing the Start layout is common when you have similar devices used by many users, or you want to pin specific apps.
|
||||||
|
|
||||||
|
For example, you can override the default set of apps with your own a set of pinned apps, and in the order you choose. As an administrator, use this feature to pin apps, remove default pinned apps, order the apps, and more.
|
||||||
|
|
||||||
|
To add apps you want pinned to the Start menu, you use a JSON file. In previous Windows versions, IT administrators used an XML file to customize the Start menu. The XML file isn't available on Windows 11 and later ***unless*** [you're an OEM](/windows-hardware/customize/desktop/customize-the-windows-11-start-menu).
|
||||||
|
|
||||||
|
This article shows you how to export an existing Start menu layout, and use the JSON in a Microsoft Intune policy.
|
||||||
|
|
||||||
|
## Before you begin
|
||||||
|
|
||||||
|
When you customize the Start layout, you overwrite the entire full layout. Users can pin and unpin apps, and uninstall apps from Start. When a user signs in or Explorer restarts, Windows reapplies the MDM policy. This action restores the specified layout and doesn't retain any user changes.
|
||||||
|
|
||||||
|
## Start menu features and areas
|
||||||
|
|
||||||
|
The Start menu consistes of set of links to applications, folders, or files that are arranged in a grid of pages.
|
||||||
|
|
||||||
|
:::row:::
|
||||||
|
:::column span="3":::
|
||||||
|
The Start menu has the following areas:
|
||||||
|
|
||||||
|
- **Pinned**: Shows pinned apps, or a subset of all of the apps installed on the device. You can create a list of pinned apps you want on the devices using the **ConfigureStartPins** policy. **ConfigureStartPins** overrides the entire layout, which also removes apps that are pinned by default
|
||||||
|
- **All apps**: Users select this option to see an alphabetical list of all the apps installed on the device.
|
||||||
|
- **Recommended**: Shows recently opened files and recently installed apps
|
||||||
|
:::column-end:::
|
||||||
|
:::column:::
|
||||||
|
:::image type="content" source="./images/windows-11-components.png" alt-text="Sample start menu layout with its components highlighted." border="false" lightbox="./images/windows-11-components.png":::
|
||||||
:::column-end:::
|
:::column-end:::
|
||||||
:::row-end:::
|
:::row-end:::
|
||||||
|
|
||||||
|
## Create the JSON file
|
||||||
|
|
||||||
Select one of the tabs to see the list of available settings:
|
On an existing Windows 11 device, set up your own Start layout with the pinned apps you want users to see. Then, use the [Windows PowerShell Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet to export the existing layout to a `LayoutModification.json` file.
|
||||||
|
|
||||||
#### [:::image type="icon" source="../images/icons/start.svg"::: **Start layout**](#tab/start)
|
The JSON file controls the Start menu layout, and lists all the apps that are pinned. You can update the JSON file to:
|
||||||
|
|
||||||
The following table lists the policies that control the Start menu layout. Select the policy name for more details.
|
- Change the order of existing apps. The apps in the JSON file are shown on Start in the same order.
|
||||||
|
- Add more apps by entering the app ID. For more information, see [Get the pinnedList JSON](#get-the-pinnedlist-json) (in this article).
|
||||||
|
|
||||||
|Policy name| CSP | GPO |
|
If you're familiar with creating JSON files, you can create your own `LayoutModification.json` file. But, it's easier and faster to export the layout from an existing device.
|
||||||
|-|-|-|
|
|
||||||
|[ConfigureStartPins](/windows/client-management/mdm/policy-csp-start#configurestartpins)|✅||
|
|
||||||
|[DisableContextMenus](/windows/client-management/mdm/policy-csp-start#disablecontextmenus)|✅||
|
|
||||||
|[ForceStartSize](/windows/client-management/mdm/policy-csp-start#forcestartsize)|✅||
|
|
||||||
|[HideAppList](/windows/client-management/mdm/policy-csp-start#hideapplist)|✅||
|
|
||||||
|[HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#hidefrequentlyusedapps)|✅||
|
|
||||||
|[HideRecentJumplists](/windows/client-management/mdm/policy-csp-start#hiderecentjumplists)|✅||
|
|
||||||
|[HideRecentlyAddedApps](/windows/client-management/mdm/policy-csp-start#hiderecentlyaddedapps)|✅||
|
|
||||||
|[HideRecommendedPersonalizedSites](/windows/client-management/mdm/policy-csp-start#hiderecommendedpersonalizedsites)|✅||
|
|
||||||
|[HideRecommendedSection](/windows/client-management/mdm/policy-csp-start#hiderecommendedsection)|✅||
|
|
||||||
|[ImportEdgeAssets](/windows/client-management/mdm/policy-csp-start#importedgeassets)|✅||
|
|
||||||
|[ShowOrHideMostUsedApps](/windows/client-management/mdm/policy-csp-start#showorhidemostusedapps)|✅||
|
|
||||||
|[StartLayout](/windows/client-management/mdm/policy-csp-start#startlayout)|✅||
|
|
||||||
|
|
||||||
#### [:::image type="icon" source="../images/icons/user.svg"::: **User options**](#tab/user)
|
### Export an existing Start layout
|
||||||
|
|
||||||
[HideChangeAccountSettings](/windows/client-management/mdm/policy-csp-start#hidechangeaccountsettings)
|
1. Create a folder to save the `.json` file. For example, create the `C:\Layouts` folder.
|
||||||
[HideLock](/windows/client-management/mdm/policy-csp-start#hidelock)
|
1. On a Windows 11 device, open the Windows PowerShell app.
|
||||||
[HideSignOut](/windows/client-management/mdm/policy-csp-start#hidesignout)
|
1. Run the following cmdlet. Name the file `LayoutModification.json`.
|
||||||
[HideSwitchAccount](/windows/client-management/mdm/policy-csp-start#hideswitchaccount)
|
|
||||||
[HideUserTile](/windows/client-management/mdm/policy-csp-start#hideusertile)
|
|
||||||
|
|
||||||
#### [:::image type="icon" source="../images/icons/folder.svg"::: **Pinned folders**](#tab/folders)
|
```powershell
|
||||||
|
Export-StartLayout -Path "C:\Layouts\LayoutModification.json"
|
||||||
|
```
|
||||||
|
|
||||||
[AllowPinnedFolderDocuments](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderdocuments)
|
### Get the pinnedList JSON
|
||||||
[AllowPinnedFolderDownloads](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderdownloads)
|
|
||||||
[AllowPinnedFolderFileExplorer](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderfileexplorer)
|
|
||||||
[AllowPinnedFolderHomeGroup](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderhomegroup)
|
|
||||||
[AllowPinnedFolderMusic](/windows/client-management/mdm/policy-csp-start#allowpinnedfoldermusic)
|
|
||||||
[AllowPinnedFolderNetwork](/windows/client-management/mdm/policy-csp-start#allowpinnedfoldernetwork)
|
|
||||||
[AllowPinnedFolderPersonalFolder](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderpersonalfolder)
|
|
||||||
[AllowPinnedFolderPictures](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderpictures)
|
|
||||||
[AllowPinnedFolderSettings](/windows/client-management/mdm/policy-csp-start#allowpinnedfoldersettings)
|
|
||||||
[AllowPinnedFolderVideos](/windows/client-management/mdm/policy-csp-start#allowpinnedfoldervideos)
|
|
||||||
|
|
||||||
#### [:::image type="icon" source="../images/icons/power.svg"::: **Power options**](#tab/power)
|
1. Open the `LayoutModification.json` file in a JSON editor, such as Visual Studio Code or Notepad. For more information, see [edit JSON with Visual Studio Code](https://code.visualstudio.com/docs/languages/json).
|
||||||
|
1. In the file, you see the `pinnedList` section. This section includes all of the pinned apps. Copy the `pinnedList` content in the JSON file. You'll use it in the next section.
|
||||||
|
|
||||||
[HideHibernate](/windows/client-management/mdm/policy-csp-start#hidehibernate)
|
In the following example, you see that Microsoft Edge, Microsoft Word, the Microsoft Store app, and Notepad are pinned:
|
||||||
[HidePowerButton](/windows/client-management/mdm/policy-csp-start#hidepowerbutton)
|
|
||||||
[HideRestart](/windows/client-management/mdm/policy-csp-start#hiderestart)
|
```json
|
||||||
[HideShutDown](/windows/client-management/mdm/policy-csp-start#hideshutdown)
|
{
|
||||||
[HideSleep](/windows/client-management/mdm/policy-csp-start#hidesleep)
|
"pinnedList": [
|
||||||
|
{ "desktopAppId": "MSEdge" },
|
||||||
|
{ "desktopAppId": "Microsoft.Office.WINWORD.EXE.15" },
|
||||||
|
{ "packagedAppId": "Microsoft.WindowsStore_8wekyb3d8bbwe!App" },
|
||||||
|
{ "packagedAppId": "Microsoft.WindowsNotepad_8wekyb3d8bbwe!App" }
|
||||||
|
]
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
1. Use the `ConfigureStartPins` policy setting to configure the Start menu, by using a JSON `LayoutModification.json` file to add apps to the Pinned section. In your JSON file, you can add more apps to this section using the following keys:
|
||||||
|
|
||||||
|
| Key | Description |
|
||||||
|
|--|--|
|
||||||
|
| packagedAppID | Use this option for Universal Windows Platform apps. To pin a UWP app, use the app's AUMID. |
|
||||||
|
| desktopAppID | Use this option for unpackaged Win32 apps. To pin a Win32 app, use the app's AUMID. If the app doesn't have an AUMID, then enter the `desktopAppLink` instead. |
|
||||||
|
| desktopAppLink | Use this option for unpackaged Win32 apps that don't have an associated AUMID. To pin this type of app, use the path to the `.lnk` shortcut that points to the app. |
|
||||||
|
|
||||||
|
## Use MDM to create and deploy a pinned list policy
|
||||||
|
|
||||||
|
Now that you have the JSON syntax, you're ready to deploy your customized Start layout to devices in your organization.
|
||||||
|
|
||||||
|
MDM providers can deploy policies to devices managed by the organization, including organization-owned devices, and personal or bring your own device (BYOD). Using an MDM provider, such as Microsoft Intune, you can deploy a policy that configures the pinned list.
|
||||||
|
|
||||||
|
This section shows you how to create a pinned list policy in Intune. There isn't a Group Policy to create a pinned list.
|
||||||
|
|
||||||
|
[!INCLUDE [intune-settings-catalog-1](../../../includes/configure/intune-settings-catalog-1.md)]
|
||||||
|
|
||||||
|
| Category | Setting name | Value |
|
||||||
|
|--|--|--|
|
||||||
|
| **Start** | Configure Start Pins | Content of the JSON file|
|
||||||
|
| **Start** | Configure Start Pins (User) | Content of the JSON file|
|
||||||
|
|
||||||
|
[!INCLUDE [intune-settings-catalog-2](../../../includes/configure/intune-settings-catalog-2.md)]
|
||||||
|
|
||||||
|
Alternatively, you can configure devices using a [custom policy][INT-1] with the [File Explorer CSP][CSP-1].
|
||||||
|
|
||||||
|
| Setting |
|
||||||
|
|--|
|
||||||
|
| - **OMA-URI:** `./User/Vendor/MSFT/Policy/Config/Start/`[ConfigureStartPins](/windows/client-management/mdm/policy-csp-Start?WT.mc_id=Portal-Microsoft_Intune_Workflows#configurestartpins)<br>- **String:** <br>- **Value:** content of the JSON file |
|
||||||
|
| - **OMA-URI:** `./Device/Vendor/MSFT/Policy/Config/Start/`[ConfigureStartPins](/windows/client-management/mdm/policy-csp-Start?WT.mc_id=Portal-Microsoft_Intune_Workflows#configurestartpins)<br>- **Data type:** <br>- **Value:** content of the JSON file |
|
||||||
|
|
||||||
|
::: zone-end
|
||||||
|
|
||||||
|
::: zone pivot="windows-10"
|
||||||
|
|
||||||
|
The easiest method for creating a customized Start layout to apply to other Windows 10 devices is to set up the Start screen on a test computer and then export the layout.
|
||||||
|
|
||||||
|
After you export the layout, decide whether you want to apply a *full* Start layout or a *partial* Start layout.
|
||||||
|
|
||||||
|
When a full Start layout is applied, the users can't pin, unpin, or uninstall apps from Start. Users can view and open all apps in the **All Apps** view, but they can't pin any apps to Start.
|
||||||
|
|
||||||
|
When [a partial Start layout](#configure-a-partial-start-layout) is applied, the contents of the specified tile groups can't be changed, but users can move those groups, and can also create and customize their own groups.
|
||||||
|
|
||||||
|
## Customize the Start screen on your test computer
|
||||||
|
|
||||||
|
To prepare a Start layout for export, you simply customize the Start layout on a test computer.
|
||||||
|
|
||||||
|
To prepare a test computer:
|
||||||
|
|
||||||
|
1. Set up a test computer on which to customize the Start layout. Your test computer should have the operating system that is installed on the users' computers (Windows 10 Pro, Enterprise, or Education). Install all apps and services that the Start layout should display.
|
||||||
|
1. Create a new user account that you'll use to customize the Start layout.
|
||||||
|
|
||||||
|
To customize Start:
|
||||||
|
|
||||||
|
1. Sign in to your test computer with the user account that you created.
|
||||||
|
1. Customize the Start layout as you want users to see it by using the following techniques:
|
||||||
|
|
||||||
|
- **Pin apps to Start**. From Start, type the name of the app. When the app appears in the search results, right-click the app, and then select **Pin to Start**.
|
||||||
|
To view all apps, select **All apps** in the bottom-left corner of Start. Right-click any app, and pin or unpin it from Start.
|
||||||
|
- **Unpin apps** that you don't want to display. To unpin an app, right-click the app, and then select **Unpin from Start**.
|
||||||
|
- **Drag tiles** on Start to reorder or group apps.
|
||||||
|
- **Resize tiles**. To resize tiles, right-click the tile and then select **Resize.**
|
||||||
|
- **Create your own app groups**. Drag the apps to an empty area. To name a group, select above the group of tiles and then type the name in the **Name group** field that appears above the group.
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> If the Start layout includes tiles for apps that are not installed on the device that the layout is later applied to, the tiles for those apps will be blank. The blank tiles will persist until the next time the user signs in, at which time the blank tiles are removed. Some system events may cause the blank tiles to be removed before the next sign-in.
|
||||||
|
|
||||||
|
### Export the Start layout
|
||||||
|
|
||||||
|
When you have the Start layout that you want your users to see, use the [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet in Windows PowerShell to export the Start layout to an .xml file. Start layout is located by default at C:\Users\username\AppData\Local\Microsoft\Windows\Shell\
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> If you include secondary Microsoft Edge tiles (tiles that link to specific websites in Microsoft Edge), see [Add custom images to Microsoft Edge secondary tiles](start-secondary-tiles.md) for instructions.
|
||||||
|
|
||||||
|
To export the Start layout to an .xml file:
|
||||||
|
|
||||||
|
1. While signed in with the same account that you used to customize Start, right-click Start, and select **Windows PowerShell**.
|
||||||
|
1. Run `Export-StartLayout` with the switch `-UseDesktopApplicationID`. For example:
|
||||||
|
|
||||||
|
```PowerShell
|
||||||
|
Export-StartLayout -UseDesktopApplicationID -Path layout.xml
|
||||||
|
```
|
||||||
|
|
||||||
|
In the previous command, `-path` is a required parameter that specifies the path and file name for the export file. You can specify a local path or a UNC path (for example, `\\FileServer01\StartLayouts\StartLayoutMarketing.xml`).
|
||||||
|
|
||||||
|
Use a file name of your choice—for example, StartLayoutMarketing.xml. Include the .xml file name extension. The [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet doesn't append the file name extension, and the policy settings require the extension.
|
||||||
|
|
||||||
|
1. (Optional) Edit the .xml file to add [a taskbar configuration](../taskbar/configure.md) or to [modify the exported layout](start-layout-xml-desktop.md). When you make changes to the exported layout, be aware that [the order of the elements in the .xml file is critical.](start-layout-xml-desktop.md#required-order)
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> If the Start layout that you export contains tiles for desktop (Win32) apps or .url links, **Export-StartLayout** will use **DesktopApplicationLinkPath** in the resulting file. Use a text or XML editor to change **DesktopApplicationLinkPath** to **DesktopApplicationID**. See [Specify Start tiles](start-layout-xml-desktop.md#specify-start-tiles) for details on using the app ID in place of the link path.
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> All clients that the start layout applies to must have the apps and other shortcuts present on the local system in the same location as the source for the Start layout.
|
||||||
|
>
|
||||||
|
> For scripts and application tile pins to work correctly, follow these rules:
|
||||||
|
>
|
||||||
|
>- Executable files and scripts should be listed in \Program Files or wherever the installer of the app places them.
|
||||||
|
>- Shortcuts that will pinned to Start should be placed in \ProgramData\Microsoft\Windows\Start Menu\Programs.
|
||||||
|
>- If you place executable files or scripts in the \ProgramData\Microsoft\Windows\Start Menu\Programs folder, they will not pin to Start.
|
||||||
|
>- Start on Windows 10 does not support subfolders. We only support one folder. For example, \ProgramData\Microsoft\Windows\Start Menu\Programs\Folder. If you go any deeper than one folder, Start will compress the contents of all the subfolder to the top level.
|
||||||
|
>- Three additional shortcuts are pinned to the start menu after the export. These are shortcuts to %ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs, %APPDATA%\Microsoft\Windows\Start Menu\Programs, and %APPDATA%\Microsoft\Windows\Start Menu\Programs\System Tools\.
|
||||||
|
|
||||||
|
### Configure a partial Start layout
|
||||||
|
|
||||||
|
A partial Start layout enables you to add one or more customized tile groups to users' Start screens or menus, while still allowing users to make changes to other parts of the Start layout. All groups that you add are *locked*, meaning users can't change the contents of those tile groups, however users can change the location of those groups. Locked groups are identified with an icon, as shown in the following image.
|
||||||
|
|
||||||
|
:::image type="content" source="images/windows-10-partial-layout.png" alt-text="Screenshot of the Windows 10 Start menu with partial layout.":::
|
||||||
|
|
||||||
|
When a partial Start layout is applied for the first time, the new groups are added to the users' existing Start layouts. If an app tile is in both an existing group and in a new locked group, the duplicate app tile is removed from the existing (unlocked) group.
|
||||||
|
|
||||||
|
When a partial Start layout is applied to a device that already has a StartLayout.xml applied, groups that were added previously are removed and the groups in the new layout are added.
|
||||||
|
|
||||||
|
If the Start layout is applied by Group Policy or MDM, and the policy is removed, the groups remain on the devices but become unlocked.
|
||||||
|
|
||||||
|
To configure a partial Start screen layout:
|
||||||
|
|
||||||
|
1. [Customize the Start layout](#customize-the-start-screen-on-your-test-computer).
|
||||||
|
1. [Export the Start layout](#export-the-start-layout).
|
||||||
|
1. Open the layout .xml file. There is a `<DefaultLayoutOverride>` element. Add `LayoutCustomizationRestrictionType="OnlySpecifiedGroups"` to the **DefaultLayoutOverride** element as follows:
|
||||||
|
|
||||||
|
```xml
|
||||||
|
<DefaultLayoutOverride LayoutCustomizationRestrictionType="OnlySpecifiedGroups">
|
||||||
|
```
|
||||||
|
|
||||||
|
1. Save the file and apply using any of the deployment methods.
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> Office 2019 tiles might be removed from the Start menu when you upgrade Office 201. This only occurs if Office 2019 app tiles are in a custom group in the Start menu and only contains the Office 2019 app tiles. To avoid this problem, place another app tile in the Office 2019 group prior to the upgrade. For example, add Notepad.exe or calc.exe to the group. This issue occurs because Office 2019 removes and reinstalls the apps when they are upgraded. Start removes empty groups when it detects that all apps for that group have been removed.
|
||||||
|
|
||||||
|
You can deploy the resulting .xml file to devices using one of the following methods:
|
||||||
|
|
||||||
|
- Configuration Service Provider (CSP)
|
||||||
|
- Group Policy
|
||||||
|
- Provisioning package
|
||||||
|
|
||||||
|
[!INCLUDE [tab-intro](../../../includes/configure/tab-intro.md)]
|
||||||
|
|
||||||
|
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
|
||||||
|
|
||||||
|
You can use a mobile device management (MDM) policy to deploy a customized Start and taskbar layout to users. No reimaging is required. The layout can be updated simply by overwriting the `.xml` file that contains the layout. This feature enables you to customize Start layouts for different departments or organizations, with minimal management overhead.
|
||||||
|
|
||||||
|
**Before you begin**: [Customize and export Start layout](customize-and-export-start-layout.md).
|
||||||
|
|
||||||
|
>[!WARNING]
|
||||||
|
>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.
|
||||||
|
|
||||||
|
Two features enable Start layout control:
|
||||||
|
|
||||||
|
- The **Export-StartLayout** cmdlet in Windows PowerShell exports a description of the current Start layout in .xml file format.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](/powershell/module/startlayout/import-startlayout) cmdlet.
|
||||||
|
|
||||||
|
- In Microsoft Intune, you select the Start layout XML file and add it to a device configuration profile.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>Please do not include XML Prologs like \<?xml version="1.0" encoding="utf-8"?\> in the Start layout XML file. The settings may not be reflected correctly.
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-domaingpodeployment"></a>Create a policy for your customized Start layout
|
||||||
|
|
||||||
|
The following example uses Microsoft Intune to configure an MDM policy that applies a customized Start layout:
|
||||||
|
|
||||||
|
1. Sign in to the [Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||||
|
|
||||||
|
1. Select **Devices** > **Configuration profiles** > **Create profile**.
|
||||||
|
|
||||||
|
1. Enter the following properties:
|
||||||
|
|
||||||
|
- **Platform**: Select **Windows 10 and later**.
|
||||||
|
- **Profile type**: Select **Templates** > **Device restrictions** > **Create**.
|
||||||
|
|
||||||
|
1. In **Basics**, enter the following properties:
|
||||||
|
|
||||||
|
- **Name**: Enter a descriptive name for the profile. Name your profiles so you can easily identify it later. For example, a good profile name is **Customize Start menu and taskbar**.
|
||||||
|
- **Description**: Enter a description for the profile. This setting is optional, but recommended.
|
||||||
|
|
||||||
|
1. Select **Next**.
|
||||||
|
|
||||||
|
1. In **Configuration settings**, select **Start**:
|
||||||
|
|
||||||
|
- If you're using an XML file, select **Start menu layout**. Browse to and select your Start layout XML file.
|
||||||
|
- If you don't have an XML file, configure the others settings. For more information on these settings, see [Start settings in Microsoft Intune](/mem/intune/configuration/device-restrictions-windows-10#start).
|
||||||
|
|
||||||
|
1. Select **Next**.
|
||||||
|
1. In **Scope tags**, select **Next**. For more information about scope tags, see [Use RBAC and scope tags for distributed IT](/mem/intune/fundamentals/scope-tags).
|
||||||
|
1. In **Assignments**, select the user or groups that will receive your profile. Select **Next**. For more information on assigning profiles, see [Assign user and device profiles](/mem/intune/configuration/device-profile-assign).
|
||||||
|
1. In **Review + create**, review your settings. When you select **Create**, your changes are saved, and the profile is assigned. The policy is also shown in the profiles list.
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> For third party partner MDM solutions, you may need to use an OMA-URI setting for Start layout, based on the [Policy configuration service provider (CSP)](/windows/client-management/mdm/policy-configuration-service-provider). The OMA-URI setting is `./User/Vendor/MSFT/Policy/Config/Start/StartLayout`.
|
||||||
|
|
||||||
|
#### [:::image type="icon" source="../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
|
||||||
|
|
||||||
|
You can use a provisioning package that you create with Windows Configuration Designer to deploy a customized Start and taskbar layout to users. No reimaging is required, and the Start and taskbar layout can be updated by overwriting the .xml file that contains the layout. The provisioning package can be applied to a running device. This enables you to customize Start and taskbar layouts for different departments or organizations, with minimal management overhead.
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> If you use a provisioning package to configure the taskbar, your configuration will be reapplied each time the explorer.exe process restarts. If your configuration pins an app and the user unpins that app, the user's change will be overwritten the next time the configuration is applied. To apply a taskbar configuration and allow users to make changes that will persist, apply your configuration by using Group Policy.
|
||||||
|
|
||||||
|
**Before you begin**: [Customize and export Start layout](customize-and-export-start-layout.md) for desktop editions.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](/powershell/module/startlayout/import-startlayout) cmdlet.
|
||||||
|
|
||||||
|
- [You can modify the Start .xml file](../taskbar/configure.md) to include `<CustomTaskbarLayoutCollection>` or create an .xml file just for the taskbar configuration.
|
||||||
|
|
||||||
|
- In Windows Configuration Designer, you use the **Policies/Start/StartLayout** setting to provide the contents of the .xml file that defines the Start and taskbar layout.
|
||||||
|
|
||||||
|
## Prepare the Start layout XML file
|
||||||
|
|
||||||
|
The **Export-StartLayout** cmdlet produces an XML file. Because Windows Configuration Designer produces a customizations.xml file that contains the configuration settings, adding the Start layout section to the customizations.xml file directly would result in an XML file embedded in an XML file. Before you add the Start layout section to the customizations.xml file, you must replace the markup characters in your layout.xml with escape characters.
|
||||||
|
|
||||||
|
1. Copy the contents of layout.xml into an online tool that escapes characters
|
||||||
|
1. During the procedure to create a provisioning package, you will copy the text with the escape characters and paste it in the customizations.xml file for your project
|
||||||
|
|
||||||
|
## PPKG
|
||||||
|
|
||||||
|
1. Expand **Runtime settings** > **Policies** > **Start**, and click **StartLayout**.
|
||||||
|
|
||||||
|
#### [:::image type="icon" source="../images/icons/group-policy.svg"::: **GPO**](#tab/gpo)
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
>[!WARNING]
|
||||||
|
>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.
|
||||||
|
|
||||||
|
**Before you begin**: [Customize and export Start layout](customize-and-export-start-layout.md)
|
||||||
|
|
||||||
|
## Operating system requirements
|
||||||
|
|
||||||
|
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](/troubleshoot/windows-server/group-policy/create-central-store-domain-controller) in the Microsoft Knowledge Base.
|
||||||
|
|
||||||
|
Three features enable Start and taskbar layout control:
|
||||||
|
|
||||||
|
- The [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet in Windows PowerShell exports a description of the current Start layout in .xml file format.
|
||||||
|
>[!NOTE]
|
||||||
|
>To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](/powershell/module/startlayout/import-startlayout) cmdlet.
|
||||||
|
- [You can modify the Start .xml file](../taskbar/configure.md) to include `<CustomTaskbarLayoutCollection>` 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.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>To learn how customize Start to include your line-of-business apps when you deploy Windows 10, see [Customize the Windows 10 Start layout]( https://go.microsoft.com/fwlink/p/?LinkId=620863).
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-domaingpodeployment"></a>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](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)).
|
||||||
|
|
||||||
|
## <a href="" id="bkmk-localgpimport"></a>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**.
|
||||||
|
|
||||||
|
>[!NOTE]
|
||||||
|
>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](#bkmk-domaingpodeployment).
|
||||||
|
>
|
||||||
|
>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](/previous-versions/windows/it-pro/windows-vista/cc766291(v=ws.10)). 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:
|
||||||
|
|
||||||
|
1. On the test computer, press the Windows key, type **gpedit**, and then select **Edit group policy (Control panel)**.
|
||||||
|
1. Go to **User Configuration** or **Computer Configuration** > **Administrative Templates** >**Start Menu and Taskbar**.
|
||||||
|
1. Right-click **Start Layout** in the right pane, and click **Edit**.
|
||||||
|
1. Enter the following settings, and then click **OK**:
|
||||||
|
1. Select **Enabled**.
|
||||||
|
1. Under **Options**, specify the path to the .xml file that contains the Start and taskbar layout. For example, type **C:\\Users\\Test01\\StartScreenMarketing.xml**.
|
||||||
|
1. Optionally, enter a comment to identify the Start and taskbar layout.
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> 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:
|
||||||
|
>
|
||||||
|
> `(ls <path>).LastWriteTime = Get-Date`
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
[!INCLUDE [clear-history-of-recently-opened-documents-on-exit-u](includes/clear-history-of-recently-opened-documents-on-exit-u.md)]
|
::: zone-end
|
||||||
[!INCLUDE [clear-the-recent-programs-list-for-new-users-u](includes/clear-the-recent-programs-list-for-new-users-u.md)]
|
|
||||||
[!INCLUDE [clear-tile-notifications-during-log-on-u](includes/clear-tile-notifications-during-log-on-u.md)]
|
|
||||||
[!INCLUDE [disable-context-menus-in-the-start-menu-um](includes/disable-context-menus-in-the-start-menu-um.md)]
|
|
||||||
[!INCLUDE [disable-editing-quick-settings-m](includes/disable-editing-quick-settings-m.md)]
|
|
||||||
[!INCLUDE [do-not-keep-history-of-recently-opened-documents-um](includes/do-not-keep-history-of-recently-opened-documents-um.md)]
|
|
||||||
[!INCLUDE [do-not-use-the-search-based-method-when-resolving-shell-shortcuts-u](includes/do-not-use-the-search-based-method-when-resolving-shell-shortcuts-u.md)]
|
|
||||||
[!INCLUDE [do-not-use-the-tracking-based-method-when-resolving-shell-shortcuts-u](includes/do-not-use-the-tracking-based-method-when-resolving-shell-shortcuts-u.md)]
|
|
||||||
[!INCLUDE [force-start-to-be-either-full-screen-size-or-menu-size-um](includes/force-start-to-be-either-full-screen-size-or-menu-size-um.md)]
|
|
||||||
[!INCLUDE [prevent-changes-to-taskbar-and-start-menu-settings-um](includes/prevent-changes-to-taskbar-and-start-menu-settings-um.md)]
|
|
||||||
[!INCLUDE [prevent-users-from-customizing-their-start-screen-u](includes/prevent-users-from-customizing-their-start-screen-u.md)]
|
|
||||||
[!INCLUDE [prevent-users-from-uninstalling-applications-from-start-um](includes/prevent-users-from-uninstalling-applications-from-start-um.md)]
|
|
||||||
[!INCLUDE [remove-recently-added-list-from-start-menu-um](includes/remove-recently-added-list-from-start-menu-um.md)]
|
|
||||||
[!INCLUDE [remove-all-programs-list-from-the-start-menu-um](includes/remove-all-programs-list-from-the-start-menu-um.md)]
|
|
||||||
[!INCLUDE [remove-and-prevent-access-to-the-shut-down-restart-sleep-and-hibernate-commands-um](includes/remove-and-prevent-access-to-the-shut-down-restart-sleep-and-hibernate-commands-um.md)]
|
|
||||||
[!INCLUDE [remove-common-program-groups-from-start-menu-u](includes/remove-common-program-groups-from-start-menu-u.md)]
|
|
||||||
[!INCLUDE [remove-logoff-on-the-start-menu-u](includes/remove-logoff-on-the-start-menu-u.md)]
|
|
||||||
[!INCLUDE [remove-personalized-website-recommendations-from-the-recommended-section-in-the-start-menu-um](includes/remove-personalized-website-recommendations-from-the-recommended-section-in-the-start-menu-um.md)]
|
|
||||||
[!INCLUDE [remove-recommended-section-from-start-menu-um](includes/remove-recommended-section-from-start-menu-um.md)]
|
|
||||||
[!INCLUDE [show-run-as-different-user-command-on-start-u](includes/show-run-as-different-user-command-on-start-u.md)]
|
|
||||||
[!INCLUDE [show-or-hide-most-used-list-from-start-menu-um](includes/show-or-hide-most-used-list-from-start-menu-um.md)]
|
|
||||||
[!INCLUDE [start-layout-um](includes/start-layout-um.md)]
|
|
||||||
|
|
||||||
## Next steps
|
The Windows OS exposes many CSPs that apply to the Start menu. For a list, see [Supported CSP policies for Windows 11 Start menu](supported-csp-start-menu-layout-windows.md).
|
||||||
|
|
||||||
> [!div class="nextstepaction"]
|
## Start layout example
|
||||||
> Review the .
|
|
||||||
>
|
|
||||||
>
|
|
||||||
> [guide >](guide.md)
|
|
||||||
|
|
||||||
<!--links-->
|
Here you can find an example of Start layout that you can use as a reference:
|
||||||
|
|
||||||
[WIN-1]: /windows/client-management/mdm/policy-csp-start
|
[!INCLUDE [example-start-layout](includes/example-start-layout.md)]
|
||||||
|
|
||||||
|
## User experience
|
||||||
|
|
||||||
<!--
|
After the settings are applied, sign in to the device. You'll see the Start layout that you configured:
|
||||||
|
|
||||||
## Taskbar
|
|
||||||
|
|
||||||
[DisableControlCenter](/windows/client-management/mdm/policy-csp-start#disablecontrolcenter)
|
|
||||||
[DisableEditingQuickSettings](/windows/client-management/mdm/policy-csp-start#disableeditingquicksettings)
|
|
||||||
[HidePeopleBar](/windows/client-management/mdm/policy-csp-start#hidepeoplebar)
|
|
||||||
[HideTaskViewButton](/windows/client-management/mdm/policy-csp-start#hidetaskviewbutton)
|
|
||||||
[NoPinningToTaskbar](/windows/client-management/mdm/policy-csp-start#nopinningtotaskbar)
|
|
||||||
[SimplifyQuickSettings](/windows/client-management/mdm/policy-csp-start#simplifyquicksettings)
|
|
||||||
|
|
||||||
###
|
|
||||||
|
|
||||||
|
|
||||||
# Supported configuration service provider (CSP) policies for Windows 11 Start menu
|
|
||||||
|
|
||||||
The Windows OS exposes CSPs that are used by MDM providers, like [Microsoft Intune](/mem/intune/fundamentals/what-is-intune). In an MDM policy, these CSPs are settings that you configure in a policy. When the policy is ready, you deploy the policy to your devices.
|
|
||||||
|
|
||||||
This article lists the CSPs that are available to customize the Start menu for Windows 11 devices. Windows 11 uses the [Policy CSP - Start](/windows/client-management/mdm/policy-csp-start). For more general information, see [Configuration service provider (CSP) reference](/windows/client-management/mdm/configuration-service-provider-reference).
|
|
||||||
|
|
||||||
For information on customizing the Start menu layout using policy, see [Customize the Start menu layout](customize-and-export-start-layout.md).
|
|
||||||
|
|
||||||
## Existing Windows CSP policies that Windows 11 supports
|
|
||||||
|
|
||||||
- **Start/ShowOrHideMostUsedApps**: This policy enforces always showing Most Used Apps, or always hiding Most Used Apps in the Start menu. If you use this policy, the [Start/HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#start-hidefrequentlyusedapps) policy is ignored.
|
|
||||||
|
|
||||||
The [Start/HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#start-hidefrequentlyusedapps) policy enforces hiding Most Used Apps on the Start menu. You can't use this policy to enforce always showing Most Used Apps on the Start menu.
|
|
||||||
|
|
||||||
**The following policies are supported starting with Windows 11, version 22H2:**
|
|
||||||
|
|
||||||
- [Start/HideAppList](/windows/client-management/mdm/policy-csp-start#start-hideapplist)
|
|
||||||
- [Start/DisableContextMenus](/windows/client-management/mdm/policy-csp-start#start-disablecontextmenus)
|
|
||||||
|
|
||||||
## Existing CSP policies that Windows 11 doesn't support
|
|
||||||
|
|
||||||
- [Start/StartLayout](/windows/client-management/mdm/policy-csp-start#start-startlayout)
|
|
||||||
- Group policy: `User Configuration\Administrative Templates\Start Menu and Taskbar\Start Layout`
|
|
||||||
|
|
||||||
- [Start/HideRecentlyAddedApps](/windows/client-management/mdm/policy-csp-start#start-hiderecentlyaddedapps)
|
|
||||||
- Group policy: `Computer Configuration\Administrative Templates\Start Menu and Taskbar\Remove "Recently added" list from Start Menu`
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> The following two policies are supported starting in Windows 11, version 22H2
|
|
||||||
|
|
||||||
- [Start/HideAppList](/windows/client-management/mdm/policy-csp-start#start-hideapplist)
|
|
||||||
- Group policy:
|
|
||||||
- `Computer Configuration\Administrative Templates\Start Menu and Taskbar\Remove All Programs list from the Start menu`
|
|
||||||
- `User Configuration\Administrative Templates\Start Menu and Taskbar\Remove All Programs list from the Start menu`
|
|
||||||
|
|
||||||
- [Start/DisableContextMenus](/windows/client-management/mdm/policy-csp-start#start-disablecontextmenus)
|
|
||||||
- Group policy:
|
|
||||||
|
|
||||||
- `Computer Configuration\Administrative Templates\Start Menu and Taskbar\Disable context menus in the Start Menu`
|
|
||||||
- `User Configuration\Administrative Templates\Start Menu and Taskbar\Disable context menus in the Start Menu`
|
|
||||||
|
|
||||||
|
::: zone pivot="windows-11"
|
||||||
:::image type="content" source="images/windows-11.png" alt-text="Screenshot of the Windows 11 Start menu." border="false":::
|
:::image type="content" source="images/windows-11.png" alt-text="Screenshot of the Windows 11 Start menu." border="false":::
|
||||||
|
|
||||||
:::image type="content" source="images/windows-11-no-recommended.png" alt-text="Screenshot of the Windows 11 Start menu without recommendations." border="false":::
|
::: zone-end
|
||||||
|
|
||||||
|
::: zone pivot="windows-10"
|
||||||
|
:::image type="content" source="images/windows-10.png" alt-text="Screenshot of the Windows 10 Start menu." border="false":::
|
||||||
|
|
||||||
|
::: zone-end
|
||||||
|
|
||||||
|
## Start layout configuration errors
|
||||||
|
|
||||||
|
If your Start layout customization isn't applied as you expect, open the **Event Viewer**. Go to **Applications and Services Log** > **Microsoft** > **Windows** > **ShellCommon-StartLayoutPopulation** > **Operational**. Look for the following events:
|
||||||
|
|
||||||
|
- **Event 22**: The XML is malformed. The specified file isn't valid XML. This event can happen if the file has extra spaces or unexpected characters. Or, if the file isn't saved in the UTF8 format.
|
||||||
|
- **Event 64**: The XML is valid, and has unexpected values. This event can happen when the configuration isn't understood, elements aren't in [the required order](start-layout-xml-desktop.md#required-order), or source isn't found, such as a missing or misspelled `.lnk`.
|
||||||
@ -1,399 +0,0 @@
|
|||||||
---
|
|
||||||
title: Customize and export the Start layout
|
|
||||||
description: Learn how to customize the Windows Start layout and export the configuration to apply to other devices.
|
|
||||||
ms.topic: how-to
|
|
||||||
ms.date: 03/04/2024
|
|
||||||
zone_pivot_groups: windows-versions-11-10
|
|
||||||
appliesto:
|
|
||||||
ms.collection:
|
|
||||||
- tier1
|
|
||||||
---
|
|
||||||
|
|
||||||
# Customize and export the Start layout
|
|
||||||
|
|
||||||
This article describes how to customize the Windows Start menu, export its configuration, and deploy the customization to other devices. The article is intended for IT professionals who manage devices in a business or educational environment.\
|
|
||||||
If you are looking for OEM information, see the article [Customize the Start layout](/windows-hardware/customize/desktop/customize-the-windows-11-start-menu)
|
|
||||||
|
|
||||||
::: zone pivot="windows-11"
|
|
||||||
|
|
||||||
Your organization can deploy a customized Start layout to your Windows 11 devices. Customizing the Start layout is common when you have similar devices used by many users, or you want to pin specific apps.
|
|
||||||
|
|
||||||
For example, you can override the default set of apps with your own a set of pinned apps, and in the order you choose. As an administrator, use this feature to pin apps, remove default pinned apps, order the apps, and more.
|
|
||||||
|
|
||||||
To add apps you want pinned to the Start menu, you use a JSON file. In previous Windows versions, IT administrators used an XML file to customize the Start menu. The XML file isn't available on Windows 11 and later ***unless*** [you're an OEM](/windows-hardware/customize/desktop/customize-the-windows-11-start-menu).
|
|
||||||
|
|
||||||
This article shows you how to export an existing Start menu layout, and use the JSON in a Microsoft Intune policy.
|
|
||||||
|
|
||||||
## Before you begin
|
|
||||||
|
|
||||||
When you customize the Start layout, you overwrite the entire full layout. Users can pin and unpin apps, and uninstall apps from Start. When a user signs in or Explorer restarts, Windows reapplies the MDM policy. This action restores the specified layout and doesn't retain any user changes.
|
|
||||||
|
|
||||||
## Start menu features and areas
|
|
||||||
|
|
||||||
The Start menu consistes of set of links to applications, folders, or files that are arranged in a grid of pages.
|
|
||||||
|
|
||||||
:::row:::
|
|
||||||
:::column span="3":::
|
|
||||||
The Start menu has the following areas:
|
|
||||||
|
|
||||||
- **Pinned**: Shows pinned apps, or a subset of all of the apps installed on the device. You can create a list of pinned apps you want on the devices using the **ConfigureStartPins** policy. **ConfigureStartPins** overrides the entire layout, which also removes apps that are pinned by default
|
|
||||||
- **All apps**: Users select this option to see an alphabetical list of all the apps installed on the device.
|
|
||||||
- **Recommended**: Shows recently opened files and recently installed apps
|
|
||||||
:::column-end:::
|
|
||||||
:::column:::
|
|
||||||
:::image type="content" source="./images/windows-11-components.png" alt-text="Sample start menu layout with its components highlighted." border="false" lightbox="./images/windows-11-components.png":::
|
|
||||||
:::column-end:::
|
|
||||||
:::row-end:::
|
|
||||||
|
|
||||||
## Create the JSON file
|
|
||||||
|
|
||||||
On an existing Windows 11 device, set up your own Start layout with the pinned apps you want users to see. Then, use the [Windows PowerShell Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet to export the existing layout to a `LayoutModification.json` file.
|
|
||||||
|
|
||||||
The JSON file controls the Start menu layout, and lists all the apps that are pinned. You can update the JSON file to:
|
|
||||||
|
|
||||||
- Change the order of existing apps. The apps in the JSON file are shown on Start in the same order.
|
|
||||||
- Add more apps by entering the app ID. For more information, see [Get the pinnedList JSON](#get-the-pinnedlist-json) (in this article).
|
|
||||||
|
|
||||||
If you're familiar with creating JSON files, you can create your own `LayoutModification.json` file. But, it's easier and faster to export the layout from an existing device.
|
|
||||||
|
|
||||||
### Export an existing Start layout
|
|
||||||
|
|
||||||
1. Create a folder to save the `.json` file. For example, create the `C:\Layouts` folder.
|
|
||||||
1. On a Windows 11 device, open the Windows PowerShell app.
|
|
||||||
1. Run the following cmdlet. Name the file `LayoutModification.json`.
|
|
||||||
|
|
||||||
```powershell
|
|
||||||
Export-StartLayout -Path "C:\Layouts\LayoutModification.json"
|
|
||||||
```
|
|
||||||
|
|
||||||
### Get the pinnedList JSON
|
|
||||||
|
|
||||||
1. Open the `LayoutModification.json` file in a JSON editor, such as Visual Studio Code or Notepad. For more information, see [edit JSON with Visual Studio Code](https://code.visualstudio.com/docs/languages/json).
|
|
||||||
1. In the file, you see the `pinnedList` section. This section includes all of the pinned apps. Copy the `pinnedList` content in the JSON file. You'll use it in the next section.
|
|
||||||
|
|
||||||
In the following example, you see that Microsoft Edge, Microsoft Word, the Microsoft Store app, and Notepad are pinned:
|
|
||||||
|
|
||||||
```json
|
|
||||||
{
|
|
||||||
"pinnedList": [
|
|
||||||
{ "desktopAppId": "MSEdge" },
|
|
||||||
{ "desktopAppId": "Microsoft.Office.WINWORD.EXE.15" },
|
|
||||||
{ "packagedAppId": "Microsoft.WindowsStore_8wekyb3d8bbwe!App" },
|
|
||||||
{ "packagedAppId": "Microsoft.WindowsNotepad_8wekyb3d8bbwe!App" }
|
|
||||||
]
|
|
||||||
}
|
|
||||||
```
|
|
||||||
|
|
||||||
1. Use the `ConfigureStartPins` policy setting to configure the Start menu, by using a JSON `LayoutModification.json` file to add apps to the Pinned section. In your JSON file, you can add more apps to this section using the following keys:
|
|
||||||
|
|
||||||
| Key | Description |
|
|
||||||
|--|--|
|
|
||||||
| packagedAppID | Use this option for Universal Windows Platform apps. To pin a UWP app, use the app's AUMID. |
|
|
||||||
| desktopAppID | Use this option for unpackaged Win32 apps. To pin a Win32 app, use the app's AUMID. If the app doesn't have an AUMID, then enter the `desktopAppLink` instead. |
|
|
||||||
| desktopAppLink | Use this option for unpackaged Win32 apps that don't have an associated AUMID. To pin this type of app, use the path to the `.lnk` shortcut that points to the app. |
|
|
||||||
|
|
||||||
## Use MDM to create and deploy a pinned list policy
|
|
||||||
|
|
||||||
Now that you have the JSON syntax, you're ready to deploy your customized Start layout to devices in your organization.
|
|
||||||
|
|
||||||
MDM providers can deploy policies to devices managed by the organization, including organization-owned devices, and personal or bring your own device (BYOD). Using an MDM provider, such as Microsoft Intune, you can deploy a policy that configures the pinned list.
|
|
||||||
|
|
||||||
This section shows you how to create a pinned list policy in Intune. There isn't a Group Policy to create a pinned list.
|
|
||||||
|
|
||||||
[!INCLUDE [intune-settings-catalog-1](../../../includes/configure/intune-settings-catalog-1.md)]
|
|
||||||
|
|
||||||
| Category | Setting name | Value |
|
|
||||||
|--|--|--|
|
|
||||||
| **Start** | Configure Start Pins | Content of the JSON file|
|
|
||||||
| **Start** | Configure Start Pins (User) | Content of the JSON file|
|
|
||||||
|
|
||||||
[!INCLUDE [intune-settings-catalog-2](../../../includes/configure/intune-settings-catalog-2.md)]
|
|
||||||
|
|
||||||
Alternatively, you can configure devices using a [custom policy][INT-1] with the [File Explorer CSP][CSP-1].
|
|
||||||
|
|
||||||
| Setting |
|
|
||||||
|--|
|
|
||||||
| - **OMA-URI:** `./User/Vendor/MSFT/Policy/Config/Start/`[ConfigureStartPins](/windows/client-management/mdm/policy-csp-Start?WT.mc_id=Portal-Microsoft_Intune_Workflows#configurestartpins)<br>- **String:** <br>- **Value:** content of the JSON file |
|
|
||||||
| - **OMA-URI:** `./Device/Vendor/MSFT/Policy/Config/Start/`[ConfigureStartPins](/windows/client-management/mdm/policy-csp-Start?WT.mc_id=Portal-Microsoft_Intune_Workflows#configurestartpins)<br>- **Data type:** <br>- **Value:** content of the JSON file |
|
|
||||||
|
|
||||||
::: zone-end
|
|
||||||
|
|
||||||
::: zone pivot="windows-10"
|
|
||||||
|
|
||||||
The easiest method for creating a customized Start layout to apply to other Windows 10 devices is to set up the Start screen on a test computer and then export the layout.
|
|
||||||
|
|
||||||
After you export the layout, decide whether you want to apply a *full* Start layout or a *partial* Start layout.
|
|
||||||
|
|
||||||
When a full Start layout is applied, the users can't pin, unpin, or uninstall apps from Start. Users can view and open all apps in the **All Apps** view, but they can't pin any apps to Start.
|
|
||||||
|
|
||||||
When [a partial Start layout](#configure-a-partial-start-layout) is applied, the contents of the specified tile groups can't be changed, but users can move those groups, and can also create and customize their own groups.
|
|
||||||
|
|
||||||
## Customize the Start screen on your test computer
|
|
||||||
|
|
||||||
To prepare a Start layout for export, you simply customize the Start layout on a test computer.
|
|
||||||
|
|
||||||
To prepare a test computer:
|
|
||||||
|
|
||||||
1. Set up a test computer on which to customize the Start layout. Your test computer should have the operating system that is installed on the users' computers (Windows 10 Pro, Enterprise, or Education). Install all apps and services that the Start layout should display.
|
|
||||||
1. Create a new user account that you'll use to customize the Start layout.
|
|
||||||
|
|
||||||
To customize Start:
|
|
||||||
|
|
||||||
1. Sign in to your test computer with the user account that you created.
|
|
||||||
1. Customize the Start layout as you want users to see it by using the following techniques:
|
|
||||||
|
|
||||||
- **Pin apps to Start**. From Start, type the name of the app. When the app appears in the search results, right-click the app, and then select **Pin to Start**.
|
|
||||||
To view all apps, select **All apps** in the bottom-left corner of Start. Right-click any app, and pin or unpin it from Start.
|
|
||||||
- **Unpin apps** that you don't want to display. To unpin an app, right-click the app, and then select **Unpin from Start**.
|
|
||||||
- **Drag tiles** on Start to reorder or group apps.
|
|
||||||
- **Resize tiles**. To resize tiles, right-click the tile and then select **Resize.**
|
|
||||||
- **Create your own app groups**. Drag the apps to an empty area. To name a group, select above the group of tiles and then type the name in the **Name group** field that appears above the group.
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> If the Start layout includes tiles for apps that are not installed on the device that the layout is later applied to, the tiles for those apps will be blank. The blank tiles will persist until the next time the user signs in, at which time the blank tiles are removed. Some system events may cause the blank tiles to be removed before the next sign-in.
|
|
||||||
|
|
||||||
### Export the Start layout
|
|
||||||
|
|
||||||
When you have the Start layout that you want your users to see, use the [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet in Windows PowerShell to export the Start layout to an .xml file. Start layout is located by default at C:\Users\username\AppData\Local\Microsoft\Windows\Shell\
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> If you include secondary Microsoft Edge tiles (tiles that link to specific websites in Microsoft Edge), see [Add custom images to Microsoft Edge secondary tiles](start-secondary-tiles.md) for instructions.
|
|
||||||
|
|
||||||
To export the Start layout to an .xml file:
|
|
||||||
|
|
||||||
1. While signed in with the same account that you used to customize Start, right-click Start, and select **Windows PowerShell**.
|
|
||||||
1. Run `Export-StartLayout` with the switch `-UseDesktopApplicationID`. For example:
|
|
||||||
|
|
||||||
```PowerShell
|
|
||||||
Export-StartLayout -UseDesktopApplicationID -Path layout.xml
|
|
||||||
```
|
|
||||||
|
|
||||||
In the previous command, `-path` is a required parameter that specifies the path and file name for the export file. You can specify a local path or a UNC path (for example, `\\FileServer01\StartLayouts\StartLayoutMarketing.xml`).
|
|
||||||
|
|
||||||
Use a file name of your choice—for example, StartLayoutMarketing.xml. Include the .xml file name extension. The [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet doesn't append the file name extension, and the policy settings require the extension.
|
|
||||||
|
|
||||||
1. (Optional) Edit the .xml file to add [a taskbar configuration](../taskbar/configure.md) or to [modify the exported layout](start-layout-xml-desktop.md). When you make changes to the exported layout, be aware that [the order of the elements in the .xml file is critical.](start-layout-xml-desktop.md#required-order)
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> If the Start layout that you export contains tiles for desktop (Win32) apps or .url links, **Export-StartLayout** will use **DesktopApplicationLinkPath** in the resulting file. Use a text or XML editor to change **DesktopApplicationLinkPath** to **DesktopApplicationID**. See [Specify Start tiles](start-layout-xml-desktop.md#specify-start-tiles) for details on using the app ID in place of the link path.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> All clients that the start layout applies to must have the apps and other shortcuts present on the local system in the same location as the source for the Start layout.
|
|
||||||
>
|
|
||||||
> For scripts and application tile pins to work correctly, follow these rules:
|
|
||||||
>
|
|
||||||
>- Executable files and scripts should be listed in \Program Files or wherever the installer of the app places them.
|
|
||||||
>- Shortcuts that will pinned to Start should be placed in \ProgramData\Microsoft\Windows\Start Menu\Programs.
|
|
||||||
>- If you place executable files or scripts in the \ProgramData\Microsoft\Windows\Start Menu\Programs folder, they will not pin to Start.
|
|
||||||
>- Start on Windows 10 does not support subfolders. We only support one folder. For example, \ProgramData\Microsoft\Windows\Start Menu\Programs\Folder. If you go any deeper than one folder, Start will compress the contents of all the subfolder to the top level.
|
|
||||||
>- Three additional shortcuts are pinned to the start menu after the export. These are shortcuts to %ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs, %APPDATA%\Microsoft\Windows\Start Menu\Programs, and %APPDATA%\Microsoft\Windows\Start Menu\Programs\System Tools\.
|
|
||||||
|
|
||||||
### Configure a partial Start layout
|
|
||||||
|
|
||||||
A partial Start layout enables you to add one or more customized tile groups to users' Start screens or menus, while still allowing users to make changes to other parts of the Start layout. All groups that you add are *locked*, meaning users can't change the contents of those tile groups, however users can change the location of those groups. Locked groups are identified with an icon, as shown in the following image.
|
|
||||||
|
|
||||||
:::image type="content" source="images/windows-10-partial-layout.png" alt-text="Screenshot of the Windows 10 Start menu with partial layout.":::
|
|
||||||
|
|
||||||
When a partial Start layout is applied for the first time, the new groups are added to the users' existing Start layouts. If an app tile is in both an existing group and in a new locked group, the duplicate app tile is removed from the existing (unlocked) group.
|
|
||||||
|
|
||||||
When a partial Start layout is applied to a device that already has a StartLayout.xml applied, groups that were added previously are removed and the groups in the new layout are added.
|
|
||||||
|
|
||||||
If the Start layout is applied by Group Policy or MDM, and the policy is removed, the groups remain on the devices but become unlocked.
|
|
||||||
|
|
||||||
To configure a partial Start screen layout:
|
|
||||||
|
|
||||||
1. [Customize the Start layout](#customize-the-start-screen-on-your-test-computer).
|
|
||||||
1. [Export the Start layout](#export-the-start-layout).
|
|
||||||
1. Open the layout .xml file. There is a `<DefaultLayoutOverride>` element. Add `LayoutCustomizationRestrictionType="OnlySpecifiedGroups"` to the **DefaultLayoutOverride** element as follows:
|
|
||||||
|
|
||||||
```xml
|
|
||||||
<DefaultLayoutOverride LayoutCustomizationRestrictionType="OnlySpecifiedGroups">
|
|
||||||
```
|
|
||||||
|
|
||||||
1. Save the file and apply using any of the deployment methods.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> Office 2019 tiles might be removed from the Start menu when you upgrade Office 201. This only occurs if Office 2019 app tiles are in a custom group in the Start menu and only contains the Office 2019 app tiles. To avoid this problem, place another app tile in the Office 2019 group prior to the upgrade. For example, add Notepad.exe or calc.exe to the group. This issue occurs because Office 2019 removes and reinstalls the apps when they are upgraded. Start removes empty groups when it detects that all apps for that group have been removed.
|
|
||||||
|
|
||||||
You can deploy the resulting .xml file to devices using one of the following methods:
|
|
||||||
|
|
||||||
- Configuration Service Provider (CSP)
|
|
||||||
- Group Policy
|
|
||||||
- Provisioning package
|
|
||||||
|
|
||||||
[!INCLUDE [tab-intro](../../../includes/configure/tab-intro.md)]
|
|
||||||
|
|
||||||
#### [:::image type="icon" source="../images/icons/intune.svg"::: **Intune/CSP**](#tab/intune)
|
|
||||||
|
|
||||||
You can use a mobile device management (MDM) policy to deploy a customized Start and taskbar layout to users. No reimaging is required. The layout can be updated simply by overwriting the `.xml` file that contains the layout. This feature enables you to customize Start layouts for different departments or organizations, with minimal management overhead.
|
|
||||||
|
|
||||||
**Before you begin**: [Customize and export Start layout](customize-and-export-start-layout.md).
|
|
||||||
|
|
||||||
>[!WARNING]
|
|
||||||
>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.
|
|
||||||
|
|
||||||
Two features enable Start layout control:
|
|
||||||
|
|
||||||
- The **Export-StartLayout** cmdlet in Windows PowerShell exports a description of the current Start layout in .xml file format.
|
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
>To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](/powershell/module/startlayout/import-startlayout) cmdlet.
|
|
||||||
|
|
||||||
- In Microsoft Intune, you select the Start layout XML file and add it to a device configuration profile.
|
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
>Please do not include XML Prologs like \<?xml version="1.0" encoding="utf-8"?\> in the Start layout XML file. The settings may not be reflected correctly.
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-domaingpodeployment"></a>Create a policy for your customized Start layout
|
|
||||||
|
|
||||||
The following example uses Microsoft Intune to configure an MDM policy that applies a customized Start layout:
|
|
||||||
|
|
||||||
1. Sign in to the [Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
|
||||||
|
|
||||||
1. Select **Devices** > **Configuration profiles** > **Create profile**.
|
|
||||||
|
|
||||||
1. Enter the following properties:
|
|
||||||
|
|
||||||
- **Platform**: Select **Windows 10 and later**.
|
|
||||||
- **Profile type**: Select **Templates** > **Device restrictions** > **Create**.
|
|
||||||
|
|
||||||
1. In **Basics**, enter the following properties:
|
|
||||||
|
|
||||||
- **Name**: Enter a descriptive name for the profile. Name your profiles so you can easily identify it later. For example, a good profile name is **Customize Start menu and taskbar**.
|
|
||||||
- **Description**: Enter a description for the profile. This setting is optional, but recommended.
|
|
||||||
|
|
||||||
1. Select **Next**.
|
|
||||||
|
|
||||||
1. In **Configuration settings**, select **Start**:
|
|
||||||
|
|
||||||
- If you're using an XML file, select **Start menu layout**. Browse to and select your Start layout XML file.
|
|
||||||
- If you don't have an XML file, configure the others settings. For more information on these settings, see [Start settings in Microsoft Intune](/mem/intune/configuration/device-restrictions-windows-10#start).
|
|
||||||
|
|
||||||
1. Select **Next**.
|
|
||||||
1. In **Scope tags**, select **Next**. For more information about scope tags, see [Use RBAC and scope tags for distributed IT](/mem/intune/fundamentals/scope-tags).
|
|
||||||
1. In **Assignments**, select the user or groups that will receive your profile. Select **Next**. For more information on assigning profiles, see [Assign user and device profiles](/mem/intune/configuration/device-profile-assign).
|
|
||||||
1. In **Review + create**, review your settings. When you select **Create**, your changes are saved, and the profile is assigned. The policy is also shown in the profiles list.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> For third party partner MDM solutions, you may need to use an OMA-URI setting for Start layout, based on the [Policy configuration service provider (CSP)](/windows/client-management/mdm/policy-configuration-service-provider). The OMA-URI setting is `./User/Vendor/MSFT/Policy/Config/Start/StartLayout`.
|
|
||||||
|
|
||||||
#### [:::image type="icon" source="../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
|
|
||||||
|
|
||||||
You can use a provisioning package that you create with Windows Configuration Designer to deploy a customized Start and taskbar layout to users. No reimaging is required, and the Start and taskbar layout can be updated by overwriting the .xml file that contains the layout. The provisioning package can be applied to a running device. This enables you to customize Start and taskbar layouts for different departments or organizations, with minimal management overhead.
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> If you use a provisioning package to configure the taskbar, your configuration will be reapplied each time the explorer.exe process restarts. If your configuration pins an app and the user unpins that app, the user's change will be overwritten the next time the configuration is applied. To apply a taskbar configuration and allow users to make changes that will persist, apply your configuration by using Group Policy.
|
|
||||||
|
|
||||||
**Before you begin**: [Customize and export Start layout](customize-and-export-start-layout.md) for desktop editions.
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](/powershell/module/startlayout/import-startlayout) cmdlet.
|
|
||||||
|
|
||||||
- [You can modify the Start .xml file](../taskbar/configure.md) to include `<CustomTaskbarLayoutCollection>` or create an .xml file just for the taskbar configuration.
|
|
||||||
|
|
||||||
- In Windows Configuration Designer, you use the **Policies/Start/StartLayout** setting to provide the contents of the .xml file that defines the Start and taskbar layout.
|
|
||||||
|
|
||||||
## Prepare the Start layout XML file
|
|
||||||
|
|
||||||
The **Export-StartLayout** cmdlet produces an XML file. Because Windows Configuration Designer produces a customizations.xml file that contains the configuration settings, adding the Start layout section to the customizations.xml file directly would result in an XML file embedded in an XML file. Before you add the Start layout section to the customizations.xml file, you must replace the markup characters in your layout.xml with escape characters.
|
|
||||||
|
|
||||||
1. Copy the contents of layout.xml into an online tool that escapes characters
|
|
||||||
1. During the procedure to create a provisioning package, you will copy the text with the escape characters and paste it in the customizations.xml file for your project
|
|
||||||
|
|
||||||
## PPKG
|
|
||||||
|
|
||||||
1. Expand **Runtime settings** > **Policies** > **Start**, and click **StartLayout**.
|
|
||||||
|
|
||||||
#### [:::image type="icon" source="../images/icons/group-policy.svg"::: **GPO**](#tab/gpo)
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
>[!WARNING]
|
|
||||||
>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.
|
|
||||||
|
|
||||||
**Before you begin**: [Customize and export Start layout](customize-and-export-start-layout.md)
|
|
||||||
|
|
||||||
## Operating system requirements
|
|
||||||
|
|
||||||
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](/troubleshoot/windows-server/group-policy/create-central-store-domain-controller) in the Microsoft Knowledge Base.
|
|
||||||
|
|
||||||
Three features enable Start and taskbar layout control:
|
|
||||||
|
|
||||||
- The [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet in Windows PowerShell exports a description of the current Start layout in .xml file format.
|
|
||||||
>[!NOTE]
|
|
||||||
>To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](/powershell/module/startlayout/import-startlayout) cmdlet.
|
|
||||||
- [You can modify the Start .xml file](../taskbar/configure.md) to include `<CustomTaskbarLayoutCollection>` 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.
|
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
>To learn how customize Start to include your line-of-business apps when you deploy Windows 10, see [Customize the Windows 10 Start layout]( https://go.microsoft.com/fwlink/p/?LinkId=620863).
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-domaingpodeployment"></a>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](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)).
|
|
||||||
|
|
||||||
## <a href="" id="bkmk-localgpimport"></a>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**.
|
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
>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](#bkmk-domaingpodeployment).
|
|
||||||
>
|
|
||||||
>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](/previous-versions/windows/it-pro/windows-vista/cc766291(v=ws.10)). 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:
|
|
||||||
|
|
||||||
1. On the test computer, press the Windows key, type **gpedit**, and then select **Edit group policy (Control panel)**.
|
|
||||||
1. Go to **User Configuration** or **Computer Configuration** > **Administrative Templates** >**Start Menu and Taskbar**.
|
|
||||||
1. Right-click **Start Layout** in the right pane, and click **Edit**.
|
|
||||||
1. Enter the following settings, and then click **OK**:
|
|
||||||
1. Select **Enabled**.
|
|
||||||
1. Under **Options**, specify the path to the .xml file that contains the Start and taskbar layout. For example, type **C:\\Users\\Test01\\StartScreenMarketing.xml**.
|
|
||||||
1. Optionally, enter a comment to identify the Start and taskbar layout.
|
|
||||||
|
|
||||||
> [!IMPORTANT]
|
|
||||||
> 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:
|
|
||||||
>
|
|
||||||
> `(ls <path>).LastWriteTime = Get-Date`
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
::: zone-end
|
|
||||||
|
|
||||||
The Windows OS exposes many CSPs that apply to the Start menu. For a list, see [Supported CSP policies for Windows 11 Start menu](supported-csp-start-menu-layout-windows.md).
|
|
||||||
|
|
||||||
## Start layout example
|
|
||||||
|
|
||||||
Here you can find an example of Start layout that you can use as a reference:
|
|
||||||
|
|
||||||
[!INCLUDE [example-start-layout](includes/example-start-layout.md)]
|
|
||||||
|
|
||||||
## User experience
|
|
||||||
|
|
||||||
After the settings are applied, sign in to the device. You'll see the Start layout that you configured:
|
|
||||||
|
|
||||||
::: zone pivot="windows-11"
|
|
||||||
:::image type="content" source="images/windows-11.png" alt-text="Screenshot of the Windows 11 Start menu." border="false":::
|
|
||||||
|
|
||||||
::: zone-end
|
|
||||||
|
|
||||||
::: zone pivot="windows-10"
|
|
||||||
:::image type="content" source="images/windows-10.png" alt-text="Screenshot of the Windows 10 Start menu." border="false":::
|
|
||||||
|
|
||||||
::: zone-end
|
|
||||||
184
windows/configuration/start/policy-settings.md
Normal file
184
windows/configuration/start/policy-settings.md
Normal file
@ -0,0 +1,184 @@
|
|||||||
|
---
|
||||||
|
title: Start menu policy settings
|
||||||
|
description: Learn about the policy settings to configure the Windows Start menu.
|
||||||
|
ms.topic: reference
|
||||||
|
ms.date: 03/15/2024
|
||||||
|
appliesto:
|
||||||
|
zone_pivot_groups: windows-versions-11-10
|
||||||
|
---
|
||||||
|
|
||||||
|
# Start menu policy settings
|
||||||
|
|
||||||
|
This reference article provides a comprehensive list of policy settings for Start menu.
|
||||||
|
|
||||||
|
:::row:::
|
||||||
|
:::column span="2":::
|
||||||
|
The list of settings is sorted alphabetically and organized in four categories:
|
||||||
|
|
||||||
|
1. **Start layout**: settings to control the Start menu layout
|
||||||
|
1. **User options**: settings to control the options exposed when selecting the user icon
|
||||||
|
1. **Pinned folders**: settings to control the folders pinned for quick access
|
||||||
|
1. **Power options**: settings to control the options exposed when selecting the power icon
|
||||||
|
|
||||||
|
:::column-end:::
|
||||||
|
:::column span="2":::
|
||||||
|
::: zone pivot="windows-10"
|
||||||
|
:::image type="content" source="./images/windows-10-settings.png" alt-text="Sample start menu layout with its components highlighted." border="false" lightbox="./images/windows-10-settings.png":::
|
||||||
|
::: zone-end
|
||||||
|
|
||||||
|
::: zone pivot="windows-11"
|
||||||
|
:::image type="content" source="./images/windows-11-settings.png" alt-text="Sample start menu layout with its components highlighted." border="false" lightbox="./images/windows-11-settings.png":::
|
||||||
|
::: zone-end
|
||||||
|
|
||||||
|
:::column-end:::
|
||||||
|
:::row-end:::
|
||||||
|
|
||||||
|
For information about how to configure these settings, see [Configure the Start menu](configure.md).
|
||||||
|
|
||||||
|
Select one of the tabs to see the list of available settings:
|
||||||
|
|
||||||
|
#### [:::image type="icon" source="../images/icons/start.svg"::: **Start layout**](#tab/start)
|
||||||
|
|
||||||
|
The following table lists the policies that control the Start menu layout. Select the policy name for more details.
|
||||||
|
|
||||||
|
|Policy name| CSP | GPO |
|
||||||
|
|-|-|-|
|
||||||
|
|[ConfigureStartPins](/windows/client-management/mdm/policy-csp-start#configurestartpins)|✅||
|
||||||
|
|[DisableContextMenus](/windows/client-management/mdm/policy-csp-start#disablecontextmenus)|✅||
|
||||||
|
|[ForceStartSize](/windows/client-management/mdm/policy-csp-start#forcestartsize)|✅||
|
||||||
|
|[HideAppList](/windows/client-management/mdm/policy-csp-start#hideapplist)|✅||
|
||||||
|
|[HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#hidefrequentlyusedapps)|✅||
|
||||||
|
|[HideRecentJumplists](/windows/client-management/mdm/policy-csp-start#hiderecentjumplists)|✅||
|
||||||
|
|[HideRecentlyAddedApps](/windows/client-management/mdm/policy-csp-start#hiderecentlyaddedapps)|✅||
|
||||||
|
|[HideRecommendedPersonalizedSites](/windows/client-management/mdm/policy-csp-start#hiderecommendedpersonalizedsites)|✅||
|
||||||
|
|[HideRecommendedSection](/windows/client-management/mdm/policy-csp-start#hiderecommendedsection)|✅||
|
||||||
|
|[ImportEdgeAssets](/windows/client-management/mdm/policy-csp-start#importedgeassets)|✅||
|
||||||
|
|[ShowOrHideMostUsedApps](/windows/client-management/mdm/policy-csp-start#showorhidemostusedapps)|✅||
|
||||||
|
|[StartLayout](/windows/client-management/mdm/policy-csp-start#startlayout)|✅||
|
||||||
|
|
||||||
|
#### [:::image type="icon" source="../images/icons/user.svg"::: **User options**](#tab/user)
|
||||||
|
|
||||||
|
[HideChangeAccountSettings](/windows/client-management/mdm/policy-csp-start#hidechangeaccountsettings)
|
||||||
|
[HideLock](/windows/client-management/mdm/policy-csp-start#hidelock)
|
||||||
|
[HideSignOut](/windows/client-management/mdm/policy-csp-start#hidesignout)
|
||||||
|
[HideSwitchAccount](/windows/client-management/mdm/policy-csp-start#hideswitchaccount)
|
||||||
|
[HideUserTile](/windows/client-management/mdm/policy-csp-start#hideusertile)
|
||||||
|
|
||||||
|
#### [:::image type="icon" source="../images/icons/folder.svg"::: **Pinned folders**](#tab/folders)
|
||||||
|
|
||||||
|
[AllowPinnedFolderDocuments](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderdocuments)
|
||||||
|
[AllowPinnedFolderDownloads](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderdownloads)
|
||||||
|
[AllowPinnedFolderFileExplorer](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderfileexplorer)
|
||||||
|
[AllowPinnedFolderHomeGroup](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderhomegroup)
|
||||||
|
[AllowPinnedFolderMusic](/windows/client-management/mdm/policy-csp-start#allowpinnedfoldermusic)
|
||||||
|
[AllowPinnedFolderNetwork](/windows/client-management/mdm/policy-csp-start#allowpinnedfoldernetwork)
|
||||||
|
[AllowPinnedFolderPersonalFolder](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderpersonalfolder)
|
||||||
|
[AllowPinnedFolderPictures](/windows/client-management/mdm/policy-csp-start#allowpinnedfolderpictures)
|
||||||
|
[AllowPinnedFolderSettings](/windows/client-management/mdm/policy-csp-start#allowpinnedfoldersettings)
|
||||||
|
[AllowPinnedFolderVideos](/windows/client-management/mdm/policy-csp-start#allowpinnedfoldervideos)
|
||||||
|
|
||||||
|
#### [:::image type="icon" source="../images/icons/power.svg"::: **Power options**](#tab/power)
|
||||||
|
|
||||||
|
[HideHibernate](/windows/client-management/mdm/policy-csp-start#hidehibernate)
|
||||||
|
[HidePowerButton](/windows/client-management/mdm/policy-csp-start#hidepowerbutton)
|
||||||
|
[HideRestart](/windows/client-management/mdm/policy-csp-start#hiderestart)
|
||||||
|
[HideShutDown](/windows/client-management/mdm/policy-csp-start#hideshutdown)
|
||||||
|
[HideSleep](/windows/client-management/mdm/policy-csp-start#hidesleep)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
[!INCLUDE [clear-history-of-recently-opened-documents-on-exit-u](includes/clear-history-of-recently-opened-documents-on-exit-u.md)]
|
||||||
|
[!INCLUDE [clear-the-recent-programs-list-for-new-users-u](includes/clear-the-recent-programs-list-for-new-users-u.md)]
|
||||||
|
[!INCLUDE [clear-tile-notifications-during-log-on-u](includes/clear-tile-notifications-during-log-on-u.md)]
|
||||||
|
[!INCLUDE [disable-context-menus-in-the-start-menu-um](includes/disable-context-menus-in-the-start-menu-um.md)]
|
||||||
|
[!INCLUDE [disable-editing-quick-settings-m](includes/disable-editing-quick-settings-m.md)]
|
||||||
|
[!INCLUDE [do-not-keep-history-of-recently-opened-documents-um](includes/do-not-keep-history-of-recently-opened-documents-um.md)]
|
||||||
|
[!INCLUDE [do-not-use-the-search-based-method-when-resolving-shell-shortcuts-u](includes/do-not-use-the-search-based-method-when-resolving-shell-shortcuts-u.md)]
|
||||||
|
[!INCLUDE [do-not-use-the-tracking-based-method-when-resolving-shell-shortcuts-u](includes/do-not-use-the-tracking-based-method-when-resolving-shell-shortcuts-u.md)]
|
||||||
|
[!INCLUDE [force-start-to-be-either-full-screen-size-or-menu-size-um](includes/force-start-to-be-either-full-screen-size-or-menu-size-um.md)]
|
||||||
|
[!INCLUDE [prevent-changes-to-taskbar-and-start-menu-settings-um](includes/prevent-changes-to-taskbar-and-start-menu-settings-um.md)]
|
||||||
|
[!INCLUDE [prevent-users-from-customizing-their-start-screen-u](includes/prevent-users-from-customizing-their-start-screen-u.md)]
|
||||||
|
[!INCLUDE [prevent-users-from-uninstalling-applications-from-start-um](includes/prevent-users-from-uninstalling-applications-from-start-um.md)]
|
||||||
|
[!INCLUDE [remove-recently-added-list-from-start-menu-um](includes/remove-recently-added-list-from-start-menu-um.md)]
|
||||||
|
[!INCLUDE [remove-all-programs-list-from-the-start-menu-um](includes/remove-all-programs-list-from-the-start-menu-um.md)]
|
||||||
|
[!INCLUDE [remove-and-prevent-access-to-the-shut-down-restart-sleep-and-hibernate-commands-um](includes/remove-and-prevent-access-to-the-shut-down-restart-sleep-and-hibernate-commands-um.md)]
|
||||||
|
[!INCLUDE [remove-common-program-groups-from-start-menu-u](includes/remove-common-program-groups-from-start-menu-u.md)]
|
||||||
|
[!INCLUDE [remove-logoff-on-the-start-menu-u](includes/remove-logoff-on-the-start-menu-u.md)]
|
||||||
|
[!INCLUDE [remove-personalized-website-recommendations-from-the-recommended-section-in-the-start-menu-um](includes/remove-personalized-website-recommendations-from-the-recommended-section-in-the-start-menu-um.md)]
|
||||||
|
[!INCLUDE [remove-recommended-section-from-start-menu-um](includes/remove-recommended-section-from-start-menu-um.md)]
|
||||||
|
[!INCLUDE [show-run-as-different-user-command-on-start-u](includes/show-run-as-different-user-command-on-start-u.md)]
|
||||||
|
[!INCLUDE [show-or-hide-most-used-list-from-start-menu-um](includes/show-or-hide-most-used-list-from-start-menu-um.md)]
|
||||||
|
[!INCLUDE [start-layout-um](includes/start-layout-um.md)]
|
||||||
|
|
||||||
|
## Next steps
|
||||||
|
|
||||||
|
> [!div class="nextstepaction"]
|
||||||
|
> Review the .
|
||||||
|
>
|
||||||
|
>
|
||||||
|
> [guide >](guide.md)
|
||||||
|
|
||||||
|
<!--links-->
|
||||||
|
|
||||||
|
[WIN-1]: /windows/client-management/mdm/policy-csp-start
|
||||||
|
|
||||||
|
|
||||||
|
<!--
|
||||||
|
|
||||||
|
## Taskbar
|
||||||
|
|
||||||
|
[DisableControlCenter](/windows/client-management/mdm/policy-csp-start#disablecontrolcenter)
|
||||||
|
[DisableEditingQuickSettings](/windows/client-management/mdm/policy-csp-start#disableeditingquicksettings)
|
||||||
|
[HidePeopleBar](/windows/client-management/mdm/policy-csp-start#hidepeoplebar)
|
||||||
|
[HideTaskViewButton](/windows/client-management/mdm/policy-csp-start#hidetaskviewbutton)
|
||||||
|
[NoPinningToTaskbar](/windows/client-management/mdm/policy-csp-start#nopinningtotaskbar)
|
||||||
|
[SimplifyQuickSettings](/windows/client-management/mdm/policy-csp-start#simplifyquicksettings)
|
||||||
|
|
||||||
|
###
|
||||||
|
|
||||||
|
|
||||||
|
# Supported configuration service provider (CSP) policies for Windows 11 Start menu
|
||||||
|
|
||||||
|
The Windows OS exposes CSPs that are used by MDM providers, like [Microsoft Intune](/mem/intune/fundamentals/what-is-intune). In an MDM policy, these CSPs are settings that you configure in a policy. When the policy is ready, you deploy the policy to your devices.
|
||||||
|
|
||||||
|
This article lists the CSPs that are available to customize the Start menu for Windows 11 devices. Windows 11 uses the [Policy CSP - Start](/windows/client-management/mdm/policy-csp-start). For more general information, see [Configuration service provider (CSP) reference](/windows/client-management/mdm/configuration-service-provider-reference).
|
||||||
|
|
||||||
|
For information on customizing the Start menu layout using policy, see [Customize the Start menu layout](customize-and-export-start-layout.md).
|
||||||
|
|
||||||
|
## Existing Windows CSP policies that Windows 11 supports
|
||||||
|
|
||||||
|
- **Start/ShowOrHideMostUsedApps**: This policy enforces always showing Most Used Apps, or always hiding Most Used Apps in the Start menu. If you use this policy, the [Start/HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#start-hidefrequentlyusedapps) policy is ignored.
|
||||||
|
|
||||||
|
The [Start/HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#start-hidefrequentlyusedapps) policy enforces hiding Most Used Apps on the Start menu. You can't use this policy to enforce always showing Most Used Apps on the Start menu.
|
||||||
|
|
||||||
|
**The following policies are supported starting with Windows 11, version 22H2:**
|
||||||
|
|
||||||
|
- [Start/HideAppList](/windows/client-management/mdm/policy-csp-start#start-hideapplist)
|
||||||
|
- [Start/DisableContextMenus](/windows/client-management/mdm/policy-csp-start#start-disablecontextmenus)
|
||||||
|
|
||||||
|
## Existing CSP policies that Windows 11 doesn't support
|
||||||
|
|
||||||
|
- [Start/StartLayout](/windows/client-management/mdm/policy-csp-start#start-startlayout)
|
||||||
|
- Group policy: `User Configuration\Administrative Templates\Start Menu and Taskbar\Start Layout`
|
||||||
|
|
||||||
|
- [Start/HideRecentlyAddedApps](/windows/client-management/mdm/policy-csp-start#start-hiderecentlyaddedapps)
|
||||||
|
- Group policy: `Computer Configuration\Administrative Templates\Start Menu and Taskbar\Remove "Recently added" list from Start Menu`
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> The following two policies are supported starting in Windows 11, version 22H2
|
||||||
|
|
||||||
|
- [Start/HideAppList](/windows/client-management/mdm/policy-csp-start#start-hideapplist)
|
||||||
|
- Group policy:
|
||||||
|
- `Computer Configuration\Administrative Templates\Start Menu and Taskbar\Remove All Programs list from the Start menu`
|
||||||
|
- `User Configuration\Administrative Templates\Start Menu and Taskbar\Remove All Programs list from the Start menu`
|
||||||
|
|
||||||
|
- [Start/DisableContextMenus](/windows/client-management/mdm/policy-csp-start#start-disablecontextmenus)
|
||||||
|
- Group policy:
|
||||||
|
|
||||||
|
- `Computer Configuration\Administrative Templates\Start Menu and Taskbar\Disable context menus in the Start Menu`
|
||||||
|
- `User Configuration\Administrative Templates\Start Menu and Taskbar\Disable context menus in the Start Menu`
|
||||||
|
|
||||||
|
:::image type="content" source="images/windows-11.png" alt-text="Screenshot of the Windows 11 Start menu." border="false":::
|
||||||
|
|
||||||
|
:::image type="content" source="images/windows-11-no-recommended.png" alt-text="Screenshot of the Windows 11 Start menu without recommendations." border="false":::
|
||||||
|
|
||||||
@ -1,10 +1,8 @@
|
|||||||
items:
|
items:
|
||||||
- name: Customize and export the Start layout
|
- name: Configure Start
|
||||||
href: customize-and-export-start-layout.md
|
|
||||||
- name: Configure the Start menu
|
|
||||||
href: configure.md
|
href: configure.md
|
||||||
- name: Start layout and taskbar
|
- name: Start policy settings
|
||||||
href: windows-10-start-layout-options-and-policies.md
|
href: policy-settings.md
|
||||||
- name: Use XML
|
- name: Use XML
|
||||||
items:
|
items:
|
||||||
- name: Add image for secondary Microsoft Edge tiles
|
- name: Add image for secondary Microsoft Edge tiles
|
||||||
|
|||||||
@ -1,190 +0,0 @@
|
|||||||
---
|
|
||||||
title: Customize and manage the Windows 10 Start and taskbar layout
|
|
||||||
description: On Windows devices, customize the start menu layout and taskbar using XML, group policy, provisioning package, or MDM policy. You can add pinned folders, add a start menu size, pin apps to the taskbar, and more.
|
|
||||||
ms.topic: how-to
|
|
||||||
ms.date: 08/05/2021
|
|
||||||
appliesto:
|
|
||||||
- ✅ <a href=/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
|
||||||
---
|
|
||||||
|
|
||||||
# Customize the Start menu and taskbar layout on Windows 10 and later devices
|
|
||||||
|
|
||||||
> **Looking for consumer information?** [See what's on the Start menu](https://support.microsoft.com/help/17195/windows-10-see-whats-on-the-menu)
|
|
||||||
>
|
|
||||||
> **Looking for OEM information?** See [Customize the Taskbar](/windows-hardware/customize/desktop/customize-the-windows-11-taskbar) and [Customize the Start layout](/windows-hardware/customize/desktop/customize-the-windows-11-start-menu).
|
|
||||||
|
|
||||||
Your organization can deploy a customized Start and taskbar to Windows 10 Professional, Enterprise, or Education devices. Use a standard, customized Start layout on devices that are common to multiple users, and devices that are locked down. Configuring the taskbar allows you to pin useful apps for your users, and remove apps that are pinned by default.
|
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
>Support for applying a customized taskbar using MDM is added in Windows 10, version 1701.
|
|
||||||
|
|
||||||
As administrator, you can use these features to customize Start and taskbar to meet your organization needs. This article describes the different ways you can customize Start and taskbar, and lists the Start policies. It also includes taskbar information on a clean operating system (OS) installation, and when an OS is upgraded.
|
|
||||||
|
|
||||||
>[!NOTE]
|
|
||||||
>For information on using the layout modification XML to configure Start with roaming user profiles, see [Deploy Roaming User Profiles](/windows-server/storage/folder-redirection/deploy-roaming-user-profiles#step-7-optionally-specify-a-start-layout-for-windows-10-pcs).
|
|
||||||
>
|
|
||||||
>Using CopyProfile for Start menu customization in Windows 10 isn't supported. For more information [Customize the Default User Profile by Using CopyProfile](/windows-hardware/manufacture/desktop/customize-the-default-user-profile-by-using-copyprofile)
|
|
||||||
|
|
||||||
## Use XML
|
|
||||||
|
|
||||||
On an existing Windows device, you can set up the **Start** screen, and then export the layout to an XML file. When you have the XML file, add this file to a group policy, a Windows Configuration Designer provisioning package, or a mobile device management (MDM) policy. Using these methods, you can deploy the XML file to your devices. When the devices receive your policy, they'll use the layout configured in the XML file.
|
|
||||||
|
|
||||||
For more information, see [Customize and export Start layout](customize-and-export-start-layout.md).
|
|
||||||
|
|
||||||
For the **taskbar**, you can use the same XML file as the start screen. Or, you can create a new XML file. When you have the XML file, add this file to a group policy or a provisioning package. Using these methods, you can deploy the XML file to your devices. When the devices receive your policy, they'll use the taskbar settings you configured in the XML file.
|
|
||||||
|
|
||||||
For more information, see [Configure Windows 10 taskbar](../taskbar/configure.md).
|
|
||||||
|
|
||||||
## Use group policy
|
|
||||||
|
|
||||||
Using group policy objects (GPO), you can manage different parts of the Start menu and taskbar. You don't need to reimage the devices. Using administrative templates, you configure settings in a policy, and then deploy this policy to your devices. [Start menu policy settings](#start-menu-policy-settings) (in this article) lists the policies you can configure.
|
|
||||||
|
|
||||||
## Use provisioning packages
|
|
||||||
|
|
||||||
Provisioning packages are containers that include a set of configuration settings. They're designed to configure a device quickly, without installing a new image. For more information on what provisioning packages are, and what they do, see [Provisioning packages](../provisioning-packages/provisioning-packages.md).
|
|
||||||
|
|
||||||
Using a provisioning package, you can customize the Start and taskbar.
|
|
||||||
|
|
||||||
## Use a mobile device management (MDM) solution
|
|
||||||
|
|
||||||
Using an MDM solution, you add an XML file to a policy, and then deploy this policy to your devices.
|
|
||||||
|
|
||||||
If you use Microsoft Intune for your MDM solution, then you can use settings to configure Start and the taskbar. For more information on the settings you can configure, see [Start settings in Microsoft Intune](/mem/intune/configuration/device-restrictions-windows-10#start).
|
|
||||||
|
|
||||||
## Start menu policy settings
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
The following list includes the different Start options, and any policy or local settings. The settings in the list can also be used in a provisioning package. If you use a provisioning package, see the [Windows Configuration Designer reference](../wcd/wcd-policies.md#start).
|
|
||||||
|
|
||||||
- **User tile**
|
|
||||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Remove Logoff on the Start menu`
|
|
||||||
- **Local setting**: None
|
|
||||||
- **MDM policy**:
|
|
||||||
- Start/HideUserTile
|
|
||||||
- Start/HideSwitchAccount
|
|
||||||
- Start/HideSignOut
|
|
||||||
- Start/HideLock
|
|
||||||
- Start/HideChangeAccountSettings
|
|
||||||
|
|
||||||
- **Most used**
|
|
||||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Remove frequent programs from the Start menu`
|
|
||||||
- **Local setting**: Settings > Personalization > Start > Show most used apps
|
|
||||||
- **MDM policy**: Start/HideFrequentlyUsedApps
|
|
||||||
|
|
||||||
- **Suggestions, Dynamically inserted app tile**
|
|
||||||
- **Group policy**: `Computer Configuration\Administrative Templates\Windows Components\Cloud Content\Turn off Microsoft consumer experiences`
|
|
||||||
|
|
||||||
This policy also enables or disables notifications for:
|
|
||||||
|
|
||||||
- A user's Microsoft account
|
|
||||||
- App tiles that Microsoft dynamically adds to the default Start menu
|
|
||||||
|
|
||||||
- **Local setting**: Settings > Personalization > Start > Occasionally show suggestions in Start
|
|
||||||
- **MDM policy**: Allow Windows Consumer Features
|
|
||||||
|
|
||||||
- **Recently added**
|
|
||||||
- **Group policy**: `Computer configuration\Administrative Template\Start Menu and Taskbar\Remove "Recently Added" list from Start Menu`
|
|
||||||
|
|
||||||
This policy applies to:
|
|
||||||
|
|
||||||
- Windows 10 version 1803 and later
|
|
||||||
|
|
||||||
- **Local setting**: Settings > Personalization > Start > Show recently added apps
|
|
||||||
- **MDM policy**: Start/HideRecentlyAddedApps
|
|
||||||
|
|
||||||
- **Pinned folders**
|
|
||||||
- **Local setting**: Settings > Personalization > Start > Choose which folders appear on Start
|
|
||||||
- **MDM policy**: AllowPinnedFolder
|
|
||||||
|
|
||||||
- **Power**
|
|
||||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands`
|
|
||||||
- **Local setting**: None
|
|
||||||
- **MDM policy**:
|
|
||||||
- Start/HidePowerButton
|
|
||||||
- Start/HideHibernate
|
|
||||||
- Start/HideRestart
|
|
||||||
- Start/HideShutDown
|
|
||||||
- Start/HideSleep
|
|
||||||
|
|
||||||
- **Start layout**
|
|
||||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Prevent users from customizing their Start screen`
|
|
||||||
|
|
||||||
When a full Start screen layout is imported with Group Policy or MDM, users can't pin, unpin, or uninstall apps from the Start screen. Users can see and open all apps in the **All Apps** view, but they can't pin any apps to the Start screen. When a partial Start screen layout is imported, users can't change the tile groups applied by the partial layout. They can change other tile groups, and create their own tile groups.
|
|
||||||
|
|
||||||
**Start layout** policy can be used to pin apps to the taskbar based on an XML File you provide. Users can change the order of pinned apps, unpin apps, and pin more apps to the taskbar.
|
|
||||||
|
|
||||||
- **Local setting**: None
|
|
||||||
- **MDM policy**:
|
|
||||||
- Start layout
|
|
||||||
- ImportEdgeAssets
|
|
||||||
|
|
||||||
- **Jump lists**
|
|
||||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Do not keep history of recently opened documents`
|
|
||||||
- **Local setting**: Settings > Personalization > Start > Show recently opened items in Jump Lists on Start or the taskbar
|
|
||||||
- **MDM policy**: Start/HideRecentJumplists
|
|
||||||
|
|
||||||
- **Start size**
|
|
||||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Force Start to be either full screen size or menu size`
|
|
||||||
- **Local setting**: Settings > Personalization > Start > Use Start full screen
|
|
||||||
- **MDM policy**: Force Start size
|
|
||||||
|
|
||||||
- **App list**
|
|
||||||
- **Local setting**: Settings > Personalization > Start > Show app list in Start menu
|
|
||||||
- **MDM policy**: Start/HideAppList
|
|
||||||
|
|
||||||
- **All settings**
|
|
||||||
- **Group policy**: `User Configuration\Administrative Templates\Prevent changes to Taskbar and Start Menu Settings`
|
|
||||||
- **Local setting**: None
|
|
||||||
|
|
||||||
- **Taskbar**
|
|
||||||
- **Local setting**: None
|
|
||||||
- **MDM policy**: Start/NoPinningToTaskbar
|
|
||||||
|
|
||||||
> [!NOTE]
|
|
||||||
> In the **Settings** app > **Personalization** > **Start**, there is a **Show more tiles on Start** option. The default tile layout for Start tiles is 3 columns of medium sized tiles. **Show more tiles on Start** enables 4 columns. To configure the 4-column layout when you [customize and export a Start layout](customize-and-export-start-layout.md), turn on the **Show more tiles** setting, and then arrange your tiles.
|
|
||||||
|
|
||||||
## Taskbar options
|
|
||||||
|
|
||||||
Starting in Windows 10 version 1607, you can pin more apps to the taskbar, and remove default pinned apps from the taskbar. You can select different taskbar configurations based on device locale or region.
|
|
||||||
|
|
||||||
There are three app categories that could be pinned to a taskbar:
|
|
||||||
|
|
||||||
- Apps pinned by the user
|
|
||||||
- Default Windows apps pinned during the OS installation, such as Microsoft Edge, File Explorer, and Store
|
|
||||||
- Apps pinned by your organization, such as in an unattended Windows setup
|
|
||||||
|
|
||||||
In an unattended Windows setup file, it's recommended to use the [layoutmodification.xml method](../taskbar/configure.md) to configure the taskbar options. It's not recommended to use [TaskbarLinks](/windows-hardware/customize/desktop/unattend/microsoft-windows-shell-setup-taskbarlinks).
|
|
||||||
|
|
||||||
The following example shows how apps are pinned. In OS configured to use a right-to-left language, the taskbar order is reversed:
|
|
||||||
|
|
||||||
- Windows default apps to the left (blue circle)
|
|
||||||
- Apps pinned by the user in the center (orange triangle)
|
|
||||||
- Apps that you pin using XML to the right (green square)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
If you apply the taskbar configuration to a clean install or an update, users can still:
|
|
||||||
|
|
||||||
- Pin more apps
|
|
||||||
- Change the order of pinned apps
|
|
||||||
- Unpin any app
|
|
||||||
|
|
||||||
> [!TIP]
|
|
||||||
> In Windows 10 version 1703, you can apply the `Start/NoPinningToTaskbar` MDM policy. This policy 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 following apps are pinned to the taskbar:
|
|
||||||
|
|
||||||
- Apps you specifically add
|
|
||||||
- Any default apps you don't remove
|
|
||||||
|
|
||||||
After the layout is applied, users can pin more apps to the taskbar.
|
|
||||||
|
|
||||||
## Start layout configuration errors
|
|
||||||
|
|
||||||
If your Start layout customization isn't applied as you expect, open the **Event Viewer**. Go to **Applications and Services Log** > **Microsoft** > **Windows** > **ShellCommon-StartLayoutPopulation** > **Operational**. Look for the following events:
|
|
||||||
|
|
||||||
- **Event 22**: The XML is malformed. The specified file isn't valid XML. This event can happen if the file has extra spaces or unexpected characters. Or, if the file isn't saved in the UTF8 format.
|
|
||||||
- **Event 64**: The XML is valid, and has unexpected values. This event can happen when the configuration isn't understood, elements aren't in [the required order](start-layout-xml-desktop.md#required-order), or source isn't found, such as a missing or misspelled `.lnk`.
|
|
||||||
@ -538,3 +538,50 @@ If the OS is configured to use a right-to-left language, then the taskbar order
|
|||||||
After the layout is applied, users can pin more apps, change the order, and unpin apps.
|
After the layout is applied, users can pin more apps, change the order, and unpin apps.
|
||||||
|
|
||||||
::: zone-end
|
::: zone-end
|
||||||
|
|
||||||
|
<!-- form Start article to move
|
||||||
|
|
||||||
|
Configuring the taskbar allows you to pin useful apps for your users, and remove apps that are pinned by default.
|
||||||
|
|
||||||
|
> **Looking for consumer information?** [See what's on the Start menu](https://support.microsoft.com/help/17195/windows-10-see-whats-on-the-menu)
|
||||||
|
>
|
||||||
|
> **Looking for OEM information?** See [Customize the Taskbar](/windows-hardware/customize/desktop/customize-the-windows-11-taskbar) and [Customize the Start layout](/windows-hardware/customize/desktop/customize-the-windows-11-start-menu).
|
||||||
|
|
||||||
|
For the **taskbar**, you can use the same XML file as the start screen. Or, you can create a new XML file. When you have the XML file, add this file to a group policy or a provisioning package. Using these methods, you can deploy the XML file to your devices. When the devices receive your policy, they'll use the taskbar settings you configured in the XML file.
|
||||||
|
|
||||||
|
## Taskbar options
|
||||||
|
|
||||||
|
There are three app categories that could be pinned to a taskbar:
|
||||||
|
|
||||||
|
- Apps pinned by the user
|
||||||
|
- Default Windows apps pinned during the OS installation, such as Microsoft Edge, File Explorer, and Store
|
||||||
|
- Apps pinned by your organization, such as in an unattended Windows setup
|
||||||
|
|
||||||
|
In an unattended Windows setup file, it's recommended to use the [layoutmodification.xml method](../taskbar/configure.md) to configure the taskbar options. It's not recommended to use [TaskbarLinks](/windows-hardware/customize/desktop/unattend/microsoft-windows-shell-setup-taskbarlinks).
|
||||||
|
|
||||||
|
The following example shows how apps are pinned. In OS configured to use a right-to-left language, the taskbar order is reversed:
|
||||||
|
|
||||||
|
- Windows default apps to the left (blue circle)
|
||||||
|
- Apps pinned by the user in the center (orange triangle)
|
||||||
|
- Apps that you pin using XML to the right (green square)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
If you apply the taskbar configuration to a clean install or an update, users can still:
|
||||||
|
|
||||||
|
- Pin more apps
|
||||||
|
- Change the order of pinned apps
|
||||||
|
- Unpin any app
|
||||||
|
|
||||||
|
> [!TIP]
|
||||||
|
> In Windows 10 version 1703, you can apply the `Start/NoPinningToTaskbar` MDM policy. This policy 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 following apps are pinned to the taskbar:
|
||||||
|
|
||||||
|
- Apps you specifically add
|
||||||
|
- Any default apps you don't remove
|
||||||
|
|
||||||
|
After the layout is applied, users can pin more apps to the taskbar.
|
||||||
|
-->
|
||||||
Loading…
x
Reference in New Issue
Block a user