A DESCRIPTION OF THE PROBLEM :
When i try to add the parameter -Dsun.java2d.dpiaware=false to a certain java process, this do nothing, because the java manifest have a configuration which is overlaying to that.

Activity

Yes, Microsoft recommended the manifest entry for Windows 7.
-Dsun.java2d.dpiaware=false is not a supported setting.
We may end up removing the manifest entry for JDK 9 as it doesn't play well
with per-monitor dpi-awareness in windows 8.1

Philip Race
added a comment - 2015-05-12 15:29 Yes, Microsoft recommended the manifest entry for Windows 7.
-Dsun.java2d.dpiaware=false is not a supported setting.
We may end up removing the manifest entry for JDK 9 as it doesn't play well
with per-monitor dpi-awareness in windows 8.1

I believe that we need to leave the dpiAvare=true option in the manifest file for JDK 9 because JDK 9 is the DPI aware application. It reads DPI settings from the OS system and scales the whole app accordingly to it.

Alexander Scherbatiy (Inactive)
added a comment - 2016-05-27 14:26 I believe that we need to leave the dpiAvare=true option in the manifest file for JDK 9 because JDK 9 is the DPI aware application. It reads DPI settings from the OS system and scales the whole app accordingly to it.

The Rampdown phase start [1] milestone is approaching, it means we are not targeting "9" to fix P4s anymore, unless the fix is ready and not risky, safe enough not introduce P2-P3 regressions; if this is a case you can retarget back to "9" right before the push the reviewed code.
[1] http://openjdk.java.net/projects/jdk8/milestones#Rampdown_start

Victor Dyakov
added a comment - 2016-08-29 13:01 The Rampdown phase start [1] milestone is approaching, it means we are not targeting "9" to fix P4s anymore, unless the fix is ready and not risky, safe enough not introduce P2-P3 regressions; if this is a case you can retarget back to "9" right before the push the reviewed code.
[1] http://openjdk.java.net/projects/jdk8/milestones#Rampdown_start