Deploying Database Tools with MSIX/App Attach

Question

Deploying Database Tools with MSIX/App Attach

Alex Dresser 5

I am trying to deploy SQL Server Management Studio and pgAdmin to AVD via MSIX App Attach but it is not working as expected.

I have tried with SQL Server Management Studio 19 and 21. SSMS 19 just gives me an error that the "Principle is not valid" and SSMS 21 at least tries to work but then boots up a Folder Explorer window.

PgAdmin tries to connect but ultimately I get an error saying "Unable to Connect to PgAdmin Server"

I have packaged these applications the same way as all of our other applications which work fine. (with the exception of PowerBI which also gives me a "Principle is not valid" error)

I am using the same certificate to sign all of these too.

Is there something specific when deploying this kind of software that I might be missing?

If someone here has successfully deployed any of these in the past it would be very helpful to hear how.

Satish Mada 425 Reputation points Microsoft External Staff Moderator

2025-07-30T10:26:59.7366667+00:00
Hi Alex Dresser.

Welcome to the Azure Q&A portal.

As you are encountering a "Principal is not valid" error with SSMS 19, and with SSMS 21, instead of launching correctly, a folder explorer opens. These issues could be related to how the application is packaged or potentially the permissions of the account running the application. Regarding pgAdmin, the "Unable to Connect to pgAdmin Server" error suggests there might be configuration problems with pgAdmin itself or connectivity issues with the database server it is trying to access.

For SSMS:

Check what’s inside the package: Make sure all the files SSMS needs are included in the MSIX package. Also, make sure the certificate used to sign the package is trusted by the AVD machine.

Try installing it normally: Install SSMS directly on a virtual machine (without using MSIX) to see if it works. This helps you figure out if the problem is with the app or the packaging.

Check user permissions: Make sure the user on the AVD machine has permission to run SSMS. Also, check if any settings SSMS needs are set up properly.

For pgAdmin:

Check the settings: Make sure pgAdmin is set up correctly to connect to the database. Double-check the server name, port number, and login details.

Check the firewall: Make sure the AVD machine can connect to the PostgreSQL server. The firewall should allow traffic on the correct port (usually 5432).

Please refer App Attach in Azure Virtual Desktop | Microsoft Learn
MSIX Packaging Tool Overview - MSIX | Microsoft Learn
Alex Dresser 5 Reputation points

2025-08-11T13:20:55.4933333+00:00
Hey Satish, thank you for your response.

Regarding what you mentioned-

For SSMS:

Check what’s inside the package: Make sure all the files SSMS needs are included in the MSIX package. Also, make sure the certificate used to sign the package is trusted by the AVD machine. - I have already done this and all other MSIX packages work.

Try installing it normally: Install SSMS directly on a virtual machine (without using MSIX) to see if it works. This helps you figure out if the problem is with the app or the packaging. - I believe it is with the packaging as we have other environments that have it working when it is installed locally. My question was geared to find out why it does not work via AppAttach

Check user permissions: Make sure the user on the AVD machine has permission to run SSMS. Also, check if any settings SSMS needs are set up properly. - They do have permissions to run everything.

For pgAdmin:

Check the settings: Make sure pgAdmin is set up correctly to connect to the database. Double-check the server name, port number, and login details. - I have not set any of those up as I do not get to that part.

Check the firewall: - the firewall is via our Azure tenant.
Satish Mada 425 Reputation points Microsoft External Staff Moderator

2025-08-14T10:53:06.63+00:00
Hi Alex Dresser,

Thank you for your response

This points to MSIX virtualization limitations that affect how these applications interact with the system when containerized.

SSMS Specific Solutions

Issue 1: SSMS 19 "Principal is not valid" Error

Root Cause: Missing system dependencies and incorrect registry virtualization permissions

Detailed Solution:

Step 1: Add missing system dependency during packaging

bash# During MSIX packaging, manually add this fileSource: C:\Windows\SysWOW64\mscoree.dllDestination: Package\VFS\SystemX86\mscoree.dll

Step 2: Fix virtual registry permissions

Extract the MSIX package using MSIX Hero or PowerShell:

Load and fix registry permissions:

Repackage with corrected permissions:

Step 3: Alternative registry handling approach For SSMS startup registry writes, implement StartupTask in Package.appxmanifest instead of registry modifications:

xml<Package.Extensions> <Extension Category="windows.startupTask" Executable="Ssms.exe" EntryPoint="Windows.FullTrustApplication"> <StartupTask TaskId="SSMSStartup" Enabled="true" DisplayName="SQL Server Management Studio" /> </Extension></Package.Extensions>

Issue 2: SSMS 21 Opens Folder Explorer Instead of Application

Root Cause: Incorrect application manifest entry points or file associations

Solution Steps:

Step 1: Verify Package.appxmanifest application entries

xml<Application Id="SSMS" Executable="VFS\ProgramFilesX64\Microsoft SQL Server Management Studio 21\Common7\IDE\Ssms.exe" EntryPoint="Windows.FullTrustApplication"> <uap:VisualElements DisplayName="SQL Server Management Studio" Description="Database management tool" /></Application>

Step 2: Check for conflicting file associations

Remove any file associations that might redirect to explorer.exe

Ensure primary executable isn't accidentally set to a folder path

Step 3: Test package registration manually

powershell# Test package outside AVD firstAdd-AppxPackage -Path "SSMS21.msix" -ForceApplicationShutdown# Verify registrationGet-AppxPackage -Name "*SSMS*" | Select Name, Status, InstallLocation# Test launchStart-Process "shell:AppsFolder\[PackageFamilyName]!SSMS"

Issue 3 pgAdmin Specific Solutions

Issue: "Unable to Connect to PgAdmin Server"

Root Cause: pgAdmin's internal server (localhost:5050) cannot start properly within MSIX virtualization

Detailed Solutions:

Solution 1: Include pgAdmin server configuration in MSIX package

Capture complete pgAdmin environment:

Ensure all Python dependencies are included

Package the entire pgAdmin web server stack

Include configuration files in the virtual file system

Configure pgAdmin for MSIX isolation:

Solution 2: Alternative packaging approach for pgAdmin

Use Application Virtualization instead of full MSIX containerization:

Consider using flexible virtualization for pgAdmin

Allow specific registry/file system writes needed by the internal server

Modify Package.appxmanifest for enhanced permissions:

Solution 3: Pre-configure pgAdmin server settings

Include pre-configured server connections in the package:

Package with default server definitions

Avoid requiring user to create initial server connections

Bundle PostgreSQL client libraries:

Include libpq.dll and related dependencies

Ensure SSL support libraries are present

General MSIX App Attach Compatibility Solutions

Enhanced Packaging Approach for Database Tools

Step 1: Use Advanced Installer or MSIX Hero instead of standard MSIX Packaging Tool

These tools provide better control over virtualization settings

Allow more granular permission configuration

Step 2: Implement Flexible Virtualization

xml<virtualization:FileSystemWriteVirtualization> <virtualization:ExcludedDirectories> <virtualization:ExcludedDirectory>$(KnownFolder:LocalAppData)\Microsoft\SQL Server Management Studio</virtualization:ExcludedDirectory> </virtualization:ExcludedDirectories></virtualization:FileSystemWriteVirtualization><virtualization:RegistryWriteVirtualization> <virtualization:ExcludedKeys> <virtualization:ExcludedKey>HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio</virtualization:ExcludedKey> </virtualization:ExcludedKeys></virtualization:RegistryWriteVirtualization>

Step 3: Test packages comprehensively outside AVD

powershell# Complete testing sequence$PackagePath = "C:\Path\To\Package.msix"# StageAdd-AppxPackage -Path $PackagePath -Stage# Register for userAdd-AppxPackage -Path $PackagePath -Register -ForceApplicationShutdown# Test launchStart-Process "shell:AppsFolder\[PackageFamilyName]![AppId]"# Monitor for errorsGet-WinEvent -LogName "Microsoft-Windows-AppXDeployment/Operational" -MaxEvents 20

please refer to below documentation for more details

Core MSIX App Attach Documentation:

Understanding how packaged desktop apps run - Registry and file system virtualization behavior

Test MSIX packages for App Attach - Testing methodology outside AVD

App Attach in Azure Virtual Desktop - Complete App Attach setup guide

SSMS-Specific Guidance:

Packaging SQL Server Management Studio to MSIX - Microsoft Tech Community detailed walkthrough

Advanced MSIX Features:

Flexible Virtualization - Registry and file system exclusions

MSIX Common Packaging Tutorials - Best practices and troubleshooting

Please let us know if you need any further assistance.
Alex Dresser 5 Reputation points

2025-08-14T11:50:46.7033333+00:00

Hey Satish,

I have already attempted the first steps you suggested for SSMS - as per this article https://techcommunity.microsoft.com/blog/modernworkappconsult/fixed-azure-virtual-desktop-avd---packaging-the-sql-server-management-studio-ssm/3457856 and they were not helpful. The issue still persists.

I will try the follow up steps you suggested.

Thank you!
Alex Dresser 5 Reputation points

2025-08-14T12:25:17.27+00:00
Hey Satish,

I checked the steps for SSMS 21.

It all looks correct to me and I have attached a screenshot from the manifest.

Step 2: Check for conflicting file associations

Remove any file associations that might redirect to explorer.exe - there is no mention of explorer.exe anywhere in the app manifest.

Ensure primary executable isn't accidentally set to a folder path - It is not as shown in the screenshot

Step 3: Test package registration manually - I ran the command and it returned an error for the certificate although that is expected because I'm using a self-signed certificate which is not trusted on my machine. It is trusted in the AVD
Satish Mada 425 Reputation points Microsoft External Staff Moderator

2025-08-21T16:00:13.7633333+00:00
Hi Alex Dresser,

Thanks for checking those steps and sharing the info. It sounds like your MSIX package looks good, but there are a few more things we should check to get this working.

Certificate and Trust

You mentioned that running the manual registration command showed a certificate error on your local machine because you’re using a self-signed certificate. That’s expected locally, but on the AVD session host, we need to make sure:

Your self-signed certificate is properly installed and trusted in the Trusted Root Certification Authorities on all AVD session hosts.

Sometimes the certificate also needs to be in the Trusted Publishers store to make sure the MSIX app can run without issues.

It would be good to run the same registration command on the actual AVD session host to check if the certificate error still happens there.

SSMS 21 Opening File Explorer Instead of the App

Double-check that the MSIX package manifest points to the right program to start—usually, that should be the actual SSMS program (Ssms.exe), not a folder or other file.

Make sure your AVD base image has all the extra software SSMS 21 needs, like Visual C++ libraries or .NET versions.

Try turning on detailed logging for MSIX on the AVD host to see exactly what’s going on when the app tries to start.

Other Things to Try

Try running the SSMS program directly from inside the MSIX package folder on the AVD host to see if it works outside of MSIX.

Check the Windows Event Logs on the AVD host for any error messages when you try to open SSMS through MSIX.

Make sure the users have the right permissions to run the app on the virtual desktop.

If This Still Doesn’t Work

You could test using a certificate from a trusted certificate authority instead of the self-signed one, just to rule out certificate issues.

Or try packaging a simpler version of SSMS with just the essential files to see if something in the full package is causing the problem.

If you can, please share the Event Logs from the AVD session host during the app launch. That can help us find more specific errors and fix the issue.
Satish Mada 425 Reputation points Microsoft External Staff Moderator

2025-08-25T09:28:03.2033333+00:00

Hi Alex Dresser,

Just checking in to see if you had a chance to review the response provided by me.

Feel free to reach out if you have any further queries.
Alex Dresser 5 Reputation points

2025-08-26T07:14:16.4333333+00:00
Hey Satish,

Thank you for your follow up on my comment.

I will do my best to answer the steps you provided -

Certificate and Trust - I use the same certificate for all the other packages and they deploy fine. Additionally, since I am deploying via App Attach it would not let me even package the app into App Attach if one of the session hosts does not recognize the certificate. It is not a certificate issue currently.

SSMS 21 Opening File Explorer Instead of the App - I tried these steps and it did not help unfortunately. The logging does not point to anything specific.

Other Things to Try - I packaged SSMS 20 installer only using MSIX Hero. What this did is that it deploys the installer and once installed you can add SSMS 20 via the Start Menu option in the Application Groups. This is basically like deploying it locally so it's only a test/workaround.

If This Still Doesn’t Work

Or try packaging a simpler version of SSMS with just the essential files to see if something in the full package is causing the problem. - I have tried packaging everything from SSMs 18 - 21 and none of them work. I believe that SSMS is not designed to be packaged as all indicators point to that.
Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-09-15T23:55:54.01+00:00
Hello Alex Dresser,

Can you try below steps to see if it works for you?

Step 1: Prepare the Assets

Download the SSMS installer (e.g., SSMS-Setup-ENU.exe).

Create a simple PowerShell script (install_ssms.ps1) that will execute the installer silently.

Step 2: Create the PowerShell Script The script's job is to execute the installer.

Save this as install_ssms.ps1.

Start-Process -FilePath ".\SSMS-Setup-ENU.exe" -ArgumentList "/install", "/quiet", "/norestart" -Wait -PassThru exit $LASTEXITCODE

Step 3: Create the Package

Open the MSIX Packaging Tool.

Choose "Create a new package".

On the Package information page, fill in your details (Name, Publisher, Version).

On the Prepare computer page, it's best to use a clean VM. Take a snapshot if you can.

On the Installation page, you will not install SSMS. Instead, you will simply copy the files. · Click "Browse" and select your SSMS-Setup-ENU.exe and install_ssms.ps1 files. The tool will copy them into the package.

Proceed through the remaining screens without making changes related to the installation. The tool will finish and create an MSIX package containing just your two files.

Step 4: Edit the Package Manifest to Run the Script because you need to tell the package to run your PowerShell script upon installation.

Unpack the MSIX package using the MSIX Packaging Tool's "Package editor" or a tool like makeappx.exe.

Open the AppxManifest.xml file.

Find the <Applications> section. You will define an application that runs your script.

Modify it to look something like this:

<Applications> <Application Id="InstallSSMS" Executable="powershell.exe" EntryPoint="Windows.FullTrustApplication"> <uap:VisualElements DisplayName="Install SQL Server Management Studio" Description="Runs the SSMS installer locally" BackgroundColor="transparent" /> <uap:Extension Category="windows.customInstall"> <uap:CustomInstall Folder="Contents"> <uap:OnInstall Command="powershell.exe -ExecutionPolicy Bypass -File `"install_ssms.ps1`""/> </uap:CustomInstall> </uap:Extension> </Application> </Applications>

Repack the MSIX file.

Step 5: Deploy via App Attach

Stage this new MSIX package in your Azure Storage Account.

Register it to your host pool as you normally would with App Attach.

When a user logs in, the package will be attached.
Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-09-16T19:39:46.2166667+00:00

Hello Alex Dresser,

Just checking in if you got a chance to try out the suggestions shared by me earlier.
Let me know if you have any blockers or any questions regarding it.
Alex Dresser 5 Reputation points

2025-09-17T06:30:42.52+00:00

Hey Ankit,

Thank you for the suggestion. I have not tried it yet but it looks interesting and I will go ahead with testing it at some point.

I will let you know if it helps.

Thank you!

1 answer

Your answer

Satish Mada 425 Reputation points Microsoft External Staff Moderator

2025-07-30T10:26:59.7366667+00:00

Hi Alex Dresser.

Welcome to the Azure Q&A portal.

As you are encountering a "Principal is not valid" error with SSMS 19, and with SSMS 21, instead of launching correctly, a folder explorer opens. These issues could be related to how the application is packaged or potentially the permissions of the account running the application. Regarding pgAdmin, the "Unable to Connect to pgAdmin Server" error suggests there might be configuration problems with pgAdmin itself or connectivity issues with the database server it is trying to access.

For SSMS:

Check what’s inside the package: Make sure all the files SSMS needs are included in the MSIX package. Also, make sure the certificate used to sign the package is trusted by the AVD machine.

Try installing it normally: Install SSMS directly on a virtual machine (without using MSIX) to see if it works. This helps you figure out if the problem is with the app or the packaging.

Check user permissions: Make sure the user on the AVD machine has permission to run SSMS. Also, check if any settings SSMS needs are set up properly.

For pgAdmin:

Check the settings: Make sure pgAdmin is set up correctly to connect to the database. Double-check the server name, port number, and login details.

Check the firewall: Make sure the AVD machine can connect to the PostgreSQL server. The firewall should allow traffic on the correct port (usually 5432).

Please refer App Attach in Azure Virtual Desktop | Microsoft Learn
MSIX Packaging Tool Overview - MSIX | Microsoft Learn
Alex Dresser 5 Reputation points

2025-08-11T13:20:55.4933333+00:00

Hey Satish, thank you for your response.

Regarding what you mentioned-

For SSMS:

Check what’s inside the package: Make sure all the files SSMS needs are included in the MSIX package. Also, make sure the certificate used to sign the package is trusted by the AVD machine. - I have already done this and all other MSIX packages work.

Try installing it normally: Install SSMS directly on a virtual machine (without using MSIX) to see if it works. This helps you figure out if the problem is with the app or the packaging. - I believe it is with the packaging as we have other environments that have it working when it is installed locally. My question was geared to find out why it does not work via AppAttach

Check user permissions: Make sure the user on the AVD machine has permission to run SSMS. Also, check if any settings SSMS needs are set up properly. - They do have permissions to run everything.

For pgAdmin:

Check the settings: Make sure pgAdmin is set up correctly to connect to the database. Double-check the server name, port number, and login details. - I have not set any of those up as I do not get to that part.

Check the firewall: - the firewall is via our Azure tenant.
Alex Dresser 5 Reputation points

2025-08-14T11:50:46.7033333+00:00

Hey Satish,

I have already attempted the first steps you suggested for SSMS - as per this article https://techcommunity.microsoft.com/blog/modernworkappconsult/fixed-azure-virtual-desktop-avd---packaging-the-sql-server-management-studio-ssm/3457856 and they were not helpful. The issue still persists.

I will try the follow up steps you suggested.

Thank you!
Alex Dresser 5 Reputation points

2025-08-14T12:25:17.27+00:00

Hey Satish,

I checked the steps for SSMS 21.

It all looks correct to me and I have attached a screenshot from the manifest.

Step 2: Check for conflicting file associations

Remove any file associations that might redirect to explorer.exe - there is no mention of explorer.exe anywhere in the app manifest.

Ensure primary executable isn't accidentally set to a folder path - It is not as shown in the screenshot

Step 3: Test package registration manually - I ran the command and it returned an error for the certificate although that is expected because I'm using a self-signed certificate which is not trusted on my machine. It is trusted in the AVD
Satish Mada 425 Reputation points Microsoft External Staff Moderator

2025-08-25T09:28:03.2033333+00:00

Hi Alex Dresser,

Just checking in to see if you had a chance to review the response provided by me.

Feel free to reach out if you have any further queries.
Alex Dresser 5 Reputation points

2025-08-26T07:14:16.4333333+00:00

Hey Satish,

Thank you for your follow up on my comment.

I will do my best to answer the steps you provided -

Certificate and Trust - I use the same certificate for all the other packages and they deploy fine. Additionally, since I am deploying via App Attach it would not let me even package the app into App Attach if one of the session hosts does not recognize the certificate. It is not a certificate issue currently.

SSMS 21 Opening File Explorer Instead of the App - I tried these steps and it did not help unfortunately. The logging does not point to anything specific.

Other Things to Try - I packaged SSMS 20 installer only using MSIX Hero. What this did is that it deploys the installer and once installed you can add SSMS 20 via the Start Menu option in the Application Groups. This is basically like deploying it locally so it's only a test/workaround.

If This Still Doesn’t Work

Or try packaging a simpler version of SSMS with just the essential files to see if something in the full package is causing the problem. - I have tried packaging everything from SSMs 18 - 21 and none of them work. I believe that SSMS is not designed to be packaged as all indicators point to that.
Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-09-16T19:39:46.2166667+00:00

Hello Alex Dresser,

Just checking in if you got a chance to try out the suggestions shared by me earlier.
Let me know if you have any blockers or any questions regarding it.
Alex Dresser 5 Reputation points

2025-09-17T06:30:42.52+00:00

Hey Ankit,

Thank you for the suggestion. I have not tried it yet but it looks interesting and I will go ahead with testing it at some point.

I will let you know if it helps.

Thank you!

Answer 1

Alex Dresser 5

Hey Ankit,

I tried testing out your steps but I run into an issue on Step 3.

Step 3: Create the Package

Open the MSIX Packaging Tool.
Choose "Create a new package".
On the Package information page, fill in your details (Name, Publisher, Version).
On the Prepare computer page, it's best to use a clean VM. Take a snapshot if you can.
On the Installation page, you will not install SSMS. Instead, you will simply copy the files. · Click "Browse" and select your SSMS-Setup-ENU.exe and install_ssms.ps1 files. The tool will copy them into the package.
Proceed through the remaining screens without making changes related to the installation. The tool will finish and create an MSIX package containing just your two files.

It is not possible to select more than 1 file while Browsing to select an installer. How can I select both the ps1 and exe files?

Thank you in advance!

Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-03T23:56:00.6566667+00:00

Hello @Alex Dresser ,

Thank you for the feedback on the steps shared.

Can you please confirm if you have tried to select one file first and again click browse button and then select the file ? (this should allow you to select more than 1 file)

If it doesn't, then you can create a separate folder and then place your both files (SSMS-setup.exe and insall_ssms.ps1) in that folder and then on the installation page you can choose "Add folder" instead of Browse and this will select the entire folder into your package.

Let me know what works out best for you!
Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-06T18:14:40.8766667+00:00

Hello @Alex Dresser ,

Just checking in the shared steps worked out for you.
Alex Dresser 5 Reputation points

2025-10-07T11:10:46.22+00:00

Hey Ankit,

neither of those options is available to me. I tried selecting the files 1 at a time but it just replaces the file. It does not allow me to select a folder instead it just opens the folder.
Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-09T20:11:14.6033333+00:00
Hello Alex,

Apologies for the miss from my end.

Would it be possible to use another tool to implement this?

If yes, are you open to try "MSIX Hero" for it now?

Download MSIX Hero from the Microsoft Store

Open your existing MSIX package or create a new one

Use the intuitive interface to drag/drop multiple files

Edit the manifest directly within the tool

If MSIX Hero doesn't suit then try below work-around to see if this works out as step-5

On the Installation page, browse and select just your SSMS-setup.exe file

Complete the package creation process - this will generate a basic MSIX file
then

Add the second file using Package Editor:

Open the MSIX Packaging Tool->Select Package editor instead of Create a new package

Open the MSIX file you just created

In the Package Editor, you can now drag and drop your install_ssms.ps1 file directly into the file structure view

Save the updated package
Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-13T17:48:34.6766667+00:00

Hey Alex, just checking in if you got a chance to try out the above method and it worked for you?
Alex Dresser 5 Reputation points

2025-10-14T06:14:31.2766667+00:00

Hey Ankit, I have tried following the instructions. I did manage to package a whole folder using the MSIX. I then loaded that package into the MSIX Package Editor and tried to modify the app manifest with the information you sent over "<Applications> <Application Id="InstallSSMS" Executable="powershell.exe" EntryPoint="Windows.FullTrustApplication"> <uap:VisualElements DisplayName="Install SQL Server Management Studio" Description="Runs the SSMS installer locally" BackgroundColor="transparent" /> <uap:Extension Category="windows.customInstall"> <uap:CustomInstall Folder="Contents"> <uap:OnInstall Command="powershell.exe -ExecutionPolicy Bypass -File "install_ssms.ps1""/> </uap:CustomInstall> </uap:Extension> </Application> </Applications>". Once I save the manifest file I get an error in the Package editor saying it's not able to Parse the manifest file and that I should fix the errors first.

Ankit Yadav 4,555 Microsoft External Staff Moderator

It seems that the xml file is invalid,

can you try below xml file to see if this fixes the issue:

<?xml version="1.0" encoding="utf-8"?>
<Package xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10"
        xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10"
        xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities"
        xmlns:desktop="http://schemas.microsoft.com/appx/manifest/desktop/windows10">
<Identity Name="SSMS.Installer"
           Publisher="CN=YourPublisher"
           Version="1.0.0.0" />
<Properties>
<DisplayName>SSMS Installer</DisplayName>
<PublisherDisplayName>Your Company</PublisherDisplayName>
<Description>SSMS deployment via App Attach</Description>
</Properties>
<Resources>
<Resource Language="en-us" />
</Resources>
<Dependencies>
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17763.0" MaxVersionTested="10.0.19041.0" />
</Dependencies>
<Capabilities>
<Capability Name="internetClient" />
<rescap:Capability Name="runFullTrust" />
</Capabilities>
<Applications>
<Application Id="InstallSSMS" Executable="powershell.exe" EntryPoint="Windows.FullTrustApplication">
<uap:VisualElements
       DisplayName="Install SQL Server Management Studio"
       Description="Runs the SSMS installer locally"
       BackgroundColor="transparent"
       Square150x150Logo="Assets\StoreLogo.png"
       Square44x44Logo="Assets\StoreLogo.png" />
<Extensions>
<uap:Extension Category="windows.customInstall">
<uap:CustomInstall Folder="Contents">
<uap:OnInstall Command="powershell.exe -ExecutionPolicy Bypass -File &quot;install_ssms.ps1&quot;"/>
</uap:CustomInstall>
</uap:Extension>
</Extensions>
</Application>
</Applications>
</Package>

Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-14T18:37:59.7833333+00:00
if you are using alternative way ie using MSIX Hero, it has Built-in Manifest Editor Instead of manually editing the XML in Package Editor, try this in MSIX Hero:

Create your package with the folder containing both files

In MSIX Hero, use the "Manifest" tab - it provides a form-based editor that prevents syntax errors

Set the application type to "Full Trust"

Configure the custom install command in the appropriate section
Alex Dresser 5 Reputation points

2025-10-15T07:27:33.2366667+00:00

Hey Ankit, thank you for the steps you shared.

I tried changing the XML with what you shared but I still get an error - /[local-name()="Package" and namespace-uri()="http://schemas.microsoft.com/appx/manifest/foundation/windows10"]/[local-name()="Properties" and namespace-uri()="http://schemas.microsoft.com/appx/manifest/foundation/windows10"][1]

Content for element '{http://schemas.microsoft.com/appx/manifest/foundation/windows10}Properties' is incomplete according to the DTD/Schema.

Expecting: {http://schemas.microsoft.com/appx/manifest/foundation/windows10}Logo.

I do not see a "Manifest" option anywhere in MSIX Hero. Where is this option located? Do I need to access one of the Tools options first?
Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-15T21:10:29.5033333+00:00
Thanks for sharing the error details, it says that the schema requires a Logo element in the Properties section. try it by adding this line to your Properties:

<Properties> <DisplayName>SSMS Installer</DisplayName> <PublisherDisplayName>Your Company</PublisherDisplayName> <Logo>Assets\StoreLogo.png</Logo> <Description>SSMS deployment via App Attach</Description> </Properties>

You must also create the logo file:

Create an Assets folder in your package

Add a PNG file named StoreLogo.png (keep it small maybe max 50pixel)

Make sure this folder and file are included in your package
Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-15T21:12:45.8766667+00:00
Regarding:

I do not see a "Manifest" option anywhere in MSIX Hero. Where is this option located? Do I need to access one of the Tools options first?

In MSIX Hero:

Open your package in MSIX Hero

Look for these tabs in the main interface:

"Files" (shows package contents)

"Details" or "Information" ← THIS IS THE MANIFEST EDITOR

"Certificates"

"Registry"

Click the "Details" or "Information" tab - this is MSIX Hero's visual manifest editor

You'll see form fields for:

Package Name

Publisher

etc etc

Alternative: Use Right-Click on the AppxManifest.xml file

-In the "Files" tab, right-click on the AppxManifest.xml file

-Choose "Edit" or "View Manifest" · This should open the visual editor for you.
Alex Dresser 5 Reputation points

2025-10-16T07:42:47.41+00:00

Hey Ankit,

thank you for the clarification.

Here is what I did :

I opened the msix package in MSIX Hero - I edited the AppManifest.xml with the code you provided to me (made sure to replace the variables) - I saved and closed this - I packaged the msix file into a vhdx file and uploaded it to the file share - I created an App Attach volume using the vhdx - I deployed it to the Remote App Group - Tried to run it from Windows App and it tries to start but crashes after a few seconds and then it never opens - I tried to get on a session host via RDP and when I click on the SSMS it just never opens. It seems like this is not working.

Is there something I have missed or I should do differently?
Ankit Yadav 4,555 Reputation points Microsoft External Staff Moderator

2025-10-28T12:55:59.1533333+00:00
Hello Alex,

Sorry for the delay in response,

It looks like the custom install task isn't executing as expected. While the package might be getting staged correctly, the actual SSMS installation doesn’t seem to be happening.

Here are a few common issues to check :

Custom Install Not Triggering: Custom install tasks only run during package provisioning—not when the app is launched by the user.

PowerShell Execution Policy: The script might be blocked by the system’s execution policy. Try making your install command more explicit to bypass this.

Script Path Issues : Your PowerShell script may not be locating the EXE file correctly. Double-check that install_ssms.ps1 is pointing to the right path.

Let me know if you'd like help reviewing the script or adjusting the install command.
Alex Dresser 5 Reputation points

2025-11-05T13:20:56.3366667+00:00

Hey Ankit, thank you for the steps provided.

I have reviewed those steps already but none of them seem to be causing the issue. It just seems like (from all the testing) SSMS is not meant to be packaged into an MSIX at all.

The other apps I have deployed work fine but SSMS and PowerBI are just not taking.

Share via

Deploying Database Tools with MSIX/App Attach

1 answer

Your answer