Strange Windows 2025 Server GUI issues

Karel Hruska 20 Reputation points
2026-05-26T08:03:06.4533333+00:00

Hi all,
we are running Windows 2025 Server on our ASUS RS700A-E12-RS4U equipped with nVidia A4000 graphics card and we experience strange GUI issues while using remote desktop connection. Currently we have experienced following:

  • in ANSYS Fluent the GUI exhibits strange artifacts after some time of usage, while using the software with artifacts shown it leads in program crash in some cases
  • in MS Word the GUI partially disapperars - the ribbon gets black while the sheet is still visible
  • in some cases the whole scrfeen gets covered by a pink web (?)

Detailed hardware configuration:
2x CPU AMD Epyc 9274F (24-core, 4,05GHz)
1024 GiB RAM DDR5 ECC reg 4800MHz (16 x 64 GiB modules)
1x NVMe SSD 3,84 TiB, Gen.4 (DWPD 1)
LAN 10GbE SFP+, Dual Port (+ transievery) + 5m LC-LC
1x GPU Nvidia RTX A4000, SingleSlot, PCI-E

Software & Drivers:
Windows 2025 Server
MS Office 2021 LTSC
ANSYS 2026 R1
nVidia Drivers 595.97
option "Use the hardware default graphics adapter for all Remote Desktop Services sessions" is Enabled

Does anybody have an idea how to fix it?

Thank you!
Karel

Windows for business | Windows Server | User experience | Remote desktop services and terminal services
0 comments No comments

4 answers

Sort by: Most helpful
  1. Daphne Huynh (WICLOUD CORPORATION) 660 Reputation points Microsoft External Staff Moderator
    2026-05-27T03:06:47.0333333+00:00

    Welcome to Microsoft Q&A Forum! 

    Based on your scenario, the issue is very likely related to GPU rendering behavior over RDP, especially when using NVIDIA A4000 with hardware acceleration enabled.

    Your symptoms are consistent with known RDP graphics issues:

    • ANSYS Fluent shows rendering artifacts and may crash
    • Microsoft Word ribbon turns black while content remains visible
    • Entire screen occasionally becomes pink or corrupted

    These are typical signs of RDP rendering pipeline instability with GPU acceleration.

    This behavior usually occurs due to how RDP handles graphics:

    • By default, RDP uses a software renderer (Microsoft Basic Render Driver) for stability
    • Enabling “Use the hardware default graphics adapter for all RDS sessions” forces RDP to use the physical GPU, which can introduce instability depending on drivers and workload
    • Pink artifacts, black UI, and screen corruption can occur specifically in RDP sessions with NVIDIA GPUs
    • The issues are typically driver or rendering pipeline related, not application-specific

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

    1. Rule out networking issues

    Test RDP to localhost from the server console

    • If the issue disappears, likely network/RDP transport-related
    • If it persists, problem is local to server (GPU / driver / RDS)

    2. Graphics driver and application acceleration

    • Ensure NVIDIA driver is stable (not just latest)
    • Test with hardware acceleration disabled inside applications such as ANSYS Fluent and Microsoft Word (disable hardware graphics acceleration)

    Many UI corruption issues only appear when applications use GPU acceleration over RDP

    3. RDP graphics pipeline

    You currently have “Use the hardware default graphics adapter” Enabled. This is a key trigger. Please test by disabling it.

    Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Remote Session Environment → Use hardware graphics adapters for all RDS sessions (Disabled)

    This is a known workaround for RDP artifact issues. If artifacts disappear, root cause can be GPU + RDP rendering path

    4. Windows and application updates

    Ensure:

    • Windows Server 2025 is fully patched
    • Office and ANSYS versions are updated

    Some RDP and graphics issues are resolved by cumulative updates / hotfixes

    5. RDP listener / session reset

    • Recreate the RDP listener (if misconfigured)
    • Restart Remote Desktop Services and Display-related services

    Incorrect session configuration can affect rendering.

    6. Clean boot / third-party interference

    Perform a clean boot

    • Disable all non-Microsoft services
    • Test without antivirus or third-party monitoring tools

    Third-party components (especially AV or GPU utilities) can interfere with RDP graphics.

    7. Application-specific considerations

    ANSYS Fluent:

    • Requires GPU/OpenGL (may not behave reliably over RDP)
    • Check vendor guidance for remote usage scenarios

    Microsoft Office:

    • Known to show black UI issues with GPU acceleration
    • Disabling hardware acceleration is a common workaround

    8. Additional RDP factors to validate

    • Try different NVIDIA driver versions (not only the latest)
    • Clear RDP cache: C:\Users<user>\AppData\Local\Microsoft\Terminal Server Client\Cache

    Corrupted bitmap cache can also cause visual artifacts and rendering issues.

    I hope this information is helpful and thank you for choosing Microsoft Q&A to raise your concern.

    Was this answer helpful?


  2. Karel Hruska 20 Reputation points
    2026-05-26T08:20:22.77+00:00

    Here are the screenshots (please do not delete, they are anonymised and published with permission):

    ANSYS Fluent:ANSYS_Fluent_v2

    ANSYS_Fluent

    MS Excel:

    MS_Word

    Remote Desktop:

    Desktop

    Was this answer helpful?

    0 comments No comments

  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. AI answer

    2026-05-26T08:03:27.1133333+00:00

    The described symptoms match known Remote Desktop graphics issues where hardware GPUs and specific drivers cause rendering artifacts, black UI regions, or full-screen corruption in RDP sessions.

    From the available information, the only directly relevant and supported guidance is:

    1. For WPF/.NET applications on systems with NVIDIA GPUs, Microsoft documents that RDP display issues can be caused by the NVIDIA driver or multiple NVIDIA GPUs. The documented workarounds are:
      • Uninstall the NVIDIA drivers from the computer.
      • Remove one of the NVIDIA graphics cards from the computer (if multiple are present).
      • Migrate affected WPF applications from .NET Framework 3.5 to .NET Framework 4.
      While the scenario here is Windows Server 2025 and different applications, this shows that NVIDIA drivers and GPU configuration can directly cause RDP-side rendering problems and that removing or changing the NVIDIA driver stack is a validated mitigation.
    2. Remote Desktop graphics and black-screen issues in other Windows versions are resolved by applying specific cumulative updates. For those versions, Microsoft’s guidance is to ensure the OS is fully updated with the relevant KBs to fix RDP display problems.

    Given only the supported guidance in the context, the actionable steps that align with documented mitigations are:

    1. Validate that Windows Server 2025 is fully updated with the latest cumulative/security updates, as RDP graphics issues in other versions have been fixed via servicing.
    2. Test whether the issue reproduces after removing or disabling the NVIDIA driver stack:
      • Temporarily uninstall the NVIDIA display driver and use the in-box Microsoft Basic Display Adapter to see if RDP artifacts disappear.
      • If multiple GPUs or GPU paths are present, test with only a single active NVIDIA adapter.
    3. If any affected application uses WPF on .NET Framework 3.5, migrate it to .NET Framework 4 or later, as this is a documented workaround for RDP display corruption with NVIDIA GPUs.

    If removing or changing the NVIDIA driver eliminates the artifacts in RDP, the next step is to work with NVIDIA for a server-certified driver version for Windows Server 2025 that does not exhibit these issues.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was 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.