From c77d424231bb08d822163703764decdf5e1cf46c Mon Sep 17 00:00:00 2001 From: Kurt Sarens <56369685+kurtsarens@users.noreply.github.com> Date: Sat, 30 May 2020 16:10:21 -0700 Subject: [PATCH 1/5] Update manage-updates-baselines-windows-defender-antivirus.md May 2020 Update --- ...es-baselines-windows-defender-antivirus.md | 23 ++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-defender-antivirus/manage-updates-baselines-windows-defender-antivirus.md b/windows/security/threat-protection/windows-defender-antivirus/manage-updates-baselines-windows-defender-antivirus.md index 8146772e45..90822a5761 100644 --- a/windows/security/threat-protection/windows-defender-antivirus/manage-updates-baselines-windows-defender-antivirus.md +++ b/windows/security/threat-protection/windows-defender-antivirus/manage-updates-baselines-windows-defender-antivirus.md @@ -58,11 +58,32 @@ All our updates contain: * serviceability improvements * Integration improvements (Cloud, MTP)
+
+ May-2020 (Platform: 4.18.2005.4 | Engine: 1.1.17100.2) + + Security intelligence update version: **1.317.20.0** + Released: **May 26, 2020** + Platform: **4.18.2005.4** + Engine: **1.1.17100.2** + Support phase: **Security and Critical Updates** + +### What's new +* Improved logging for scan events +* Improved user mode crash handling. +* Added event tracing for Tamper protection +* Fixed AMSI Sample submission +* Fixed AMSI Cloud blocking +* Fixed Security update install log + +### Known Issues +No known issues +
+
April-2020 (Platform: 4.18.2004.5 | Engine: 1.1.17000.2) - Security intelligence update version: **TBD** + Security intelligence update version: **1.315.12.0**  Released: **April 30, 2020**  Platform: **4.18.2004.5**  Engine: **1.1.17000.2** From bd4fcff39785fbde819cafcb04f168ea9ec57126 Mon Sep 17 00:00:00 2001 From: Kurt Sarens <56369685+kurtsarens@users.noreply.github.com> Date: Sat, 30 May 2020 18:23:24 -0700 Subject: [PATCH 2/5] SupportLogLocation parameter Adding new parameter SupportLogLocation and usage explanation --- ...llect-diagnostic-data-update-compliance.md | 34 +++++++++++++++++-- ...ne-arguments-windows-defender-antivirus.md | 4 +-- 2 files changed, 33 insertions(+), 5 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data-update-compliance.md b/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data-update-compliance.md index 1cae26190b..0b217d93f5 100644 --- a/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data-update-compliance.md +++ b/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data-update-compliance.md @@ -38,14 +38,19 @@ On at least two devices that are not reporting or showing up in Update Complianc c. Enter administrator credentials or approve the prompt. 2. Navigate to the Windows Defender directory. By default, this is `C:\Program Files\Windows Defender`. - +> [!NOTE] +> If you're running an updated Windows Defender Platform version, please run `MpCmdRun` from the following location: `C:\ProgramData\Microsoft\Windows Defender\Platform\`. 3. Type the following command, and then press **Enter** ```Dos - mpcmdrun -getfiles + mpcmdrun.exe -GetFiles ``` - + 4. A .cab file will be generated that contains various diagnostic logs. The location of the file will be specified in the output in the command prompt. By default, the location is `C:\ProgramData\Microsoft\Windows Defender\Support\MpSupportFiles.cab`. +> [!NOTE] +> To redirect the cab file to a a different path or UNC share, use the below command: +> `mpcmdrun.exe -GetFiles -SupportLogLocation ` +> for more information see '[Redirect diagnostic data to a UNC share](#Redirect-diagnostic-data-to-a-UNC-share)' 5. Copy these .cab files to a location that can be accessed by Microsoft support. An example could be a password-protected OneDrive folder that you can share with us. @@ -60,6 +65,29 @@ On at least two devices that are not reporting or showing up in Update Complianc Please contact me at: ``` +## Redirect diagnostic data to a UNC share +To collect diagnostic data on a central repository, you can specify the SupportLogLocation parameter. + +```Dos +mpcmdrun.exe -GetFiles -SupportLogLocation +``` +Copies the diagnostic data to the specified path. If the path is not specified, the diagnostic data will be copied to the location specified in the Support Log Location Configuration. + +When the SupportLogLocation parameter is used, a folder structure as below will be created in the destination path: +```Dos +\\MpSupport--.cab +``` +| field | Description | +|:----|:----| +| path | The path as specified on the commandline or retrieved from configuration +| MMDD | Month Day when the diagnostic data was collected (eg 0530) +| hostname | the hostname of the device on which the diagnostic data was collected. +| HHMM | Hours Minutes when the diagnostic data was collected (eg 1422) + +> [!NOTE] +> When using a File share please make sure that domain accounts used to collect the diagnostic package has write access to the share. +> To prevent data loss, you can deny these accounts from deleting data. + ## See also diff --git a/windows/security/threat-protection/windows-defender-antivirus/command-line-arguments-windows-defender-antivirus.md b/windows/security/threat-protection/windows-defender-antivirus/command-line-arguments-windows-defender-antivirus.md index b42e1c8729..4922a7ff73 100644 --- a/windows/security/threat-protection/windows-defender-antivirus/command-line-arguments-windows-defender-antivirus.md +++ b/windows/security/threat-protection/windows-defender-antivirus/command-line-arguments-windows-defender-antivirus.md @@ -36,7 +36,7 @@ MpCmdRun.exe [command] [-options] ``` Here's an example: ``` -MpCmdRun.exe -scan -2 +MpCmdRun.exe -Scan -ScanType 2 ``` | Command | Description | @@ -44,7 +44,7 @@ MpCmdRun.exe -scan -2 | `-?` **or** `-h` | Displays all available options for this tool | | `-Scan [-ScanType [0\|1\|2\|3]] [-File [-DisableRemediation] [-BootSectorScan] [-CpuThrottling]] [-Timeout ] [-Cancel]` | Scans for malicious software. Values for **ScanType** are: **0** Default, according to your configuration, **-1** Quick scan, **-2** Full scan, **-3** File and directory custom scan. | | `-Trace [-Grouping #] [-Level #]` | Starts diagnostic tracing | -| `-GetFiles` | Collects support information | +| `-GetFiles [-SupportLogLocation ]` | Collects support information. | | `-GetFilesDiagTrack` | Same as `-GetFiles`, but outputs to temporary DiagTrack folder | | `-RemoveDefinitions [-All]` | Restores the installed Security intelligence to a previous backup copy or to the original default set | | `-RemoveDefinitions [-DynamicSignatures]` | Removes only the dynamically downloaded Security intelligence | From 22cd81e37e514419131c47b0a716d25c0606f653 Mon Sep 17 00:00:00 2001 From: Kurt Sarens <56369685+kurtsarens@users.noreply.github.com> Date: Sun, 31 May 2020 11:05:55 -0700 Subject: [PATCH 3/5] general doc for diag data making it a general doc to collect diagnostic data --- ...ta-update-compliance.md => collect-diagnostic-data.md} | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) rename windows/security/threat-protection/windows-defender-antivirus/{collect-diagnostic-data-update-compliance.md => collect-diagnostic-data.md} (92%) diff --git a/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data-update-compliance.md b/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data.md similarity index 92% rename from windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data-update-compliance.md rename to windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data.md index 0b217d93f5..ecbbb8d074 100644 --- a/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data-update-compliance.md +++ b/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data.md @@ -1,6 +1,6 @@ --- -title: Collect diagnostic data for Update Compliance and Windows Defender Windows Defender Antivirus -description: Use a tool to collect data to troubleshoot Update Compliance issues when using the Windows Defender Antivirus Assessment add in +title: Collect diagnostic data of Windows Defender Windows Defender Antivirus +description: Use a tool to collect data to troubleshoot Windows Defender Antivirus keywords: troubleshoot, error, fix, update compliance, oms, monitor, report, windows defender av search.product: eADQiWindows 10XVcnh ms.pagetype: security @@ -17,13 +17,13 @@ ms.reviewer: manager: dansimp --- -# Collect Update Compliance diagnostic data for Windows Defender AV Assessment +# Collect Windows Defender AV diagnostic **Applies to:** - [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559) -This article describes how to collect diagnostic data that can be used by Microsoft support and engineering teams to help troubleshoot issues you may encounter when using the Windows Defender AV Assessment section in the Update Compliance add-in. +This article describes how to collect diagnostic data that can be used by Microsoft support and engineering teams to help troubleshoot issues you may encounter when using the Windows Defender AV. Before attempting this process, ensure you have read [Troubleshoot Windows Defender Antivirus reporting](troubleshoot-reporting.md), met all require prerequisites, and taken any other suggested troubleshooting steps. From ec6e3599e22145a67136b4205eb5a015efee6ac0 Mon Sep 17 00:00:00 2001 From: Kurt Sarens <56369685+kurtsarens@users.noreply.github.com> Date: Sun, 31 May 2020 11:09:59 -0700 Subject: [PATCH 4/5] add ref to diag data page add reference to collecting diagnostic data page --- .../command-line-arguments-windows-defender-antivirus.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-defender-antivirus/command-line-arguments-windows-defender-antivirus.md b/windows/security/threat-protection/windows-defender-antivirus/command-line-arguments-windows-defender-antivirus.md index 4922a7ff73..8a16818ba6 100644 --- a/windows/security/threat-protection/windows-defender-antivirus/command-line-arguments-windows-defender-antivirus.md +++ b/windows/security/threat-protection/windows-defender-antivirus/command-line-arguments-windows-defender-antivirus.md @@ -44,7 +44,7 @@ MpCmdRun.exe -Scan -ScanType 2 | `-?` **or** `-h` | Displays all available options for this tool | | `-Scan [-ScanType [0\|1\|2\|3]] [-File [-DisableRemediation] [-BootSectorScan] [-CpuThrottling]] [-Timeout ] [-Cancel]` | Scans for malicious software. Values for **ScanType** are: **0** Default, according to your configuration, **-1** Quick scan, **-2** Full scan, **-3** File and directory custom scan. | | `-Trace [-Grouping #] [-Level #]` | Starts diagnostic tracing | -| `-GetFiles [-SupportLogLocation ]` | Collects support information. | +| `-GetFiles [-SupportLogLocation ]` | Collects support information. See '[collecting diagnostic data](collect-diagnostic-data.md)' | | `-GetFilesDiagTrack` | Same as `-GetFiles`, but outputs to temporary DiagTrack folder | | `-RemoveDefinitions [-All]` | Restores the installed Security intelligence to a previous backup copy or to the original default set | | `-RemoveDefinitions [-DynamicSignatures]` | Removes only the dynamically downloaded Security intelligence | @@ -58,5 +58,6 @@ MpCmdRun.exe -Scan -ScanType 2 ## Related topics +- [Reference topics for collecting diagnostic data](collect-diagnostic-data.md) - [Reference topics for management and configuration tools](configuration-management-reference-windows-defender-antivirus.md) - [Windows Defender Antivirus in Windows 10](windows-defender-antivirus-in-windows-10.md) From ad6261e8b9cb82d456acfd7342da8a51557ff1f1 Mon Sep 17 00:00:00 2001 From: Kurt Sarens <56369685+kurtsarens@users.noreply.github.com> Date: Sun, 31 May 2020 15:03:39 -0700 Subject: [PATCH 5/5] refining and updating reference links refining and updating reference links --- .../collect-diagnostic-data.md | 44 ++++++++++--------- .../troubleshoot-reporting.md | 2 +- 2 files changed, 24 insertions(+), 22 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data.md b/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data.md index ecbbb8d074..c3c1d2b052 100644 --- a/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data.md +++ b/windows/security/threat-protection/windows-defender-antivirus/collect-diagnostic-data.md @@ -17,7 +17,7 @@ ms.reviewer: manager: dansimp --- -# Collect Windows Defender AV diagnostic +# Collect Windows Defender AV diagnostic data **Applies to:** @@ -25,28 +25,29 @@ manager: dansimp This article describes how to collect diagnostic data that can be used by Microsoft support and engineering teams to help troubleshoot issues you may encounter when using the Windows Defender AV. -Before attempting this process, ensure you have read [Troubleshoot Windows Defender Antivirus reporting](troubleshoot-reporting.md), met all require prerequisites, and taken any other suggested troubleshooting steps. - -On at least two devices that are not reporting or showing up in Update Compliance, obtain the .cab diagnostic file by taking the following steps: +On at least two devices that are experiencing the same issue, obtain the .cab diagnostic file by taking the following steps: 1. Open an administrator-level version of the command prompt as follows: - + a. Open the **Start** menu. b. Type **cmd**. Right-click on **Command Prompt** and click **Run as administrator**. c. Enter administrator credentials or approve the prompt. - + 2. Navigate to the Windows Defender directory. By default, this is `C:\Program Files\Windows Defender`. + > [!NOTE] > If you're running an updated Windows Defender Platform version, please run `MpCmdRun` from the following location: `C:\ProgramData\Microsoft\Windows Defender\Platform\`. -3. Type the following command, and then press **Enter** - + +3. Type the following command, and then press **Enter** + ```Dos mpcmdrun.exe -GetFiles ``` 4. A .cab file will be generated that contains various diagnostic logs. The location of the file will be specified in the output in the command prompt. By default, the location is `C:\ProgramData\Microsoft\Windows Defender\Support\MpSupportFiles.cab`. + > [!NOTE] > To redirect the cab file to a a different path or UNC share, use the below command: > `mpcmdrun.exe -GetFiles -SupportLogLocation ` @@ -54,29 +55,32 @@ On at least two devices that are not reporting or showing up in Update Complianc 5. Copy these .cab files to a location that can be accessed by Microsoft support. An example could be a password-protected OneDrive folder that you can share with us. -6. Send an email using the Update Compliance support email template, and fill out the template with the following information: - - ``` - I am encountering the following issue when using Windows Defender Antivirus in Update Compliance: - - I have provided at least 2 support .cab files at the following location: +> [!NOTE] +>If you have a problem with Update compliance, send an email using the Update Compliance support email template, and fill out the template with the following information: +>``` +> I am encountering the following issue when using Windows Defender Antivirus in Update Compliance: +> I have provided at least 2 support .cab files at the following location: +> +> +> My OMS workspace ID is: +> +> Please contact me at: - My OMS workspace ID is: - - Please contact me at: - ``` ## Redirect diagnostic data to a UNC share To collect diagnostic data on a central repository, you can specify the SupportLogLocation parameter. ```Dos mpcmdrun.exe -GetFiles -SupportLogLocation ``` + Copies the diagnostic data to the specified path. If the path is not specified, the diagnostic data will be copied to the location specified in the Support Log Location Configuration. When the SupportLogLocation parameter is used, a folder structure as below will be created in the destination path: + ```Dos \\MpSupport--.cab ``` + | field | Description | |:----|:----| | path | The path as specified on the commandline or retrieved from configuration @@ -85,9 +89,7 @@ When the SupportLogLocation parameter is used, a folder structure as below will | HHMM | Hours Minutes when the diagnostic data was collected (eg 1422) > [!NOTE] -> When using a File share please make sure that domain accounts used to collect the diagnostic package has write access to the share. -> To prevent data loss, you can deny these accounts from deleting data. - +> When using a File share please make sure that account used to collect the diagnostic package has write access to the share. ## See also diff --git a/windows/security/threat-protection/windows-defender-antivirus/troubleshoot-reporting.md b/windows/security/threat-protection/windows-defender-antivirus/troubleshoot-reporting.md index 2efa65178d..05e621e3b8 100644 --- a/windows/security/threat-protection/windows-defender-antivirus/troubleshoot-reporting.md +++ b/windows/security/threat-protection/windows-defender-antivirus/troubleshoot-reporting.md @@ -62,7 +62,7 @@ In order for devices to properly show up in Update Compliance, you have to meet If the above prerequisites have all been met, you might need to proceed to the next step to collect diagnostic information and send it to us. > [!div class="nextstepaction"] -> [Collect diagnostic data for Update Compliance troubleshooting](collect-diagnostic-data-update-compliance.md) +> [Collect diagnostic data for Update Compliance troubleshooting](collect-diagnostic-data.md)