A DESCRIPTION OF THE PROBLEM :
While the issue has been patched for Java 17 and Java 21, unfortunately the patch (and no other workaround) has been applied to Java 25. Therefore, Java 25 is still broken and shows the same erroneous behavior as Java 17 and 21 did before they were "revert patched". Consequently, Java 25 cannot be safely used currently for projects involving AWT/Swing applications being executed on Windows using a RDP session.

The last comment from C. Langer on https://bugs.openjdk.org/browse/JDK-8348625 mentions that there were plans to introduce a workaround flag into the Java 25 codebase to avoid this bug, but this flag has not yet been implemented. This prevents us and our customers from updating to Java 25 and locks us to the fixed Java 21.

Is there any plan to fix the bug or provide the mentioned workaround in Java 25 and future Java versions, or do we have to manually patch the AWT DLLs in the Java 25 JDK we use (as well as in all future JDKs), so that the "IsValidMonitor" procedure in "Devices.cpp" also returns "TRUE" for the situations where it currently incorrectly returns "FALSE"?

REGRESSION : Last worked in version 21.0.9