Thread Info
  • Locked Locked
  • Replies 6 replies
  • Subscribers 16 subscribers
  • Views 31806 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Intercept-X on Windows 7 x64 crashes Excel and Winword 2016

Markus Kleinlercher

On a client's Win7 machine the installation of Intercept-x (with Sophos Endpoint Agent 11.5.3) crashes Excel and Winword 2016 (Office 365 16.0.7678.2074).

Eventlog (sorry German...):

Name der fehlerhaften Anwendung: EXCEL.EXE, Version: 16.0.7668.2074, Zeitstempel: 0x588df37c
Name des fehlerhaften Moduls: mso20win32client.dll, Version: 0.0.0.0, Zeitstempel: 0x588d4641
Ausnahmecode: 0x0004e453
Fehleroffset: 0x000fd3a8
ID des fehlerhaften Prozesses: 0x166c
Startzeit der fehlerhaften Anwendung: 0x01d2831bdaf22978
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Microsoft Office\root\Office16\EXCEL.EXE
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll
Berichtskennung: 18d3b813-ef0f-11e6-8858-3417ebccf615

 

After uninstalling Intercept-X Excel and Winword work fine again.

Has anybody else this problem or a solution?



This thread was automatically locked due to age.
Parents

  • I've had a similar issue with Office 2013.  The way I have gotten around it for now is to uncheck the "Use recommended settings" option in the base policy.  From there, I was then able to scroll down and uncheck the option to "Protect office applications."  After applying the policy, and updating the client, Word and Excel would launch fine.

     

    This isn't the way I want to leave things.  What could we be missing that is causing Office applications to crash?

  • in reply to MatthewShafer

    MatthewShafer said:

    I've had a similar issue with Office 2013.  The way I have gotten around it for now is to uncheck the "Use recommended settings" option in the base policy.  From there, I was then able to scroll down and uncheck the option to "Protect office applications."  After applying the policy, and updating the client, Word and Excel would launch fine.

     

    This isn't the way I want to leave things.  What could we be missing that is causing Office applications to crash?

     

     

    Matthew, you are a lifesaver.  We had the exact same issue going on, and this fixed the issue.  I hope Sophos takes note, so we can get this working correctly.  

Reply
  • in reply to MatthewShafer

    MatthewShafer said:

    I've had a similar issue with Office 2013.  The way I have gotten around it for now is to uncheck the "Use recommended settings" option in the base policy.  From there, I was then able to scroll down and uncheck the option to "Protect office applications."  After applying the policy, and updating the client, Word and Excel would launch fine.

     

    This isn't the way I want to leave things.  What could we be missing that is causing Office applications to crash?

     

     

    Matthew, you are a lifesaver.  We had the exact same issue going on, and this fixed the issue.  I hope Sophos takes note, so we can get this working correctly.  

Children
No Data
Unfiltered HTML