Recently when I tried to update Android SDK to latest version i.e 2.2, API 8, revision 2 from eclipse, I got a warning on the lines below
Failed to rename directory
-= Warning ! =-
A folder failed to be renamed or moved. On Windows this typically means that a program is using that folder (for example Windows Explorer.) Please close all running programs that may be locking the directory.
Many people have reported this error and though there are various solutions (like renaming the tools folder under <Android_Installation_Path>\android-sdk-windows\tools and update from that folder etc), there is no single solution that fixed this bug.
Ther bug is also reported in the code.google.com
http://code.google.com/p/android/issues/detail?id=4410#makechanges
The core issue is indeed somebody else locked the tools folder. So I tried the following solution and it worked like charm
- Close Eclipse and close all instances of windows explorer in which the <Android_Installation_Path>\android-sdk-windows\tools folder was opened
- Now run the AVD Manager independently as follows
- Open a command prompt.
- Go to the directory where android sdk is installed at, and then its tools subdirectory.
- Run Android.bat.
- At this point, update just as you would if you were running the AVD Manager from within Eclipse (make sure the proxy settings are mentioned if you are behind the proxy).
You should be able to update the Android SDK now.
Dec 08, 2010 @ 14:30:00
Thanks, you. I finally got this working.
Feb 09, 2011 @ 01:09:38
really helpful , thanks a lot
Oct 20, 2011 @ 19:05:19
I had another problem. An Android device was connected to the pc, so adb was running.. has to disconnect it. It seems logical, but i never thought that was the problem…
Nov 05, 2011 @ 17:33:44
thanks!
Nov 11, 2011 @ 17:57:37
+1 for this, worked great going from version 14 to 15.
Nov 22, 2011 @ 23:15:39
This didn’t work for me.
Install Android Marketplace and Google Apps on Amazon Kindle Fire | Esotech Inc.
Jan 08, 2012 @ 03:31:35
Feb 07, 2012 @ 08:52:09
Running Eclipse with administrator privileges takes care of this error when updating the SDK.
Mar 04, 2012 @ 05:38:40
gracias amigo!