LayoutModification.xml
requires the following order for tags directly under the LayoutModificationTemplate node:LayoutModification.xml
file.Element | Attributes | Description |
---|---|---|
LayoutModificationTemplate | xmlns xmlns:defaultlayout xmlns:start Version | Use to describe the changes to the default Start layout |
LayoutOptions Parent: LayoutModificationTemplate | StartTileGroupsColumnCount FullScreenStart | Use to specify: - Whether to use full screen Start on the desktop - The number of tile columns in the Start menu |
RequiredStartGroupsCollection Parent: LayoutModificationTemplate | n/a | Use to contain collection of RequiredStartGroups |
RequiredStartGroups Parent: RequiredStartGroupsCollection | Region | Use to contain the AppendGroup tags, which represent groups that can be appended to the default Start layout |
AppendGroup Parent: RequiredStartGroups | Name | Use to specify the tiles that need to be appended to the default Start layout |
start:Tile Parent: AppendGroup | AppUserModelID Size Row Column | Use to specify any of the following: - A Universal Windows app - A Windows 8 or Windows 8.1 app Note that AppUserModelID is case-sensitive. |
start:Folder Parent: start:Group | Name (in Windows 10, version 1809 and later only) Size Row Column LocalizedNameResourcetag | Use to specify a folder of icons; can include Tile, SecondaryTile, and DesktopApplicationTile. |
start:DesktopApplicationTile Parent: AppendGroup | DesktopApplicationID DesktopApplicationLinkPath Size Row Column | Use to specify any of the following: - A Windows desktop application with a known AppUserModelID - An application in a known folder with a link in a legacy Start Menu folder - A Windows desktop application link in a legacy Start Menu folder - A Web link tile with an associated .url file that is in a legacy Start Menu folder |
start:SecondaryTile Parent: AppendGroup | AppUserModelID TileID Arguments DisplayName Square150x150LogoUri ShowNameOnSquare150x150Logo ShowNameOnWide310x150Logo Wide310x150LogoUri BackgroundColor ForegroundText IsSuggestedApp Size Row Column | Use to pin a Web link through a Microsoft Edge secondary tile. Note that AppUserModelID is case-sensitive. |
TopMFUApps Parent: LayoutModificationTemplate | n/a | Use to add up to 3 default apps to the frequently used apps section in the system area. Note: Only applies to versions of Windows 10 earlier than version 1709. In Windows 10, version 1709, you can no longer pin apps to the Most Frequently Used apps list in Start. |
Tile Parent: TopMFUApps | AppUserModelID | Use with the TopMFUApps tags to specify an app with a known AppUserModelID. Note: Only applies to versions of Windows 10 earlier than version 1709. In Windows 10, version 1709, you can no longer pin apps to the Most Frequently Used apps list in Start. |
DesktopApplicationTile Parent: TopMFUApps | LinkFilePath | Use with the TopMFUApps tags to specify an app without a known AppUserModelID. Note: Only applies to versions of Windows 10 earlier than version 1709. In Windows 10, version 1709, you can no longer pin apps to the Most Frequently Used apps list in Start. |
AppendOfficeSuite Parent: LayoutModificationTemplate | n/a | Use to add the in-box installed Office suite to Start. For more information, see Customize the Office suite of tiles. Do not use this tag with AppendDownloadOfficeTile |
AppendDownloadOfficeTile Parent: LayoutModificationTemplate | n/a | Use to add a specific Download Office tile to a specific location in Start Do not use this tag with AppendOfficeSuite |
Attribute | Description |
---|---|
Size | Determines how large the tile will be. - 1x1 - small tile - 2x2 - medium tile - 4x2 - wide tile - 4x4 - large tile |
Row | Specifies the row where the tile will appear. |
Column | Specifies the column where the tile will appear. |
%APPDATA%MicrosoftWindowsStart MenuPrograms
or the all users profile %ALLUSERSPROFILE%MicrosoftWindowsStart MenuPrograms
.Attribute | Required/optional | Description |
---|---|---|
AppUserModelID | Required | Must point to Microsoft Edge. Note that AppUserModelID is case-sensitive. |
TileID | Required | Must uniquely identify your Web site tile. |
Arguments | Required | Must contain the URL of your Web site. |
DisplayName | Required | Must specify the text that you want users to see. |
Square150x150LogoUri | Required | Specifies the logo to use on the 2x2 tile. |
Wide310x150LogoUri | Optional | Specifies the logo to use on the 4x2 tile. |
ShowNameOnSquare150x150Logo | Optional | Specifies whether the display name is shown on the 2x2 tile. The values you can use for this attribute are true or false. |
ShowNameOnWide310x150Logo | Optional | Specifies whether the display name is shown on the 4x2 tile. The values you can use for this attribute are true or false. |
BackgroundColor | Optional | Specifies the color of the tile. You can specify the value in ARGB hexadecimal (for example, #FF112233) or specify 'transparent'. |
ForegroundText | Optional | Specifies the color of the foreground text. Set the value to either 'light' or 'dark'. |
%ALLUSERSPROFILE%MicrosoftWindowsStart MenuPrograms
directory. Use a DesktopApplicationTile tag with the LinkFilePath attribute set to the .lnk file name and path.<AppendOfficeSuiteChoice Choice='DesktopBridgeSubscription'/>
<AppendOfficeSuiteChoice Choice='DesktopBridge'/>
Choice=DesktopBridgeSubscription
on devices running Windows 10, version 1803, that have Office 365 preinstalled. This will set the heading of the Office suite of tiles to Office 365, to highlight the Office 365 apps that you've made available on the device.Choice=DesktopBridge
on devices running versions of Windows 10 earlier than version 1803, and on devices shipping with perpetual licenses for Office. This will set the heading of the Office suite of tiles to Create.XML Parser Error Code | Description |
1 | The parser detected an invalid character when scanning white space outside element content. |
2 | The parser detected an invalid start of a processing instruction, element, comment, or document type declaration outside element content. |
3 | The parser detected a duplicate attribute name. |
4 | The parser detected the markup character ‘<‘ in an attribute value. |
5 | The start and end tag names of an element were different. |
6 | The parser detected an invalid character in element content. |
7 | The parser detected an invalid start of an element, comment, processing instruction, or CDATA(character Data) section in element content. |
8 | The parser detected in element content the CDATA closing character sequence ‘]]>’ without the matching opening character sequence ‘<![CDATA[‘. |
9 | The parser detected an invalid character in a comment. |
10 | The parser detected in a comment the character sequence ‘–‘ (two hyphens) not followed by ‘>’. |
11 | The parser detected an invalid character in a processing instruction data segment. |
12 | A processing instruction target name was ‘xml’ in any of the cases- lower, upper or toggle. |
13 | The parser detected an invalid digit in a hexadecimal character reference (of the form �, for example ັ). |
14 | The parser detected an invalid digit in a decimal character reference (of the form &#dddd;). |
15 | A character reference did not refer to an authorized XML character. |
16 | The parser detected an invalid character in an entity reference name. |
17 | The parser detected an invalid character in an attribute value. |
18 | The parser detected a possible invalid start of a document type declaration. |
19 | The parser detected a second document type declaration. |
20 | An element name was not specified correctly. The beginning character was not a letter, ‘_’, or ‘:’, or the parser detected an invalid character either in or following the element name. |
21 | An attribute was not specified correctly. The beginning character of the attribute name was not a letter, ‘_’, or ‘:’, or a character other than ‘=’ was detected following the attribute name, or one of the delimiters of the value was not correct, or an invalid character was detected in or following the name. |
22 | An empty element tag was not terminated by a markup language character ‘>’ following the ‘/’. |
23 | The element end tag wasn’t specified correctly. The beginning character was not a letter, ‘_’, or ‘:’, or the tag wasn’t terminated by ‘>’. |
24 | The parser detected an invalid start of a comment or CDATA section in element content. |
25 | A processing instruction target name wasn’t specified correctly. The starting character of the processing instruction target name wasn’t a letter, ‘_’, or ‘:’, or the parser detected an invalid character in or following the processing instruction target name. |
26 | A processing instruction wasn’t terminated by the closing character sequence ‘?>’. |
27 | The parser detected an invalid character following ‘&’ in a character reference or entity reference. |
28 | The version information wasn’t present in the XML declaration. |
29 | The ‘version’ in the XML declaration wasn‘t specified correctly. ‘version’ was not followed by ‘=’, or the value was not present or improperly delimited, or the value specified a bad character, or the start and end delimiters didn’t match, or the parser detected an invalid character following the version information value closing delimiter in the XML declaration. |
30 | The parser detected an invalid attribute instead of the optional encoding declaration in the XML declaration. |
31 | The encoding declaration value in the XML declaration was missing or incorrect. The value did not start with lowercase or uppercase A through Z, or ‘encoding’ wasn’t followed by ‘=’, or the value was missing or improperly delimited or it specified a bad character, or the start and end delimiters didn’t match, or the parser detected an invalid character following the closing delimiter. |
32 | The parser detected an invalid attribute instead of the optional standalone declaration in the XML declaration. |
33 | The ‘standalone’ attribute in the XML declaration wasn’t specified correctly. ‘standalone’ wasn’t followed by a ‘=’, or the value was either missing or improperly delimited, or the value was neither ‘yes’ nor ‘no’, or the value specified a bad character, or the start and end delimiters did n’t match, or the parser detected an invalid character following the closing delimiter. |
34 | The XML declaration wasn’t terminated by the proper character sequence ‘?>’, or contained an invalid attribute. |
35 | The parser detected the start of a document type declaration after the end of the root element. |
36 | The parser detected the start of an element after the end of the root element. |
300 | The parser reached the end of the concerned document before the document was complete. |
301 | The %HANDLER procedure for XML-INTO or XML-SAX returned a non-zero value, causing the XML parsing to end. |
302 | The parser doesn’t support the requested CCSID value or the first character of the XML document was not ‘<‘. |
303 | The concerned document was too large for the parser to handle. The parser tried to parse the incomplete document, but the data at the end of the document was necessary for the parsing to complete. |
500-999 | Internal error in the external parser. Report the error to your service representative. |
10001-19999 | Internal error in the parser. Report the error to your service representative. |