Power BI File Corrupted? Check Its Excel Data

How-to basics · Updated November 21, 2026

A Power BI file can show corrupted-looking Excel data, but importing an Excel workbook into Power BI normally does not change or corrupt the original workbook. Power BI reads the source into a model or uses it during refresh; the problem may instead be in the source file, the import or transformation steps, the model, or the way a visual displays the data.

What “corrupted data” can mean

People use “corrupted” to describe several different problems. A report might show blank values, errors, unexpected totals, garbled characters, missing rows, or values that differ from the Excel sheet. Those symptoms do not by themselves prove that a file is physically damaged. They can result from a changed data type, a failed refresh, a changed worksheet layout, or a filter in the report.

It is useful to distinguish the files involved. An Excel workbook usually has an .xlsx or .xlsm extension and contains the source data. A Power BI Desktop report usually has a .pbix extension and contains report definitions and a data model. A .pbit file is a template and generally does not include the imported data. These files are not interchangeable: a PBIX is not simply an Excel workbook with a different extension.

For example, an Excel column may contain numbers in most rows but the text value “N/A” in one row. Power Query may then infer a type, convert some values, or produce errors depending on the transformation steps. The source workbook can still open normally even though the Power BI preview or report contains errors.

How Power BI uses an Excel workbook

With the common Excel import workflow, Power BI reads data from a selected workbook and loads it into the Power BI model. Power Query can select sheets or tables, remove rows, rename columns, change types, and apply other transformations before the data is loaded. Those steps affect the data prepared for the report; they do not ordinarily edit cells in the source workbook.

When you refresh an imported model, Power BI reads the source again and repeats the query steps. That means the report can change after someone edits, renames, moves, or replaces the workbook, even though the Power BI file itself was not damaged. If the source is an Excel file on OneDrive, SharePoint, or a shared drive, check that Power BI is reaching the intended current file and that credentials and access are still valid.

Power BI reports can also use other kinds of connections, and a report may combine data from more than one source. So a value that looks wrong in a visual might come from a relationship, a measure, a filter, or another table—not necessarily from Excel. In the usual Excel connector workflow, however, Excel data is imported rather than queried as a live DirectQuery source.

Find out whether the source or report is at fault

Start by preserving both files. Make copies of the PBIX and the source workbook before attempting repairs, especially if either file is stored in a synchronized folder. Then compare the same rows and columns in Excel, Power Query, the model, and the report. This helps locate the stage at which the values change.

  1. Open the workbook in Excel. Check whether it opens without a repair warning and whether the affected cells contain the expected values. Look for formulas that return errors, hidden rows, unexpected filters, and changed sheet or table names.
  2. Inspect Power Query. In Power BI Desktop, select Home > Transform data. Choose the relevant query and review its Applied Steps. Select steps one at a time to see whether a particular operation introduces errors, removes rows, or changes values.
  3. Compare the loaded model. Check the table and column involved, including its data type and whether the expected records are present. If the query preview looks right but the report does not, inspect visual-level, page-level, and report-level filters, as well as relationships and measures.
  4. Check refresh information. A refresh error, an old “last refreshed” time, or a source-path warning may mean the report is displaying an earlier successful load rather than the current workbook data.

For instance, if the Excel table has 500 rows but the Power Query preview has 480, look for a filter or a “Removed Errors” or “Removed Rows” step. If all 500 rows reach the model but a chart shows only 300, investigate the chart’s filters, interactions, and categories before changing the source file.

Common causes of Excel values looking wrong

Type conversion is a frequent source of confusion. A column that mixes dates, numbers, and text may not be interpreted consistently. Dates can also appear shifted or invalid when values are read using a different locale or when text dates are ambiguous. A value such as 03/04/2026 could mean March 4 or April 3, depending on the convention used when it is interpreted.

Other common causes include:

  • Changed workbook structure: A sheet, Excel table, column heading, or file location was renamed or moved after the query was created.
  • Errors or blanks in source rows: A formula error, empty cell, or text entry in a mostly numeric column produces a different result from an ordinary number.
  • Query steps: Filters, removed duplicates, merged queries, changed types, and replaced values can alter the output intentionally or unexpectedly.
  • Model logic: Relationships, aggregation settings, measures, and filter context can make totals differ from a simple sum in Excel.
  • Refresh or access issues: Power BI may be unable to access the current file, or a refresh may fail before loading the latest changes.

Formatting can also mislead. Excel may display a stored value with a currency symbol, rounded decimals, or a date format. Power BI may show the underlying value using a different format. A visual difference in display is not necessarily a change to the stored source value.

Safe troubleshooting and recovery steps

Make one change at a time and refresh or inspect the result after each change. First confirm that the source workbook is healthy and that Power BI points to the correct file. If the workbook itself fails to open in Excel for Microsoft 365 on Windows, try a copy: use File > Open > Browse, select the workbook, select the arrow beside Open, and choose Open and Repair if that option is available. Repair may not recover every file, so keep the untouched original.

If Excel opens correctly, but Power Query shows errors, select the failing query step and determine why it fails. Correct the source values or adjust the transformation only when you understand the intended data. For example, replacing text “N/A” with a blank may be appropriate for one dataset, but it would be wrong if “N/A” is a meaningful category. Check the results against known records before loading the changes.

If the query preview and model look correct but the report is wrong, inspect the visual and model logic rather than repeatedly repairing the workbook. If only the PBIX fails to open, try a separate copy and check for an earlier version in the location where it is stored, such as SharePoint, OneDrive, or a backup system. A PBIX file does not have a general-purpose Excel-style repair command, and renaming its extension or manually editing its internal contents is not a reliable repair method. If no usable copy exists, rebuilding the report from the source workbook may be necessary.

Preventing the problem from returning

Stable source structure makes refreshes more dependable. In Excel, format source ranges as named tables when appropriate, keep column headings consistent, and avoid changing sheet names or moving files without updating the Power BI connection. Decide how blanks, errors, and mixed-type columns should be handled instead of relying on automatic type detection for every refresh.

Also keep recoverable copies. Store the source workbook and PBIX in a location with version history or a separate backup process, and save a copy before major changes to queries or the model. After changing a workbook’s layout, test a refresh in Power BI Desktop before publishing or relying on the report. For a shared report, check that the refresh configuration and access to the source match the way the file is stored.

Finally, document important transformations. A short note explaining why a column is converted to text, why certain rows are excluded, or how a total is calculated can prevent a later maintainer from “fixing” an intentional rule and creating a real data-quality problem.

Frequently Asked Questions

Can Power BI corrupt my Excel file?
In the normal import workflow, Power BI reads the workbook and applies transformations to data loaded into its model; it does not write those transformations back to the original Excel cells. If the workbook itself changed, check whether another user, process, or application edited it.

Why does Power BI show different numbers from Excel?
Check whether the report is refreshed, whether the same rows are included, and whether filters, data types, relationships, measures, or number formatting differ. Excel may display a formatted or rounded value while Power BI calculates or displays it differently.

Will refreshing Power BI fix corrupted-looking data?
Refresh can bring in corrected source data, but it will not automatically fix a bad query step, an incorrect measure, or a damaged source workbook. Confirm the source and inspect the query before refreshing repeatedly.

Can I repair a corrupted PBIX file in Excel?
No. A PBIX is a Power BI Desktop report file, not an Excel workbook. Excel’s Open and Repair feature is for supported Excel files; for a PBIX that will not open, work from a backup or earlier version and consider rebuilding the report if necessary.

Should I delete and recreate the Power BI query?
Not as a first step. Review the source path and Applied Steps to identify the cause, and keep a copy of the PBIX before changing queries. Recreating a query may remove transformations or break relationships and visuals that depend on it.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.