appinstaller

7 Topics

Removal of an AppX/MSIX package leaving unwanted clutter in the user registry.
MSIX is supposed to be a clean uninstall. However, I have some detected some unnecessary garbage left behind when uninstalling under HKCU\Software\Classes. Take a package and install it. Then Uninstall it. Repeat that a few times. Open Regedit. Browse to HKCU\Software\Classes. Do a find on the package name,. You will find there is a key starting with AppX (followed by random looking letters) with subkeys Application, DefaultIcon, and possibly Shell. These were added during the installation of the package. Keep searching (F3). You will find the same information under an AppX... key for each package you originally installed. This does not appear to be due to delayed removal, as they remain weeks or months later.
TIMOTHY_MANGAN
Aug 02, 2025 Place MSIX
66Views
0likes
0Comments
Opening the msix file results in an error: "The app didn't start."
But Appinstaller start normally when I switch to Administrator User.
Solved
HumanMusic
Dec 27, 2023 Place MSIX
8.2KViews
0likes
17Comments
AppInstaller fails on fresh windows installations
When I try to install the msixbundle via an .appinstaller file, it fails on fresh windows installations (Windows 10 as well as Windows 11) and shows the following error: The error message is also misleading. It says "Installing this package requires administrator privileges. From an Administrator PowerShell prompt, run the command: Add-AppxPackage C:\Users\x\Downloads\OurInstaller.appinstaller" The Add-AppxPackage command doesn't work if called like this. The path has to be passed via the -AppInstallerFile flag instead, i.e. Add-AppxPackage -AppInstallerFile C:\Users\x\Downloads\OurInstaller.appinstaller Directly installing the app via the .msixbundle file works flawlessly, though. But then it doesn't support automatic updates of course. Also, as soon as I install Visual Studio, the installation via the .appinstaller file works too without any problems. How could we fix that?
ThomasDanecker
Jun 08, 2022 Place MSIX
1.4KViews
0likes
1Comment
'Error parsing app package' error after version change
I integrated MSIX into a WinForms project and configured it as a package bundle and deployed to an Azure App Service. Everything works fine and I can install the app. But when I deploy a new version it fails to auto update and when I try to install the application again it fails with "Error parsing app package" error. If I sign out or restart my PC, it works. I'm not sure what to do to solve this, because the installer works. How can I solve this? It looks like a caching issue or something similar, as described here. The Delivery Optimization Service doesn't download the entire App Installer file and because of this it fails to parse it. https://stackoverflow.com/questions/64381453/appinstaller-xml-issue/68976913#68976913 I even tried the suggested workaround - to pad the contents of the App Installer file. But still doesn't work. Not sure what else can I do here. This is my App Installer file. I removed sensitive information so the urls will not work. ``` <?xml version="1.0" encoding="utf-8"?> <AppInstaller Uri="https://d1-myapp-setup-wba.azurewebsites.net/POS.Installer.appinstaller" Version="1.0.0.46" xmlns="http://schemas.microsoft.com/appx/appinstaller/2017/2"> <MainBundle Name="954a406f-c23f-4089-9b7f-b2241bfb3245" Version="1.0.0.46" Publisher="CN=MyCompany" Uri="https://d1-myapp-setup-wba.azurewebsites.net/POS.Installer_1.0.0.46_Test/POS.Installer_1.0.0.46_AnyCPU.msixbundle" /> <UpdateSettings> <OnLaunch HoursBetweenUpdateChecks="0" /> </UpdateSettings> </AppInstaller> ``` This is my web.config in the Azure App Service: ``` <?xml version="1.0" encoding="utf-8"?> <configuration> <system.webServer> <staticContent> <mimeMap fileExtension=".msix" mimeType="application/msix" /> <mimeMap fileExtension=".msixbundle" mimeType="application/msixbundle" /> <mimeMap fileExtension=".appx" mimeType="application/vns.ms-appx" /> <mimeMap fileExtension=".appxbundle" mimeType="application/vns.ms-appx" /> <mimeMap fileExtension=".appinstaller" mimeType="application/xml" /> </staticContent> <httpProtocol> <customHeaders> <add name="Pragma" value="no-cache" /> <add name="Cache-Control" value="max-age=0, no-cache, no-store, must-revalidate" /> <add name="Expires" value="Sat, 01 Jan 2000 00:00:00 GMT"/> </customHeaders> </httpProtocol> </system.webServer> </configuration> ```
Solved
szilardd
Nov 10, 2021 Place MSIX
5.4KViews
0likes
4Comments
Deployment by Appinstaller cause URI handling popup without the app link
I have a win32 app wrapped into MSIX by MSIX packaging tool for using the https://docs.microsoft.com/en-us/windows/uwp/launch-resume/web-to-app-linking feature. After installing the app by .appinstaller file I got a popup "How do you want to open this website?": there is no application that I have installed. https://docs.microsoft.com/en-us/windows/msix/app-installer/app-installer-file-overview content: <?xml version="1.0" encoding="utf-8"?> <AppInstaller xmlns="http://schemas.microsoft.com/appx/appinstaller/2018" Version="1.0.0.9" Uri="https://camarowebtoapp20201005195335.azurewebsites.net/packages/camaro.appinstaller" > <MainPackage Name="ConsoleApp" Publisher="CN=vshmelev" Version="2.0.1.0" ProcessorArchitecture="x64" Uri="https://camarowebtoapp20201005195335.azurewebsites.net/packages/ConsoleApp_2.0.1.0_x64__xc65amp813vx8.msix" /> <UpdateSettings> <OnLaunch HoursBetweenUpdateChecks="0"/> </UpdateSettings> </AppInstaller> However, if I install the app directly by the .msix the app link listed in the popup Sample project sources: https://github.com/wadim1611/msixDeployment OS info: - Windows 10 Enterprise - version: 2004 - OS build: 19041.508 - Experience: Windows Feature Experience Pack 120.2212.31.0 The only logs that I could find are: What I'm doing wrong? Can I get more detailed logs for the app installation?
vshmelev
Feb 06, 2021 Place MSIX
2.4KViews
0likes
4Comments
Is It Possible To Use Publish Single File In .Net Core 3 With AppInstaller/MSIX?
Hi, Where I work we have a WPF application that we converted to .NET Core 3.0 and migrated to MSIX/AppInstaller from ClickOnce. I noticed that .NET Core 3.0 has the ability to publish as a single file. However if I add this setting to my .csproj for my WPF application and/or make modifications to the .wapproj: <ItemGroup> <ProjectReference Include="..\..\Application\MyWpfDotNetCore3App.csproj"> <DesktopBridgeSelfContained>True</DesktopBridgeSelfContained> <DesktopBridgeIdentifier>win-x64</DesktopBridgeIdentifier> <Properties>SelfContained=%(DesktopBridgeSelfContained);RuntimeIdentifier=%(DesktopBridgeIdentifier);PublishReadyToRun=true</Properties> <SkipGetTargetFrameworkProperties>True</SkipGetTargetFrameworkProperties> </ProjectReference> </ItemGroup> And then publish or build the MSIX and AppInstaller files (either using VS or Azure Devops), the MSIX bundle still contains all of the loose files for the app and its dependencies. This isn't really an issue, but I would just like to know if MSIX/AppInstaller currently supports this functionality or if I am doing something wrong?
Solved
StephenJeffreyWhite
Nov 30, 2019 Place MSIX
3KViews
0likes
2Comments
Use custom appinstaller file in Visual Studio packaging process
Hi! Still new to MSIX and trying to figure out the workflows. I have a WPF Bridge app and a Windows Application Packaging project in Visual Studio. I have successfully used Visual Studio's Publish -> Create App Package wizard. Now I'd like to add the option to the appinstaller file to show a prompt when there's an update ( <UpdateSettings><OnLaunch ShowPrompt="true" ... ). Is there a way to have that option included in the packaging process through Visual Studio? The only alternative that I can see is to manually edit the generated appinstaller file in AppPackages every time I publish, which I'd prefer not to have to do. Thanks!
Solved
twastvedt
Nov 18, 2019 Place MSIX
2.4KViews
0likes
5Comments