The program can't start because api-ms-win-crt-string-l1-1-0.dll is missing

[Anonymous]

After installing the december 2018 version, Power BI Desktop fails on startup with: The program can't start because api-ms-win-crt-string-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem. I've seen this on two different windows 2012 r2 servers. No problems on my win 10 enterprise client. Why the problem on server 2012 r2? Regards Henrik

[ahmedoye]

You will have this error once your PC is missing some drivers required to run Power BI. Unfortunately, you won’t see this in the specification of requirements for Power BI installation. You will have to download and install that driver and everything will be back to normal.

Fortunately, i just wrote about this on my blog here on how you can resolve this issue painlessly. This requires downloading and installing Microsoft C ++ Redistributable. Check it out here Most Common Power BI Installation Errors And Their Solutions - Foresight BI - Achieve More With Less

[v-yuezhe-msft]

@Anonymous,

Maybe some operations you take on the operating system or some virus software delete this dll file accidentally. I would recommend you run windows update regularly to ensure operating system is in a healthy status before installing Power BI Desktop. 

Regards,
Lydia

[Anonymous]

Hi Lydia.

I dont think thats the problem, because when I uninstall the december version and reinstall the november version, Power BI Desktop starts without problems. Any ideas?

Regards

Henrik

[v-yuezhe-msft · Accepted solution]

@Anonymous,

I install Power BI Desktop December release(2.65.5313.1381) in a Windows server 2012 R2, there is no issue launching Power  BI Desktop. It seems that the issue is specific for your own operating system. Do you get the same issue when installing Power BI Desktop December release in other OS?

Regards,
Lydia

[Anonymous]

Hi Lydia

I downloaded a new installation file, an now Power BI Desktop runs without problems.

As you said - it is Version: 2.65.5313.1381 64-bit (december 2018).

I had the issue on two different server 2012 r2 - no idea why, but most important, that its running again.

Thanks for the reply

Henrik