You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm trying to update my Local Jira Core to version 8.4.1., running on my Windows 10 PC. During the installation process I receive the following message: You do not have write permissions to the existing installation directory.
I'm however the administrator (and only user) of the PC on which I want to do the upgrade. I have all the rights and Windows doesn't prompt me for my administrator password anyway.
So I don't know how to proceed now.
The solution was not in the read + write permissions (that can be changed per file but not per directory, even not with all the methods suggestions), but appeared to be even easier: I had to run the installer as an administrator. Starting it as a user with administrator rights wasn't enough.
Running as an administrator (right mouse button) worked and the installation succeeded.
But thanks a lot for your support!
You need to check if you have read + write permissions on the Jira installation directory.
In a windows system, it is usually C:\Program Files\Atlassian
Many times, windows does not allow write permissions directly and you need to explicitly enable these permissions.
Just make sure that you have read + write permissions on the Jira installation directory and your issue should be resolved.
Thanks for your reply and I think you touch the core of the problem here, but I cannot solve it. In Windows the read-only attribute of folders / directories cannot be switched off.
The attribute can be disabled for all files in the folder (& subfolders), which I did. That should be sufficient, but the update installer still stops with the same error message. I'm afraid it is triggered by the read only-attribute of the Atlassian folder of Jira subfolder, although every file within these folder can be changed or deleted.