User Profile
alexmarin89
Iron Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Re: Windows 11 context menu
Edijs_Perkums_MasterPackager Yes you can add context menus by using MSIX Sparse Packages. First, you need to set your MSIX to allow external content to reference content outside its package, in a specific location on disk. Next, the app must point to your Win32 executable and lastly enable the Unvirtualized Resources capability. Once you have done all that, install the sparse package from your MSI package and you should by on your way. A more in-depth article on this https://www.advancedinstaller.com/how-to-create-sparse-package.html. PS: I work for the Advanced Installer team.MSIX Dependencies
Hi, I've tried to create an MSIX package which has a dependency for another MSIX package. As far as i know, if you manually deploy an MSIX package that has a dependency, the dependency must be manually installed before, because the main MSIX package does not know where the dependency is (makes sense). So i started to make an .appinstaller file which contained the <Dependencies> element so that the installation could first install the dependency, and afterwards the main MSIX. Inside the element, the URI is set to an UNC path. When i try to install the package via the .appinstaller file, the following error occurs: Looking through the https://docs.microsoft.com/en-us/uwp/schemas/appinstallerschema/element-dependencies about this, i can see that my package name is declared correctly. However, my appinstaller file was missing the dependency ProcessorAchitecture, which was X64 (in some cases, i see that the AppInstaller is looking for the _native version by default). After placing the ProcessorAchitecture to X64 in the .appinstaller, i tried the installation again, but this time with the following error: I then went and manually tried to install the dependency first (from my local pc), and then the MSIX package (without the .appinstaller file). The dependency is installed on the system, as the Get-AppxLog suggests: 09/11/20 - Mon 9:45:32 PM 613 Performance summary of Deployment Add operation on Package Caphyon.SampleApplication_2.0.0.0_x64__4crez2cfzhms2: Overall time: 5329 ms Gap: 16 ms Enqueue cost: 109 ms Dequeue delay: 0 ms Gap: 16 ms Bundle processing cost: 0 ms Indexing cost: 63 ms Resolve dependency cost: 15 ms Gap: 16 ms Check approval cost: 297 ms Evaluation cost: 2843 ms Hardlinking evaluation cost: 2750 ms Stage required cost: 79 ms Flushing and closing files cost: 0 ms Gap: 15 ms Machine register cost: 63 ms Stage user data cost: 0 ms Gap: 31 ms Registration cost: 359 ms Gap: 16 ms Repository commit transaction cost: 1328 ms Gap: 31 ms Data flush cost: 0 ms Post DeStage repository commit transaction cost: 0 ms Remaining cost: 32 ms But when i try to install the main package it appears it doesn't detect the dependency: The AppxManifest file seems to be ok according to the https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-packagedependency: <Dependencies> <TargetDeviceFamily MaxVersionTested="10.0.19041.0" MinVersion="10.0.17763.0" Name="Windows.Desktop"/> <PackageDependency MinVersion="2.0.0.0" Name="Caphyon.SampleApplication" Publisher="CN=TestCert_2020-3-25_14-56-53"/> </Dependencies> The dependency has a publisher specified and it's signed, so it doesn't fall in the framework category, and the dependency version is equal to the minimum version specified here. In the end, i managed to install the main MSIX and dependency in the following order: 1. Manually install the dependency first 2. Install the main app via the .appinstaller file from the URI share Somehow, it then detects that the dependency is installed. If i try to uninstall the main MSIX package and leave the MSIX dependency on the system, and then try to reinstall the main MSIX manually from my PC, the same error code as mentioned earlier appears. I couldn't find any additional error codes other than 0x80070057, which is specified https://docs.microsoft.com/en-us/windows/win32/appxpkg/troubleshooting that: "One or more arguments are not valid If you check the AppXDeployment-Server event log and see the following event; While installing the package, the system failed to register the windows.repositoryExtension extension due to the following error: The parameter is incorrect. You may get this error if the manifest elements DisplayName or Description contain characters disallowed by Windows firewall; namely | and all , due to which Windows fails to create the AppContainer profile for the package. Please remove these characters from the manifest and try installing the package. " Am i missing something here?Re: How to collect software inventory with SCCM CB for deployed MSIX apps?
Bigair-MifiHi, you can use the WMI class SMS_G_System_WINDOWS8_APPLICATION to create a query in SCCM. As an example: select SMS_R_System.Name, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_WINDOWS8_APPLICATION on SMS_G_System_WINDOWS8_APPLICATION.ResourceID = SMS_R_System.ResourceId where SMS_G_System_WINDOWS8_APPLICATION.ApplicationName = "microsoft.windowscommunicationsapps" This will show you all the computers with "microsoft.windowscommunicationsapps". To get all MSIX/Appx apps from the infrastructure, you could use: select distinct SMS_G_System_WINDOWS8_APPLICATION.ApplicationName, SMS_G_System_WINDOWS8_APPLICATION.FamilyName, SMS_G_System_WINDOWS8_APPLICATION.FullName, SMS_G_System_WINDOWS8_APPLICATION.Publisher, SMS_G_System_WINDOWS8_APPLICATION.Version, SMS_G_System_WINDOWS8_APPLICATION.Architecture from SMS_G_System_WINDOWS8_APPLICATION Additionally you have a default report called https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/list-of-reports If you want to do something in the database, you can use the v_GS_WINDOWS8_APPLICATION view.Re: Way to package a shortcut with MSIX
Priyanka_AggarwalHi, The shortcut trick from APP-V to link Java with IE doesn't currently work with MSIX. Maybe in the future it will be possible when linking for MSIX packages becomes available. For the moment, as far as i know, msix linking is in the backlog.Re: Writing to local registry
HiJeffWhiteside . After you add RegistryWriteVirtualization and FileSystemWriteVirtualization, when you try to install the MSIX package, indeed these capabilities appear. Capabilities: "Write registry entries and files that are not cleaned up on uninstall". However, when you try to install it, you receive the following error "This app package is not supported for installation by App Installer because it uses certain restricted capabilities.". The xmlns:rescap XML namespace declaration is added in the package manifest. The only way i got this to install is by running powershell as admin and use add-appxpackage. Am i missing something?Re: [MSIX] - Packaging GIMP
TheStingPilotI tested 2.10.12 by creating the folder structure specified in their git board (C:\Output\Gimp) and installed it there (the path should be after installation C:\Output\Gimp\Gimp 2). After that in the capture with Advanced Installer i specified the application folder to be GIMP 2, that solved for me the problem of copying the dlls to system32 and system64. But that doesn't work either. However, i've done more tests and i was thinking maybe something has changed since the 2.10 release of GIMP...and indeed something has changed. I made a capture for GIMP 2.8.22. When you try to build it the first time you will receive some errors that GIMP 2\32\lib\gimp\2.0\python\gimp.pyd.debug' is not a valid Portable Executable for 'Build_MSIX_APPX->x64' build and other 4 or 5 .debug files. I've deleted the files, doesn't seem to affect how it works. But of course i ran into the issues with the dlls that are not loading. So again i've copied the dlls in System32 and System64. I also changed the Application Folder to be in GIMP 2. And after that, everything works! GIMP 2.8.22.0 works with MSIX! I am now curious what are the differences, i will try to do some more digging to see if maybe it's something that can be solved for the latest 2.10 releases also. I thought maybe it's some hardcoding in some files, the only thing i found it in pygimp.interp located in lib\gimp\2.0\interpreters: python=C:\Output\Gimp\GIMP 2\bin\pythonw.exe python2=C:\Output\Gimp\GIMP 2\bin\pythonw.exe /usr/bin/python=C:\Output\Gimp\GIMP 2\bin\pythonw.exe :Python:E::py::python: However, trying to dehardcode that file doesn't solve much. And with a normal installation if you delete that file it doesn't seem to affect the functionality of GIMP, so that's a no go there also. You can get the MSIX for 2.8.22.0 https://1drv.ms/u/s!Aur7_pRUgEnsiLljrcV30jjD_eWdpg?e=XHDVWV.
