[RESOLVED] project compiling with elevation shield when compiled in W10

i have a one form project, with some control arrays

creates an instance of IE, does some webscraping
allows user editing
rewrites the web page and ftp uploads it back to the website, using a shell object

no manifest or init commoncontrols, no API declares
does write one file to app.path, but the exe is portable and not installed to program files

can anyone see anything, that may be causing the executable to elevate to run as admin, when compiled on windows 10
or where to start looking

i made up some new do nothing project no shield appeared when compiled

maybe i need to copy the form one procedure at a time into a new procedure, and compile each addition

What is the name of the executable that is generated? I remember reading somewhere that certain words in an executable's name will trigger this (setup, install and similar).

orderform.exe \orderform2.exe

looks like you got it in one
saved mynew.exe, no shield

Experienced this too with a file with the string "updater" in the application name.
And it is an updater... But I replaced the word "updater" with "downloader" et voila, no more problems.

Of course just adding a manifest that declares your program's requestedExecutionLevel means these sorts of appcompat shims aren't applied. Hard to believe we're still talking about this a decade after it was introduced.