Bug 33134 - Xamarin Android Player not able to intall the Devices
Summary: Xamarin Android Player not able to intall the Devices
Status: RESOLVED DUPLICATE of bug 30212
Alias: None
Product: Xamarin Android Player
Classification: Xamarin
Component: Player ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-08-15 06:48 UTC by SAQLAIN RAZA
Modified: 2015-08-17 07:07 UTC (History)
2 users (show)

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


Attachments
Xamarin Android Player Error (48.86 KB, image/png)
2015-08-15 06:48 UTC, SAQLAIN RAZA
Details


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 or GitHub 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:
Status:
RESOLVED DUPLICATE of bug 30212

Description SAQLAIN RAZA 2015-08-15 06:48:08 UTC
Created attachment 12525 [details]
Xamarin Android Player Error

Hi,
     Xamarin Android Studio is not able to install the Devices. After taking very long to download the Device at the End it gives Error. Recently, i have just Update the Windows Operating system from Windows 7(64 bit) to Windows 10.
I have attached the error with this email which is in image form. Please solve the issue and send me reply.



Thanks.
Comment 1 Mark Simpson 2015-08-17 07:07:03 UTC
This is due to issues with VirtualBox and Windows 10.

*** This bug has been marked as a duplicate of bug 30212 ***