* Does your emule system tray icon sometimes no longer work?
* Does emule crash?
* Does Explorer show low resolution icons, bitmaps or blurry text?
* You can live with a single manually set DPI for all your screens?
Then this will solve not only Emule.exe but many other software in Microsoft Windows 10 as from every release upto 24th of may 2017. You can find more information in the public beta test section of emule how this solution eventually came. It is possible that you might have came here for other software that behaves strangely at anothe High DPI other than 100% or systray Icons or blurry text, bitmaps, icons.
-----------------------------------------------
I found out what the problem in any current build is for Windows 10 and change of DPI%.
Microsoft offers for example standard values like 150%, or in my case the last standard value of 175% and on 4k Displays Microsoft should offer standard value 200%.
As soon as one uses these Microsoft suggested standard values problems arise. Now this is because at these standard values people can have multiple screens eacht with their own DPI%.
However, the solution to all problems is not to choose a value that Microsoft offers but to manually enter your own High DPI% number value, even if it is 150% (but ignoring microsoft offering to do it.)
So one must not choose Microsoft standard values, one can pick any value upto 500% but a person must manually enter the number like I did with 149% manually, and manually 150% works too, but Microsoft suggested 150% does not work.
Scenario's tested when using Microsoft standard High DPI suggested or manually override High DPI, rebooted after every change of DPI%, crashed en restarted explorer.exe, played games that change resolution. And the conclusion at the end.
DPI=150%, microsoft recommended, emule in systray works fine when killing explorer.exe and restart explorer.exe and nicely pops up back.
After playing a game emule is still in the systray and one can show emule.exe with it, but emule can no longer minimize to systray
Killing explorer.exe and restart explorer.exe fixes this systray issue.
[FAILED]
DPI=175%, microsoft recommended, emule in systray works fine when killing explorer.exe and restart explorer.exe and nicely pops up back.
After playing a game emule is still in the systray and one can show emule.exe with it, but emule can no longer minimize to systray
Killing explorer.exe and restart explorer.exe fixes this systray issue.
[FAILED]
DPI=175%, microsoft does not recommend it, MANUALLY override, all displays get 175% DPI, every procedure fine.
[SUCCESS]
DPI=200%, microsoft recommended, see 175% microsoft recommended and 150% microsoft recommended
[FAILED]
DPI=150%, microsoft does not recommend it, MANUALLY override, all displays get 150% DPI, every procedure fine.
[SUCCESS]
DPI=200%, microsoft does not recommend it, MANUALLY override, all displays get 200% DPI, every procedure fine.
[SUCCESS]
-----------------------------------------------------------------
Conclusion, the standard High DPI% that Microsoft offers must be manually overridden, even if it is the same High DPI% which is very ironic.
I can now use 150% DPI since I do not use the Microsoft recommended 150% DPI but I override it with a manually 150% DPI.
One must manually simply override suggested Microsoft values and I can not use it for example.
This is PERFECT since I now have a beautiful DPI% although I must enter the 150 value manually and force it and DO NOT USE MICROSOFT RECOMMENDED DPI%
In the future Microsoft will work this out eventually, but all my screens have the same resolution and same DPI%.
*) Note, a MANUALLY override DPI is at the same location as the Microsoft suggested DPI, always use MANUALLY override it always works. But your screens all will have the same DPI that is the price.
Now this fixes everything. Again Microsoft its bugs not the user. User trusts a Microsof suggested value like I did, and that caused all the bugs which only become visible like after playing games or playing an emulator of the C64 at a 320x240 screen resolution change for example.
These bugs show up only when every step is repeated, if you never do game or never play an emulator that changes display resolution you would never see this bug in Microsoft Windows 10 DPI scaling.
Original Thread See Page 14,15 how conclusion is that it is not Emule.exe fault, but Windows Explorer.exe that only Microsoft can fix is faulty.
https://forum.emule-...howtopic=159790
This post has been edited by MMouse: 24 May 2017 - 04:50 PM