The following forum(s) have migrated to Microsoft Q&A (Preview): Developing Universal Windows apps!
Visit Microsoft Q&A (Preview) to post new questions.

Learn More

 locked
Error -1073741819 when building UWP app in Release mode using 64-bit .NET Native Toolchain RRS feed

  • Question

  • When building our UWP app in Release mode using the 32-bit .NET Native Toolchain we seem to be running out of memory, so we have tried to move to 64-bit Native Toolchain compilation by adding the following options to the various PropertyGroup sections of the .csproj file 

    <UseDotNetNativeToolchain>true</UseDotNetNativeToolchain>
    <Use64Bitcompiler>true</Use64Bitcompiler>

    We now get the following error during build:
    C:\Program Files (x86)\Microsoft SDKs\UWPNuGetPackages\microsoft.net.native.compiler\2.2.7-rel-27913-00\tools\Microsoft.NetNative.targets(801,5): error MSB6006: "ilc.exe" exited with code -1073741819.

    We cannot find any information on this error code anywhere - nor its hex equivalent C0000005. Also, we are wondering whether the 64-bit compiler is actually being used, as the path indicates a 32-bit program.

    Any clue or help would be greatly appreciated.

    Monday, November 18, 2019 9:47 AM

All replies

  • Hi,

    You can try to adjust the level of detail of the log file:

    Tools->Options->Projects and Solutions>Build and Run->Change "MSBuild project build output verbosity" to Diagnostic.

    Also, when you choose to compile UWP apps with .Net Native, check out this document, which mentions some unsupported APIs. If you use these APIs, it is recommended not to use .Net Native for project compilation.

    By the way, We invite you to post new questions in the "Developing Universal Windows apps" forum’s new home on Microsoft Q&A (Preview)!

    Best regards.


    "Developing Universal Windows apps" forum will be migrating to a new home on Microsoft Q&A (Preview)!
    We invite you to post new questions in the "Developing Universal Windows apps" forum’s new home on Microsoft Q&A (Preview)!
    For more information, please refer to the sticky post.


    Monday, November 18, 2019 11:33 AM
  • Hi,

    Does my reply solve your problem? Do you have any other questions you want to clarify?

    The UWP section of MSDN is about to be locked down. If you have other questions, please come to Microsoft Q&A to ask questions, and we will continue to answer your questions there.

    Best regards.


    "Developing Universal Windows apps" forum will be migrating to a new home on Microsoft Q&A (Preview)!
    We invite you to post new questions in the "Developing Universal Windows apps" forum’s new home on Microsoft Q&A (Preview)!
    For more information, please refer to the sticky post.

    Tuesday, December 3, 2019 8:09 AM
  • Hi,

    Sorry to disturb you again, we are confirming the status of the question. Did my response resolve your issue?

    Since the UWP section of the MSDN Forum will be locked down in the near future, after that, if you have new questions, welcome to our new community: Microsoft Q&A, where we will continue to answer your questions.

    Best regards.


    "Developing Universal Windows apps" forum will be migrating to a new home on Microsoft Q&A (Preview)!
    We invite you to post new questions in the "Developing Universal Windows apps" forum’s new home on Microsoft Q&A (Preview)!
    For more information, please refer to the sticky post.

    Friday, December 6, 2019 6:25 AM
  • Hi,

    Sorry to disturb you again, did you solve your problem?

    Since the UWP section of the MSDN Forum will be locked down in the near future, after that, if you have new questions, welcome to our new community: Microsoft Q&A, where we will continue to answer your questions.

    Best regards.


    "Developing Universal Windows apps" forum will be migrating to a new home on Microsoft Q&A (Preview)!
    We invite you to post new questions in the "Developing Universal Windows apps" forum’s new home on Microsoft Q&A (Preview)!
    For more information, please refer to the sticky post.

    Wednesday, December 11, 2019 8:07 AM