write protect

[klabautermann]

there is the possibility to setup the name changes to protect against?

[jassing]

You can name the setup.exe that you build to anything you want.
"to protect against..." What?

[klabautermann]

I want to create a setup and the name of setup.exe protected from change!
how and where you can adjust it?

[jassing]

that's not possible -- an administrator can rename just about any file that is not in use...
The closest you can come is to examine _SourceFilename and make sure it's named whatever you want, if not show a dialog/page "Sorry; file renamed, can't execute" and exit.

[klabautermann]

hmm,
my english is not so good but if I understood you correctly then you can arrange for a check to the name in the setup! right?

If so, then the question arises just how I should proceed because it has the xxx.exe is not running when they were renamed yyy.exe is!

Perhaps there's an example for me?

[jassing]

you can arrange for a check to the name in the setup! right?

Yes. Use _SourceFilename

has the xxx.exe is not running when they were renamed yyy.exe is!

and

Perhaps there's an example for me?

I think it's the other way around -- you need to provide us a small sample project to illustrate / replicate your issue.