title: Blank Universal Windows App - C++/CX returns exit code 1 (0x1)
body: <p>In a Windows App I developed with Visual Studio I was having the following problem: When you close the window App with the X (Close the App) while debugging, some of the threads end with exit code 1 (0x1).</p>
  
  <pre><code>The thread 0x17bc has exited with code 0 (0x0).
  The thread 0x784 has exited with code 0 (0x0).
  The thread 0x3f74 has exited with code 0 (0x0).
  The thread 0x3590 has exited with code 0 (0x0).
  The thread 0x7c4 has exited with code 1 (0x1).
  The thread 0x34d4 has exited with code 1 (0x1).
  The thread 0x3328 has exited with code 1 (0x1).
  The thread 0x164c has exited with code 1 (0x1).
  The thread 0x2fb8 has exited with code 1 (0x1).
  The thread 0x2b50 has exited with code 1 (0x1).
  The thread 0x3c80 has exited with code 1 (0x1).
  The thread 0x20cc has exited with code 1 (0x1).
  The thread 0x3520 has exited with code 1 (0x1).
  The thread 0x359c has exited with code 1 (0x1).
  The thread 0x13bc has exited with code 1 (0x1).
  The thread 0x3cb4 has exited with code 1 (0x1).
  The thread 0x1e74 has exited with code 1 (0x1).
  The program '[15492] AppTest.exe' has exited with code 1 (0x1).
  </code></pre>
  
  <p>After trying unsuccessfully to solve it, I tried to create a Blank App with Visual Studio 15 to see how everything was linked, to reproduce it, but the issue is happening also with the new created App. I didn't touch anything, just <em>New Project -> Build Blank App (UWP - C++/CX) -> Build &amp; Run</em>, but still the same.</p>
  
  <p>I thought that having an old version of VS could be the issue, so I downloaded VS19, repeated the process, and got surprised by the fact that it also happens in there.</p>
  
  <p>Did anyone face a similar issue? Could it be my VS settings?</p>
  
  <p>Any help will be much appreciated.</p>