While updating Android Studio I got the following error. The patch was downloaded and extracted, but there was some conflict with jre/bin/java Access denied. The error message is shown in the below screenshot.

The Error message is as shown in the linked image:
(Click image to enlarge)

| improve this question | | | | |
  • I think you download the patch using private network, try to change public network and downloaded it again so that the server can trust your id. – abu-ahmed al-khatiri Oct 24 '18 at 9:58
  • I have this issue too. I installed Android Studio under /opt/android-studio chowned as root. When I update I run sudo su and then /opt/android-studio/bin/studio.sh. – dcow Nov 3 '18 at 19:20
  • Anyone find a solution to this? I have Android Studio installed in my home folder and I still got this error. – authentictech Apr 22 '19 at 16:50
  • 1
    It actually worked for me the second time. I'll leave this comment to let people know that Android Studio update process might just be a bit fickle. – authentictech Apr 22 '19 at 17:11
  • 1
    @authentictech Same for me. I just closed all programs included Android Studio. Then when started Android Studio and I was prompted again to update, everything worked, no errors. I didn't change any permission or kill any process or restart my system. I'm using ubuntu 18.04. I'll leave this comment for same reason, to let people know that Android Studio update process might just be a bit fickle. – cesargastonec Feb 24 at 20:32

11 Answers 11


Kill java for update

ps -A |grep java

output of this command will give the list of java processes running on your system. Note down Process ID (PID) of that process whom you want to kill and run

kill -9 PID

| improve this answer | | | | |
  • 1
    Nice, I thought no java was running, but I was using ps -a instead of ps -A. – Marek Lisý Feb 9 '19 at 15:44
  • 1
    I use ps aux | grep java, and in between all the java processes someone may have, the only one to be killed to perform this upgrade is the gradle daemon, which is specified by "org.gradle.launcher.daemon.bootstrap.GradleDaemon" – Alessio May 3 '19 at 6:28
  • how does this fix anything?? you could just click "Cancel" too, but neither will complete the update. Or am I missing something? – oliversisson Jul 20 '19 at 10:45
  • 3
    Ah, I see. The steps I took were: (1) close Android Studio (2) kill all java processes with kill -9 (3) run Android Studio with studio and update – oliversisson Jul 20 '19 at 11:06
  • thanks you saved my day – Mohammad Sommakia Aug 24 '19 at 1:38

What I found worked for me is with Android Studio running (before initiating the update patch download) I did ps -ef|grep jre on the command line and saw there were 2 jre process running, the one for Android Studio and one of which was for the Gradle daemon which was also using the jre shipped inside Android Studio. The Gradle daemon process will have something like this: gradle-5.3.1/lib/gradle-launcher-5.3.1.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 5.3.1

towards the end of its command line when you list processes with ps though of course the specific version you have may not be 5.3.1.

Killing the Gradle process and then starting the update download and then restart from inside Android Studio let the update proceed successfully.

| improve this answer | | | | |
  • 2
    The only thing that worked for me. I killed the java process (Gradle) before installing the upgrade. Another solution is to hit the update notification as soon as you see it. Doing it so the AS will not have time to instantiate Gradle and the upgrade will be finished successfully. – Alexander Haroldo da Rocha Aug 26 '19 at 12:58
  • 1
    This worked for me – Aeiman Bakeer Nov 28 '19 at 16:38
  • 1
    This answer worked for me, the "Kill java for update" answer did not. This was updating Android Studio 3.1 to 3.5. – tonylo Jan 9 at 17:05

Those answer above does not work for me. I'm about to upgrading to android studio 3.5 and I met this issue.

Kill the java process just make the upgrade terminated and then android studio restarted with the old version.

My work around is remove the old android-studio directory and download a new one from website and place it exactly where the old one is.

Hope it helps someone!

| improve this answer | | | | |

Java process can respawn after kill due to gradle build. The easiest way is to close the project (File -> Close project).

Now that you are back in the Select project menu, you are sure that no gradle is running.

Go to configure at the bottom right and update Android Studio.

| improve this answer | | | | |
  • Only method that worked for me. – Christian Mar 5 at 7:51

I had the same problem when I tried to update Android Studio installed by JetBrains Toolbox app. In this case, the update should be done via Toolbox, not from IDE.

| improve this answer | | | | |

Try uninstalling dart and flutter plugins and then reinstalling the dart and flutter plugins it works for me.

| improve this answer | | | | |
  • 4
    Can you please write a fuller explanation? Give example commands that a new user could follow to resolve the issue. – Tom Brossman Oct 27 '18 at 10:18
  • This is not neccesary to uninstalling dart and flutter plugins, disable these plugins also work. – Nikhil Aug 30 '19 at 12:55

None of the answers above solved the problem for me. What I managed to do is to change the default jdk from the project structure.

Before you update Go to File -> Project Structure-> SDK Location. Then change the location to OpenJDK or Oracle JDK that you should have already installed in your machine. After that, update your android studio and every thing should be alright (Hopefully ... you how Google treats developers ;) )

| improve this answer | | | | |

It is very simple problem.

Thing that you will have to do is - go to the java named file in android installation folder (may be in /opt/android_studio/jre/jre/bin/java or [the folder you extracted the android tar file to]/jre/jre/bin/java) and set permission - read and write.

Now you can update again.

| improve this answer | | | | |
  • type -p java in terminal will show path to java. Or locate java will show all files with java in name. – LeonidMew Mar 14 '19 at 21:25
  • this should work, but it did not for me. Finally i tried the jetbrains toolbox app way and worked – Val Martinez Oct 20 '19 at 12:23

I got this to work by closing the current project I had (this happened to be a flutter/dart project) I then made a new project and found a really extremely basic template. I was then able to upgrade. whatever project I had open before was locking up that directory.

| improve this answer | | | | |

For me this problem got fixed by following steps:

  1. change the path of java in the current project. (File -> Project Structure-> SDK Location)
  2. Close the current project.
  3. Restarted the machine (since multiple unsuccessful attempts in had done so thought of restarting).

Next time when i launched studio, it did not opened any project (since i had closed in the previous session). Now from Configure options i updated, and it worked successfully.

| improve this answer | | | | |

I also got the same problem when updating from android studio 3.5 to 3.6. It was resolved after closing project from file menu and then updating from configure > check for updates.

| improve this answer | | | | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.