I have a CSV (see excerpt below) which loads without trouble on the Dec 2018 version of Power BI desktop (2.65.5313.701 (December 2018)) but completely crashes PowerBI on the current Feb 2019 version (2.65.5376.1681). One field from the CSV has the following characters for a null result "- ** None **". I'm presuming that the curent PowerBI is trying to interpret the characters in the field as some kind of command rather than as text data. I presume this is a bug that was inadvertantly created with the release of some new functionality for PowerBI. Hoping that this gets raised as a PowerBI bug for urgent bug fix, as now we have to put in a pre-processing step to remove any leading "-"s from any CSV file before loading it into PowerBI. Have replicated on both 32 and 64 bit versions, but have not yet tried the cloud version of PowerBI. Neither Tableau nor Qlik are effected by this string in a CSV file. Happy to provide the complete file to anyone who'd like to test the impact on the curent Power BI, but the following excerpt should still do the trick.