Windows App for macOS 11.4.2 renders published RemoteApps as transparent/black/frozen windows on external monitors

Selena Kunsman 30 Reputation points
2026-09-25T13:15:41.89+00:00

Since updating the Microsoft Windows App for macOS to version 11.4.2, our users have been unable to use published RemoteApp connections on external displays.

Environment:

  • Client: Windows App for macOS, version 11.4.2 (confirmed to work correctly on version 11.3.3 and 11.4.1)

Connection Type: RemoteApp (published application, not a full desktop)

Server: Windows Server with Remote Desktop Services

  • macOS Version: 14.5 sonoma and later (not tested on golden gate)

Symptom: When launching a published RemoteApp (not a full desktop session) and attempting to use it on an external monitor, the session window becomes completely transparent, or sometimes black, and freezes. If it's transparent, only the macOS window control buttons (close, minimize, full-screen) are visible over a blank/transparent area. Otherwise, when launching sometimes there seems to be 2 windows of the same app running. When I move either to an external monitor, it freezes and some of it turns black.

Troubleshooting already performed:

Confirmed on multiple Macs — the issue affects all macOS users, not just one machine.

  1. Version isolation — reverting to Windows App 11.3.3 and 11.4.1 resolves the issue entirely.
  2. Web client works — connecting via the Chrome web client works perfectly with no display issues for the same app.

Single instance confirmed — using Task Manager inside the session shows only one instance of the application running, so the "duplicate windows" that appear are a rendering artifact, not actual duplicate processes.

  1. macOS settings — "Displays have separate Spaces" is enabled in Mission Control. Toggling Stage Manager has no effect.

Workaround: Users are currently using the web client, which bypasses the issue entirely.

Question: Is this a known regression in the macOS Windows App for RemoteApp connections? Are there any client-side settings that can force the app to render correctly on a secondary display? Since updating the Microsoft Windows App for macOS to version 11.4.2, our users have been unable to use published RemoteApp connections on external displays.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop clients
0 comments
Answer accepted by question author and recommended by moderator
Fredrik Wenngren 80 Reputation points
2026-09-28T13:20:01.9233333+00:00

In our case Windows App-version 11.4.2 was also the cause, thanks for showing this here. Rolling back users to 11.4.1 solved all issues for all OSX-users.

Was this answer helpful?

3 people found this answer helpful.
0 comments

1 additional answer

Sort by: Newest
Most helpful Newest Oldest
  1. Allan Solomon Mejia 10,225 Reputation points
    2026-09-25T13:45:40.71+00:00

    Hi @Selena Kunsman

    Your version isolation is significant: the issue occurs with Windows App 11.4.2, while 11.3.3/11.4.1 and the web client work correctly with the same RemoteApp.

    Microsoft's release notes show that Windows App 11.4.2 (3104) was released September 17, 2026, but they currently don't document a RemoteApp/external-monitor rendering regression in that release.

    Microsoft's current Windows App known-issues page also doesn't list this specific transparent/black/frozen RemoteApp behavior on macOS.

    Given that multiple Macs reproduce it, 11.3.3/11.4.1 work,11.4.2 fails, the web client works, and the server-side application continues running, the evidence strongly isolates the behavior to Windows App 11.4.2's macOS client/rendering path, rather than the published RemoteApp itself. This is an inference from your controlled testing, not a currently documented Microsoft known issue.

    I cannot find verified Microsoft documentation for a client-side setting that specifically corrects this 11.4.2 RemoteApp rendering behavior.

    For now, keep using the working web client or the previously working Windows App version, and report the regression to Microsoft with the 11.4.2 build number, macOS version, external-display configuration, and reproduction steps.

    Microsoft documents the available macOS display settings, including how multiple displays interact with Displays have separate Spaces, but since you've already confirmed that setting is enabled and earlier Windows App versions work with the same configuration, I wouldn't treat that as the root cause here.

    References:

    What's new in Windows App

    Known issues and limitations of Windows App

    Configure display settings in Windows App

    Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.

    Was this answer helpful?

    3 people found this answer helpful.

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.