MicrosoftDocs · Roy (RDMacLachlan) · Jul 2, 2026
diff --git a/msix-src/app-installer/troubleshoot-appinstaller-issues.md b/msix-src/app-installer/troubleshoot-appinstaller-issues.md
@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot installation issues with the App Installer file
 description: Common issues when sideloading applications with the App Installer file.
-ms.date: 4/28/2021
+ms.date: 07/02/2026
 ms.topic: troubleshooting-general
 keywords: windows 10, uwp, app installer, AppInstaller, sideload
 ms.custom:
@@ -77,10 +77,10 @@ Windows 10 applications can have framework dependencies based on the application
 When installing from an HTTP endpoint, it is important to verify that all required files are accessible. The easiest method to verify this is by following the links provided in the HTML page generated by Visual Studio. You must check these files:
 
 - an `.appinstaller` file, found at `Additional Links > App Installer File` on the Visual Studio generated page
-- an `.appx`, `.appxbundle`, `.misx` or `msixbundle` file, found at `Additional Links > Package Bundle` on the Visual Studio generated page
+- an `.msix`, `.msixbundle`, `.appx`, or `.appxbundle` file, found at `Additional Links > Package Bundle` on the Visual Studio generated page
 
 > [!NOTE]
-> Depending on your configuration, there might be more than one `.appx`, `.appxbundle`, `.misx` or `msixbundle` file involved in your deployment. Ensure that all of them are accessible.
+> Depending on your configuration, there might be more than one `.msix`, `.msixbundle`, `.appx`, or `.appxbundle` file involved in your deployment. Ensure that all of them are accessible.
 
 ### Files served with wrong MIME type
 

diff --git a/msix-src/desktop/azure-dev-ops.md b/msix-src/desktop/azure-dev-ops.md
@@ -1,7 +1,7 @@
 ---
 description: You can configure a pipeline with a YAML file to create automated builds for your MSIX project.
 title: Configure CI/CD pipeline with YAML file
-ms.date: 01/11/2021
+ms.date: 07/02/2026
 ms.topic: how-to
 keywords: windows 10, uwp
 ms.custom: RS5
@@ -211,7 +211,7 @@ A Release Pipeline Task That Modifies the Uris in the .appinstaller File
   $xName =
     [System.Xml.Linq.XName]"{http://schemas.microsoft.com/appx/appinstaller/2018}MainPackage"
   $doc.Root.Element($xName).Attribute("Uri").Value = [string]::Format('{0}{1}',
-    $fileShare, 'MsixDesktopApp.appx')
+    $fileShare, 'MsixDesktopApp.msix')
   $doc.Save("$localFilePath")
 displayName: 'Modify URIs in App Installer File'
 ```

diff --git a/msix-src/desktop/desktop-to-uwp-known-issues.md b/msix-src/desktop/desktop-to-uwp-known-issues.md
@@ -1,7 +1,7 @@
 ---
 description: This article describes known issues that can occur when you create an MSIX package for your desktop app.
 title: Known Issues with packaged desktop apps
-ms.date: 07/29/2019
+ms.date: 07/02/2026
 ms.topic: troubleshooting-known-issue
 keywords: windows 10, uwp, msix
 ms.assetid: 71f8ffcb-8a99-4214-ae83-2d4b718a750e
@@ -86,7 +86,7 @@ set APPXSIP_LOG=1
 Then, from the **Command Prompt**, sign your application again. For example:
 
 ```
-signtool.exe sign /a /v /fd SHA256 /f APPX_TEST_0.pfx C:\Users\Contoso\Desktop\pe\VLC.appx
+signtool.exe sign /a /v /fd SHA256 /f APPX_TEST_0.pfx C:\Users\Contoso\Desktop\pe\VLC.msix
 ```
 
 Information about files that contain a bad PE cert will appear in the **Console Window**. For example:

diff --git a/msix-src/package/asset-packages.md b/msix-src/package/asset-packages.md
@@ -1,7 +1,7 @@
 ---
 title: Introduction to asset packages
 description: Asset packages are a type of package that act as a centralized location for an application’s common files.
-ms.date: 07/02/2019
+ms.date: 07/02/2026
 ms.topic: concept-article
 keywords: windows 10, msix, packaging, package layout, asset package
 ---
@@ -44,8 +44,8 @@ The easiest way to create asset packages is using the packaging layout. However,
 Use one of these commands to create the asset package using MakeAppx.exe (for MSIX and .appx).
 
 ```cmd
-MakeAppx.exe pack /r /m AppxManifest.xml /f MappingFile.txt /p Videos.appx
 MakeAppx.exe pack /r /m AppxManifest.xml /f MappingFile.txt /p Videos.msix
+MakeAppx.exe pack /r /m AppxManifest.xml /f MappingFile.txt /p Videos.appx
 ```
 
 It should be noted here that all of the files referenced in the AppxManifest (the logo files) cannot be moved into asset packages – these files must be duplicated across architecture packages.

diff --git a/msix-src/package/package-folding.md b/msix-src/package/package-folding.md
@@ -1,7 +1,7 @@
 ---
 title: Developing with asset packages and package folding
 description: Learn how to efficiently organize your app with asset packages and package folding.
-ms.date: 04/30/2018
+ms.date: 07/02/2026
 ms.topic: concept-article
 keywords: windows 10, packaging, package layout, asset package
 ---
@@ -20,10 +20,10 @@ To understand how package folding doesn’t impact your development process, let
 
 At a high level, when you split some of your app’s files into other packages (that are not architecture packages), you will not be able to access those files directly relative to where your code runs. This is because these packages are all installed into different directories from where your architecture package is installed. For example, if you’re making a game and your game is localized into French and German and you built for both x86 and x64 machines, then you should have these app package files within the app bundle of your game:
 
-- 	MyGame_1.0_x86.appx
-- 	MyGame_1.0_x64.appx
-- 	MyGame_1.0_language-fr.appx
-- 	MyGame_1.0_language-de.appx
+- 	MyGame_1.0_x86.msix
+- 	MyGame_1.0_x64.msix
+- 	MyGame_1.0_language-fr.msix
+- 	MyGame_1.0_language-de.msix
 
 When your game is installed to a user’s machine, each app package file will have its own folder in the **WindowsApps** directory. So for a French user running 64-bit Windows, your game will look like this:
 
@@ -68,19 +68,19 @@ MyGame
 If you want to split your game into 3 packages: an x64 architecture package, an asset package for audios, and an asset package for videos, your game will be divided into these packages:
 
 ```example
-MyGame_1.0_x64.appx
+MyGame_1.0_x64.msix
 |-- Engine
 |   `-- ...
 |-- XboxLive
 |   `-- ...
 `-- Game.exe
-MyGame_1.0_Audios.appx
+MyGame_1.0_Audios.msix
 `-- Audios
     |-- Level1
     |   `-- ...
     `-- Level2
         `-- ...
-MyGame_1.0_Videos.appx
+MyGame_1.0_Videos.msix
 `-- Videos
     |-- Level1
     |   `-- ...
@@ -128,21 +128,21 @@ When using package folding for asset packages, you can still access the files yo
 Now for a more complicated package folding example. Let’s say that you want to split your files based on level instead, and if you want to keep the same structure as the original project folder, your packages should look like this:
 
 ```example
-MyGame_1.0_x64.appx
+MyGame_1.0_x64.msix
 |-- Engine
 |   `-- ...
 |-- XboxLive
 |   `-- ...
 `-- Game.exe
-MyGame_Level1.appx
+MyGame_Level1.msix
 |-- Audios
 |   `-- Level1
 |       `-- ...
 `-- Videos
     `-- Level1
         `-- ...
 
-MyGame_Level2.appx
+MyGame_Level2.msix
 |-- Audios
 |   `-- Level2
 |       `-- ...

diff --git a/msix-src/package/packaging-layout.md b/msix-src/package/packaging-layout.md
@@ -1,7 +1,7 @@
 ---
 title: Package creation with the packaging layout
 description: The packaging layout is a single document that describes packaging structure of the app, such as the bundles of an app (primary and optional).
-ms.date: 04/30/2018
+ms.date: 07/02/2026
 ms.topic: how-to
 keywords: windows 10, packaging, package layout, asset package
 ---
@@ -126,7 +126,7 @@ Here's an example of a more complicated packaging layout:
   </PackageFamily>
 
   <!-- Existing packages that need to be included/referenced in the bundle -->
-  <PrebuiltPackage Path="C:\prebuilt\DLC2.appxbundle" />
+  <PrebuiltPackage Path="C:\prebuilt\DLC2.msixbundle" />
 
 </PackagingLayout>
 ```

diff --git a/msix-src/package/sign-app-package-using-signtool.md b/msix-src/package/sign-app-package-using-signtool.md
@@ -1,7 +1,7 @@
 ---
 title: Sign an app package using SignTool
 description: This article describes how to use SignTool to manually sign an app package or bundle with a certificate.
-ms.date: 09/30/2018
+ms.date: 07/02/2026
 ms.topic: how-to
 keywords: windows 10, uwp
 ms.assetid: 171f332d-2a54-4c68-8aa0-52975d975fb1
@@ -74,10 +74,6 @@ The certificate used to sign your app must be either a .pfx file or be installed
 
 To sign your app package with a certificate from a .pfx file, use the following syntax:
 
-```syntax
-SignTool sign /fd <Hash Algorithm> /a /f <Path to Certificate>.pfx /p <Your Password> <File path>.appx
-```
-
 ```syntax
 SignTool sign /fd <Hash Algorithm> /a /f <Path to Certificate>.pfx /p <Your Password> <File path>.msix
 ```
@@ -86,20 +82,12 @@ Note that the `/a` option allows **SignTool** to choose the best certificate aut
 
 If your certificate is not a .pfx file, use the following syntax:
 
-```syntax
-SignTool sign /fd <Hash Algorithm> /n <Name of Certificate> <File Path>.appx
-```
-
 ```syntax
 SignTool sign /fd <Hash Algorithm> /n <Name of Certificate> <File Path>.msix
 ```
 
 Alternatively, you can specify the SHA1 hash of the desired certificate instead of &lt;Name of Certificate&gt; using this syntax:
 
-```syntax
-SignTool sign /fd <Hash Algorithm> /sha1 <SHA1 hash> <File Path>.appx
-```
-
 ```syntax
 SignTool sign /fd <Hash Algorithm> /sha1 <SHA1 hash> <File Path>.msix
 ```

diff --git a/msix-src/package/unsigned-package.md b/msix-src/package/unsigned-package.md
@@ -1,7 +1,7 @@
 ---
 title: Create an unsigned MSIX package
 description: This topic describes how to create and install an unsigned MSIX package
-ms.date: 05/26/2023
+ms.date: 07/02/2026
 ms.topic: how-to
 keywords: windows 11, uwp, desktop, msix
 ---
@@ -36,7 +36,7 @@ Here's an example.
 Here's an example of the syntax.
 
 ```powershell
-Add-AppxPackage -Path ".\MyEmployees.appx" -AllowUnsigned
+Add-AppxPackage -Path ".\MyEmployees.msix" -AllowUnsigned
 ```
 
 When your app is ready to be distributed, you should ensure that the package is signed. Be sure to remove the special OID, and ensure that the publisher name is the same as the certificate subject name.