Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 0x3000048 | Event Viewer -> Windows Logs -> Application | -> Termsrv event ID 1306/20499 |
| Affected build range | Windows 11 23H2 | OS Build Information | |
| Registry key involved | HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppHost\RdpService | Registry Editor | -> Check for RDP settings |
| Relevant service/endpoint URL | https://rdweb.wvd.microsoft.com/api/oauth2/token | Network Monitor | -> OAuth token endpoint |
| Log line signature | Event ID 1306, Event ID 20499 | RemoteDesktopServices event log | |
Log Files to Check
C:\Windows\System32\winevt\Logs\Application.evtxC:\Windows\System32\winevt\Logs\Security.evtx
What This Error Actually Means
The error code 0x3000048 is a specific failure condition encountered when attempting to establish an Azure Virtual Desktop (AVD) session from a Windows 11 23H2 client machine. This error indicates that the remote desktop device or resource is busy, temporarily unavailable, or has hit capacity limits. The component raising this error is typically the Remote Desktop Protocol (RDP) service on the AVD host pool's session hosts.
This error can also be triggered by network issues such as blocked UDP port 3478 and TCP port 443 traffic due to Network Security Groups (NSGs). Additionally, it may arise from insufficient resources or misconfigured settings on the session host VMs within the AVD environment. The exact cause will depend on the specific circumstances of your deployment.
Affected Versions and Scope
This error is specifically observed in Windows 11 build 23H2 when attempting to connect to an Azure Virtual Desktop instance. It does not affect other versions or configurations that do not utilize AVD for remote desktop sessions. The issue is confined to environments where the RDP service is actively used and managed through Microsoft's cloud-based virtualization platform.
Where To Look First: Logs and Event IDs
To diagnose this error, start by examining the Application event log on both the client machine and session host VMs. The relevant log file path for the Application logs is
C:\Windows\System32\winevt\Logs\Application.evtx. You should look for entries with Event ID 1306 or 20499, which are specific to Remote Desktop Services (RDS) and indicate issues related to RDP connections.
Additionally, check the Security log file at
C:\Windows\System32\winevt\Logs\Security.evtx for any security-related events that might provide context about why the connection attempt failed. Use Event Viewer or PowerShell cmdlets like
Get-WinEvent -LogName "Application" | Where-Object { $_.Id -eq 1306 } to filter and review these logs efficiently.
Root Causes
Cause 1: Session Host Capacity Reached
This occurs when the session host VMs in your AVD environment have reached their maximum capacity for concurrent user sessions. To identify this cause, monitor the health of session hosts within the AVD host pool via the Azure portal or PowerShell cmdlets like
Get-AzWvdSessionHost -ResourceGroupName "MyRG" -Name "MyPool".
Cause 2: Network Security Group (NSG) Rules Blocking RDP Traffic
If your network configuration includes NSGs that block UDP port 3478 and TCP port 443, this can prevent the establishment of an AVD session. Use Azure CLI or PowerShell to inspect NSG rules with commands like
Get-AzNetworkSecurityGroup -Name "MyNSG" | Get-AzNetworkSecurityRuleConfig.
Cause 3: Misconfigured RDP Service Settings on Session Hosts
Incorrect settings in the registry can also lead to this error. Check the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppHost\RdpService for any misconfigurations that might be preventing proper RDP functionality.
Fix Procedure
- Check Session Host Health: Use the Azure portal or PowerShell cmdlets like
Get-AzWvdSessionHost -ResourceGroupName "MyRG" -Name "MyPool" to verify that session hosts are healthy and not at capacity.
Adjust NSG Rules:
Ensure UDP port 3478 and TCP port 443 are allowed through your NSGs. Use the Azure portal or PowerShell cmdlets like New-AzNetworkSecurityRuleConfig -Name "AllowRDP" -Description "Allows RDP traffic on UDP 3478/TCP 443" -Access Allow -Protocol Tcp/UDP -Direction Inbound -Priority 100 -SourceAddressPrefix Internet -SourcePortRange * -DestinationAddressPrefix VirtualNetwork -DestinationPortRange 3478,443.
Review RDP Service Settings:
Use Registry Editor to inspect and correct settings in the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppHost\RdpService. Ensure that all necessary services are enabled and configured correctly.
- Restart RDP Service: After making changes, restart the Remote Desktop Services service on session hosts to apply new settings. Use PowerShell cmdlets like
Restart-Service -Name TermService.
Error Code Variants
| Error Code | Description |
| 0x3000049 | The remote desktop device or resource is busy, but the issue might be due to a temporary network outage. |
| 0x3000050 | The session host has hit its capacity limit and cannot accept new connections. |
Verification
After implementing the fixes, verify that the issue is resolved by attempting to establish a connection again. Check for successful log entries in
C:\Windows\System32\winevt\Logs\Application.evtx. Additionally, ensure that session hosts are reporting healthy status via the Azure portal or PowerShell cmdlets like
Get-AzWvdSessionHost -ResourceGroupName "MyRG" -Name "MyPool".
Prevention
To prevent recurrence of this issue, implement a baseline configuration for your AVD environment that includes:
- Proper capacity planning and scaling mechanisms to ensure session hosts do not hit their limits.
- Network policies that allow necessary RDP traffic through NSGs without blocking UDP port 3478 or TCP port 443.
Additionally, use Intune/Entra policies to enforce consistent settings across all session hosts. For example, you can configure registry settings via OMA-URI
./Device/Vendor/MSFT/RemoteDesktop/RdpServiceSettings. Regularly monitor the health and capacity of your AVD environment using Azure Monitor or PowerShell cmdlets like
Get-AzWvdSessionHostUsageMetrics -ResourceGroupName "MyRG" -Name "MyPool".
By following these guidelines, you can effectively troubleshoot and prevent issues related to error code 0x3000048 in your Azure Virtual Desktop environment.