In this article, we will look at multiple solutions to fix Cloud PC session disconnect error code 0x3. When you are using the Windows 365 Cloud PC, the remote session gets disconnected and returns an error code 0x3. This can be resolved, and I will share the solutions for that.
There are multiple ways to access the Cloud PCs and connect to your Windows 365 Cloud PCs. When you connect to Cloud PC, a secure session is established between your computer and the Cloud PC hosted in Azure. However, sometimes your Cloud PC session may get disconnected, and you may end up seeing error code 0x3.
Recently, one of my customers reported issues with Cloud PCs disconnecting after regular intervals of time. When the users got back to their PC, they discovered error code 0x3, and they had to use the retry option to connect to the Cloud PC.
The screenshot below shows that message that appears after the Cloud PC session is disconnected. The remote desktop services session ended because the remote computer didn’t receive any input from you. Error code: 0x3. Extended error code: 0x3.
We see the Cloud PC session disconnected message along with error code 0x3 on Windows 365 app. The Retry option works for many users, which basically reconnects to your Cloud PC. If that doesn’t work, go to the next section for solutions.
Fix Cloud PC Session Disconnect Error Code 0x3
There are two main reasons why you encounter Windows 365 Cloud PC session disconnect error code 0x3.
- According to Microsoft, Error code: 0x3 can occur when the Cloud PC’s processor is over-utilized.
- You encounter Cloud PC disconnect error code 0x3 when you have configured the idle session time limits for your Cloud PCs.
Solution 1: Restart Cloud PC to resolve Error Code 0x3
When your Cloud PC session disconnects and shows error code 0x3, the recommended solution is to restart the Cloud PC. To accomplish that, sign in to windows365.microsoft.com > select the cog icon next to the Cloud PC > Restart.
Solution 2: Review Idle Session Limits for Cloud PCs
If you have configured the idle session limits for your Cloud PCs, there are chances that your Cloud PC may get disconnected after meeting the idle session time limit. To resolve this, go to Intune Admin center and navigate to Devices > Configuration profiles. Edit the policy and increase the idle session time limit.
Troubleshoot Error Code 0x3 for Cloud PCs using Event Viewer
Whenever you encounter disconnection errors such as error code 0x3 for Windows 365 Cloud PCs, the event viewer is the best option to troubleshoot the issues. I have covered about the troubleshooting connection errors for Windows 365 Cloud PCs in a separate article. The event viewer logs contain the event ID and the details of Cloud PC disconnection, which are important for troubleshooting.
To access the Cloud PC sessions logs in event viewer, launch the Event Viewer. Navigate to Microsoft\Windows\Terminal Services-LocalSessionManager\Operational. Here you will find the events about Cloud PC being connected, disconnected and other related events.
In this case, we see the Event ID 40 is created when the Cloud PC session is disconnected. We see the description as “Session 2 has been disconnected, reason code 3“.
The next event that we see is Event ID 24 and the details include “Remote Desktop Services: Session has been disconnected.”
After the user reconnects to the Cloud PC, we see the Event ID 25 indicating that “Remote Desktop Services: Session reconnection succeeded.” We also see the session ID in the General tab of the event properties.