Forum Discussion
WVD Environment not picking up MSIX App Attach
guys any update on this problem
i see explorer also opening up in my case
plz can someone help
- cws-apellegrinoSep 23, 2023Copper Contributor
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...
- JeffRobichaudDec 13, 2023Copper Contributor
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
- cws-apellegrinoSep 23, 2023Copper Contributor
Also running into the same issue.
Environment is Windows Server 2019.
Installed MSIX dependency of WindowsAppRuntime 1.2MSIX 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.