AVD host pools getting sxs 1.0.2607.31750 this morning

The documented rollout behavior explains part of what is being seen:

• Azure Virtual Desktop SxS Network Stack updates are installed automatically.
• Rollout is progressive through flighting and can take several weeks.
• Some versions might not reach non-validation environments, so multiple SxS versions can appear across environments.
• The currently documented latest versions are Production: 1.0.2605.19825 and Validation: 1.0.2608.28350.

Based on that, seeing 1.0.2605.19825 alongside another SxS version is consistent with the documented rollout model, but the provided documentation does not list 1.0.2607.31750 as a current latest production version.

For the install/retry behavior and performance impact, the supported troubleshooting path in the documentation is to verify whether the stack is healthy and, if needed, reinstall the SxS stack:

1. Sign in to an affected session host VM as an administrator.
2. Open an elevated PowerShell prompt and run qwinsta.exe.
3. Check the rdp-sxs entry in the SESSIONNAME column.
4. Confirm the STATE column for both rdp-tcp and rdp-sxs is Listen.
   • If either entry is missing or not in Listen, that indicates a stack issue.
5. Stop the boot loader service:

      Stop-Service RDAgentBootLoader
   

6. In Control Panel > Programs > Programs and Features or Settings > Apps on Windows 11, uninstall the latest Remote Desktop Services SxS Network Stack version, or the version listed in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations under ReverseConnectionListener. Risk: uninstalling the stack affects AVD connectivity on that session host until reinstall and restart complete.
7. Back in PowerShell, locate the latest SxS installer already present on the VM:

      $sxsMsi = (Get-ChildItem "$env:SystemDrive\Program Files\Microsoft RDInfra\" | ? Name -like SxSStack*.msi | Sort-Object CreationTime -Descending | Select-Object -First 1).FullName
      $sxsMsi
   

8. Reinstall it:

      msiexec /i $sxsMsi
   

9. Restart the session host VM.
10. Run qwinsta.exe again and verify rdp-tcp and rdp-sxs both show Listen.
11. If they still do not show Listen, the documented next step is to re-register the VM and reinstall the agent component.

If the host status is showing Unavailable or Upgrading, that is specifically called out as a sign that the agent or stack did not install successfully.

• What's new in the Azure Virtual Desktop SxS Network Stack?
• Troubleshoot common Azure Virtual Desktop Agent issues