TOPIC:

Hello,

I had problems debugging an application with XIDE.
The strange thing is that the application requires elevated rights to run when the assembly file name contains the word "upda", but it does not require them, when the contained word is "upd" alone.
For example: using the assembly file name "bnUpdTester" it works normally, with the filename "bnUpdaTester" it requires elevated rights.
Wolfgang
P.S. I'm using Windows 10 1809 and XIDE

Hi Wolfgang,

I remember that apps with update or setup in their name are automatically handled as updates that need elevated rights.
In your app name is this the case 'bnUPDATEster'.

Stefan

Hi Wolfgang,

found the link:
docs.microsoft.com/en-us/previous-versio...detection-technology

Stefan

Hi Stefan,

thank you very much! Initially my application filename was bnUpdateTester... so I wondered why it requested elevated rights. I knew something like this with the word "setup" and "install", but didn't knew until today that also "update" triggered this detection.
Anyway, I'm more happy than ever to have changed the update process of my applications to the download of a zip file from the internet and an internal extraction (all from inside of the application).
Wolfgang

This is the reason why XIDE install files are named for example XIDE_Set_up_1.17.exe and not XIDE_Setup_1.17.exe

I will ask Microsoft immediately that they should also include set_up as a keyword for higher rights (I had also similar problems. I remember that for one program also the manifest contents triggered the higher rights)

In the last years Windows became kinder with our programs whereas some antivirus programs got more aggressive deleting our exe files. And this because of behavior driven controls and not because of signatures. Create and delete many temporary files and immediately the antivirus program starts looking at you...

Arne

Yeah, to me it looks like that antiviruses have became the real viruses lately..

About namings, can still use S_e_t_u_p, SE7up, Set-up etc, they will never win this battle! But I will stop giving you more names to report in advance

It is possible to switch off this strange behavior by including the following code into the manifest file of the exe:
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>

ArneOrtlinghaus wrote: It is possible to switch off this strange behavior by including the following code into the manifest file of the exe:
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>

Thanks for the info Arne!

Hi Arne,
thank you very much! This is interesting.
Wolfgang