Follow up on existing Support Request: Blue Screen after NET RC Installed

Hi Carol Bender,

Thank you for reaching out. Based on the details you provided, your VM is experiencing RDP failures due to the SxSStackListenerCheck error. This check ensures the VM’s Side-by-Side (SxS) network stack is functioning, which is required for Windows App RDP connections. When the listener fails, RDP sessions cannot establish, and the VM appears unavailable in the Azure Portal.

In your case, the issue may have been triggered by the installation and removal of .NET 10 RC, which can leave the SxS stack in an inconsistent state. Additionally, Microsoft documentation indicate that running an unsupported OS SKU is another common cause for SxSStackListenerCheck failures.

Could you please follow below recommendation steps:

• Confirm whether the VM is unable to boot entirely or if the issue is specifically with RDP access. If the VM cannot boot, please check the Boot Diagnostics logs in the Azure portal under the Help option for your VM.
• If you can access the VM, for example through the Serial Console, verify the following registry keys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations Ensure fReverseConnectMode and fEnableWinStation are both set to 1, which are required for RDP functionality.

Reference: Operating systems and licenses

• Verify Registry Settings (if VM accessible via Serial Console)

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations Ensure fReverseConnectMode and fEnableWinStation are both set to 1, which are required for RDP functionality.

Troubleshoot issues with the Azure Virtual Desktop side-by-side stack

• Manual OS Disk Repair

1. Take a snapshot of the VM’s OS disk to preserve data.
2. Create a disk from this snapshot and attach it as a data disk to a healthy "repair" VM.
3. Run chkdsk /f and DISM commands on the attached disk to fix any file corruption.

Reference: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/troubleshoot-recovery-disks-portal-windows

• Azure VM Repair Feature:

Alternatively, use Azure's automated VM Repair tool to snapshot, repair, and restore the OS disk, streamlining disk recovery tasks.

Reference: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/repair-windows-vm-using-azure-virtual-machine-repair-commands

• Ensure the Azure VM agent is running and healthy, as a ‘Not Ready’ status or failing extensions can impact VM health and connectivity.

Reference: https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/troubleshoot

Hope this helps! If issue persists, could you please provide below details

Did the blue screen issue begin right after installing .NET RC, or did it happen after you uninstalled it?

1. Have you tried reinstalling .NET Framework 4.8 or .NET 6/7 runtimes after the crash?
2. When you say the VM is unusable, do you mean you can't boot, can't establish RDP connections, or is it a different problem?
3. Are you able to access the VM via the Serial Console?
4. Have you checked the Boot Diagnostics logs in the Azure Portal?
5. Is the Azure VM Agent showing any errors or in a ‘Not Ready’ state?
6. Have you recently attempted to restart or redeploy the VM?

Thanks,
Manish Deshpande.

Hello Carol Bender,

I wanted to check if my last response made sense. I’d be glad to assist further or explain anything in more detail and please accept as Yes and upvote if the answer is helpful so that it can help others in the community.