Bug 32721 - Latest version breaks Windows 8.1
Summary: Latest version breaks Windows 8.1
Status: RESOLVED INVALID
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-03 14:11 UTC by Ernesto Rojo Jr
Modified: 2015-08-19 03:33 UTC (History)
2 users (show)

Tags:
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 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 INVALID

Description Ernesto Rojo Jr 2015-08-03 14:11:56 UTC
I just updated my Android player to the latest public release (0.4.4). I had Hyper-V enabled, so I turned that off and restarted my computer. I was unable to boot back into Windows. I kept running into KERNEL_SECURITY_CHECK_FAILUREs. I was able to recover by doing a system restore to the recovery point created before the Android Player was updated.
Comment 1 Mark Simpson 2015-08-19 03:33:05 UTC
I have been unable to reproduce this despite numerous attempts. XAP does not have any kernel drivers (directly, there are some used by VirtualBox) that could trigger a fault like this.
My guess would be that in this case something went wrong when Windows disabled Hyper-V, unrelated to the update of XAP.
I'm going to close this as I do not believe it to be an XAP issue and it is not been possible to reproduce.