Is there an issue with Sophos Intercept X and Internet Explorer 11?

We have seen Internet Explorer crash on every machine we install Sophos Interecpt X on. All of the Computers are Windows 10 (ver 1709).

 

We have had to change main browsers because of the constant crashing. On first opening it crashes on my own machine everytime. I have checked the LoadAppInit_DLLS in the registry and both are 0 (following on from another thread I read here).

 

Any idea what to try?  I have gathered some dumps of the crashes but don't have the experience to look at them.

 

Thank you

N@

  • Today I am on Windows Version 1803 with Sophos Intercept X Version 2.0.3.

     

    I must admit that IE is now working a lot better. I have not had any "crashes" like before, but because I have left the ProcDump running in the background it keeps logging issues while I am using IE.

     

    If I didn't have the log going I wouldn't notice any issues.

     

    I tested upgrading to Intercept X 2.0.3 when I had 1709 and this was still crashing.

     


     

    Can anyone else test:

     

    Windows Version: 1803

    Intercept X Version: 2.0.3

     

    More information about Sophos versions: http://downloads.sophos.com/readmes/sesc_interceptx_rneng.html

  • In reply to Natalie Evans:

    The latest Windows feature (1803) update is making its way through the company - My machine has updated and Sophos is now up-to-date.

    I though I would test Internet Explorer 11 with enhanced protection enabled to see if it still crashes.

    It is better and I am not seeing the 'Internet Explorer is not responding' message however occasionally it does crash and I get the message saying 'A problem caused the page to re-open'.

    Then usually a message saying that it was unable to return it the webpage.

    When I disable enhanced protection it works fine with no crashes.

    So to summarise: Better but still not fixed.

  • In reply to Daniel Mortimore:

    Daniel Mortimore

    The latest Windows feature (1803) update is making its way through the company - My machine has updated and Sophos is now up-to-date.

    ...

    So to summarise: Better but still not fixed.

     

    This has been my experience as well.

  • Just had a message from Sophos that the IE11 fix will be with Sophos update 2.0.4 in the next couple of weeks.

    Here's hoping.

  • In reply to Natalie Evans:

    I agree with Natalie on this one. I recently updated my Windows 10 version to 1803 and have not experienced a IE11 crashed since the upgrade. I was previously on 1709 and I felt like every time a site had enhanced flash or java scripts within the site, IE would crash and display IE has stopped responding.

     

    I've been on 1803 since it was released and again haven't ran into that issue not once since the upgrade. I hope 2.0.4 will fix the issue on previous versions of 1803 because 1709 was a big issue with this.

  • In reply to Daniel Mortimore:

    Daniel Mortimore

    Just had a message from Sophos that the IE11 fix will be with Sophos update 2.0.4 in the next couple of weeks.

    Here's hoping.

     

     

    Thank you for letting us know, I will test this when it is out!

     

    N@

  • To update everyone on this thread:

    An advisory has just been released for this. The fix is currently in development and will be pushed out to Central customers by the end of May 2018.

    Regards,

  • In reply to FloSupport:

    All 

    I have rolled out the latest Intercept X client to a limited test group and initial results are prominsing.  Has anyone fully deployed 2.0.5?

    Thanks

    Kevin

  • In reply to kevin Whiteman:

    Hi Kevin,

     

    After testing with 2.0.4 on myself I then enabled the extra protection settings to everyone.

    We are now on Intercept X 2.0.5.2 and all is still fine.

  • In reply to kevin Whiteman:

    We currently have Sophos Intercept X 2.0.5 with IE 11.112.17134.0 installed on our network

     

    More information about Sophos versions: http://downloads.sophos.com/readmes/sesc_interceptx_rneng.html

     

    I have tried to "break/Crash" IE this morning and I can't; before it was obvious within minutes that it was not working properly. Unfortunately because this issue took so long to fix, most of our users have moved to alternate browsers which means it hasn't been thoroughly tested.

     

    Everything seems to now be ok....

  • In reply to Natalie Evans:

    It works on our end also. It only took 5 months to Sophos to resolve the issue </irony>.

    To Sophos: I think a 5 months credit is in order to all your affected customers. We were literally unable to use InterceptX on all our computers for 5 months.

  • In reply to David Kirouac:

    Works for me also, all users that had crashes multiple times per day haven't had any issues after the fix.  I completely agree about the credit.