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?

Hello, rau1. Thank you for visiting the Microsoft Community. We understand the problem you are having. Your current issue appears to be a Power Query-related issue, we suggest you ask the following questions to ask questions and research: Power Query - Microsoft Fabric Community (Users who have the same problems as you in this area will prefer to ask questions and share their ideas.) The experts here will provide you with more specialized solutions to your Power Query problems. Sincere greetings Hannah.Z- MSFT |Microsoft Community Support Specialist

OK thanks, I've done as suggested.

I'm having a similar issue that I only noticed towards the end of December with Excel 365 crashing whenever I edit external data properties for any type of database connection I've been using, including a legacy Microsoft Query. Excel restarts without warning and the event viewer refers to exception code 0xc0000374 with the faulting module name being ntdll.dll, version 10.0.19041.5007. Googling this isn't much help as it appears this is rather a generic issue to do with heap corruption. I've tried an online repair of Excel, as well as running the Windows system file checker, but to no avail. I'm running Windows 10 Pro 64-bit and my Windows updates are up-to-date. I am running the 32-bit version of Excel 365 as we're still needing to access a legacy ODBC connection that only supports 32-bit. Just today there was a new Office (AKA Microsoft) 365 update available so I've proceeded with it too, but I'm still getting the same crash in Excel. I've tried clearing data caches and deleting temporary files, and I've also tried using a different user profile on the same computer, but also no joy. As I'm not only getting crashes with Power Query related tables but also Microsoft Query related tables, I chose to post here rather than in the Microsoft Fabric Community forum where I see the OP did indeed raise his issue again. At this point I'll probably wait for Tuesday's Windows updates and if those don't solve the issue, I see no other course of action other than to go through the hassle of performing a Windows reset and then reinstalling all my applications.

Hello, rau1. I am glad to hear your update on the problem, and hope that your problem can be solved more professionally and properly. Best Regards, Hannah.Z

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.

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-06T12:00:01+00:00

Hello, rau1.

Thank you for visiting the Microsoft Community.

We understand the problem you are having. Your current issue appears to be a Power Query-related issue, we suggest you ask the following questions to ask questions and research:

Power Query - Microsoft Fabric Community

(Users who have the same problems as you in this area will prefer to ask questions and share their ideas.)

The experts here will provide you with more specialized solutions to your Power Query problems.

Sincere greetings

Hannah.Z- MSFT |Microsoft Community Support Specialist
Was this answer helpful?

0 comments No comments
Anonymous

2025-01-06T23:42:38+00:00

OK thanks, I've done as suggested.
Was this answer helpful?

0 comments No comments
Anonymous

2025-01-08T14:53:38+00:00

I'm having a similar issue that I only noticed towards the end of December with Excel 365 crashing whenever I edit external data properties for any type of database connection I've been using, including a legacy Microsoft Query. Excel restarts without warning and the event viewer refers to exception code 0xc0000374 with the faulting module name being ntdll.dll, version 10.0.19041.5007. Googling this isn't much help as it appears this is rather a generic issue to do with heap corruption.

I've tried an online repair of Excel, as well as running the Windows system file checker, but to no avail. I'm running Windows 10 Pro 64-bit and my Windows updates are up-to-date. I am running the 32-bit version of Excel 365 as we're still needing to access a legacy ODBC connection that only supports 32-bit.

Just today there was a new Office (AKA Microsoft) 365 update available so I've proceeded with it too, but I'm still getting the same crash in Excel.

I've tried clearing data caches and deleting temporary files, and I've also tried using a different user profile on the same computer, but also no joy.

As I'm not only getting crashes with Power Query related tables but also Microsoft Query related tables, I chose to post here rather than in the Microsoft Fabric Community forum where I see the OP did indeed raise his issue again.

At this point I'll probably wait for Tuesday's Windows updates and if those don't solve the issue, I see no other course of action other than to go through the hassle of performing a Windows reset and then reinstalling all my applications.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2025-01-09T01:26:10+00:00

Hello, rau1.

I am glad to hear your update on the problem, and hope that your problem can be solved more professionally and properly.

Best Regards,

Hannah.Z
Was this answer helpful?

0 comments No comments
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