I have a spimple request, since the beginning of Windows 8 more and more applications (compiled) need the feature to be DPI-Aware.

In Powershell Studio 2017 (act. Version) the predefined Manifest-Files from you set the DPI-Awareness only to "System-Aware" which results in the bad behavior for Windows 10, that you have to restart the application or have to logout and back onto Windows.... that is really bad.
To fix this behavior you just have to change your Mainfest-Line to:

You can define your own manifest at any time when packaging. It would help if you could define "bad behavior" (maybe with a screenshot) so we can try to replicate what you see and evalute possible options.

Attached is a screenshot of the problem.
You can see there, it's the Powershellstudio Manifest: "Embed a default manifest for elevation"
If you compile the script and make an *.exe File and open that with notepad++ you can see, that the dpi state is: <dpiAware>true</dpiaware>.
That only means, that the application is "System Aware" - You have to logout and login (Windows) to perform scaling.

But if you copy all that manifest content and change the line of dpiAware to "true/pm" it's per Monitor aware, so the scaling works just on the flow, you don't have to worry about anything.

Using a customManifest has the worse thing, that I need to worry about the Version etc.