When I run any freepascal program that I compiled on my windows 10 desktop computer on any other PC, I always get a warning:

We could not verify who created this file, are you sure you want to run this file?

When I search for a way to fix this, I get a bunch of results telling how to bypass the windows protection and let the file run without the warning, but I don't see any results on how to actually properly take care of this, so the program actually CAN be properly verified and run without the warning and without modifying the windows installation.

Does anyone know how this is normally achieved, and how to implement this with my freepascal console applications?

James

Are you by chance running it from a shared smb folder or something like that? I run all my fpc apps on Windows 10, but from a local drive and don't get warnings.

On Jun 28, 2017 11:56 AM, "James Richters"
wrote:

When I run any freepascal program that I compiled on my windows 10 desktop computer on any other PC, I always get a warning:

We could not verify who created this file, are you sure you want to run this file?

When I search for a way to fix this, I get a bunch of results telling how to bypass the windows protection and let the file run without the warning, but I don’t see any results on how to actually properly take care of this, so the program actually CAN be properly verified and run without the warning and without modifying the windows installation.

Does anyone know how this is normally achieved, and how to implement this with my freepascal console applications?

James

Hi,

James Richters wrote

Does anyone know how this is normally achieved, and how to implement this with my freepascal console applications?

I'm not a Windows developer, but You have to code sign your executable, probably, just like any normal Windows app you'd release. Does this Stackoverflow link provide any help?

https://stackoverflow.com/questions/252226/signing-a-windows-exe-file

Charlie

Are you by chance running it from a shared smb folder or something like that?

Yes I am running them on a network share… If I copy the file to my laptop hard drive then I don’t get the warning anymore. However I still get the secutiy warning if the program is downloaded, even if I download it to the original development pc.

I'm not a Windows developer, but You have to code sign your executable, probably, just like any normal Windows app you'd release. Does this Stackoverflow link provide any help? https://stackoverflow.com/questions/252226/signing-a-windows-exe-file

Thank you for the link, that does help explain things and gets me pointed in the right direction.

James

Am 28.06.2017 20:32 schrieb "James Richters" <

: >Are you by chance running it from a shared smb folder or something like

that?

Yes I am running them on a network share… If I copy the file to my laptop

hard drive then I don’t get the warning anymore. However I still get the secutiy warning if the program is downloaded, even if I download it to the original development pc.

To run programs without annoying prompt from a network share you need to change the security settings on the computer you want to run the application on (it's the same in Windows 7 by the way):
- open "Internet Options"
- go to tab "Security"
- select category "Local Intranet"
- click button "Sites"
- uncheck "automatically determine Intranet"
- check the other three checkboxes (or at least the one about network paths)
- confirm all dialogs

The dialog that occurs when you download a program is also controlled somewhere, but it's cause is an alternate datastream that gets attached to the downloaded file. I don't know right now whether signing the execuable makes a difference here aside from the dialog looking less warning like...

Regards,
Sven

Sven Barth wrote

- open "Internet Options"

The wording on these option pages seem to indicate that they are for websites. That is all they talk about.

What about local files on the computer which are not part of any website?

They are not only about websites, but also files in the local intranet (e.g. network shares in your network or even local network shares)

What about local files on the computer which are not part of any website?

*shrugs* Those settings are somewhere else. Most likely local security policy...

Regards,
Sven