> Source: [sk166315](https://support.checkpoint.com/results/sk/sk166315)

# sk166315 - Endpoint Security Client's Compliance blade not recognizing Windows Defender as Anti-Virus

| Property | Value |
|----------|-------|
| Solution ID | sk166315 |
| Date Created | 2020-04-13 |
| Last Modified | 2021-02-11 |
| Technical Level | General |
| Products | Endpoint Security |
| Versions | Cloud, E89.X, E88.X |

## Symptoms

- * Compliance blade is not recognizing Windows Defender as Anti-Virus.
* Machine gets restricted.

## Cause

The cause of this issue is a communication problem between the client and the server.   
The server sends the Windows Defender's name ("windefender" string) to the client,   
but the client expects another name ("win.defender" string). As a result, the client cannot recognize Windows Defender.

## Solution

This problem was fixed. The fix is included in:

* [Enterprise Endpoint Security E83.10 Windows Clients](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk166979&partition=Basic&product=Endpoint)

Check Point recommends to always [upgrade to the most recent version](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk117536).

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content