01: Return-Path: <bounce [at] go.sophos.com>
02: Received: from mail03.go.sophos.com ([]) by mx-ha.web.de
03: (mxweb010 []) with ESMTPS (Nemesis) ID: [ID filtered]
04: Received: from G06SNJ001 ( by mail03.go.sophos.com ID: [ID filtered]
05: Message-ID: [ID filtered]
06: X-Binding: 1777052651
07: X-elqSiteID: [ID filtered]
08: X-elqPod: 0x08083CD36F251DD373F9326EE7F29C21DA6F2F933E1C81064B1EB4C263C89E63
09: X-cID: [ID filtered]
10: List-Unsubscribe: <http://app.go.sophos.com/e/u?[UNSUB filtered]>
11: MIME-Version: 1.0
12: From: "Sophos" <news [at] sophos.com>
13: To: xxx [at] xxx
14: Reply-To: "DACH Partner Alias" <partner [at] sophos.de>
15: Date: 11 Apr 2019 xx:xx:xx -0400
16: Subject: Windows security update can cause computers running Sophos Endpoint on select
17: O/S versions to fail or hang on reboot
18: Content-Type: multipart/alternative; boundary=--boundary_x
19: Envelope-To: <xxx [at] xxx>

Dear Sophos Partner bin ich nicht,
Microsoft has released security updates that are impacting some security AV vendors, causing some of their customers using Windows 7, Windows 8.1, Windows 2008 R2, and Windows 2012 nutze ich nicht to occasionally experience system fails or hangs during boot up after application of the update.
A small number of Sophos customers bin ich nicht have reported experiencing this issue. Sophos is working very closely with Microsoft to resolve the issue. Microsoft has introduced a temporary block to stop computers not already affected from applying the latest Windows security update. Additionally, we have a work around for those impacted customers.
How do I know if my customer is impacted?
To be impacted, customers must meet all the criteria below. If they do not meet all the criteria, then they are not impacted.
1. Running Windows 7, Windows 8.1, Windows 2008 R2, or Windows 2012 nutze ich nicht
2. Running any Sophos Windows endpoint or server product except Sophos Central Intercept X nutze ich nicht. (Note: this does impact Intercept X Advanced and Intercept X Advanced with EDR.)
3. Have applied the latest Windows security update and have rebooted after the update is complete
Important note: If customers have not yet rebooted, they should uninstall the latest Microsoft security update before rebooting
As the majority of Sophos customers do not seem to be affected, it is possible that during the ongoing investigation additional criteria will be added to further limit the scope of impacted customers. KBA 133945 will continue to be updated with the latest information.
How do I help an impacted customer?
The latest information about this issue and remediation steps are documented in KBA 133945.
We are notifying all Sophos Endpoint customers via email to inform them of this situation. The KBA will continue to be updated with the latest information.
Your Sophos Team
Es gab wohl in der Tat Schwierigkeiten wie oben beschrieben, doch da ich weder die Windows-Versionen noch diese Sophos-Software nutze, scheint es mit der Datenbankpflege nicht weit her zu sein und von daher mag ich gar nicht erst auf die Softwarepflege schließen