FIXMAPI 1.0 MAPI Repair Tool has stopped working

Anonymous
2017-07-24T15:57:30+00:00

I have a user that is running Windows 10. We are using Office 365. She is trying to send an snip from the snipping tool through email. However when she sends it she get the FIXMAPI 1.0 MAPI Repair Tool has stopped working. The email still goes through but the popup message is annoying. 

I have searched and looked through other topics and the suggestions have not worked for this. I have renamed the MAPI32.dll and ran the fixmapi.exe and that has not resolved the issue. I have ran an online repair on the Office 365 and that also has not fixed the issues. Any suggestions on what to look at to resolve this issue?

Microsoft 365 and Office | Install, redeem, activate | 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
Answer accepted by question author
Anonymous
2017-08-23T12:04:34+00:00

Good morning, all!

We opened a support case with Microsoft.  Here is the information on the fix for this issue.  It looks like fix won't be released until September.  I just wanted to share.  

From Microsoft:

We have received another related incident like this and there is a fix that has been put into build 16.0.8420.100. However, the fix is not available at the moment but you can check our site for availability.

Version and build numbers of update channel releases

https://support.office.com/en-us/article/Version-and-build-numbers-of-update-channel-releases-ae942449-1fca-4484-898b-a933ea23def7?ui=en-US&rs=en-US&ad=US

Was this answer helpful?

3 people found this answer helpful.
0 comments

54 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-08-04T18:44:13+00:00

    We have the following groups setup:

    Production Group: 16.0.7870.2031

    Test Group: 16.0.8229.2073

    Those in the production group are not seeing this issue while those in the test group are. We have tried running Outlook in safe mode to rule out any third party add-in issues, but the issue still occurs.

    I have found that the error doesn't occur using 16.0.8201.2102 or lower. Its only higher versions where the problem exists.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-08-04T18:46:33+00:00

    We have the following groups setup:

    Production Group: 16.0.7870.2031

    Test Group: 16.0.8229.2073

    Those in the production group are not seeing this issue while those in the test group are. We have tried running Outlook in safe mode to rule out any third party add-in issues, but the issue still occurs.

    its seems that version 16.0.8201.2102 and lower are fine. Its higher versions where the problem occurs

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-08-07T19:30:18+00:00

    Same issue...using Win 7 and 365 with Snipping Tool.

    Also happening when trying to email a PDF by right-clicking on the document name and using the "send-to" "mail recipient" option.

    Maybe a problem with 3rd party apps with "direct to email" option?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-08-07T20:36:56+00:00

    We are also seeing this on a mass scale across the PCs on our network. We are running:

    Windows 7 Enterprise x64

    Office build: 1707.8326.2062

    As others have stated, this problem has come up once updating our Office client as it doesn't happen with a clean install.  One thing that we noted is when going to the O365 portal while logged in as any of our users, then click "Install Office" from there.  It works just fine.  We can confirm this with  2 PCs, one of which has our deployment, the other with an install from the O365 Portal, each on version number 1707.8326.2062.  The one from our deployment will crash w/ "FIXMAPI" error, the one that is downloaded from the portal works fine. 

    The only difference between our deployment is that during install we have it pointed to an .xml file for install configs.  I'm curious if anyone else who is experiencing this issue is using an .xml file for installs as well.

    Was this answer helpful?

    0 comments