Mar 19 2021 08:54 AM
Hello,
I have setup a MSIX app in our WVD environment. But when I log in as the user that has access to the app it does not show up.
I created the MSIX with the MSIX packaging tool, used msixmgr to expand the app into a VHD file, successfully added this into the portal, and assigned a user to the application group.
I installed the certificate on the VM into the Trusted People store, and have confirmed that it is there.
Am I missing anything?
Regards
Sean Buckle
Mar 23 2021 12:17 AM
Mar 24 2021 02:08 AM
Mar 24 2021 11:47 PM
Mar 25 2021 02:10 AM
Mar 29 2021 03:57 AM
Mar 29 2021 06:28 AM
Mar 29 2021 07:31 AM
Jun 23 2023 11:02 AM
guys any update on this problem
i see explorer also opening up in my case
plz can someone help
Sep 23 2023 04:51 PM
Also running into the same issue.
Environment is Windows Server 2019.
Installed MSIX dependency of WindowsAppRuntime 1.2
MSIX was freshly built from a sample .NET Maui application and then MSIXMGR to vhd/x type.
Issue occurs with both vhd and vhdx formats. Haven't gotten cim type to successfully attach in AVD Portal.
Same thing--app appears in the AVD console but on launch it just open file explorer.
Sep 23 2023 08:51 PM
@jatinkumar Another update
I used a different VM. This time Azure hosted Windows 11 and made a CIM out of the msix file.
Same result.
I wonder what we're missing...
Dec 13 2023 12:02 PM
Same here, when an app is freshly deployed. This behavior will persist until I restart the session host (VM). Once the VM is restarted, the app launches successfully.
The following log entry from the Event Viewer seems to be related to the issue, since it closely matches every failed attempt:
AppAttachProcessParser.HandleProcessStart Exception occured while retrieving process file path, using process name instead: System.ComponentModel.Win32Exception (0x80004005): Access is denied
at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.NtProcessManager.GetFirstModuleInfo(Int32 processId)
at System.Diagnostics.Process.get_MainModule()
at Microsoft.RDInfra.RDAgent.EtwReader.AppAttachProcessParser.HandleProcessStart(TraceEvent data) in C:\__w\1\s\src\RDAgent\src\ETWReader\ETWProcessors\AppAttachProcessParser.cs:line 267