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

Sophos causing Windows 10 1909/2004 task sequence to freeze

I am deploying Windows 10 1803, 1909 and 2004 via SCCM 2002.

The 1803 Task sequence (TS) works completely fine like expected, however when I try to install Sophos on 1909 or 2004, the next step after Sophos will freeze. After a reboot I can see that Sophos is installed correctly, but the stuck step has not installed. There is no events in the Sophos client that would indicate any issues. Please see the below screenshot of the TS.

This also happens when doing in In-place upgrade to 1909 and 2004 as well. As Sophos is already installed before the task sequence starts so I have been able to disable Sophos and then the TS runs fine. When I don't disable Sophos, after the task sequence is upgraded to Windows 10 1909/2004 it gets stuck after the reboot, see below screenshot.

Has anybody had any similar experiences to this?

Sophos versions currently used:

Core Agent 2.7.8

EndPoint Advanced 10.8.7

Intercept X 2.0.17

This thread was automatically locked due to age.

0 Yashraj S over 4 years ago

Hi Daniel Bolton

This thread needs to be moved to the Intercept X Forums. Please subscribe to that group so that I can move this thread there for better assistance and discussion.

Thanks,

Yashraj Singha
Manager | Global Community Support
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question, please use the "Verify Answer" button.

The New Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
0 Daniel Bolton over 4 years ago in reply to Yashraj S

I am now subscribed.
Cancel
Vote Up 0 Vote Down

Cancel
0 jak over 4 years ago

Out of interest, does it work, the in place upgrade if you disable real-time scanning before the upgrade takes place?

Are there any SCCM logs that indicate what is happening at the client?

Regards,

Jak
Cancel
Vote Up 0 Vote Down

Cancel
0 Daniel Bolton over 4 years ago in reply to jak

Hi Jak,

Unfortunately there are no SCCM logs that seem to be out of place - it's just like it suddenly stops and nothing is working anyone, until I reboot the machine.

I will try disabling the real-time scanning for the in-place upgrade. I have a ticket logged with Sophos and we've tried disabling Exploit mitigation and AMSI Protection - which haven't worked yet.

Thank you for your help.

Thanks, Dan.
Cancel
Vote Up 0 Vote Down

Cancel