At that time I googled a bit and found the solution by reading couple of articles. Today again one of my colleagues faced the same issue and I was scratching my head to find out what was the solution. Again wasted around 30mins to find the solution. Finally it got working, but 30mins gone wasted on a problem for which I already searched and found solution in past. So just to avoid any such instance, as a note-to-myself, in this article I'll document the exact steps required to fix this issue
Reason for this issue is Android SDK Manager (by default) expects the AVDs to be in C:\Documents and Settings\<win_user>\.android (in case of win xp) directory when AVD is started. But when AVDs are created (by default) SDK Manager creates it under C:\WINNT\.android directory. Here <win_user> is the name of the user using which you have logged in to Windows PC.
To resolve this, one of the solutions is to create a symbolic link to C:\WINNT\.android directory. To do so, follow below mentioned steps
- Download Sysinternal's Junction utility.
- Create a symbolic link using below command
junction "C:\Documents and Settings\<win_user>\.android" C:\WINNT\.android
- Try starting your AVD now. It should start