Forum Discussion
App Attach only working if the App is Installed Locally First
- Apr 21, 2025
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
Let me help troubleshoot this like I would with a colleague! App Attach can be tricky, and I totally get the frustration when it's not working as expected.
From what you've described, you've got most of the basics covered - the packaging and conversion steps look good. But there are a few things that often trip people up with App Attach that we should check:
- Quick question - when you say it only works if installed locally first, what exactly happens when you try to launch the app without local installation? Do you get any specific error messages?
- One common gotcha: Have you checked if the certificate is properly deployed to ALL session hosts? Sometimes even if it shows up in the certificate stores, there might be permission issues or it might not be fully trusted.
- For the MSIX package itself - did you include all the necessary dependencies when packaging? Sometimes apps need additional frameworks or runtimes that aren't immediately obvious.
- Also, just to verify - I assume you've set up the share for the .CIM file and configured the proper permissions for the users who need to access it?
If you could provide some more details about what exactly happens when you try to launch the app without local installation, that would help narrow down where things might be going wrong.
Regards: https://블랙툰.store/
- JonahBaderJan 20, 2025Brass Contributor
Hi!
1. If the app is not installed locally, and I try to launch the app as a remote app (using the Windows App or the Remote Desktop app), I experience a frozen login screen, which never unfreezes. I attached a screenshot of it.
2. I have double checked that the certificate is installed in the directories I mentioned in the original post. But I am not ruling out the certificate as the possible issue. If other people have found issues related to their certificates, I would love to figure out how they found out or what they changed.
3. I'm currently testing with a super simple Windows Form app that just shows a text box. I was hoping to rule out a dependency-related issue but even this simple app has the issue. According to the AppManifest.xml, the only dependency is Windows.Desktop.
4. I am able to mount the fileshare using PSExec with no issues using this guide: https://learn.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-app-attach