Windows 365 Cloud PC became inaccessible a few hours after provisioning

Question

I'm trying to connect to my Windows 365, but it's become inaccessible.

After the cloud PC got provisioned (Enterprise), I was initially able to connect to it with browser, and also with boot from a physical device that's configured to boot into the cloud PC

A few hours later, without having touched anything, the PC has become completely inaccessible. Can't connect through:

• Browser remote connection
• Windows 365 app
• Physical device configured to boot into Cloud PC

I have restarted the Cloud PC via windows app, but still can't connect.

First it gives an error with correlation ID, and then when I retry, it disconnects me saying another connection was made, then when I retry it gives correlation ID error again, and so on. It alternates between those two errors.

Here's a video:

https://drive.proton.me/urls/WS3N5KJ518#cCHb5ebwLRyY

No other user has access to this PC other than me.

Answer 1

Hi Roozbeh Zareian,

Thank you for posting in the Microsoft Community Forums.

Check the network connection:

Ensure that your physical device and network connection are stable and that there are no firewall or proxy settings blocking access to Windows 365 services.

Try connecting to Windows 365 using another network or device to troubleshoot network issues.

Check the connection operation status:

Log in to the Microsoft Intune Management Center and navigate to Devices > Windows 365 > All Cloud PCs.

In the Overview > Performance (Preview) list, select a connection and view its status. If the status shows “Unavailable”, see the details on the right.

Troubleshoot using the Troubleshoot this Connection button for more information on connection issues.

Check the status of the cloud computer:

In the Microsoft Intune Management Center, check if the status of the cloud computer is “Running” or “Available”.

If the cloud PC status is abnormal, try restarting the cloud PC or contacting Microsoft support.

Check the physical device configuration:

If you are connecting from a physical device that is configured to boot to the cloud computer, ensure that the physical device is properly configured and has the required software version.

Check that the Windows 365 startup registry entries on the physical device are set up correctly.

Review the error logs:

Collect the error logs on the physical device and the cloud computer for more in-depth analysis.

Logs are usually located in C:\Users{username}\AppData\Local\Temp\DiagOutputDir\Windows365\Logs and C:\Users{username}\AppData\Local\Temp\DiagOutputDir. RdClientAutoTrace and other paths.

Best regards

Neuvi

Answer 2

After provisioning a Windows 365 Cloud PC, users encountered issues accessing the system just a few hours later. This unexpected inaccessibility could be linked to network, configuration, or system glitches, affecting productivity.