Quote Originally Posted by ErosOlmi View Post
I think part of the problem is that the .EXE is downloaded from a web page.
And I think it is the same if the .EXE comes from a mail or a .ZIP inside a mail.

If the .EXE comes from a Setup, it should be ok.
I will make some tests in the week-end.
Eros,

I'm certain that is not the case for a couple reasons. The main one is that when I built the bundle, I just ran it locally - never uploaded it to GitHub - and it immediately produced the UAC. I do agree with you that Windows SmartScreen (Windows 8/10) will keep track of applications downloaded from websites and present different (Not UAC) warnings to users based on if the app is deemed unsafe or not.

One thing I'm curious about is in the ThinBasic_Bundle_UI window, Version Info tab, there is a "Application Key:" Field. Where does that number come from? Is it generated randomly each time you bundle, or is it generated once for each unique .tbasic source file? I wonder if Windows tracks application permissions by that Application Key or something in some way.

Have you been able to create a bundle from the .tbasic source code? Did it give you the UAC window when you ran the exe?

Thanks so much for looking into this - I know this isn't the most important thing for TB, so don't stress about finding an answer. It's more of just a support thing - people running the program will ask me why the UAC comes up, and if I can get it to go away they won't ever ask why it's there. :-)

*Brian