After my Visual Studio Installation suddenly lost the ability to deploy my Xamarin application for the Android emulator , I decided to uninstall EVERYTHING (Visual Studio, Xamarin, Android SDK) and start over.
Everything was reinstalled, but the Android SDK does not contain the adb.exe file. The place where I expect to find it is here:
C: \ Users \ costcopc \ AppData \ Local \ Android \ Android-SDK \ platform tools \ adb.exe
Something went wrong? How can i fix this?
I opened the cmd.exe prompt and searched the entire drive (C:>) to find the file - it does not exist.
Track my steps again
In case this helps, I will return to my steps ...
Delete
I did not install Xamarin first, as instructed . I need a clean slate, so in accordance with these instructions I also deleted:
I did not remove the Java SDK because, as my first link explained, I already used the system restore point to restore the stable version of the Java SDK.
Next up was Visual Studio. I used its installer to remove it, and then I post-uninstalled the “Additional installer” instructions that it gave.
Reinstall
First, I installed VS 2015 again, then I ran the Xamarin Studio installer, which in turn installed the Android SDK for me:

When everything seemed to be installed successfully, I started Visual Studio and tried to open the Android SDK Manager using the tools → Android → Android SDK Manager.
This worked, but I noticed that the cmd.exe window opened and remained open, it contained some strange error messages.

Here it is: "The process cannot access the file because it is being used by another process."
Despite the anomalies, I used the SDK manager to install 4 more packages.
However, I felt awkward in the error messages, so I decided it was time for a reboot. After the reboot, the situation worsened. Previously, Visual Studio, at least, could run the Android SDK manager. Now he could not start it at all:

This odd SDK path has disappeared!
Xamarin Studio also failed to start the SDK manager:

Now I decided to do a “repair” of Xamarin Studio. Xamarin acted like the Android SDK was installed, and so he did nothing to fix it.
Again, what can I do to fix this?