LoadGen Studio is not launching Microsoft Remote Desktop Client (MSRDC)

If you observe that MSRDC launches outside of LoadGen Studio successfully, but fails (briefly flashes and then exits) when started from LoadGen Studio, the cause likely lies within the interaction between LoadGen’s automation hooks and MSRDC—rather than the RDP file or command line itself.

One frequent scenario:

• You remove a subscription from the MSRDC client.
• You attempt a test session from LoadGen Studio.
• A password prompt appears for the test-user, even though everything works when Studio is closed and you run the same msrdc command line manually.

Checks & Workarounds

Residual MSRDC Processes

• Reproduce the error within Studio.
• Open Task Manager → Details → look for msrdc.exe.
• Or run PowerShell:Get-Process msrdc -IncludeUserName
• If an msrdc.exe process is still running (even hidden) when Studio triggers a session, kill it (right-click → End Task) then retry from Studio.
• If MSRDC launches normally, the leftover process was causing the conflict.

Version & installation type

• Identify whether you are using the MSI-based MSRDC or the Microsoft Store version.
• Note the exact version number (for example: 1.2.6676.0 (MSI)).
• Some interactions only occur with the Store version due to sandboxing or update mechanisms.

Event Log entries

• On Studio machine, open Event Viewer → Applications and Services Logs → Microsoft → Windows → RemoteDesktopServices-RdpCoreTS and/or TerminalServices-ClientActiveXCore.
• Seek entries at the time when MSRDC process starts and exits.
• Provide Event IDs, message codes and timestamps — these help diagnose if MSRDC crashed or was blocked by security.

Automation / Hook conflict

• Studio uses agents/hooks to hook windows/controls for automation.
• If MSRDC client was updated or its UI changed, the hook may fail.
• Try launching MSRDC from Studio with minimal automation (e.g., disable validations) to isolate.

Credentials, SSO or Subscription interference

• Verify the test user’s login flow: no interactive subscription prompts, no Windows Hello or smart-card pop-ups.
• For AVD workloads, you must use a FAT-Client profile (local session) when prepping test agents. support.loadgen.com
• Ensure no residual SSO or subscription for the user client remains in the workflow.

Integration with variables & LoadGen Workload

In the referenced AVD preparation Flow, several variables are used:

• Azure_Username,
• Azure_Password,
• Azure_AppId,
• Azure_TenantId,
• WVD_ClassicMode,
• WVD_ResourceName

Read more about preparing your Azure Virtual Desktop test infrastructure in this article.