Forum Widgets
Latest Discussions
Context Menu in MSIX package broken in Windows 11 24H2
Context Menu in MSIX package broken in Windows 11 24H2 NOTE: Please don't reply on this message with other broken issues with 24h2; start a new issue! A package of NotePad++ with the shell extension context menu that works on Windows 11 22H2 and 23H2 fails to produce the context menu when installed on 24h2. It is not on the main right-click nor the show more options display.54Views0likes1CommentFTAs for multiple application IDs
Hello. I am trying to package PuTTy into MSIX. PuTTy sets up the file extension .PPK with two verbs: 'open' which uses the Pageant application, and 'edit' which uses the PuTTygen application. I can edit the MSIX manifest and successfully associate the 'open' verb under the Application Id for Pageant, but if I also add the 'edit' verb under the Application Id for PuTTygen, it will not allow me to do so. Does anyone know if it is possible to associate the same file type extension with two separate Application Ids?CrazylarryFeb 12, 2025Copper Contributor12Views0likes1CommentMSIX Packaging tool fails to install offline for Win 11 22H2 and newer
Followed the instructions here: Using the MSIX Packaging Tool in a disconnected environment - MSIX | Microsoft Learn: dism /online /add-package /packagepath:"C:\MSIX\Msix-PackagingTool-Driver-Package~31bf3856ad364e35~amd64~~1.cab" but installation fails with error: Msix-PackagingTool-Driver-Package Error: 0x800f0818 CBS log provides the following detail: Info CBS Package doesn't match FOD for the current OS, package: Msix-PackagingTool-Driver-Package~31bf3856ad364e35~amd64~~10.0.22000.1, expected:Msix-PackagingTool-Driver-Package~31bf3856ad364e35~amd64~~10.0.22621.1 [HRESULT = 0x800f0818 - CBS_E_IDENTITY_MISMATCH]How to convert msix to msi?
Hello, I am currently working with a Windows application packaged as an .msix file, which is used for connecting to Azure Virtual Desktops (AVD). I need to convert this .msix package to an .msi package. Additionally, I am looking for a way to convert a Microsoft Store app into an .msi package. Challenges: Converting MSIX to MSI: I need a reliable method or tool to convert the existing .msix file to an .msi file without using Advanced Installer (didn't work). Microsoft Store App to MSI: I also need guidance on how to package a Microsoft Store app as an .msi. If anyone is familiar with these processes, especially in the context of the windows app (yes there is an app named "windows app"), your help would be greatly appreciated. Thank you!HodniFeb 12, 2025Occasional Reader20Views0likes0CommentsSigning MSIX packages with Azure Trusted Signing Accounts
I have a requirement to sign an MSIX package without access to a code signing certificate. I have successfully signed a powershell script using the Azure Trusted Signing Account: Trusted Signing Certificate Profile Signer role however when trying to sign either an exe of MSIX, i receive the signtool error: This file format cannot be signed because it is not recognized. Whereas the signtool documentation clearly states that .appx / .msix packages can be signed with this crypto tooling. There is no additional information in the AppX event viewer operational or debug areas that I can see. I have ensured that the publisher details match that of the certificate profile listed under the Trusted Signing Account resource in the Microsoft Packaging Tool, albeit I set a application specific publisher display name instead. Has anyone had any success using this process?GrahamGBFeb 10, 2025Brass Contributor102Views0likes9CommentsSingle MSIX package containing two parts: requiring/not requiring administrator privileges to run
My software consists of two parts: A and NA. Part A requires administrative rights to run. Part NA does not require administrative rights to run. I need to have a single MSIX installation for both parts. I have following questions: 1. Can such an installation be built? 2. Can the A part be installed (not run after installation, but installed) without administrative privileges? 3. Is there a sample/tutorial/documentation where this situation is covered?Solveda-okrasinskiFeb 10, 2025Copper Contributor16Views0likes2CommentsHow to package a Windows Desktop C++ application together with its DLL dependency using MSIX
Hello, I'm trying to understand how to package a simple Windows desktop application and a custom DLL which are written in C++, using MSIX. The steps I roughly did using latest / updated Visual Studio 2022: 1) Create a solution and project using New project -> Windows Desktop Application C++ / Windows / Desktop 2) Add a new "Dynamic-Link Library" project to the same solution. 3) Add an exported C++ function (via a .h / . cpp pair) into the dll library and use it in the windows desktop application's main function. 4) Add a reference and build dependency to the library in the application project. 5) Build and confirm that everything runs and works as expected. The output directory of the executable also contains the dll. 6) Add a new "Windows Application Packaging Project" to the solution. 7) Add the application as a project reference to the packaging project and set the application as the entry point. 😎Try to build and run the application via the packaging project. Observe error dialog "app.exe - System Error" "The code execution cannot proceed because mylib.dll was not found". Indeed if i go into the packaging project build folder (mysolution/MyMSIXProject/bin/x64/Debug/myapp), the executable itself is present (app.exe), its pdb file is present, but the mylib.dll file is missing, although its pdb file is present. If i go to the non-packaging project build dir, i can confirm the existence of both the .exe and the .dll file. I even tried doing some things like adding test.txt files, and marking them as content and changing their Item Type to "Copy file", and i observe that they do get copied into the regular executable output dir, but not to the packaging dir. I also tried creating the msix file by right clicking the packaging project and choosing Publish -> Create App Packages -> sideload, unzipping the msix file and confirming the missing .dll and .txt files. I played with a lot of the project and solution properties, but could not get the .dll and .txt files to be deployed. What am I doing wrong? How can i package / deploy extra .dll and .txt files? Thank you in advance. Here is my playground solution, in case it is helpful https://github.com/alcroito/vs_msix_playground sol1 - the solution name myd1 - the dll library project wp1 - the windows desktop executable project MyMSIX - the packaging projectalcroitoFeb 09, 2025Copper Contributor1.7KViews1like4CommentsDistribute appinstaller and MSIX via Azure blob storage.
Hey all, I have an automated CD pipeline that signs the MSIX package and uploads both the MSIX package and appinstaller file to an Azure blob storage. Since my users do not have direct access to the blob storage, I have created a web application that has access to the blob storage with an API that can download the appinstaller or MSIX package. I am able to download both the appinstaller and MSIX package when entering the URL manually in the browser. However, when I launch the appinstaller it displays an error that an app package could not be opened. The reason is "An error occurred while accessing the file from the web. Please try downloading and opening the file locally." The API returns a `FileContentResult` and uses the correct MIME. "application/appinstaller" for appinstaller and "application/msix" for the MSIX package. Any idea what could be wrong?SolvedMoodie_GhaddarJan 31, 2025Microsoft551Views0likes2CommentsRun a program included in a MSIX package from the package program entry point.
Hello. I've created an MSIX package that contains two programs: P1.EXE and P2.EXE. P1.EXE is the application entry point and it works ok. At some point of P1.EXE execution, P1.EXE runs P2.EXE. This works ok if application capabilities is defined as "Full Trust" but I don't want to have such a global access. Please help me to stablish the proper 'applicaction capabilities' combination than will allow P1.EXE to run P2.EXE Thanks in advance. VicenteSolvedVicGarJan 17, 2025Copper Contributor58Views0likes2CommentsMSIX appinstaller UpdateSettings
I have an MSIX and associated appinstaller file. Within the AppInstaller I have various Update settings such as OnLaunch / HoursBetweenUpdateCheck =0, ShowPrompt=true and automaticBackgroundTask. When I install the app using the appinstaller, this works, and the app launches. If I then close the app, and try to launch it again, the appinstaller prompt is launched, but with the message "Cannot Open App Package : failed due to unknown reason". In logs, I have the message "Error code: Activation is blocked due to the .appinstaller update settings for this app.. Activation phase: Deployment". Anyone come across anything like this? I have tried changing the AppInstaller Uri and the MainPackage Uri to local files (C:), mapped network drives and UNC paths. But the same appinstaller works for the initial installation, then fails on the update check.PeterCaugheyJan 15, 2025Copper Contributor16Views0likes0Comments
Resources
Tags
- MSIX60 Topics
- appinstaller6 Topics
- MSIX Packaging Tools4 Topics
- appattach3 Topics
- MSIX LIMITATIONS3 Topics
- APPX3 Topics
- msix packaging tool3 Topics
- MSIX AppAttach launch failure3 Topics
- Access MSIX Container3 Topics
- sideloading2 Topics