Skip to content

Commit 850a4f1

Browse files
authored
Update enable-troubleshooting-mode.md
Remove hard-coded link
1 parent 140a699 commit 850a4f1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

defender-endpoint/enable-troubleshooting-mode.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ During troubleshooting mode, you can use the PowerShell command `Set-MPPreferenc
6464

6565
- Admins can also review the changes in settings that take place during Troubleshooting mode in **Event Viewer** on the device itself.
6666
- `Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational`
67-
- Potential events may be event ID 5000, 5001, 5004, 5007 and others. See more details at [Review event logs and error codes to troubleshoot issues with Microsoft Defender Antivirus](https://learn.microsoft.com/en-us/defender-endpoint/troubleshoot-microsoft-defender-antivirus#event-id-5000).
67+
- Potential events may be event IDs 5000, 5001, 5004, 5007 and others. See more details at [Review event logs and error codes to troubleshoot issues with Microsoft Defender Antivirus](troubleshoot-microsoft-defender-antivirus#event-id-5000).
6868

6969
- Troubleshooting mode automatically turns off after reaching the expiration time (it lasts for 4 hours). After expiration, all policy-managed configurations become read-only again and revert back to how the device was configured before enabling troubleshooting mode.
7070

0 commit comments

Comments
 (0)