Forum Discussion
Is XML in Power Query is broken on macOS
Hello,
XML from Power Query seems to have broken after update (July 2nd 2026). I tried this on several Macs
To recreate just create a new file. Power Query -> XML -> Choose any xml file
For me it doesn’t work. It keeps loading endlessly
Am I the only one? Is there a workaround?
Thank you
4 Replies
- aitalaatCopper Contributor
Worth mentioning it's fixed now with latest update. However, it proves unreliable for me. I'll me exploring options presented at alternative to the system in place now. Thanks
- NikolinoDEPlatinum Contributor
Regarding the issue where Power Query gets stuck on an endless loading screen when importing XML files on your Mac: this is a known bug in the current Mac version of Excel’s XML parser.
While Microsoft works on a fix, the most reliable workaround is to convert the XML file to a CSV or JSON file first, and then import that converted file into Power Query.
Here is how to do this using a free online converter:
Step 1: Convert the XML file (Note: Only use this method if the XML file does not contain sensitive or confidential company data.)
- Go to a free conversion site like ConvertCSV (convertcsv.com/xml-to-csv.htm) or CodeBeautify (codebeautify.org/xml-to-json).
- Upload your XML file.
- If your data is relatively flat (simple lists/tables), convert it to CSV. If your data is highly nested or complex, convert it to JSON.
- Download the newly created CSV or JSON file to your Mac.
Step 2: Import the converted file into Excel
- Open a blank Excel workbook.
- Go to the Data tab on the ribbon.
- Click Get Data (or From Text/CSV / From JSON directly).
- Select your newly converted file.
- The Power Query Editor should now open normally without freezing. You can transform your data and click Load to bring it into your spreadsheet.
My answers are voluntary and without guarantee!
Hope this will help you.
Hi, since you can reproduce this on several Macs after the July 2 update, I would treat it as a likely Excel for Mac regression rather than a bad XML file. A good test would be to try another update channel or roll back one affected Mac if your org allows it. In the meantime, using Excel for Windows, Power Query Online, or another XML import path may be the most practical workaround until Microsoft confirms the bug.
- aitalaatCopper Contributor
The only test I could do was on an un-updated mac and it still worked. So I'll take your advice and research rolling back or third party tools.
Still hoping for a workaround though, it would save me hours
thanks