Bug 36126 - Unhandled exception at ... KernelBase.dll
Summary: Unhandled exception at ... KernelBase.dll
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.0.0
Hardware: PC Windows
: --- normal
Target Milestone: UWP
Assignee: Bugzilla
Depends on:
Reported: 2015-11-21 19:13 UTC by LuckyWolf19
Modified: 2016-01-26 16:40 UTC (History)
4 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 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:

Description LuckyWolf19 2015-11-21 19:13:03 UTC
See attached VS2015 solution. Running Windows 10 on Acer laptop with all latest patches and latest Xamarin Forms.

0xE0434352 was unhandled
Message: Unhandled exception at 0x762FD8A8 (KernelBase.dll) in macaroon.WinUniversal.exe: 0xE0434352 (parameters: 0x80131500, 0x00000000, 0x00000000, 0x00000000, 0x507C0000).
Comment 1 LuckyWolf19 2015-11-21 19:21:39 UTC
Forgot to mention the error occurs on a brand new Windows Universal project using PCL and following the instructions on the Xamarin website.
Comment 2 LuckyWolf19 2015-11-22 09:16:54 UTC
I created a UWP project by itself without any Xamarin related code, references, or projects. I had the same error message. So this is most likely an issue with VS2015 Community addition and the recent big patch for Windows 10. I am on version 10.0.10586 . I am now doing a repair on VS2015 to see if this fixes it.