View Single Post
Old 21st June 2022, 12:30   #42
Junior Member
Join Date: Jun 2022
Posts: 29
It has a remnant manifest still. I don't know why.

PHP Code:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
    <assemblyIdentity version=""
    <description>Nullsoft Install System v3.08</description>
            <assemblyIdentity type="win32"
I doubt the manifest matters. The results are interesting.

I did:
PHP Code:
ManifestDPIAware notset
RequestExecutionLevel none
XPStyle off
#ManifestSupportedOS all ; (commented out) 
WIN 11:
HTML Code:
Installer - result=1 get=PROCESS_SYSTEM_DPI_AWARE sysdpi=120 aware=1
Uninstaller - result=1 get=0 sysdpi=96 aware=0
test ($exedir\UnTest.exe) - result=1 get=PROCESS_SYSTEM_DPI_AWARE sysdpi=120 aware=1
Generating "Untest.exe" overrides the usual uninstaller built at runtime. It was three separate tests, actually.

a) instdir/bin/uninst.exe
b) exedir/UnTest.exe

Yes, an interesting result indeed. "Untest.exe" as the proxy uninstaller is DPI-aware. Who would have thought that?

This was the third test:

c) instdir/bin/UnTest.exe

WIN 11:
HTML Code:
test - result=1 get=PROCESS_SYSTEM_DPI_AWARE sysdpi=120 aware=1
Does this mean something in my uninstaller triggers "aware=0"?

It was a good test to do. I was about to give up. 'Thank you!'

The DPI issue remains current for the moment. Windows 10 and Windows 11 treat the uninstallers differently. In my "uninst.exe" there may be a problem with certain Exe files that are sometimes flagged as dangerous by Defender. They are not dangerous, but could that be an issue?
rgreen is offline   Reply With Quote