An unexpected error occurred( file ", line, function ")

[Ishhmn]

In Power BI Desktop, when using a slicer with date, I get the follwing error: An unexpected error occurred( file ", line, function ")

In particular, it breaks when I use the "Between" setting in the slicer as it is a Date

My Data is in csv format.

Power BI version: Version: 2.143.1204.0 64-bit (May 2025)

Data TableVisual

[and_arman]

Following the MS support team meeting with our DBA team, and after activating CPU AVX for the report server, all dashboards are operating finely. So, this is a hardware requirement on the user's side, and MS is not going to do anything in the next updated versions. 
It's related to supporting the AVX feature by your server/local machine CPU:
https://learn.microsoft.com/en-us/power-bi/report-server/system-requirements

[Danelle]

Just upgraded to the December 2026 release version and encountered this issue. Obviously still not resolved.

[and_arman]

I believe the issue is not on the MS side of the fence. This is a hardware requirement on the user side, so they are not going to do anything in the updated versions. 
To my understanding, it's related to supporting the AVX feature by your server/local machine CPU:
https://learn.microsoft.com/en-us/power-bi/report-server/system-requirements

[C4YNelis]

Hi all,

just wanted to add that after running into this problem end of November (working with the October release (2.148.1477.0 64-bit), which currently is the latest available for me), I can confirm that it has nothing to do with your report itself. That being said, sometimes it is possible to "fix it", but personally I wouldn't rely on this. The same report works on one machine, but gives me errors on the other.

I've been working on a report that has always worked just fine. Then, after making some minor adjustments, I suddenly got this error on one of the two machines I'm working with. At first, before realising the difference in behavior between the two installations, I too started tweaking measures, filters, etc. (which without any logical explaination sometimes sorted some effect, but never enough). The measure were very simple working with elementary date manipulation and a simple aggregation (no summarize or anything more complex) and there was absolutely nothing wrong with them. Other errors disappeared when clearing certain date filters (also made no sense). And then some errors didn't go away no matter what I tried.

The strangest thing though was that the same report (built as intended) worked just fine without any errors on one machine and caused me problems on the other (still does).

- Both run the exact same version of Power BI.

- The report has been a literal copy of the other one (even a shared Onedrive copy, but also a locally copied version to exclude synchronization differences).

- All preview functions are the same, which goes for the full setup of Power BI Desktop.

- The external tools are the same

- Every cache has been cleared on both machines, no difference either

- Because I suspect it's date-related, I've tried with and without the enhanced DAX Time Intelligence

- I've tried with and wihout the enhanced Report Format (PBIR), also tried PBIX vs PBIP

- I've downloaded the currently working (unedited) report from the service as a PBIX, which resulted in errors on the same machine and again ran fine on the other, confirming it has nothing to do with the report as far as I'm concerned.

The main difference between both machines is that:

- the errors occur on Windows 10 PRO (21H1 - Build: 19043.2364) and

- everything runs fine on Windows 11 Pro for Workstations (25H2 - build: 26200.7171).

Apart from that, the machine that works just fine has much more memory than the other (192GB vs 24GB) and more CPU's (40 logical processors vs 16). However, the report is a relatively simple one, I do not see how that could cause any problems.

What might be relevant is that the machine that works is also hosting both the SQL Server Database, which is the source database for this report, and the On-premises data gateway for Power BI.

Not a solution, I know, but hopefully it helps in finding the rootcause for this issue.

Cheers,

Niels

Edit: I just noticed the November update, which I installed (2.149.911.0) on both machines, but unfortunately everything stays the same. It would be nice to have this fixed before the end of the year!

[Miguel_Arias]

Hola, alquien a podido solucionar este problema? estamos a Noviembre de 2025 y seguimos con lo mismo. La vez anterior lo habia podido solucionar con la actualizacion de Febrero 2025 x32 pero ya me sale a cada rato el mensaje que debo pasar a la version x64. 

[rs3782]

Been having this issue since March 2025.  Still no fix with the June 2025 release.  I wish Microsoft would take this seriously - it's broken my model multiple times and still not solution in sight other than reverting to the Feb 2025 release.  How are we 4 versions ahead of this and still dealing with the same issue!!

[v-priyankata]

Hi @rs3782 
Apologies for the inconvenience caused, Thanks for your patience. This appears to be a known issue, and I hope Microsoft is expected to roll out a fix in one of the next updates.

[v-priyankata]

Hi @Ishhmn 

May I ask if you have resolved this issue? @stefano_deny @tamn @johnbasha33 thanks for your inputs.
@Ishhmn please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-priyankata]

Hi @Ishhmn 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

[tamn · Accepted solution]

There has been serveral bug reports about this - the issue was introduced in the March 2025 update.

It has not been fixed yet, even in the May 2025 release.

The general recommendation is, if possible, downgrade to the Feb 2025 version.

Further reading:
- https://www.reddit.com/r/PowerBI/comments/1jzy67k/power_bi_desktop_error_an_unexpected_error/
- https://www.reddit.com/r/PowerBI/comments/1jpxvxa/february_2025_power_bi_desktop_download_file/?shar...
- https://community.fabric.microsoft.com/t5/Desktop/Error-Fetching-Data-for-this-Visual/td-p/4635446

[and_arman]

Got an update from MS support which might be the case for you if you are using bi report server: 

https://learn.microsoft.com/en-us/power-bi/report-server/system-requirements

it might be related to AVX feature. 

[and_arman]

Yes. Same here. 
It's happening after the report server upgrade and is related to date format inconsistency. 

[Ahmad_1]

Does this also work for the Power BI Report Server?

[johnbasha33]

@Ishhmn 

Check your Date column type in Power Query

• Go to Power Query Editor.

• Select your Date column.

• Make sure its data type is set to Date (not Text or DateTime).

• If it’s Text, change it to Date.

• Then Close & Apply.

---

2. Ensure the date values are valid

• Dates should be in a proper format (e.g., YYYY-MM-DD or recognized locale format).

• Invalid dates or empty strings can cause the slicer error.

• In Power Query, filter out or fix rows with invalid dates.

---

3. Replace or fix null/blank dates

• Replace nulls or blanks in your Date column with a valid date or remove those rows.

• Null/blank dates can break slicer with "Between" mode.

---

4. Use a Calendar/Date table

• Create or import a proper Calendar Table with continuous dates.

• Connect your data’s Date column to this Calendar Table’s Date column.

• Use the Calendar Table’s Date in the slicer instead of the raw CSV date column.

---

5. Test slicer again

• After fixing the data type and invalid values, try the "Between" slicer again.
  
  

  Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!

[Ishhmn]

This has not worked, weirdly, if i change the scale from the left hand side of the slicer, it works, but not from the left (Lower Bound)

[stefano_deny]

Hello,

I'm experiencing the same issue. What's strange is that I tested opening the project on two other Dell laptops and the problem doesn't occur only on this somewhat old Intel desktop that I left at the company for BI project development.

I tried rolling back Power BI to the February version, but my project won't open in that version.

I hope Microsoft can fix this bug soon.