
Microsoft is working to resolve a known issue that causes its Defender for Endpoint Enterprise Endpoint Protection platform to incorrectly tag SQL Server software as end-of-life.
according to a service alert Spotted by BleepingComputer, this bug has been affecting Microsoft Defender XDR customers with SQL Server 2017 and 2019 since at least Wednesday morning.
While Defender has marked the software as no longer supported, SQL Server 2019 has Supported until January 2030While SQL Server 2017 has reached the end of extended support in October 2027Two years from now.
The company has already deployed a fix to address the bug and said that the root cause is a code issue caused by a recent change in the end-of-support software.
“Users who installed SQL Server 2019 and 2017 may see incorrect tagging within Threat and Vulnerability Management. Users may experience incorrect end-of-life tagging for SQL Server within Microsoft Defender for Endpoint Management,” Microsoft said Thursday morning, about 24 hours after the issue was confirmed.
“We are continuing to deploy a fix that is designed to reverse the offending change that introduced the code problem and will provide a timeline for completion as soon as it is available.”
Although Microsoft noted that the issue “may affect all users who have SQL Server 2017 and 2019 installed,” it has not yet provided further details on the extent of the problem.
However, this ongoing incident has been tagged as an advisory, a designation commonly used to describe a service issue that typically involves limited scope or impact.
Last week, the company resolved another bug that caused Endpoint Defender to incorrectly mark the BIOS firmware on some Dell devices as out of date, prompting users to update it.
Microsoft engineers also have Fixed black-screen crash affecting macOS devices Updated after September 29, which occurred due to an outage in the Apple enterprise security framework and after multiple security providers heard of the incidents.
In early September, Redmond downed another false positive, which was causing the anti-spam service to isolate emails and mistakenly prevent Exchange Online and Microsoft Teams users from opening URLs.


