Defender SmartScreen: typo correction & URL update

As reported in issue ticket #8665 (Correction To Microsoft Defender SmartScreen "login", replace with "log in"), there is a typo where the phrase "Debug log in Event Viewer" has lost its required spacing between "log" and "in".

Thanks to secdev-01 for finding and reporting this typo.

Additional update: the URL to the [Event 1035 - Anti-Phishing] page has been changed to reflect its permanent redirect from
- https://technet.microsoft.com/scriptcenter/dd565657(v=msdn.10).aspx
 - to -
- https://docs.microsoft.com/previous-versions/windows/internet-explorer/ie-developer/compatibility/dd565657(v=vs.85)

Closes #8665
This commit is contained in:
Trond B. Krokli 2020-11-19 01:04:18 +01:00 committed by GitHub
parent 898eac108a
commit ae9fef9a50
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -67,12 +67,12 @@ When submitting Microsoft Defender SmartScreen products, make sure to select **M
## Viewing Microsoft Defender SmartScreen anti-phishing events
> [!NOTE]
> No Smartscreen events will be logged when using Microsoft Edge version 77 or later.
> No SmartScreen events will be logged when using Microsoft Edge version 77 or later.
When Microsoft Defender SmartScreen warns or blocks a user from a website, it's logged as [Event 1035 - Anti-Phishing](https://technet.microsoft.com/scriptcenter/dd565657(v=msdn.10).aspx).
When Microsoft Defender SmartScreen warns or blocks a user from a website, it's logged as [Event 1035 - Anti-Phishing](https://docs.microsoft.com/previous-versions/windows/internet-explorer/ie-developer/compatibility/dd565657(v=vs.85)).
## Viewing Windows event logs for Microsoft Defender SmartScreen
Microsoft Defender SmartScreen events appear in the Microsoft-Windows-SmartScreen/Debug login Event Viewer.
Microsoft Defender SmartScreen events appear in the Microsoft-Windows-SmartScreen/Debug log, in the Event Viewer.
Windows event log for SmartScreen is disabled by default, users can use Event Viewer UI to enable the log or use the command line to enable it: