Outlook 2016 Crashing When Closing Minimized Messages

Topic

New Reply

Outlook 2016 (up-to-date) on W10 Pro reproduceably crashes when I click on the taskbar (I’m using Classic Shell) and use the “X Close Window” option there. If I click on the icon to restore it and then click on the X-box, there is no problem.

Any ideas?

Reply | Quote

Replies

What happens if you try it without Classic Shell?

Which version of Win10? Is it up-to-date with patches?

--Joe

Reply | Quote

W10 is not quite up-to-date. For some reason, the March 2017 updates have not shown up on my machine yet. OTOH, I just did an update of Office which appeared to be successful.

I’ll need to see if I can temporarily turn off Classic Shell.

BTW, I should not that this has been a problem for some time — a few months. It was not always so, but started long after I started using the Outlook/Classic Shell combo. The *other* Outlook problem I posted about (searching failing) is new within the past 2-3 weeks.

Reply | Quote

Have you tried running Outlook with addins disabled?

--Joe

Reply | Quote

I did and it did not solve the problem.

Interestingly, I have noticed something else: When the Outlook message in minimized and I close it from the taskbar, it seems to work — I tried 18 times and had no crashes. But when the message is in an open window and I close it from the taskbar, it crashes — 14 tries, 5 crashes. I’m not sure this is statistically significant, but it’s certain suspicious. (I reported the messages as minimized, since they were not visible, but they were probably just hidden behind other windoes — I tend to have Chrome open full screen on one screen and Outlook on the other, also full screen — both acting more-or-less as a desktop.

This does seem to implicate Classic Shell, but I’ve been able to find no reports of my problem. I’ll keep poking at it.

Reply | Quote

I rebooted with Classic Shell turned off — I do hate the native W10 start menu! — and it made no difference. Outlook crashed the second time I closed an message from the taskbar.

Reply | Quote

Have you checked the event log or reliability history?

--Joe

Reply | Quote

Now I have. I can’t make sense of it. I triggered the Outlook crash and got several events which seem related.
In the Application log, I get an error:
–
–

1000
2
100
0x80000000000000

30981
Application
mlos-pc

–
OUTLOOK.EXE
16.0.7870.2024
58bf8d83
OUTLOOK.EXE
16.0.7870.2024
58bf8d83
013856d3
005666c9
4700
01d2a01bcacae1ff
C:Program Files (x86)Microsoft OfficerootOffice16OUTLOOK.EXE
C:Program Files (x86)Microsoft OfficerootOffice16OUTLOOK.EXE
807e1e1e-0c3a-11e7-82db-d053491eaa12

Followed 7 or 8 seconds later by an Information:
–
–

1001
4
0
0x80000000000000

30982
Application
mlos-pc

–
108787062024
1
APPCRASH
Not available
0
OUTLOOK.EXE
16.0.7870.2024
58bf8d83
OUTLOOK.EXE
16.0.7870.2024
58bf8d83
013856d3
005666c9

\?C:UsersmloAppDataLocalTemp{447B1722-6C66-49AE-8691-888088D195D9} – OProcSessId.dat \?C:ProgramDataMicrosoftWindowsWERTempWERAEA.tmp.WERInternalMetadata.xml
C:ProgramDataMicrosoftWindowsWERReportArchiveAppCrash_OUTLOOK.EXE_896ae530a1d142c5f179dc60a47fff8ae3ec_00000000_2eb62846

0
807e1e1e-0c3a-11e7-82db-d053491eaa12
0
544c37a1dd8c1f6b78427e013ebbae13

I also got an Audit Success event in Security.

I’ve Googled some of the codes, but I find nothing that strikes me as related.

Reply | Quote

That isn’t much help. Have you tried a repair of Office 365?

--Joe

Reply | Quote

No. That sounds like a good idea, but I need to get my indexing problem solved, first.

Reply | Quote

It’s not unusual: Outlook 2016 crashes when I right click on message window in task bar and close

You could try Disable hardware graphics acceleration at File, Options, Advanced, Display: Outlook 2016 keeps on crashing (Windows 10)

Reply | Quote

“You could try Disable hardware graphics acceleration at File, Options, Advanced, Display: ”

Unfortunately, that does not work.

Reply | Quote

I don’t believe it is Classic Shell, because I also use that, plus Office 365 (with hardware graphics acceleration enabled) and Windows 10 1607, and I don’t have the problem. I can do exactly as described, and it just works as expected. My W10 is fully up to date, and is the Home version rather than Pro, but I don’t see that as significant.. Is your Classic Shell up to date? Mine is version 4.3.0.0.

Reply | Quote

Bundaburra — I’m running 4.3.0. In any event, I think I ruled out Classic Shell. I stopped Classic Shell and was still able to reproduce the problem.

Reply | Quote

mlo – if it works for me and not for you, then there is some other difference. I doubt that the Windows 10 level (Pro or Home) would be significant, but you mentioned that yours is not quite up to date? I also doubt that this would be a factor, but would be worth attention. I think we are both using Office 365, and currently I have version 1702, build 7870.2024 – but this changes from time to time, so again should not be significant. But possibly yours is corrupted, in which case a Repair, or even a complete reinstall, could help. Or it could come to what other software or programs that you have running at the time – you could have something else running which causes interference? Using Task Manager or Process Explorer, you could progressively shut down other tasks and see if the problem goes away. Another possibility is your scheduled tasks: have a look in the Task Scheduler, and temporarily stop and disable anything you see in there.

As the crash occurs when you try to close a message, it could also be something to do with the pst file. Two possibilities here: (1) some other program is also looking at it, and (2) the file is corrupted. For (1) you can use “Opened Files View” from Nirsoft; for (2) you could try the SCANPST tool, which you should have at “C:Program Files (x86)Microsoft OfficerootOffice16SCANPST.EXE”.

Reply | Quote

Basically classic shell is no use in windows 10 because it is having inbuilt features to use windows start menu. I don’t understand what brought you to install classic shell inspite you have an inbuilt start menu.
I have gone through all the above steps and felt that it has nothing to do with graphics nor with the updates.

My users had the same problem on two computer and I found that there are certain steps to disable to start items like addons and that helps your outlook to open with out any issue. It is something similar to open outlook in safemode
If you cannot easily fix the issues, you can ask some expert help with Microsoft ProSupport at http://www.microsoftprosupport.com/unable-start-outlook-upgrading-windows-10/

I am hoping it should resolve your issue

Reply | Quote

I’m going to mark this “solved.” I developed problems with my video card which caused random crashes. Dell swapped out both the motherboard and the video card, but not before it scrambled the Windows 10-1607 update. I was forced to reinstall the OS (keeping data) and the apps.

Somewhere along the line, this problem went away. It seems likely that one of the reinstalls fixed it.

Reply | Quote