Excel 2016 (Protected Mode) Crashing When Opening Files From Email

Anonymous
2015-09-29T23:14:57+00:00

Has anyone else encountered this problem?

  • Receive an Excel file in email (both GMail and (desktop) Outlook 2016 (using a live.com account, not a GMail one) have been tested);
  • Double click on it to open it. (Excel 2016 is already open);
  • The file opens in Excel with that irritating little "Oooooh, very dangerous! Could be scary monsters inside!" message which, I'll admit, is potentially useful for files from outside the organisation which is the only reason that I leave it on. Of course, there's no point if it doesn't actually work.

Then one of two things happens. Either

  • You go to click the Enable Editing button and Excel completely hangs on you; or
  • You get the "Excel (Protected Mode) {breathless pause...} Has! Stopped! Working! Pretending to check for a solution that has never once been found in my lifetime, please waste your time waiting" dialog.

There is nothing wrong with the file itself. I have tried with two different files, both have a problem. In both cases if instead of opening them from the Email application I save them to a trusted location I can open them without problem. But opening them directly from either browser or Outlook completely crashes Excel 2016 in a way that it didn't with Excel 2010.

Anyone else?

PS: If anyone from Microsoft responds to this post, looking into this specific question, I'll be more than happy to listen. If instead they copy and paste a script about restarting Windows in Safe Mode I may just need to throw a shoe at something.

Microsoft 365 and Office | Excel | For home | Windows

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 No comments
Answer accepted by question author
Anonymous
2015-11-10T23:39:54+00:00

I just heard back from a displaylink tech support person.  Apparently they are aware of the issue.  He had me do a work around that has fixed the issue for me.

  1. Open a blank excel document.
  2. Go to file

3.  Go to options

  1. Go to advanced
  2. Under Display
  3. Check the box...Disable graphics hardware acceleration.

7.  Click apply.

This has fixed my issue until there is a driver update.

Thanks...Matt

Was this answer helpful?

80+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2016-02-24T04:16:51+00:00

Updated to displaylink driver 7.9m5 dated 2/23/2016 and problem was resolved for me.

Was this answer helpful?

10+ people found this answer helpful.
0 comments No comments

88 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-10-18T02:27:20+00:00

    I just heard back from a display link tech support person.  Apparently they are aware of the issue.  He had me do a work around that has fixed the issue for me.

    1. Open a blank excel document.
    2. Go to file

    3.  Go to options

    1. Go to advanced
    2. Under Display
    3. Check the box...Disable graphics hardware acceleration.

    7.  Click apply.

    This has fixed my issue until there is a driver update.

    I did that, but no help, still crash on my Excel 2016, work normally on other colleagues' PC.

    Thanks for guide,

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-08-30T19:07:37+00:00

    Well spotted. Thanks for sharing.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-04-29T03:51:19+00:00

     I tried to find the details of the patches that had been done since then, but the relevant page only has details of upgraded features, not bug fixes. (Perhaps there aren't any bugs in Office. Stop laughing everyone.)

    FYI looks like you can see details of bug fixes here: https://technet.microsoft.com/en-us/office/mt465751?f=255&MSPPError=-2147217396

    This is linked from the 'For a complete list of all of the updates and changes, check this page' links on the main 'What's New and Improved in Office' page you linked above. Even then though, I can't find specifics of a fix for this issue.

    Was this answer helpful?

    0 comments No comments