Not able to connect to dev box

Nikita Kokitkar 0 Reputation points Microsoft Employee
2026-08-06T05:43:15.9466667+00:00

[Window Title]

Windows App

[Content]

We couldn't connect because there are currently no available resources. Try again later or contact tech support for help if this keeps happening.

[^] Hide details [OK]

[Footer]

For more tips on how to resolve the issue, refer to the Troubleshooting Guide

[Expanded Information]

Error code: 0x3000046

Extended error code: 0x0

Timestamp (UTC): 2026-08-06T05:41:11.1350867Z

Activity ID: 3900ba9d-7ae7-48ee-ad3b-826f441a0000

Press Ctrl+C to copy.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
0 comments No comments

1 answer

Sort by: Most helpful
  1. Daphne Huynh (WICLOUD CORPORATION) 985 Reputation points Microsoft External Staff Moderator
    2026-08-07T02:21:23.27+00:00

    Welcome to Microsoft Q&A!

    Thank you for sharing the detailed error information.

    Based on the error message: "We couldn't connect because there are currently no available resources", Error code: 0x3000046

    This typically indicates that the Dev Box service was unable to assign an available and healthy Dev Box resource for the connection request. Similar cases have been observed when a Dev Box is stuck in a Starting or Resuming state, or when the underlying resource is temporarily unavailable.  

    I would like to share the following recommended troubleshooting steps that may help you. 

    1. Verify the Dev Box state

    • Sign in to the Microsoft Dev Box portal: Microsoft Dev Box
    • Confirm that the assigned Dev Box is in a Running state and not Starting, Resuming, Stopped, or Failed.

    2. Try connecting from the Dev Box portal

    • Attempt to launch the Dev Box directly from devbox.microsoft.com.
    • It is a recommendation using the Dev Box portal when troubleshooting "no available resources" errors because it can help identify whether the issue is related to the Windows App client or the backend Dev Box resource.

    3. Run the Dev Box Troubleshoot option

    • In the Dev Box portal, select the affected Dev Box and run Troubleshoot if available.
    • Please notes that this process can help recover Dev Boxes that are hibernated or in an unhealthy state.

    4. Refresh the workspace

    • Sign out of Windows App.
    • Refresh or re-sync the workspace.
    • Reconnect to the Dev Box after the workspace has been refreshed.

    5. Check for broader service impact

    If multiple users are experiencing the same issue, review the applicable service health dashboard to determine whether there is an ongoing service-side issue affecting Dev Box availability.

    Notes: If the Dev Box shows Running but the connection continues to fail after performing the steps above, please open a support ticket and provide the Activity ID, timestamp, and Dev Box name. Similar cases have required backend investigation when the Dev Box or session host became stuck or unhealthy.

    If the answer is helpful, please click Accept Answer.

    Thank you for using Microsoft Q&A.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.