The Defender for Endpoint Downloads folder is a download cache, not really a log folder. Double-check before listing it.
Where Microsoft Defender keeps its logs
Microsoft Defender logs to Event Viewer > Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational on Windows. 1 other Windows log location is recorded below.
Microsoft Defender logs to /Library/Logs/Microsoft/mdatp/ on macOS. These paths were verified for pkg installs - a different installer, or a portable copy, can put them somewhere else.
Microsoft Defender logs to /var/log/microsoft/mdatp/ on Linux. These paths were verified for deb and rpm installs - a different installer, or a portable copy, can put them somewhere else.
Paths are printed exactly as Microsoft Defender writes them. Environment variables like %LOCALAPPDATA% and $XDG_STATE_HOME are never expanded, so a path can be pasted straight into a shell. Where a path differs between installer types or shipping flavours, each one is racked as its own card below - why that happens.
antivirusEvent Viewer > Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational
support logs (MPLog, MpSupportFiles.cab)C:\ProgramData\Microsoft\Windows Defender\Support\- MpCmdRun.exe -GetFiles writes MpSupportFiles.cab here; the MPLog-<date>.log protection logs also live in this folder
install log (install.log)/Library/Logs/Microsoft/mdatp/- Diagnostic bundles from sudo mdatp diagnostic create go to /Library/Application Support/Microsoft/Defender/wdavdiag/
How to turn on debug logging for Microsoft Defender
macOS and Linux: run mdatp log level set --level debug.
macOS and Linux: reproduce the issue and collect the logs.
macOS and Linux: switch back with mdatp log level set --level info.
Linux: change the log size limits with mdatp config log-rotation-parameters [max-current-size/max-rotated-size] --size [value in MB].
How to collect Microsoft Defender logs
Windows: open an elevated command prompt in the newest %ProgramData%\Microsoft\Windows Defender\Platform\<version> folder, or in %ProgramFiles%\Windows Defender.
Windows: to copy it to a share instead, run MpCmdRun.exe -GetFiles -SupportLogLocation <RootPath>. It writes <RootPath>\<MMDD>\MpSupport-<Hostname>-<HHMM>.cab.
macOS and Linux: run sudo mdatp diagnostic create, optionally with --path [directory].
macOS and Linux: collect the zip file at the path it prints.
From the Defender portal, you can also run Collect investigation package on the device.