Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
It crashes in Safe Mode too.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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:
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?
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
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.
It crashes in Safe Mode too.
@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
... and here's another one to upvote: https://feedbackportal.microsoft.com/feedback/idea/495495e1-93be-472a-90dc-04fde90e81da?isPrivate=true
I have the same issues, seems support also cant seem to help: When going into an excel document with active connection, as soon as I select the table or connection itself and press properties then excel stop responding. Anyone having a resolution for this?
Already tried al the overall actions line repair, safe mode, disabling add ins, setting up clean connection, re-installation, check licensing etc.
I tried a lot of things:
Event Viewer says: Faulting module name: ntdll.dll
ntdll.dll is responsible for a few things like memory management, error handling, etc.I got the exception error code c0000374 which indicates a heap corruption error, meaning memory corruption, bad drivers, or software conflicts.
Heap corruption errors can be caused by many system-level things like corrupt updates, but running both mentioned commands would have solved this if so.
What actually worked: running Excel in Win 8 compatibility mode.
I found when it crashed it was trying to find:
HKCU\Software\Classes\Wow6432Node\CLSID\{7B8A2D94-0AC9-11D1-896C-00C04FB6BFC4}
So, perhaps Win 8 compat. mode looked elsewhere for this (HKLM), and the CLSID existed there.
Merging this across to HKCU alone didn't fix the issue if ran w/o Win8 compat. mode so I guess there is a lot more to this; maybe there are other missing reg paths, or the compatibility mode bypasses security checks, maybe older DLLs in use also.