Forum Discussion
Power BI Desktop bit October 2016 release does not launch on windows 10
I was using the September release, I am talking about the release dated 3rd October.
Hi sgmc1009,
I download the latest Power BI Desktop which is released in October 3rd from this link and install it on my Windows 10 laptop, everything works well.
In your laptop, please check if any detailed error messages are logged in event viewer when Power BI Desktop crashes. In addition, is there are any possibility that you have Nahimic running in your laptop? If so, please stop Nahimic and start Power BI Desktop, for mode details, please review this similar thread.
Thanks,
Lydia Zhang
- sgmc10099 years agoFrequent Visitor
Thanks Lydia.
I don't have Nahimic installed. Looking in the logs it appears that the inability to launch relates to MSOLAP errors, the following error occurs everytime I try to launch PowerBI desktop.
- Event ID 25 from source MSOLAP$AnalysisServicesWorkspace1302910754 cannot be found.
The error code relates to the 'locale' settings I believe but I have no idea how to change it. I thought it might be related to my installing PowerBI gateway but it still couldn't launch Power BI when I uninstalled it.
I do have MSSQLEXPRESS 14 installed but not analysis services.
Hopefully someone has already overcome this.
Cheers,
Steve
- Anonymous9 years agoNot applicable
Hi sgmc1009,
Could you please post the full error message about locale in Windows Event Log? Please follow the instructions in this blog to change locale setting the error message indicates and then check if you can launch Power BI Desktop successfully.
Thanks,
Lydia Zhang- peterelot9 years agoNew Member
Anonymous wrote:Hi sgmc1009,
Could you please post the full error message about locale in Windows Event Log? Please follow the instructions in this blog to change locale setting the error message indicates and then check if you can launch Power BI Desktop successfully.
Thanks,
Lydia ZhangIs it possible to create a batch file to change locale settings? I plan to create a scheduled task to run the batch every time Windows loads. That might be a temporary fix.