Bug 31744 - "Open Android SDK Manager" should ask for elevation if VS is running non-elevated
Summary: "Open Android SDK Manager" should ask for elevation if VS is running non-elev...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 3.11 (C5)
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Ian Ceicys
Depends on:
Reported: 2015-07-08 08:26 UTC by vga
Modified: 2015-08-17 16:25 UTC (History)
6 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description vga 2015-07-08 08:26:00 UTC
VS 2015 Setup is installing the Android SDK Manager into %ProgramFiles(x86)%. This means that installing a new Android SDK manager will require elevation. If the user is running VS non-elevated we need to force the launching of the Android SDK Manager as an elevated process so it won't fail for the user later on when he tries to install a new SDK version.
Comment 2 Ian Ceicys 2015-07-14 13:04:47 UTC
Verified Fixed with VS 2015 (23020) build and XVS Build 3.11.762
Comment 3 Jon Goldberger [MSFT] 2015-08-17 16:25:29 UTC
It looks like we might have to do the same thing for Xamarin Studio. New bug report filed: #33176