We'd love to hear about it! Click here to go to the product suggestion community
does anyone have Problems with the new Windows 10 and Safe Guard Client.
I have one Client with the newest Version of Windows 10 (18.03) after Login appears a Blue Screen.
Is here someone with equal problems?
Sadly - yes I am!
Exactly the same issue.
Still doing more testing to I can narrow down what's causing it.
Did you do an inplace upgrade or a fresh clean build of 1803?
In reply to MichaelMcLannahan:
we tried both and had the same issue.
In reply to Patrick Heinz:
So did I....
What configuration version are you using?
It is the Version 8.00.2.16
Me too. However I'm also seeing this on a 1709 build I created this morning. I did do all the updates on this though before encryption, so begniing to think it may be an update included in updated 1709 and possibly part of 1803.
Can you recreate the same issue on another device?
I'm currently testing four machines - all different specs and models Dell x 2, HP x 1 and Toshiba x 1.
My own Client (1709) has the problem too but it happens not all the time (two times in a month).
It could be an Update, I think that's possible.
I have open a ticket by sophos.
Hi Patrick - To add....Have you tried disabling your network connection when logging in. I had limited success (not looked at it too long yet) when disabling the connection and preventing Sophos SafeGuard syncing with the server.
No we didn't tried this.
But for a normaly User impossbile to manage.
I hope the Sophos Support has an idea to resolve this Problem.
I know - I'm not suggesting it as a solution or a fix, just interested to know if it's comms/sync with the server that causes the BSOD.
I have also launched a ticket.
Many thanks and good luck!
If you have opened a Sophos Support Ticket, please do share the support ticket number and I will look into the case.
In reply to Haridoss Sreenivasan:
My Ticket Number is 8097102
and mine - 8097558
there is a new KBA regarding this topic:
Have a nice weekend
In reply to Funkey:
Thanks Funkey, much appreciated
To add to this case I spent all yesterday trying to reproduce this on a local account with 1803. I couldn’t get it to do it. Will continue testing on Monday and will bind the machine to the domain.