Snowflake Connection Error in Power BI – “Invalid authkind provided: KeyPair”
Hi everyone, I'm having an issue connecting Power BI Desktop to Snowflake using Key Pair authentication. I generated an unencrypted private key, configured the corresponding public key for the Snowflake user, and then tried to create/update the Snowflake connection in Power BI using Key Pair authentication. However, Power BI returns: Invalid authkind provided: KeyPair The connection was working previously, but I am now unable to configure or update the Snowflake credentials. Environment Power BI Desktop: September 2026 Version: 2.158.1177.0 (26.09) x64 Windows: Windows 11 / NT 10.0.26200 Data source: Snowflake Authentication: Key Pair Private key: Unencrypted Snowflake legacy ODBC preview feature: Disabled The detailed Power BI error report also shows: System.ArgumentException ConnectionDataExtensions.AsCredentialDataCollection and the error occurs during: UpsertConnectionAsync This makes me wonder whether this could be related to the September 2026 Power BI Desktop release or the newer Snowflake connector/credential handling, rather than the Snowflake key itself. I have already: Generated an unencrypted private key Configured the matching public key in Snowflake Selected Key Pair authentication in Power BI Tried updating/recreating the connection Has anyone experienced the same issue with the September 2026 Power BI Desktop release? Is there any known issue or workaround for: Invalid authkind provided: KeyPair I will also attach the full Power BI error details and screenshot. Thanks in advance.CMD Prompt Popping Up During Changes
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.
Images on first page of embedded report flicker and disappear
I have an Image URL visualization which shows an image of the company that is selected in a slicer. It is live on https://www.talkingengagement.ca/municipal-culture-indicators All my images are publicly hosted URLs, in the right format. They all work except for the first image that loads by default. That image flickers in and out, and sometimes disappears completely. The data responds perfectly to the slicer, the flickering problem is only with the image. I tried to troubleshoot by changing the image, changing the number and order of companies in my data; the problem is always with whichever image is loaded first. In powerBI Desktop and MyWorkspace, everything is fine. The problemarises when the report is embedded, on all browsers. The problem is intermittent
FIX THE 'LINE GRAPH' VISUAL BUG IN LATEST VERSION OF POWER BI
Power BI Desktop 2.156.951.0 (July 2026) appears to have a bug in the standard built-in 'Line Chart' visual. Marker colour formatting is being ignored. Line colour updates correctly but markers continue to render using the default series colour. An example of the issue is highlighted below where we can see that the line graph markers should be displaying in matching pink, but the visual is failing to obey the instruction and is dispalying them in deafult blue instead.
Power BI Azure maps legend colours issue
Hello, Azure Maps visual displays correct marker colours in Power BI Desktop (on the bottom). However, after publication, the legend colours shown in Power BI Service (on the top) do not match the manually configured data colours. The map rendering itself remains correct, but the generated legend uses a different colour palette and cannot be manually corrected within the Service. It has been reported through several threads in the "Need Help" forum : Power BI Azure map legend colour issues - Microsoft Fabric Community Azure map legend colours incorrect in service - Microsoft Fabric Community It has seriously impacted several of my dashboards, do we have any resolution timeline for this bug? thank you Saul_Ring liz72DataFormat.Error: The input couldn't be recognized as a valid Excel document.
I have a Power BI dashboard that uses multiple excel files stored in Onedrive as a dataset and day before yesterday got the following error while refreshing the data set - DataFormat.Error: The input couldn't be recognized as a valid Excel document. Details: [Binary] I have a Power App that is connected to these excel files as a data sources. Yesterday all of a sudden started getting the following error in one the screen which has a submit form operation - Network error when using patch function: the requested operation is invalid on SubmitForm The Submit Form operation is just taking the inputs from the UI elements and inserting in the excel file and no patch function is used explicitly. When the Power BI issue occurred, I had manually corrected the data in excel file and saved it. Post that the Power BI issue got fixed but the Power App issue cropped up. Based on the following link, the excel file is corrupted, even though I am still able to open it - https://techcommunity.microsoft.com/t5/excel/quot-the-input-couldn-t-be-recognized-as-a-valid-excel-document/m-p/50475 Since the excel file was saved in OneDrive, I had reverted it to a point where the app was working. Then the Power App issue was fixed, but again started getting the issue in Power BI. Thus, not able to figure out how to make Power App and Power BI work simultaneously which was happening earlier and at the same time fix the corrupted excel file.
Cancelling measure while creating gets stuck in endless loop
1. Created measure 2. While measure was updating local model, I hit cancel (didn't want the measure created) 3. I now have a measure part-created called 'Measure' and every time I try to update/remove it, I get the error "The model doesn't have a measure named Measure on table XXX." 4. Stuck in endless loop. Every time I click something, I get the same error and only option is to click 'Close', which repeats step 3. No way to save. Lost about 3hrs of work.Allow report authors to disable or hide table right-click context menu options in Power BI Desktop
Hi Power BI Team, I would like to request a new feature that allows report developers to disable or hide selected right-click context menu options on table and matrix visuals after publishing reports to Power BI Service. Business reasons This feature would help in reports where: Users should only view the designed report experience Include and Exclude create unexpected visual filters Copy options are not appropriate for sensitive operational information Show as a table exposes a different presentation from the approved report layout Report owners need stricter control over user interaction Reports are used in regulated, clinical, financial, or confidential environments Administrators need a consistent interaction policy across reports Important security note This feature would not replace: Row-level security Object-level security Export restrictions Build-permission controls Tenant security settings It would provide better control over the report user experience and reduce unwanted or confusing interactions. Please consider adding this capability in a future Power BI Desktop and Power BI Service release. Thanks in advance. Best regards, Maruthi Siva Prasad http://www.linkedin.com/in/maruthi-siva-prasad/
Power BI Desktop Snowflake Refresh Fails: “Cannot Convert Null to Text” While Service Still Works
Hi all, I’m seeing a sudden Power BI Desktop refresh failure with Snowflake-backed Power Query tables. Has anyone else seen this with recent Power BI Desktop / Snowflake connector builds? Is there a known regression or recommended workaround? Power BI Desktop version: 2.155.756.0 Install type: Microsoft Store app Connector: native Snowflake connector Pattern: Snowflake queries fail in Desktop, but the same SQL runs successfully in Snowflake and the dataset/report still refreshes in Power BI Service. Representative M pattern: let Source = Value.NativeQuery( Snowflake.Databases( "<snowflake_account>", "<warehouse>", [Implementation="2.0"] ){[Name="<database>"]}[Data], "<native SQL query against a Snowflake view>", null, [EnableFolding=true] ) in Source Desktop refresh error: cannot convert the value null to type Text. Things already tried: Restarted machine Uninstalled/reinstalled Power BI Desktop Cleared/re-authenticated data source credentials Removed [Implementation="2.0"] Removed [EnableFolding=true] Replaced select * with explicit column casts Tested multiple Snowflake queries/tables
