I use PowerQuery quite a bit together with Excel (Microsoft 365). Excel has started crashing whenever I access Table Design / Properties for a table created by PowerQuery. This is the scenario: Put cursor in the table Click Table Design menu click "Properties" (which is present in the "External Data Table" section of the ribbon). [Note: Properties will be greyed out for an ordinary table - AFAIK, it's only accessible for a Table created by PQ.] make some change in the window that pops up In all existing workbooks, and even a brand new one I create , following Step 3 (or sometimes Step 4) Excel crashes - and it usually restarts. So, the properties function under Table Design is inaccessible! What could be causing this? How to fix it?

An update: Based on advice given to the OP in the Fabric community forum, I've tried a full uninstall and reinstall of Office and can confirm that this did not solve my issue. I've also checked that I have no active addins. I've also tried creating a new workbook and creating a new Microsoft Query, but the moment I try to edit external data properties, Excel still crashes. Since there do not seem to be widespread complaints about Excel crashing under the above mentioned circumstances, I have to assume for now that the issue lies with something corrupted on my operating system rather than this being a bug introduced by December's Windows or Office updates. However, I'll keep an eye on any new posts responding to the OP's query on the Fabric community forum.

@rau1 - Exactly so. There is a post on the Feedback Portal that flags the bug, but then quotes the non-workaround which is less helpful. Suggest everyone upvotes it and adds to the comments. https://feedbackportal.microsoft.com/feedback/idea/6dcce8b8-e8be-ef11-95f6-0022484d7a88

I can confirm this works. Selecting properties in the 'data tab' can crash it. Changing name / database / changing SQL statement or just pointing to either can crash the application. Using the 'queries and connection' route, doesn't crash the application and it works like it always has. It even has the SAME menus! Feels like it's something that Microsoft doesn't want you to use anymore and it's forcing you to use the more annoying and time-consuming alternative PowerQuery. PowerQuery is something I use for manipulating tables, not for simple selects. The 'previous' SQL function isn't even available anymore via button in the ribbon. You can only start this by adding a hidden button to the quick-start-ribbon. As soon as I uses something from the 'previous' SQL-function. My Excel application crashes. So it's definitely a bug or even intended, so users are forced to use the 'current' SQL function.

Hi Julian, Just an update: I wasn't able to downgrade to 16.0.18129.20200, but I was able to downgrade to 16.0.18129.20158 and I can confirm that Excel is no longer crashing! Thanks very much for the advice. I've turned off auto-updating for now. Regards, Brad

I've had this exact issue with a user today. I have rolled back to version 16.0.18129.20200 which works fine. It did work in safe mode so it may be an add in causing the issue.

Excel crashes in Table Properties

Anonymous

I use PowerQuery quite a bit together with Excel (Microsoft 365).

Excel has started crashing whenever I access Table Design / Properties for a table created by PowerQuery.

This is the scenario:

- Put cursor in the table
- Click Table Design menu
- click "Properties" (which is present in the "External Data Table" section of the ribbon). [Note: Properties will be greyed out for an ordinary table - AFAIK, it's only accessible for a Table created by PQ.]
- make some change in the window that pops up

In all existing workbooks, and even a brand new one I create, following Step 3 (or sometimes Step 4) Excel crashes - and it usually restarts. So, the properties function under Table Design is inaccessible!

What could be causing this? How to fix it?

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

52 answers

Anonymous

2025-01-09T12:10:39+00:00

An update:

Based on advice given to the OP in the Fabric community forum, I've tried a full uninstall and reinstall of Office and can confirm that this did not solve my issue.

I've also checked that I have no active addins.

I've also tried creating a new workbook and creating a new Microsoft Query, but the moment I try to edit external data properties, Excel still crashes.

Since there do not seem to be widespread complaints about Excel crashing under the above mentioned circumstances, I have to assume for now that the issue lies with something corrupted on my operating system rather than this being a bug introduced by December's Windows or Office updates.

However, I'll keep an eye on any new posts responding to the OP's query on the Fabric community forum.
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2025-02-09T16:29:36+00:00

@rau1 - Exactly so.

There is a post on the Feedback Portal that flags the bug, but then quotes the non-workaround which is less helpful. Suggest everyone upvotes it and adds to the comments.

https://feedbackportal.microsoft.com/feedback/idea/6dcce8b8-e8be-ef11-95f6-0022484d7a88
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2025-01-31T10:24:28+00:00
I can confirm this works.
- Selecting properties in the 'data tab' can crash it.
- Changing name / database / changing SQL statement or just pointing to either can crash the application.
Using the 'queries and connection' route, doesn't crash the application and it works like it always has. It even has the SAME menus!

Feels like it's something that Microsoft doesn't want you to use anymore and it's forcing you to use the more annoying and time-consuming alternative PowerQuery.

PowerQuery is something I use for manipulating tables, not for simple selects.

The 'previous' SQL function isn't even available anymore via button in the ribbon.

You can only start this by adding a hidden button to the quick-start-ribbon.

As soon as I uses something from the 'previous' SQL-function. My Excel application crashes.

So it's definitely a bug or even intended, so users are forced to use the 'current' SQL function.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2025-01-10T13:43:20+00:00

Hi Julian,

Just an update:

I wasn't able to downgrade to 16.0.18129.20200, but I was able to downgrade to 16.0.18129.20158 and I can confirm that Excel is no longer crashing!

Thanks very much for the advice. I've turned off auto-updating for now.

Regards,

Brad
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2025-01-10T11:49:52+00:00

I've had this exact issue with a user today. I have rolled back to version 16.0.18129.20200 which works fine. It did work in safe mode so it may be an add in causing the issue.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments