Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 14 subscribers
  • Views 13912 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

New Endpoint and intercept X Install - Office 365 getting SysCall blocked on all apps

John Maki

After i installed the software now Excel, Outlook, Internet Explorer etc all get blocked for "'SysCall' exploit prevented in IE". I can add a global application exception, but that doesn't solve the issue as it leaves the office apps unprotected.

 

Windows 10

Office 365

Intercept X - 3.6.14



This thread was automatically locked due to age.
Parents
  • 0

    The number of affected users who cannot start Outlook is growing. Some of them can get Outlook to start by rebooting their PC. Others have to wait until I can restart their HitmanPro.Alert service. 

    Sophos support -- I'm still waiting for a follow-up call from the escalation engineer. My case number is 7837673.

Reply
  • 0

    The number of affected users who cannot start Outlook is growing. Some of them can get Outlook to start by rebooting their PC. Others have to wait until I can restart their HitmanPro.Alert service. 

    Sophos support -- I'm still waiting for a follow-up call from the escalation engineer. My case number is 7837673.

Children
  • 0 in reply to JoeStern

    Not sure if you got your issue resolved in the meantime. For Office365 slowness or inability to start - try one to exclude the "OfficeClickToRun.exe" Process from O365 from AV scanning (not Exploits)

    I found in one case a client running O365, Intercept X together with a 3rd party AV solution. In my case Opening of a small Excel document out of Outlook took up to a minute (or even longer) on a affected client- without any visible hint or obvious reason, and office programs startup.

    No idea why, but after (File or Folder (Windows)) excluding the OfficeClickToRun.exe process, which usually is found under "C:\Program Files\Common Files\microsoft shared\ClickToRun\" those client the Office 365 programs started quickly, and opening of the documents was quick as expected.

    Maybe it might work for the one or other guy here in the forum too.

    There also might also be other ClickToRun issues if I read posts like this here:M$ Technet Forum about a CLR issue

    /Sascha

Unfiltered HTML