Forum Discussion
App Attach only working if the App is Installed Locally First
This has finally been recognized by Microsoft.
Tracking ID: 5KN6-9_G
Service Issue: Azure Virtual Desktop errors with CIMFS files on Windows 11, version 24H2
Here's an important update:
It seems I can resolve this issue by using a VHDX disk instead of CIM. I followed the exact same process/setup for the two types, I just changed the format when using MSIXMGR. I can launch the remote app with no issues, and I confirmed that the app is NOT installed locally.
No clue why the CIM format would be the issue here. Any suggestions?
... And Microsoft is finally aware of the issue. See Azure Service Issue 5KN6-9_G.
Service: Windows Virtual Desktop
Region: Southeast Asia, East US, West US 2, South Africa West, West US 3, Canada Central, UK South, Global, South India, North Central US, West India, Jio India West, Central US, Japan West, Australia Southeast, Central India, East US 2 EUAP, East Asia, Canada East, West US, South Africa North, West Europe, East US 2, Japan East, Korea South, Brazil South, UK West, West Central US, South Central US, North Europe, Australia East, Korea Central
Impact Statement: You have been identified as a customer using Azure Virtual Desktop who may experience errors when attempting to use the app attach feature with a CIMFS file type starting on 01 October 2024. This is currently only impacting customers who operate on or upgrade to Windows 11, version 24H2.
Workaround: Our team has identified the ability to repackage the app attach application using a different file type (VHD or VHDX) or downgrading to a different version of Windows as a possible workaround.
Current Status: We detected this issue via receiving bug reports from customers who have experienced the application error. We are aware of this issue and are actively working on processing a fix for the bug, to be provided in an upcoming Windows update. We will provide an update by 10 April 2025, or as events warrant.