Skip to main content

Frame Agent 23-06-08 (Major Release)

Frame Server


  • Session performance and stability enhancements when using FRP8.

  • Max Video Bit Rate for FRP7 and FRP8 now supports up to 64 Mbps.

  • NVIDIA driver version is now added to logging.

  • Details on FRP version (FRP7 or FRP8) and transport protocol (UDP or TCP) to HKEY_CURRENT_USER\Environment\FRAME_SESSION_INFO registry key.

  • Optimizations to Signaling Server ( connections for FRP8.

  • App Mode 2.0 now supported with Windows 11 and Windows Server 2022 workload VMs.


  • Issue where fallback to CPU encoding fails when GPU encoding does not work.

  • Issue where ShellHandler.exe is generating high CPU usage.

  • Issue where FRP7 session may hang when closed via Session API.

  • Issue where Uploads and Download Now folders are not pinned within File Explorer in Windows 11 and Windows Server 2022.

  • Additional performance and reliability fixes.

Frame Guest Agent


  • [Early Access] Support for Azure Active Directory (AAD) and Hybrid (Classic AD + AAD) joined instances for the following deployment scenarios. Administrators can enable this feature on a per Account basis within Settings > Domain Settings.

    • Hybrid Azure AD joined devices are supported with all of our infrastructure offerings for the following operating systems:

      • Windows 10 + Windows 11 (excluding Home editions), Windows Server 2016, Windows Server 2019, or Windows Server 2022.
    • Azure AD joined devices are supported with the following infrastructure providers in the following configurations:

      • [BYO Azure IaaS]:
        • Windows 10 and 11 (excluding home editions).
        • Persistent and non-persistent Frame accounts are supported.
      • [AHV]:
        • Windows 10 and 11 (excluding home editions).
        • Persistent accounts only. Non-persistent AHV accounts are not supported.


    Newly created persistent desktops within Accounts deployed on AHV with AAD domain joined devices enabled will go through the Windows Out of Box Experience (OOBE). When the user enters their AAD credentials during the OOBE wizard, their session will disconnect and the user will need to reconnect. This is a known issue and will be fixed in a future release.


    Frame Enterprise Profiles are currently not supported with AAD joined instances.

  • Feature to automatically clean-up (delete) associated Computer Objects within the specified Active Directory OU for domain-joined Accounts when Frame VMs are terminated. By default, this feature is enabled for new Accounts and disabled for existing Accounts.

  • Auto update the Frame Agent Setup Tool (FAST) on Sandbox, Persistent Desktops, and Utility Servers upon VM start.

  • Support for UberAgent.

  • Additional logs for Enterprise Profile mount failures.


  • Issue where certain App Mode 2.0 configuration settings are improperly applied to Desktop Mode when Enterprise Profiles are enabled for an Account.
  • Additional reliability fixes.