Forum Discussion
MSIX app attach Azure portal integration public preview
I got the "No MSIX packages could be retrieved from the image path" error. Error type is "aap contains untrusted signature". I am trying to use the chome msix package provided. I can't do anything with the CRT certificate on github, it says invalid. Please advice Stefan Georgiev Thank you.
Anyone know why this is happening? UNC path is 110% correct... I made a adobereaderdc.vhd and its in the Azure File Share.
- Am getting the same with one app. I packaged it exactly the same way as I packaged notepadplusplus, but it won't have it - empty error as above. All logs from the WVD session host say it appeared to mount and scan the VHDX but I still end up with the above. No idea why as ofc it's all masked in the portal. Yet, I can Add-AppXPackage from the source MSIX fine. I generated the VHDX using MSIXMGR so what else can I do to diagnose...? 😞
- We gave up on MSIX App Attach because frankly, it's worthless right now. We know how to do it and make it work, but wasting time "packaging" stuff only to have it fail in most cases for other programs is a waste of effort. Until a vendor decides to utilize MSIX themselves there's little value. I have no use for attaching VLC and Notepad++ or other rinkydink programs that have little value if any in our production environment. I mean Microsoft doesn't even have their own product installers made into MSIX... Give me an Office Suite in MSIX and I'll be impressed.
- That's why I'd left off trying it for so long - it seemed like it wasn't ready. With it going into the portal, I assumed advances had been made and we had this app that was actually an ideal candidate. It's a shame I can't get any apparent indication why one app fails while another succeeds, when both have supposedly packaged correctly.
- Did you setup permissions for hte machine accounts?
- Does the computer account have smb reader access in iam (cant remember the excact name of the role)
Did you add the certificate to your session host?
Stefan Georgiev just released this troubleshooting methodology
https://github.com/stgeorgi/msixappattach/blob/master/Troubleshooting%20methedology%20v2.pdf
If above does not work, refer to Stefans PDF in the git link.Thogjo the issue was the .vhd -- in this case the AdobeReader package created by MSIX packager failed.
I then made one with Notepad++ and it worked! So the error I was getting is indicative of a bad .vhd/MSIX packaging.
I then immediately tried CPU-Z a super basic program, and it also failed just like Adobe Reader....
So I can only conclude at this point that this MSIX Packager is a total POS and its what is causing me headaches. If a basic program like CPU-Z can't be packaged and exported and attached then there is 0% hope right now a much more complex one will.
I'm going to give VLC player a try since that was one I saw in a demo video, but that doesn't do much for my progression to production WVD with this.
- DBR14 are you using the MSIX packaging tool to create an MSIX out of CPU-Z? Secondly, how are you creating the VHD, please try this tool https://techcommunity.microsoft.com/t5/windows-virtual-desktop/simplify-msix-image-creation-with-the-msixmgr-tool/td-p/2118585 to avoid badly structured VHDs.
Lastly we have a troubleshooting guide for MSIX app attach here you may find useful https://github.com/stgeorgi/msixappattach/blob/master/Troubleshooting%20methedology%20v2.pdf
- I have pointed that out numerous times earlier, but yes - you are correct
AADDS Is ‘no go’ with app attach
