Forum Discussion
MSIX : Modification Package Challenges
Hi KumarOne,
Will it be possible for you to test on a Windows Version 1903? We made an update to the modification package such that file overlay properly works. Also ensure that modification property is set to true in the package manifest:
<Properties> <rescap6:ModificationPackage>true</rescap6:ModificationPackage> </Properties>
More info:
-Dian
Hi Dian,
I'm trying to test the package and installation on 1909 and get's failed with below error. I have created custom self-signed certificate for package creation and testing.
The packages which were created on 1809 was signed again on 1909 using sign tool and still issue is same
"Either a new certificate must be installed for this app package or you need a new app package with trusted certificates. Your system administrator or the app developer can help. A certificate chain was processed but terminated in a root certificate that isn't trusted (0x800B0109)"
And also i have identified, the same issue with the LabCertificate provided in below location.
https://github.com/microsoft/MSIX-Labs/tree/master/MSIXLab
Any assistance will be much appreciated
- Dian HartonoApr 08, 2020
Microsoft
Hi KumarOne,
Looking at the error, it looks like the root certificate is no longer trusted. As you said, this is a self signed app so you need to install the certificate in order for the app to install.
- Right click on MSIX file
- Click Properties
- Click Digital Signatures
- Select Signature from the list
- Click Details
- Click View Certificate
- Click Install Certificate
- jvintzelApr 08, 2020Former Employee
If you are installing a self-signed certificate for testing purposes, make sure it goes into the Device store under Trusted People.
John.
- KumarOneApr 08, 2020Copper Contributor
jvintzelDian HartonoBogdan Mitrache
Hi All,
Thanks for your responses, I have now managed to get the applications tested. Below are my detailed findings
- Fixed Point 1 & 2
- Still looking forward for rest of the points(3,4,5).
- when ever i reset the application , i have noticed Modification package is getting removed
- I could see behaviour differences between Manual testing and SCCM Published testing, Has it been testing from sccm ?
"why you need to change the name of the app instead of just changing its version?"
Generally we following the Naming standard conventions , i belive it will be same across the enterprises.
Below is my scenario
Base/Main Package - MozillaFirefox68.6.0esrx64en-GB_68.5.0.0_x64
Base/Main Package - MozillaFirefox68.6.0esrx64en-GB_68.6.0.0_x64Modification Package - Firefox-ModificationPackage-01X
Unless i maintain a Unique Identity name for all packages i cannot use Modification package, again and again without any changes, if not i need to keep updating the Modification package every time with Newer version package details under dependency section. Till so far as per my observation apps seem to be working as expected in Manual testing, but not when published from SCCM. Thanks for your response i would be approaching once i have some more results.