Skip to content

Commit 3c24b18

Browse files
committed
Improved Acrolinx score
1 parent a71a31b commit 3c24b18

6 files changed

+40
-41
lines changed

defender-endpoint/configure-block-at-first-sight-microsoft-defender-antivirus.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ search.appverid: met150
3232
This article describes an antivirus/antimalware feature known as "block at first sight", and describes how to enable block at first sight for your organization.
3333

3434
> [!TIP]
35-
> This article is intended for enterprise admins and IT Pros who manage security settings for organizations. If you are not an enterprise admin or IT Pro but you have questions about block at first sight, see the [Not an enterprise admin or IT Pro?](#not-an-enterprise-admin-or-it-pro) section.
35+
> This article is intended for enterprise admins and IT Pros who manage security settings for organizations. If you aren't an enterprise admin or IT Pro but you have questions about block at first sight, see the [Not an enterprise admin or IT Pro?](#not-an-enterprise-admin-or-it-pro) section.
3636
3737
## What is "block at first sight"?
3838

@@ -57,9 +57,9 @@ Microsoft Defender Antivirus uses multiple detection and prevention technologies
5757
5858
## A few things to know about block at first sight
5959

60-
- Block at first sight can block non-portable executable files (such as JS, VBS, or macros) and executable files, running the [latest Defender antimalware platform](microsoft-defender-antivirus-updates.md) on Windows or Windows Server.
60+
- Block at first sight can block nonportable executable files (such as JS, VBS, or macros) and executable files, running the [latest Defender antimalware platform](microsoft-defender-antivirus-updates.md) on Windows or Windows Server.
6161

62-
- Block at first sight only uses the cloud protection backend for executable files and non-portable executable files that are downloaded from the Internet, or that originate from the Internet zone. A hash value of the `.exe` file is checked via the cloud backend to determine if the file is a previously undetected file.
62+
- Block at first sight only uses the cloud protection backend for executable files and nonportable executable files that are downloaded from the Internet, or that originate from the Internet zone. A hash value of the `.exe` file is checked via the cloud backend to determine if the file is a previously undetected file.
6363

6464
- If the cloud backend is unable to make a determination, Microsoft Defender Antivirus locks the file and uploads a copy to the cloud. The cloud performs more analysis to reach a determination before it either allows the file to run or blocks it in all future encounters, depending on whether it determines the file to be malicious or not a threat.
6565

@@ -98,7 +98,7 @@ Microsoft Defender Antivirus uses multiple detection and prevention technologies
9898
3. In the MAPS section, double-click **Configure the 'Block at First Sight' feature**, and set it to **Enabled**, and then select **OK**.
9999

100100
> [!IMPORTANT]
101-
> Setting to **Always prompt (0)** will lower the protection state of the device. Setting to **Never send (2)** means block at first sight will not function.
101+
> Setting to **Always prompt (0)** lowers the protection state of the device. Setting to **Never send (2)** means block at first sight won't function.
102102
103103
4. In the MAPS section, double-click **Send file samples when further analysis is required**, and set it to **Enabled**. Under **Send file samples when further analysis is required**, select **Send all samples**, and then select **OK**.
104104

@@ -118,13 +118,13 @@ You can confirm that block at first sight is enabled on individual client device
118118

119119
> [!NOTE]
120120
>
121-
> - If the prerequisite settings are configured and deployed using Group Policy, the settings described in this section will be greyed-out and unavailable for use on individual endpoints.
122-
> - Changes made through a Group Policy Object must first be deployed to individual endpoints before the setting will be updated in Windows Settings.
121+
> - If the prerequisite settings are configured and deployed using Group Policy, the settings described in this section are greyed-out and unavailable for use on individual endpoints.
122+
> - Changes made through a Group Policy Object must first be deployed to individual endpoints before the setting gets updated in Windows Settings.
123123
124124
## Turn off block at first sight
125125

126126
> [!CAUTION]
127-
> Turning off block at first sight will lower the protection state of your device(s) and your network. We do not recommend disabling block at first sight protection permanently.
127+
> Turning off block at first sight lowers the protection state of your devices and your network. We don't recommend disabling block at first sight protection permanently.
128128
129129
### Turn off block at first sight with Microsoft Intune
130130

@@ -144,22 +144,22 @@ You can confirm that block at first sight is enabled on individual client device
144144

145145
1. On your Group Policy management computer, open the [Group Policy Management Console](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)), right-click the Group Policy Object you want to configure, and then select **Edit**.
146146

147-
2. Using the **Group Policy Management Editor** go to **Computer configuration** and select **Administrative templates**.
147+
2. Using the **Group Policy Management Editor**, go to **Computer configuration** and select **Administrative templates**.
148148

149149
3. Expand the tree through **Windows components** \> **Microsoft Defender Antivirus** \> **MAPS**.
150150

151151
4. Double-click **Configure the 'Block at First Sight' feature** and set the option to **Disabled**.
152152

153153
> [!NOTE]
154-
> Disabling block at first sight does not disable or alter the prerequisite group policies.
154+
> Disabling block at first sight doesn't disable or alter the prerequisite group policies.
155155
156156
## Not an enterprise admin or IT Pro?
157157

158-
If you are not an enterprise admin or an IT Pro, but you have questions about block at first sight, this section is for you. Block at first sight is a threat protection feature that detects and blocks malware within seconds. Although there isn't a specific setting called "Block at first sight," the feature is enabled when certain settings are configured on your device.
158+
If you aren't an enterprise admin or an IT Pro, but you have questions about block at first sight, this section is for you. Block at first sight is a threat protection feature that detects and blocks malware within seconds. Although there isn't a specific setting called "Block at first sight," the feature is enabled when certain settings are configured on your device.
159159

160160
### How to manage block at first sight on or off on your own device
161161

162-
If you have a personal device that is not managed by an organization, you might be wondering how to turn block at first sight on or off. You can use the Windows Security app to manage block at first sight.
162+
If you have a personal device that isn't managed by an organization, you might be wondering how to turn block at first sight on or off. You can use the Windows Security app to manage block at first sight.
163163

164164
1. On your Windows 10 or Windows 11 computer, open the Windows Security app.
165165

@@ -174,7 +174,7 @@ If you have a personal device that is not managed by an organization, you might
174174
- To disable block at first sight, turn off **Cloud-delivered protection** or **Automatic sample submission**.
175175

176176
> [!CAUTION]
177-
> Turning off block at first sight lowers the level of protection for your device. We do not recommend permanently disabling block at first sight.
177+
> Turning off block at first sight lowers the level of protection for your device. We don't recommend permanently disabling block at first sight.
178178
179179
## See also
180180

defender-endpoint/configure-notifications-microsoft-defender-antivirus.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -35,12 +35,12 @@ If you're part of your organization's security team, you can configure how notif
3535

3636
## Configure antivirus notifications using Group Policy or the Windows Security app
3737

38-
You can configure the display of additional notifications, such as recent threat detection summaries, in the [Windows Security app](microsoft-defender-security-center-antivirus.md) and with Group Policy.
38+
You can configure the display of more notifications, such as recent threat detection summaries, in the [Windows Security app](microsoft-defender-security-center-antivirus.md) and with Group Policy.
3939

4040
> [!NOTE]
4141
> In Windows 10, version 1607 the feature was called **Enhanced notifications** and was configured under **Windows Settings** \> **Update & security** \> **Windows Defender**. In Group Policy settings for all versions of Windows 10 and Windows 11, the notification feature is called **Enhanced notifications**.
4242
43-
### Use Group Policy to disable additional notifications
43+
### Use Group Policy to disable other notifications
4444

4545
1. On your Group Policy management computer, open the [Group Policy Management Console](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)).
4646

@@ -52,10 +52,10 @@ You can configure the display of additional notifications, such as recent threat
5252

5353
5. Expand the tree to **Windows components** \> **Microsoft Defender Antivirus** > **Reporting**.
5454

55-
6. Double-click **Turn off enhanced notifications**, and set the option to **Enabled**. Then select **OK**. This will prevent additional notifications from appearing.
55+
6. Double-click **Turn off enhanced notifications**, and set the option to **Enabled**. Then select **OK**. This setting prevents more notifications from appearing.
5656

5757
> [!IMPORTANT]
58-
> Disabling additional notifications will not disable critical notifications, such as threat detection and remediation alerts.
58+
> Disabling other notifications won't disable critical notifications, such as threat detection and remediation alerts.
5959
6060
### Use the Windows Security app to disable additional notifications
6161

@@ -65,20 +65,20 @@ You can configure the display of additional notifications, such as recent threat
6565

6666
3. Scroll to the **Notifications** section and select **Change notification settings**.
6767

68-
4. Slide the switch to **Off** or **On** to disable or enable additional notifications.
68+
4. Slide the switch to **Off** or **On** to disable or enable other notifications.
6969

7070
> [!IMPORTANT]
71-
> Disabling additional notifications will not disable critical notifications, such as threat detection and remediation alerts.
71+
> Disabling other notifications won't disable critical notifications, such as threat detection and remediation alerts.
7272
7373
## Configure standard notifications on endpoints using Group Policy
7474

7575
You can use Group Policy to:
7676

77-
- Display additional, customized text on endpoints when the user needs to perform an action
77+
- Display more, customized text on endpoints when the user needs to perform an action
7878
- Hide all notifications on endpoints
7979
- Hide reboot notifications on endpoints
8080

81-
Hiding notifications can be useful in situations where you can't hide the entire Microsoft Defender Antivirus interface. See [Prevent users from seeing or interacting with the Microsoft Defender Antivirus user interface](prevent-end-user-interaction-microsoft-defender-antivirus.md) for more information. Hiding notifications will only occur on endpoints to which the policy has been deployed. Notifications related to actions that must be taken (such as a reboot) will still appear on the [Microsoft Configuration Manager Endpoint Protection monitoring dashboard and reports](/configmgr/protect/deploy-use/monitor-endpoint-protection).
81+
Hiding notifications can be useful in situations where you can't hide the entire Microsoft Defender Antivirus interface. See [Prevent users from seeing or interacting with the Microsoft Defender Antivirus user interface](prevent-end-user-interaction-microsoft-defender-antivirus.md) for more information. Hiding notifications will only occur on endpoints to which the policy is deployed. Notifications related to actions that must be taken (such as a reboot) will still appear on the [Microsoft Configuration Manager Endpoint Protection monitoring dashboard and reports](/configmgr/protect/deploy-use/monitor-endpoint-protection).
8282

8383
To add custom contact information to endpoint notifications, see [Customize the Windows Security app for your organization](/windows/security/threat-protection/windows-defender-security-center/windows-defender-security-center).
8484

@@ -94,7 +94,7 @@ To add custom contact information to endpoint notifications, see [Customize the
9494

9595
5. Double-click **Suppress all notifications** and set the option to **Enabled**.
9696

97-
6. Select **OK**. This will prevent additional notifications from appearing.
97+
6. Select **OK**. This setting prevents more notifications from appearing.
9898

9999
### Use Group Policy to hide reboot notifications
100100

@@ -110,7 +110,7 @@ To add custom contact information to endpoint notifications, see [Customize the
110110

111111
5. Double-click **Suppresses reboot notifications** and set the option to **Enabled**.
112112

113-
5. Select **OK**. This will prevent additional notifications from appearing.
113+
5. Select **OK**. This setting prevents more notifications from appearing.
114114

115115
> [!TIP]
116116
> If you're looking for Antivirus related information for other platforms, see:

defender-endpoint/configure-process-opened-file-exclusions-microsoft-defender-antivirus.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ ms.date: 03/19/2024
3131
**Platforms**
3232
- Windows
3333

34-
You can exclude files that are opened by specific processes from Microsoft Defender Antivirus scans. Note that these types of exclusions are for files that are opened by processes and not the processes themselves. To exclude a process, add a file exclusion (see [Configure and validate exclusions based on file extension and folder location](configure-extension-file-exclusions-microsoft-defender-antivirus.md)).
34+
You can exclude files that are opened by specific processes from Microsoft Defender Antivirus scans. These types of exclusions are for files that are opened by processes and not the processes themselves. To exclude a process, add a file exclusion (see [Configure and validate exclusions based on file extension and folder location](configure-extension-file-exclusions-microsoft-defender-antivirus.md)).
3535

3636
See [Important points about exclusions](configure-exclusions-microsoft-defender-antivirus.md#important-points-about-exclusions) and review the information in [Manage exclusions for Microsoft Defender for Endpoint and Microsoft Defender Antivirus](defender-endpoint-antivirus-exclusions.md) before defining your exclusion lists.
3737

@@ -68,11 +68,11 @@ Two different types of process exclusions may be set. A process may be excluded
6868

6969
For example, given the process `MyProcess.exe` running from `C:\MyFolder\` the full path to this process would be `C:\MyFolder\MyProcess.exe` and the image name is `MyProcess.exe`.
7070

71-
Image name exclusions are much more broad - an exclusion on `MyProcess.exe` will exclude any processes with this image name, regardless of the path they are run from. So for example, if the process `MyProcess.exe` is excluded by image name, it will also be excluded if it is run from `C:\MyOtherFolder`, from removable media, et cetera. As such it is recommended that whenever possible, the full path is used.
71+
Image name exclusions are much more broad - an exclusion on `MyProcess.exe` excludes any processes with this image name, regardless of the path they're run from. So for example, if the process `MyProcess.exe` is excluded by image name, it will also be excluded if it is run from `C:\MyOtherFolder`, from removable media, et cetera. As such it's recommended that whenever possible, the full path is used.
7272

7373
### Use wildcards in the process exclusion list
7474

75-
The use of wildcards in the process exclusion list is different from their use in other exclusion lists. When the process exclusion is defined as an image name only, wildcard usage is not allowed. However when a full path is used, wildcards are supported and the wildcard behavior behaves as described in [File and Folder Exclusions](configure-extension-file-exclusions-microsoft-defender-antivirus.md)
75+
The use of wildcards in the process exclusion list is different from their use in other exclusion lists. When the process exclusion is defined as an image name only, wildcard usage isn't allowed. However when a full path is used, wildcards are supported and the wildcard behavior behaves as described in [File and Folder Exclusions](configure-extension-file-exclusions-microsoft-defender-antivirus.md)
7676

7777
The use of environment variables (such as `%ALLUSERSPROFILE%`) as wildcards when defining items in the process exclusion list is also supported. Details and a full list of supported environment variables are described in [File and Folder Exclusions](configure-extension-file-exclusions-microsoft-defender-antivirus.md).
7878

@@ -88,7 +88,7 @@ The following table describes how the wildcards can be used in the process exclu
8888

8989
### Contextual Process Exclusions
9090

91-
Note that a process exclusion may also be defined via a [Contextual exclusion](configure-contextual-file-folder-exclusions-microsoft-defender-antivirus.md) allowing for example a specific file to be excluded only if it is opened by a specific process.
91+
A process exclusion may also be defined via a [Contextual exclusion](configure-contextual-file-folder-exclusions-microsoft-defender-antivirus.md) allowing, for example, a specific file to be excluded only if it's opened by a specific process.
9292

9393
## Configure the list of exclusions for files opened by specified processes
9494

@@ -134,7 +134,7 @@ The following are allowed as the \<cmdlet\>:
134134
|Remove items from the list|`Remove-MpPreference`|
135135

136136
> [!IMPORTANT]
137-
> If you have created a list, either with `Set-MpPreference` or `Add-MpPreference`, using the `Set-MpPreference` cmdlet again will overwrite the existing list.
137+
> If you have created a list, either with `Set-MpPreference` or `Add-MpPreference`, using the `Set-MpPreference` cmdlet again overwrites the existing list.
138138
139139
For example, the following code snippet would cause Microsoft Defender Antivirus scans to exclude any file that is opened by the specified process:
140140

@@ -166,7 +166,7 @@ You can retrieve the items in the exclusion list with MpCmdRun, PowerShell, [Mic
166166

167167
If you use PowerShell, you can retrieve the list in two ways:
168168

169-
- Retrieve the status of all Microsoft Defender Antivirus preferences. Each of the lists are displayed on separate lines, but the items within each list are combined into the same line.
169+
- Retrieve the status of all Microsoft Defender Antivirus preferences. Each of the lists is displayed on separate lines, but the items within each list are combined into the same line.
170170
- Write the status of all preferences to a variable, and use that variable to only call the specific list you're interested in. Each use of `Add-MpPreference` is written to a new line.
171171

172172
### Validate the exclusion list by using MpCmdRun

0 commit comments

Comments
 (0)