Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 6 subscribers
  • Views 4885 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

Windows 10 v1903 Logoff issues

Mark Lobsinger

Hello,

We are testing Windows 10 V1903.

When we logoff from the Windows 10 Desktop it goes to a Black screen and the computer is unresponsive, can't even ping the desktop.   A hard reboot is necessary to get back in.   At first I thought it was video card related but same thing happened on 4 different machines.    When we uninstall the Sophos Endpoint, windows acts as it should and logging off is possible.

I have seen the memory issues with regards to V1903 but not this.   Has this been reported and is it an issues with anyone else?

I have created a ticket.

Thanks again,

Mark



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

    I've not seen or heard of this issue.  Do you see the issue if you turn off realtime scanning for example?

    Which components do you have installed?  SAV and IntercepX?

    Typically with these issues the approach is either elimination of components/through policy changes or stopping/unloading services/drivers.  This can narrow it down to perhaps offer a workaround/acceptable exclusion, etc..

    Or

    Setup the computer to create a full mem dump on keyboard combination as per:
    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/forcing-a-system-crash-from-the-keyboard

    From the dump it is then possible to analyze what the Sophos components are doing and if they are the cause of the hang.  It's easier for Support/Dev with symbols but it's possible to get a rough idea which components/files/processes are involved.


    Regards,
    Jak

Reply
  • 0

    I've not seen or heard of this issue.  Do you see the issue if you turn off realtime scanning for example?

    Which components do you have installed?  SAV and IntercepX?

    Typically with these issues the approach is either elimination of components/through policy changes or stopping/unloading services/drivers.  This can narrow it down to perhaps offer a workaround/acceptable exclusion, etc..

    Or

    Setup the computer to create a full mem dump on keyboard combination as per:
    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/forcing-a-system-crash-from-the-keyboard

    From the dump it is then possible to analyze what the Sophos components are doing and if they are the cause of the hang.  It's easier for Support/Dev with symbols but it's possible to get a rough idea which components/files/processes are involved.


    Regards,
    Jak

Children
Unfiltered HTML