Issue with MOVE Local Files on windows 7 x64

[tzachk]

Hi Support,

During my repair/upgrade process I need to copy the configuration files to a temporary folder and after the repair/upgrade completes, move the configuration files back overwriting the newely created ones.
Everything is working OK, I'm able to copy aside, reboot, repair and move back the files overwriting the new ones (I use NATIVE_OVERWRITE with ALWAYS and NATIVE_OVERWRITE_OLDER with TRUE just for moving and overwriting the old configurations files).

My application starts successfully after the repair/upgrade completes.
The only issue I've noticed is that the old configuration files moved back from the %TEMP% dir, now have a lock icon (I'm using windows 7 64 bit) appearing on the file icon (like the locked folder lock icon). I can access the configuration files just fine, but it seems that something did change that needs attention.

Anything?

Regards,
T.

[FrancescoT]

Dear Tzachk,

seems that your file inherit your folder settings and very probably it is quite regular on Win 7.

Let me see if am able to find more info about.

Regards

[tzachk]

Hi Francesco,

I've tried to manually replicate it.
I copied the files aside to the %TEMP% and then moved back overwriting the exisiting files.
The files moved, overwrited the exisiting ones, but I didn't get the lock icon and the permissions didn't change.
Checking the security permissions on the files moved with the installer, I've noticed that the files with the lock icon changed permissions.

Checking the %TEMP% folder permissions I see that these are the new permissions the files got.
To summary:
- If I use the installer to copy files from installdir to %TEMP% and then move back to installdir, the files retain permissions they got from the %TEMP% folder.
- If I copy myslef the files from installdir to %TEMP% and then move back to installdir, the files receives back the permission of the installdir.

In my case the files lost the Users group permissions, and only because I was a local administrator I continued to work fine, because this permission was not lost.

I wonder if the flags I used has something to do with this problem. I'll check.

Regards,
T.

[tzachk]

Hi Francesco.

The flags do not have any effect.
However I found a workaround. I create a temp folder under the $TARGETDIR$ and thus the permissions do not change during the copy/move procedures.
I don't like the workaround because I think temp operations should be done on folder located under the TEMPDIR, but it is working.

i.e. of course I need to delete the temp folder under $TARGETDIR$ at the end of the move if I want the uninstaller to remove the $TARGETDIR$ folder.

Regards,
Tzach.

[FrancescoT]

Dear Tzach,

as alternative, you could use "Set Access Control" command to give access to Everyone to that file.

Regards.

[tzachk]

Hi Francesco,

Granting everyone permission control is not good. Your'e breaking the ACL.
I consider the current behaviour of MOVE local files as a bug, and think you should fix it as it is not the way that the operating system acts.

Regards,
T.

[FrancescoT]

Dear Tzach,

... if you can provide me a very sample project that replicate the issue I will check it.
I'm not quite sure that exist a bug ... but probably I'm wrong.

Regards.

[tzachk]

Hi Francesco,

very easy to replicate.
- Create a folder under program files and put some files in it.
- Create an InstallAware project in which you copy the files to $TEMPDIR$
- Delete the original files in the folder you created under program files
- Move the files from TEMPDIR to the folder you created under program files.

You'll notice that the moved files retained the permissions they got in TEMPDIR.
This is not usuall windows behavior, and is a bug.
If you do the same manually, the files shall get the program files permissions.

Regards,
T.

[FrancescoT]

Dear Tzach,

I will try to replicate the issue ... but if you have a sample that demostrates the issue ... this will speed up my job.

Regards