Power BI Desktop issues starting March 2025 release when running under Parallel's Desktop
Please be aware that I have identified a bug or compability issue with Power BI Desktop (versions starting with March 2025 and after) that present as very odd behavior when run under the latest version Parallel's Desktop Pro Edition v20.3.0 (55895) virtual machine (Windows 11 Pro v24H2, build 26100.3915, 16 GB RAM) on a MacBook Pro (M4 Pro Apple Silicon chip).
I have created a simplified test PBIX file with one static date table that displays a broken visual in the newer PBI versions when one uses the Advanced Filter option under the filter pane. If one replaces the Advanced filter with a Basic filter option to filter the same visual, the visual displays fine. When one clicks the See details from the broken visual they get the following dialog.
Broken visual details dialog
This buggy behavior is not present in the February 2025 released version of the PBI app (run under Parallels Desktop virtual machine) or in more recent versions that are run on a physical PC.
This is a copy of the issue I raised int Forums yesterday.
Power BI Desktop issues starting March 2025 releas... - Microsoft Fabric Community
11 Comments
- Stinkys
Advocate II
Are you using ARM64 in either Windows (Snapdragon) or Mac/VM? If so please see this thread which includes instructions to downgrade to the Feb Power BI Desktop release - https://community.fabric.microsoft.com/t5/Issues/March-2025-Update-Error-fetching-data-for-this-visual/idi-p/4633481#comments And then hop on over to this thread to upvote ARM64 official support, because at present Microsoft have said ARM64 is officially not supported. https://community.fabric.microsoft.com/t5/Fabric-Ideas/Make-power-BI-desktop-fully-compatible-with-ARM-CPU-such-as/idi-p/4681097#M160671 - rmsolfest
Advocate II
Yes - I am on a Macbook Pro (M4 Pro) running Parallels Desktop. I have not had any issues with Power BI Desktop until the March 2025 release, which has displayed an odd bug only with using advanced filters. I have submitted the info here and to Parallels, but I am getting finger pointing and no resolution. - rmsolfest
Advocate II
This appears to be an issue with Power BI application compatibility when running under an ARM processor. My VM provider said "We have tested and was able to reproduce the issue and Surface Pro X (an ARM Host)." Microsoft Power BI application developers: Please update the Power BI application to fully support ARM processors. - Stinkys
Advocate II
rmsolfest - Microsoft employees have confirmed via several channels that this is not a priority and that ARM architecture is not supported. If you haven't already, please hop on over to this thread and upvote for visibility. https://community.fabric.microsoft.com/t5/Fabric-Ideas/Make-power-BI-desktop-fully-compatible-with-ARM-CPU-such-as/idi-p/4681097#M160671 - xavier_rouhaudRegular Visitorsame issue for me (Mac M4 + Parallels Desktop)
- marcz_frRegular VisitorLooks like that the July 25 version has still the issue... tested on Mac Studio M2 Ultra / Parallels Desktop 20 / Win 11 ARM / Power Bi Version number: v:2.145.1105.0 (07/14/25) Same error message : Unexpected error file "", line, function "" I can't work anymore on Power BI and can't downgrade my file....
- rmsolfest
Advocate II
Very frustrating and unbelievable that Microsoft Power BI does not support ARM processors even though they sell and praise the Microsoft Surface laptop with an ARM processor. - marcz_frRegular Visitor
Does anyone test the August 2025 version on ARM ?
actually I'm working on Windows 11 Canary version (beta) on Mac M2 with paralles Desktop and PowerBI works fine but that's not a real solution on long time... - rmsolfest
Advocate II
FYI - STILL AN ISSUE I just retested my sample PBIX file with the latest build with not improvement/change.
PBI Version: 2.146.705.0 64-bit (August 2025);
Parallel's Desktop Pro Edition v20.4.1 (55996);
Virtual machine: Windows 11 Pro v24H2, build 26100.4061, 16 GB RAM;
Hardware: MacBook Pro (M4 Pro Apple Silicon chip)
- mohamedashour93New MemberHi all, I have been in the same situation for the last 7 months. As you have alluded to, there is the solution of downgrading to Feb-25 x64 bit edition or using the latest july-25 release but 32-bit edition. It is super slow but that is the only option available. Shame on microsoft for this.