White screen when multiple displays connected

Forum / NoMachine for Windows / White screen when multiple displays connected

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
  • #33702

    NoMachine was working fine with a single monitor. Since I connected two more displays to the server when I connect I only get a white window without any error messages. If I disconnect the extra monitors I can reach the desktop again.

    Server: Windows 10 with NoMachine 7.6.2

    Client: PopOS (Ubuntu) 20.10 with NoMachine 7.6.2

    I don’t need access to all displays on the remote machine, the main display would be enough for remote maintenance.

    Any advice would be appreciated.


    Hi ps75,

    This a known limitation and we have a Feature Request opened. Please take a look at this article  Displaying NoMachine on monitors beyond 4k.


    Hi Carin,

    Thank you for the quick reply.

    The implementation of this feature request: https://www.nomachine.com/FR05N03113, which permits to treat each monitor of a multi-monitor set-up as an invidual monitor, will also permit to noticeably increase the upper limit of maximum resolution supported.

    Does that mean, that even though I want to access only one monitor of the three on the remote machine, I can’t enforce that kind of behavior?


    I need to say yes, you cannot enforce that behavior as NoMachine would still send all displays until that feature is implemented.

    Despite this FR05N03113 – Creating a separate video stream for each monitor would be beneficial in your setup, I think what you really need is FR09Q03870 – Providing NoMachine Windows packages at 64bit
    since I think that your issue is due to an out of memory problem of 32bit application.

    On that regard, please can you tell about resolutions you are using on remote screen.


    I have 2x 4K and 1 FHD displays in the following configuration:
    – 2160 x 3840 (4K portrait)
    – 3840 x 2160 (4K landscape)
    – 1920 x 1080 (FHD landscape)


    Your used resolution are very likely related to the out of memory issue described in following FR – FR09Q03870 – Providing NoMachine Windows packages at 64bit.

Viewing 6 posts - 1 through 6 (of 6 total)

This topic was marked as solved, you can't post.