Share via

Windows App v2.0.804.0 (msrdc.exe) consumes 9–13GB virtual memory and causes system freeze

Zach Yang 0 Reputation points
2025-11-21T07:09:35.26+00:00

Product: Windows App for Windows (v2.0.804.0 64bit version/32bit version )
OS: Win11 Pro 24H2
Hardware: CPU Intel Pentium Gold G7400T, Memory: 8GB DDR4

Issue:

  • While streaming Windows 365 (Cloud PC), msrdc.exe virtual memory increases up to 9–13 GB.
  • This causes system lag / black screen.
  • GPU shared memory usage rises sharply.
  • Windows Event Log shows “Resource-Exhaustion-Detector”.
    User's image Troubleshooting already attempted:
    • Reset / reinstalled the app. not working
    • Using the 32bit version, the Resource-Exhaustion-Detector error was gone. But the streaming will keep on black screening
  • Temporary method: Use previous version of Windows App (2.0.633.0). and the issue seems to be good now Hi Microsoft Support, can you give me one update or suggestion about the issue I mentioned.

Moved from Microsoft 365 and Office | Other

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Zach Yang 0 Reputation points
    2025-11-21T07:20:40.4266667+00:00

    Besides that, is it possible that the Windows 365 side caused this issue? like some rendering settings or decoding settings?

    0 comments
  2. Ivy Bui (WICLOUD CORPORATION) 165 Reputation points Microsoft External Staff Moderator
    2025-11-28T09:01:00.7966667+00:00

    Hello Zach Yang, I am Ivy

    Thank you for sharing the details and logs regarding the Windows App (v2.0.804.0) issue where msrdc.exe consumes excessive virtual memory (9–13 GB) during Windows 365 Cloud PC streaming, causing system lag and black screens.

    We’ve reviewed your observations and troubleshooting steps. Here are our recommendations:

    1. Stay on Known Stable Version

    • Continue using Windows App v2.0.633.0 as a temporary workaround until a fix is released.

    2. Collect Diagnostic Data

    • Use Performance Monitor (PerfMon) to capture (5 mins):
      • Process(msrdc)\Private Bytes
      • Process(msrdc)\Working Set
      • Memory\Committed Bytes
      • Process(msrdc)\Handle Count, plus GPU Adapter Memory/Dedicated Usage (if available), and Memory\Committed Bytes.
    • Capture during:
      • Baseline (idle)
      • Spike (when memory reaches 9–13 GB)
      • Post workload (after streaming stops)
    • Export logs (CSV) and share with us for deeper analysis.

    3. Update Components

    • Ensure:
      • Windows App is at the latest stable version.
      • WebView2 Runtime and GPU drivers are updated.
      • Windows 11 patches are applied.

    4. Optimize Settings

    • Temporarily disable multi-monitor and high-DPI scaling in Windows App settings.
      • Use single display mode to reduce rendering overhead.

    5. Run Built-in Diagnostics

    • In Windows App, go to Settings → Inspect Connection → Troubleshoot and share the report.

    Next Steps

    Please:

    • Collect PerfMon logs as outlined.
    • Confirm if reverting to v2.0.633.0 resolves the issue consistently.
    • Share diagnostic outputs for escalation to the Windows App engineering team.

    I hope this help you. If you have any question, please feel free to ask.

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.