mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 11:53:37 +00:00
Merge pull request #6701 from MaratMussabekov/patch-146
added registry keys
This commit is contained in:
@ -22,7 +22,7 @@ ms.custom: nextgen
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
|
||||
|
||||
Block at first sight is a feature of next-generation protection that provides a way to detect and block new malware within seconds. This protection is enabled by default when certain prerequisite settings are also enabled. In most cases, these prerequisite settings are also enabled by default, so the feature is running without any intervention.
|
||||
Block at first sight provides a way to detect and block new malware within seconds. This protection is enabled by default when certain prerequisite settings are also enabled. In most cases, these prerequisite settings are also enabled by default, so the feature is running without any intervention.
|
||||
|
||||
You can [specify how long the file should be prevented from running](configure-cloud-block-timeout-period-windows-defender-antivirus.md) while the cloud-based protection service analyzes the file. And, you can [customize the message displayed on users' desktops](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-security-center/wdsc-customize-contact-information) when a file is blocked. You can change the company name, contact information, and message URL.
|
||||
|
||||
@ -117,14 +117,28 @@ For a list of Windows Defender Antivirus device restrictions in Intune, see [Dev
|
||||
|
||||
If you had to change any of the settings, you should re-deploy the Group Policy Object across your network to ensure all endpoints are covered.
|
||||
|
||||
### Confirm block at first sight is enabled with the Windows Security app
|
||||
### Confirm block at first sight is enabled with Registry editor
|
||||
|
||||
You can confirm that block at first sight is enabled in your Windows security settings.
|
||||
1. Start Registry Editor.
|
||||
|
||||
Block at first sight is automatically enabled as long as **Cloud-delivered protection** and **Automatic sample submission** are both turned on.
|
||||
2. Go to **HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows Defender\Spynet**, and make sure that
|
||||
|
||||
1. **SpynetReporting** key is set to **1**
|
||||
|
||||
2. **SubmitSamplesConsent** key is set to either **1** (Send safe samples) or **3** (Send all samples)
|
||||
|
||||
3. Go to **HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows Defender\Real-Time Protection**, and make sure that
|
||||
|
||||
1. **DisableIOAVProtection** key is set to **0**
|
||||
|
||||
2. **DisableRealtimeMonitoring** key is set to **0**
|
||||
|
||||
### Confirm Block at First Sight is enabled on individual clients
|
||||
|
||||
You can confirm that block at first sight is enabled on individual clients using Windows security settings.
|
||||
|
||||
Block at first sight is automatically enabled as long as **Cloud-delivered protection** and **Automatic sample submission** are both turned on.
|
||||
|
||||
1. Open the Windows Security app.
|
||||
|
||||
2. Select **Virus & threat protection**, and then, under **Virus & threat protection settings**, select **Manage Settings**.
|
||||
|
Reference in New Issue
Block a user