Hi all,
I’m seeing recently a recurring issue in Power BI Desktop where a brief CMD window appears during report load and sometimes during semantic model-related changes. After digging into it, I found that the CMD window is actually SQLDUMPER.EXE.
From what I understand, SQLDUMPER.EXE is a Microsoft diagnostic utility that gets triggered when an internal Microsoft component crashes or throws an exception. In this case, the actions seem to be tied to msmdsrv.exe, which is the backend model/query engine used by Power BI Desktop.
What the issue looks like
The black CMD window appears briefly.
It first happens while the report is opening, specifically during “Preparing report”.
It can also happen later when making changes that affect the semantic model, for example renaming a field or making other model-related modifications.
The issue does not seem to be a simple visual/UI problem. It looks more like the backend model engine is hitting an exception and SQLDUMPER is collecting a dump.
My troubleshooting so far
Confirmed the CMD window is SQLDUMPER.EXE
Using process monitoring, I confirmed that the CMD window is SQLDUMPER.EXE. Looking deeper, the process triggering it appears to be msmdsrv.exe, which is the Analysis Services/model engine running behind Power BI Desktop.No issue with a PBIX that has no external file connection
In my tests, the issue does not appear when the PBIX contains only embedded data and no external data source connection to a file. You can simulate it just entering a dummy data using "Enter Data" in power bi. Issue will not happen on those reports.Happens in both Store version and downloaded version
I tested both:the Microsoft Store/App version
the downloaded installer version
The issue happens in both.
Preview features do not seem to be the root cause
Turning off some preview features, such as On-object interaction, seemed to reduce the frequency somewhat, possibly because they trigger semantic model changes more often.
However, this did not solve the issue completely, so I do not think this is purely a preview feature problem.Cache clearing and fresh install did not fix it
I tried:clearing cache
fresh installation
switching to the downloaded version
None of these resolved the problem.
Running Power BI as Administrator prevents the issue
While investigating logs, I noticed some apparent file access-related problems involving msmdsrv.exe. That led me to try Run as administrator.
When I ran Power BI Desktop as Administrator, the issue did not appear.
I even turned all preview features back on and tested again as Administrator, and it still did not happen.Moving the PBIX to a simple local folder did not help
I also moved the report to a simple folder path such as: C:\test. This did not solve the issue.
Current conclusion
So far, on my machine, the only thing that prevents the issue is running Power BI Desktop as Administrator, which is obviously not a real solution.
At this point, I suspect this may be one of the following:
a Power BI Desktop bug
a permissions / file access / credential issue
something related to external data source connections
possibly some interaction between the local Analysis Services engine (msmdsrv.exe) and file-based external sources
Main questions
Is anyone else seeing SQLDUMPER.exe appear during “Preparing report” or during semantic model changes?
Has anyone identified the exact trigger?
Has Microsoft acknowledged this anywhere?
Is there any proper fix besides running Power BI as Administrator?
Thanks in advance. I’m sharing this in case it helps others narrow down the issue.
16 Comments
- markperroneFrequent Visitor
September 2026 - 6 months later - cmd window still opens. Another issue is when a measure is updated ANOTHER WINDOW comes forward. VERY ANNOYING. Geesh MS get your act together.
- DanielM16Frequent VisitorA lot of users in our company reported the same issue. Hope this will be fixed soon!
- KNikNew MemberHas anyone found a fix for this? Using admin privileges isn’t possible in most use cases. Even version 2.154.956.0 did not resolve this issue. Microsoft, this is a seriously disruptive bug that is hindering developers work!
- burakdemirtas
Advocate II
It feels like with every update, this problem just keeps getting worse. The main reason seems to be that each update adds more "interactive features" that try to access the semantic model for every visual and make changes, which leads to more frequent CMD prompts popping up. It’s unbelievable that no one from MSFT has really looked into it yet. - pbiuserNCNew MemberThis summarizes what I've experienced very accurately. I tried most of (if not all) of the same fixes/workarounds, and the only thing that helped was reverting back to February version. This seemed to help a lot, but like many, my IT depart controls when these are updated, so as soon at the March rollout was auto-installed again, it started happening frequently. It seems like since the April version, it's only gotten worse. Like many others, I don't have admin access to my local pc, to open PBI as admin, which is absolutely not reasonable work around anyway. Microsoft - you can do better, and you owe users a reasonable and timely fix. This is extremely cumbersome when you are making edits to a report. It causes a significant amount of lag time after simple changes like updating a field name, creating a simple measure, etc. This has increased the time it takes design/edit PBI reports significantly. Show us why we love PBI, and fix this!
- Chipsnump
Advocate I
Same problems here since Feb'26, it always happens when there are changes and refresh the files. It's very annoying during DAX were entered as well. - zjd4atcdcFrequent VisitorMS is much better at breaking things than fixing them. I reverted to the February version, and it is still an issue. Guess we have to wait until they decide to fix it for a future version.
- dmkblesser
Advocate II
I tested this in a previous version Version: 2.150.2455.0 64-bit (January, 2026) and cannot reproduce the issue. A problem introduced by the newer version. - Matthew_Martell
Helper II
This is happening to developers at our workplace too. We don't have access to 'run as administrator' though. 🙁 Power BI version is 2.152.882.0 (March 2026) - mwhaNew MemberThis started for me about a week ago - only change that I'm aware of around that same time was the addition of Co-Pilot premium. Power BI Reports now take twice as long to open, and will sometimes completely fail to open and just sits on a white screen, playing a blocked action sound anytime you click anywhere until you kill it in the task manager. C:\Program Files\WindowsApps\Microsoft.MicrosoftPowerBIDesktop_2.152.1279.0_x64__8wekyb3d8bbwe\bin\\SQLDUMPER.EXE