Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I selected the "Start SDK Manager" icon in VS 2013 and attempted to update the Android SDK. This failed, though, saying “A folder failed to be moved. On Windows this typically means android sdk manager...").
I then closed and restarted VS2013 / Xamarin. Subsequent attempts to open the SDK manager just result in an err msg ("Command did not execute successfully due to an unexpected exception. Please check the output window for additional information"). Here are the "More Details":
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at Mono.VisualStudio.Extension.ProcessWrapper.RunWithOutput(String executable, Int32 waitTime, String workingDir, IVsOutputWindowPane outputPane, String arguments)
at Mono.Android.VisualStudio.Commands.StartSdkManager.Execute(IMenuCommand command)
at Mono.VisualStudio.Extension.TracingExtensions.ShieldUI(ITracer tracer, Action action, String format, String args)
ALSO: Trying to build the project fails, with: "Warning 1 All projects referencing HHS_CorePCL.csproj must install nuget package Microsoft.Bcl.Build. For more information, see http://go.microsoft.com/fwlink/?LinkID=317569. HHSMobile.Android" ("HHS_CorePCL" is the name of my Portable Class Library project in this solution).
I have checked this issue but unable to reproduce it . I have attempted on VS2012 and VS2013 both to update SDK Manager and it installed successfully.
Screenshot regarding SDK update on VS2012
Screenshot regarding SDK update on VS2013
Microsoft Visual Studio Professional 2013
Version 12.0.21005.1 REL
Microsoft .NET Framework
Xamarin.Android 4.12.02001 (a1e3982a)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 1.10.47 (3d6a125d)
Visual Studio extension to enable development for Xamarin.iOS
Please let me know ,If I miss anything to reproduce this issue.
I have just come across the exact same scenario using Visual Studio 2013 Premium.
This morning I needed to add Google Maps support to a project I'm working on. Following instructions on the Xamarin web site, I opened the Android SDK Manager and selected to install the Google Play Services API. The installation failed half-way with the exact same error as reported above.
Now, when trying to open the Android SDK Manager I get the following error:
Command did not execute successfully due to an unexpected exception. Please check the ouput window for additional information.
The output window has no information at all.
My Android projects do still build.
VS 2013 Premium version: 4.5.51654
Xamarin version: 220.127.116.11
Xamarin.Android version: 18.104.22.168
I also have Xamarin.iOS installed
Issue remains exactly as described by: B. Clay Shannon 2014-03-27 15:21:18 EDT
I was running VS 2012 Ultimate and attempting to update Android SDK.
This looks like it may be a virus protection issue (AVG, in my case) that causes a corruption in the Xamarin install. Reinstalling Xamarin fixes damage. Upon then downloading Android SDK update the second time AVG threw an error on the same folder name allowing me to ALLOW this exception. Android SDK download proceeds normally.
I'll mark the bug as resolved answered.
Please feel free to reopen it if you can still see an issue with current bits.