I downloaded Greenshot v1.1.6 and wanted to install it on 64bit Win7 in a directory
which already EXISTS.
Unfortunately Greenshot does not like this and tells the user:
"Setup was unable to create the directory
Error 5: Access is denied
Greenshot should allow (as 99,9% of all other programs as well) to be installed in an EXISTING directory.
This should be easy to implement
Yes, this should work... in fact for me it does, it's something Innosetup (what created our installer) should handle without any problems.
Due to the access denied, I would actually assume you can't write to this directory?
I CAN write to this directory. But it seems to me that GS tries to create an already existing dir which is not possible.
GS should check at first if dir exists and only if it NOT exist create it.
As the installer is not written by us, and used in a lot of products it would have been funny if such a simple task wouldn't work. So before I replied the first time I did a few tests, which showed that installing in an existing directory works.
This doesn't mean I am saying it should work in your case, it just must be something else.
The error you see comes from the fact that the installer can't write to the directory, that is what access denied says.
Even if you can write there that doesn't mean that every process you start can! Since Windows 7 they are run with less rights (standard user token) except if they request admin rights (full administrator token). For Greenshot we decided against requesting Admin rights this as this makes it only possible to install Greenshot when someone has or knows an account that has these rights. e.g. I can install Greenshot at work, although not in program files, even though I can't install most other applications.
To install in directories where only an admin can write, you need to start the installer with right-click and select the "run as administrator" from the context menu.
Maybe you are admin, and only admins can write in your directory. This would explain the error, and the solution would be to run the installer as admin.
I know also cases where people modified (disabled) the User Access Control (UAC) behavior of Windows, this causes some weird issues with access rights. Maybe you disabled UAC?
I have full adminstration rights and full write permissions. Maybe there is another issue (blank in path name, underscore in pathname, Too long path name,...)
Anyway meanwhile I switched to NO-Installer zip version.
So the problem is not relevant any more - for me.
Can confirm. When trying to update on Windows 8.1 x64, installer somehow broke permissions on the installation folder (folder owner was uknown, I had no permissions to view it even as adminstrator).
Deleted the folder manually after which the (re)installation proceeded sucessfuly.