I have built an MSIX package for installing DB2 Connect. It is a complex install, that requires configuration file execution, manual license activation and a registry merge post install of the App itself. I was able (after numerous attempts) to get this install working using powershell execution. It installs cleanly on the Hyper-V I built it on and all post install steps clearly worked before I close the installer and generate the package. The package installs without error on a test machine, but the post-install pieces are not there, when checked. There are no errors in the log. The Windows App Certification Kit will not open MSIX files. Any help or suggestions are appreciated.

David Hed How did you launch RegEdit? (as I don't see you have Powershell or any other tools open) If you launch it normally, it won't be able to see any of the registry entries, that is expected behaviour. To launch a local exe like regedit inside the container, you would need to enable developer mode and then use the Invoke-CommandInDesktopPackage command, or a 3rd party tool like Hover, MSIX Hero or MSIX Commander.

Where are these 'post install pieces'? If they are config files under %APPDATA% for example, they get captured by the MSIX Packaging Tool, but the MSIX runtime redirects app requests for appdata to a different location. Use the PSF to work around this, I recommend PsfTooling or try to capture using Advanced Installer.

Dan Gough Dan,I appreciate the reply. While that tool is helpful to know about, it does not help in my situation. I have reached out directly to someone I know on the Microsoft MSIX Team.

Hi David Hed, Could you clarify what you mean when you say the post install pieces are not there? Do you mean they are not in the package at all, or do you mean they are in the package but don't have any effect when you install it? You can check this by opening the package for editing in the MSIX Packaging Tool and looking for the files and registry keys added post install. If the post install pieces are not in the package, please double check the settings in the packaging tool to make sure they are not in the exclusions list. If they are in the package but don't have the expected effect when installed, please make sure they are in a location that is merged with the filesystem or registry at runtime. You can see a list of supported locations at https://docs.microsoft.com/en-us/windows/msix/desktop/desktop-to-uwp-behind-the-scenes If the post install involves creating file type associations or services or any other registration like that, it should be translated to an entry in your app's manifest. If it is not being translated, please let us know what information is missing so that we can investigate.

Chacon I have verified that all pieces are in the package. The part that is not coming through are the registry entries. The entries are in the Virtual Registry in the package. I have set the package to run with elevated privileges.

App installs with no errors, but does not fully install

23 Replies

Dan Gough
Brass Contributor
Apr 17, 2020
Where are these 'post install pieces'? If they are config files under %APPDATA% for example, they get captured by the MSIX Packaging Tool, but the MSIX runtime redirects app requests for appdata to a different location. Use the PSF to work around this, I recommend PsfTooling or try to capture using Advanced Installer.
- David Hed
  Copper Contributor
  Apr 21, 2020
  Dan Gough
  Dan,
  I appreciate the reply. While that tool is helpful to know about, it does not help in my situation. I have reached out directly to someone I know on the Microsoft MSIX Team.
  - Chacon
    Microsoft
    Apr 21, 2020
    Hi David Hed,
    
    Could you clarify what you mean when you say the post install pieces are not there? Do you mean they are not in the package at all, or do you mean they are in the package but don't have any effect when you install it? You can check this by opening the package for editing in the MSIX Packaging Tool and looking for the files and registry keys added post install.
    
    If the post install pieces are not in the package, please double check the settings in the packaging tool to make sure they are not in the exclusions list.
    
    If they are in the package but don't have the expected effect when installed, please make sure they are in a location that is merged with the filesystem or registry at runtime. You can see a list of supported locations at https://docs.microsoft.com/en-us/windows/msix/desktop/desktop-to-uwp-behind-the-scenes
    
    If the post install involves creating file type associations or services or any other registration like that, it should be translated to an entry in your app's manifest. If it is not being translated, please let us know what information is missing so that we can investigate.

Forum Discussion

App installs with no errors, but does not fully install

23 Replies

Resources