> > Yes, I had exactly the same problem last night, with no apparent other > > running program blocking the folder renaming. In the end I just quit > > Eclipse and deleted the particular 1.6 r1 folder manually in Explorer > > (Windows 7 64-bit), after which the update ran without problems. > > (Before that, the update had failed both with the "$ android" method > > and when launching Android SDK and AVD Manager from Eclipse | > > Windows.) I've solved the same thing in the same way. The message about disabling your anti-virus software is somewhat misleading. In desperation I moved the 1.6 r1 folder to another location on my disk - and not in the same sub directory tree either. The install of 1.r r2 then succeeded.
Now I have a 1.6 emulated device and this shows up in the SDK / AVD manager. Once I'd done the platform move, there was a big red X against the 1.6 device. My guess is that it is the SDK/AVD manager that has a lock on the 1.6 folder.... David Blythman -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
