vcruntime140.dll is missing on UWP XBOX app

Roman Shpuntov 96 Reputation points
2020-06-10T08:35:12.213+00:00

I have UWP application, my app is forking fine on Windows 10 desktop PC and does not work on XBOX (crash on startup). My app consists from XAML app and some DLL (for example X.DLL). The X.DLL files is compiled with - x64 Native Tools Command Prompt for VS 2019. I investigated some startup issues of my app and observed the next situation:

  1. On load my app I have crash when I run app with X.DLL.
  2. On load my app I have not crash when I run app without X.DLL.
  3. I compared two load logs from above steps and I found some problem: app depends from vcruntime140d_app.dll and vcruntime140_1d_app.dll
  4. X.DLL depends from vcruntime140.dll
  5. On XBOX I have not vcruntime140.dll as a result I have crash on load app

I put the vcruntime140.dll and vcruntime140_1.dll libraries inside of my application project and it worked. I believe that it is not correct to distribute the application with the vcruntime140.dll and vcruntime140_1.dll libraries, because these libraries already exists, but it is named differently (vcruntime140d_app.dll and vcruntime140_1d_app.dll). Of course I want to fix this problem. My questions:

  1. Why are you renaming vcruntime140.dll to vcruntime140_app.dll on building stage? How can this be avoided?
  2. What about the fact that in your application project depends from the vcruntime140.dll and vcruntime140_1.dll system libraries?
  3. Is this a bug and will you fix it?

Please give me advice how can I fix it inside my app.
Thanks!

Universal Windows Platform (UWP)
{count} votes

Accepted answer
  1. Roman Shpuntov 96 Reputation points
    2020-06-18T07:00:45.717+00:00

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.