VMware Horizon Community
vmit11
Contributor
Contributor
Jump to solution

App volumes failing to attach on Win 11

Win11 22H2, App Volumes 2303.1
I have created an application for Win 11 but when it attaches at login it immediately detaches. For example, right after I login I can see the shortcut for the application but then it gets removed. If I view disk management, I do not see the VHD attached.

I have tested the same application by attaching it to a windows 10 machine and it works fine.

Any ideas why windows 11 would have an issue?

Tags (2)
Reply
0 Kudos
1 Solution

Accepted Solutions
vmit11
Contributor
Contributor
Jump to solution

After reading the release notes, I have found out that this is a known issue when using vTPM with instant clones, which is required for windows 11.

 

  • Application packages and Writable Volumes cannot be attached to instant-clone desktop pools which have the Add vTPM Device to VMs option selected in the Horizon console. [AVM-31057]

    For more information about the Add vTPM Device to VMs option, see the Windows Desktops and Applications in Horizon 8 documentation.

    For more information about the Virtual Trusted Platform Module (vTPM), see the vSphere Virtual Machine Administration documentation.

    Workaround: Follow the instructions as mentioned in this knowledge base article.

View solution in original post

Reply
0 Kudos
1 Reply
vmit11
Contributor
Contributor
Jump to solution

After reading the release notes, I have found out that this is a known issue when using vTPM with instant clones, which is required for windows 11.

 

  • Application packages and Writable Volumes cannot be attached to instant-clone desktop pools which have the Add vTPM Device to VMs option selected in the Horizon console. [AVM-31057]

    For more information about the Add vTPM Device to VMs option, see the Windows Desktops and Applications in Horizon 8 documentation.

    For more information about the Virtual Trusted Platform Module (vTPM), see the vSphere Virtual Machine Administration documentation.

    Workaround: Follow the instructions as mentioned in this knowledge base article.

Reply
0 Kudos