Forum Widgets
Latest Discussions
Add Environment Variable to MSIX package using PSF Fixups in Packaging Tool - what am I missing?
Hi everyone, I am currently testing packaging apps into the MSIX format and have been successful for any simple installers. Now that I am trying to package more advanced installers I have to utilize PSF Fixups, in which I have issues with the Environment Fixup. Even though I have read up on previous discussions regarding this, I simply cannot get this fixup to be successfully added and recognized within the MSIX App. I am judging this based on that the same app will tell in its own app options whether the environment variable is available or not. Some key info (Tried attaching several screenshots, but it wilI not let me. Hopefully the necessary information comes across): Using MSIX Packaging Tool version 1.2024.405.0 Using the included PSF Fixup for Environment Variables within MSIX Packaging Tool. All PSF Fixup files are included in the MSIX Package. In the manifest file the executable "PsfLauncher64.exe" is pointed at. Basically, the config.json is formatted in the following way if I were to change out anything referring to the actual app name. What am I possibly missing out on or have misunderstood here? Any help in leading me into the right direction is very much appreciated, thanks!
Reset user choice for windows.protocol tel:
Hi everyone, we ship an MSIX that registers a full-trust Dialer.exe as a windows.protocol handler for tel: so users can place calls from Outlook etc. Goal After installing our MSIX, we’d like Windows to show the “How do you want to open this?” prompt again for tel: so users see the new option. With our old MSI this was easy, we deleted HKCU\Software\Microsoft\Windows\Shell\Associations\UrlAssociations\<protocol>\UserChoice via the manifest entry: <RemoveRegistryKey Id="WipeDialerOnInstall" Root="HKCU" Key="SOFTWARE\Microsoft\Windows\Shell\Associations\UrlAssociations\tel\UserChoice" Action="removeOnInstall"/> Problem With MSIX there seems to be no manifest option to mimic that. We tried deleting UserChoice on first app start (HKCU, RegDeleteTree/SHDeleteKey), but it did not work. Questions Is there any supported or recommended way to trigger the default-app prompt (or clear the choice) for a specific protocol when using MSIX? Is deleting UserChoice from a full-trust MSIX app considered supported/allowed for Store submissions? Any guidance or stance appreciated! Thanks!
How to run edge inside MSIX
HI there, I have a MSIX that starts msedge (psflauncher.exe and then the config.ini executbable points to edge with an argument to open website. When testing i see that Edge starts outside the bubble, and does not see the files inside. Is there a way to run Edge inside the Virtual Environment? thanks,.WapProj build using "unvirtualizedResources" removed entry from manifest
I have a .wapproj that needs to use RegistryWriteVirtualization (aka "Flexible Virtualization) as described in Flexible virtualization - MSIX | Microsoft Learn This is for an MSIX package that will not be delivered via the Microsoft Store. The changes are made to the Package.appxmanifest file, and saved. The build action in Visual Studio removed the Capability declaration line for "unvirtualizedResources" from the Package.appxmaifest file before processing the file, leading to an error complaining that the RegistryWriteVirtualization requires this capability. Workaround: I can mark the file read-only outside of Visual Studio to keep VS from changing the file as a temporary workaround to prove out that the code depending upon these settings works. Why workaround is not acceptable: This workaround is not long-term viable, as other developers and automated workflows working on the project will lose the read-only setting (as it will not persist in GitHub) and have a broken build. It is clear that the VS code looking at this file is aware of both the desktop6 and virtualization schemas and their requirements and restrictions, but seemingly, although aware of other rescap capability extensions is unaware of this one. Requested action: Please add support for missing capabilities declarations in Visual Studio and/or underlying tools.
Why is it impossible to sign a .exe that is included in an msix?
I have a solution that has two projects. One projects makes a wpf exe. I call signtool in the post build step and it signs the .exe no problem. The other wapproj project publishes this into an msix and signs the msix bundle no problem. The .exe inside the .msix however is never signed. Why? The msix refuses to use the build output from the dependent project. I get the signing the bundle package prevents alteration on distribution, but this does nothing for protection after installation. No matter what I do I can't sign the contents inside the msix. Is this pointless? Why does Visual Studio only support signing the distribution package and not the contents inside the msix?I'm not seeing what I expected to see with Windows Application Packaging
I'm following along in a YouTube video I found that covers MSIX. I've created a simple WPF app in .NET 9, which is just a Hello World app. Then I added the Windows Application Packaging project. Or at least that's what I'm trying to do. What I got was two new projects added to my VS solution. Given my app's name is MyApp, one of the new projects is called MyAppInstaller, and the other new app is called "MyAppInstaller (Package)". I was expecting to see only the MyAppInstaller project added. I'm wondering if I've done something wrong.
Issues Editing MSIX Package to Disable LaunchWhenReady
We’re trying to disable the LaunchWhenReady setting in our MSIX package by following the guidance provided in Microsoft's documentation. https://learn.microsoft.com/en-us/windows/msix/app-installer/how-to-create-custom-app-installer-ux We initially tried using the MSIX Packaging Tool & Advanced installer to make the necessary changes in existing MSIX package, but were unable to get it working as expected.
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.
