Android Studio Update stuck cleaning up?

Question

I just downloaded and installed Android Studio 0.8. When I ran it, I received a notice that there was an update. I immediately downloaded the patch and it auto-ran. After patching, the dialog titled "Update" appears to be stuck with the following prompt:

Updating Android Studio (build 135.1245622) to Android Studio (build.135.1248636)

(progress bar animation)

Cleaning Up

If I click on the Cancel button, I get a new Yes/No dialog box saying:

The patch has not been applied yet.

Are you sure you want to abort the operation?

How can I fix this problem?

Running on Windows 8.1 JDK version 1.8.0_05

Answer 1

I've also experienced this with the latest updates (0.8.1 - 0.8.4), both in Windows 7 and Windows 8.1, but there's actually nothing wrong.

The "Cleaning Up" part takes an amazingly long time (literally, several minutes), but it finishes OK. You just need to wait. :)

Very surprising for what would seem to be such a small update (at least judging from the downloaded file size).

Answer 2

It took an hour for the "cleaning up..." step to finish on my Windows 8 machine. For whoever still has this problem, I don't know if it's a coincidence, but it finished 1 minute after I closed all my other open applications (e.g. browser).

Answer 3

I had the same issue while updating to version 0.8.2 The update froze at the 'cleaning up' screen. It was very late, so I let it run while I watched tv and fell asleep. Next morning I started my computer and the update screen was still there :O So I found this forum and did everything you guys said, but nothing seemed to work for me. I cancelled the update and got a Java IOException. It said that the update couldn't delete files and or folders inside the Temp folder of the LocalAppdata dir (C:\Users[UserName]\AppData\Local\Temp). I logged out and logged in again and started Android Studio. Everything ran fine and the update was succesfully applied.

So if someone experiences this too and the update freezes for longer than 1 hour, you can try to abort it, log out and log in again. And maybe it works again.