Warning to avoid PBI release version 2.142.1277.0 (May 2025)

[nathanshambo]

This is just a warning and it may not apply to all PBI admins and developers.  The May 2025 release version 2.142.1277.0 seems to be a bad release.  When I updated from the prior release version 2.140.1577.0 (Feb 2025) the desktop software experensed a critical failure and was unable to execute any DAX code.  I tried repairing the install and confirmed my system was completely updated.  My Semantic Model was working perfectly without any issues on release version 2.140.1577.0 (Feb 2025).  But the May 2025 update seems to have something wrong with it.  Fortunetely, I was able to rollback to the prior release and my Model is perfect again.

This is just a warning and my experience may be an edge case.

[nathanshambo]

Just a small update.  I saw and tried the latest May release version (May 18, 2025).  Unfortunately, the issue has persisted and I have rolled back to the February release again.

I was able to grab a screen image of the error and I found a Reddit post that seems to discuss a very similar issue for an older release.  I did dig a bit into my code and I was able to isolate that the issue is related to time intelligence filters.  Unfortunately, I cannot alter the existing code as it serves specific business needs.  I will need to wait for the next release.

Version: 2.143.878.0 64-bit (May 2025) error message upon application launch.

Older Reddit post discussing similar issue

https://www.reddit.com/r/PowerBI/comments/1jzy67k/power_bi_desktop_error_an_unexpected_error/

[v-achippa · Accepted solution]

Hi @nathanshambo,

Thank you for the response, this issue is not resolved in the May 2025 version and this is a known regression introduced with this version. It is related to internal changes in the DAX engine and model format handling. I recommend rolling back to the stable February 2025 version for now.

If you haven't already consider submitting a report through the issues forum, please consider submitting a detailed report include any error messages and feedback. This can help microsoft identify and address the problem more quickly. We understand the inconvenience caused by these issues and appreciate your patience as microsoft works towards a resolution.

Issues - Microsoft Fabric Community

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thanks and regards,

Anjan Kumar Chippa

[burakkaragoz]

Hi @nathanshambo ,

I also noticed some weird behavior after updating to that version. Rolling back to the previous one fixed it for me too.

If anyone else is seeing issues with visuals or performance, def worth trying an older version until this gets patched.

Appreciate you sharing this!

---

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and formatting supported by AI

[v-achippa]

Hi @nathanshambo,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @Ritaf1983 for the prompt response.

Have you raised this in the Issue's forum? As we haven’t heard back from you, we wanted to kindly follow up to check if the issue is resolved? or let us know if you need any further assistance.
If any response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Thanks and regards,

Anjan Kumar Chippa

[Ritaf1983]

Hi @nathanshambo 
If the issue is with power bi desktop :

I'm using the mentioned version and haven’t experienced any issues.
Similarly, there have been no reports in the developer group I manage or in the forum issues.
In order for Microsoft’s product managers to investigate the matter, I recommend creating a more detailed post with an example—or even a PBIX file if possible—and reporting it as an issue.

https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues
If the issue is with the report server 
On Report Server, it's always recommended to hold off on updating to the latest version and to work with the previous one instead, as it often takes time for a new release to stabilize.
In any case, it's advisable to report the issue in detail so the product team can investigate and address it properly

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly