diff --git a/windows/application-management/msix-app-packaging-tool.md b/windows/application-management/msix-app-packaging-tool.md index cd0dce59af..a147f74977 100644 --- a/windows/application-management/msix-app-packaging-tool.md +++ b/windows/application-management/msix-app-packaging-tool.md @@ -23,14 +23,19 @@ The MSIX Packaging Tool (Preview) is now available to install from the Microsoft - A valid MSA alias (to access the app from the Store) ## What's new -v1.2018.808.0 +v1.2018.821.0 +- Command Line Support +- Ability to use existing local virtual machines for packaging environment. +- Ability to cross check publisher information in the manifest with a signing certificate to avoid signing issues. +- Minor updates to the UI for added clarity. + +v1.2018.807.0 - Ability to add/edit/remove file and registry exclusion items is now supported in Settings menu. -- Fixed an issue where signing in with password protected certificates would fail in the tool. +- Fixed an issue where signing with password protected certificates would fail in the tool. - Fixed an issue where the tool was crashing when editing an existing MSIX package. - Fixed an issue where the tool was injecting whitespaces programmatically to install location paths that was causing conversion failures. - Minor UI tweaks to add clarity. -- Minor updates to the logs for added clarity. - +- Minor updates to the logs to add clarity. ## Installing the MSIX Packaging Tool @@ -45,12 +50,169 @@ This is an early preview build and not all features are supported. Here is what - Create a modification package for a newly created Application MSIX Package by launching the tool and selecting the **Modification package** icon. - Open your MSIX package to view and edit its content/properties by navigating to the **Open package editor** tab. Browse to the MSIX package and select **Open package**. -Features not supported in the tool are currently greyed out. Here are some of the highlighted missing features: +## Creating an application package using the Command line interface +To create a new MSIX package for your application, run the MsixPackagingTool.exe create-package command in a Command prompt window. -- Package Support Framework integration. For more detail on how you can use Package Support Framework today, check out the article posted on the [MSIX blog](https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMSIX-Blog%2FMSIX-Package-Support-Framework-is-now-available-on-GitHub%2Fba-p%2F214548&data=02%7C01%7Cpezan%40microsoft.com%7Cbe2761c174cd465136ce08d5f1252d8a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636680064344941094&sdata=uW3oOOEYQxd0iVgsJkZXZTQwlvf%2FimVCaOdFUXcRoeY%3D&reserved=0). -- Packaging on existing virtual machines. You can still install the Tool on a fresh VM, but the tool cannot currently spawn off a conversion from a local machine to an existing VM. -- Command Line Interface support -- Conversion of App-V 4.x packages +Here are the parameters that can be passed as command line arguments: + + +|Parameter |Description | +|---------|---------| +|-?
--help | Show help information | +|--template | [required] path to the conversion template XML file containing package information and settings for this conversion | +|--virtualMachinePassword | [optional] The password for the Virtual Machine to be used for the conversion environment. Notes: The template file must contain a VirtualMachine element and the Settings::AllowPromptForPassword attribute must not be set to true. | + +Examples: + +- MsixPackagingTool.exe create-package --template c:\users\documents\ConversionTemplate.xml +- MSIXPackagingTool.exe create-package --template c:\users\documents\ConversionTemplate.xml --virtualMachinePassword pswd112893 + +## Conversion template file + + +```xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + +## Conversion template parameter reference +Here is the complete list of parameters that you can use in the Conversion template file. + + +|ConversionSettings entries |Description | +|---------|---------| +|Settings:: AllowTelemetry |[optional] Enables telemetry logging for this invocation of the tool. | +|Settings:: ApplyAllPrepareComputerFixes |[optional] Applies all recommended prepare computer fixes. Cannot be set when other attributes are used. | +|Settings:: GenerateCommandLineFile |[optional] Copies the template file input to the SaveLocation directory for future use. | +|Settings:: AllowPromptForPassword |[optional] Instructs the tool to prompt the user to enter passwords for the Virtual Machine and for the signing certificate if it is required and not specified. | +|ExclusionItems |[optional] 0 or more FileExclusion or RegistryExclusion elements. All FileExclusion elements must appear before any RegistryExclusion elements. | +|ExclusionItems::FileExclusion |[optional] A file to exclude for packaging. | +|ExclusionItems::FileExclusion::ExcludePath |Path to file to exclude for packaging. | +|ExclusionItems::RegistryExclusion |[optional] A registry key to exclude for packaging. | +|ExclusionItems::RegistryExclusion:: ExcludePath |Path to registry to exclude for packaging. | +|PrepareComputer::DisableDefragService |[optional] Disables Windows Defragmenter while the app is being converted. If set to false, overrides ApplyAllPrepareComputerFixes. | +|PrepareComputer:: DisableWindowsSearchService |[optional] Disables Windows Search while the app is being converted. If set to false, overrides ApplyAllPrepareComputerFixes. | +|PrepareComputer:: DisableSmsHostService |[optional] Disables SMS Host while the app is being converted. If set to false, overrides ApplyAllPrepareComputerFixes. | +|PrepareComputer:: DisableWindowsUpdateService |[optional] Disables Windows Update while the app is being converted. If set to false, overrides ApplyAllPrepareComputerFixes. | +|SaveLocation |[optional] An element to specify the save location of the tool. If not specified, the package will be saved under the Desktop folder. | +|SaveLocation::Path |The path to the folder where the resulting MSIX package is saved. | +|Installer::Path |The path to the application installer. | +|Installer::Arguments |The arguments to pass to the installer. You must pass the arguments to force your installer to run unattended/silently. | +|Installer::InstallLocation |[optional] The full path to your application's root folder for the installed files if it were installed (e.g. "C:\Program Files (x86)\MyAppInstalllocation"). | +|VirtualMachine |[optional] An element to specify that the conversion will be run on a local Virtual Machine. | +|VrtualMachine::Name |The name of the Virtual Machine to be used for the conversion environment. | +|VirtualMachine::Username |[optional] The user name for the Virtual Machine to be used for the conversion environment. | +|PackageInformation::PackageName |The Package Name for your MSIX package. | +|PackageInformation::PackageDisplayName |The Package Display Name for your MSIX package. | +|PackageInformation::PublisherName |The Publisher for your MSIX package. | +|PackageInformation::PublisherDisplayName |The Publisher Display Name for your MSIX package. | +|PackageInformation::Version |The version number for your MSIX package. | +|PackageInformation:: MainPackageNameForModificationPackage |[optional] The Package identity name of the main package name. This is used when creating a modification package that takes a dependency on a main (parent) application. | +|Applications |[optional] 0 or more Application elements to configure the Application entries in your MSIX package. | +|Application::Id |The App ID for your MSIX application. This ID will be used for the Application entry detected that matches the specified ExecutableName. You can have multiple Application ID for executables in the package | +|Application::ExecutableName |The executable name for the MSIX application that will be added to the package manifest. The corresponding application entry will be ignored if no application with this name is detected. | +|Application::Description |[optional] The App Description for your MSIX application. If not used, the Application DisplayName will be used. This description will be used for the application entry detected that matches the specified ExecutableName | +|Application::DisplayName |The App Display Name for your MSIX package. This Display Name will be used for the application entry detected that matches the specified ExecutableName | +|Capabilities |[optional] 0 or more Capability elements to add custom capabilities to your MSIX package. “runFullTrust” capability is added by default during conversion. | +|Capability::Name |The capability to add to your MSIX package. | + +## Delete temporary conversion files using Command line interface +To delete all the temporary package files, logs, and artifacts created by the tool, run the MsixPackagingTool.exe cleanup command in the Command line window. + +Example: +- MsixPackagingTool.exe cleanup ## How to file feedback diff --git a/windows/client-management/mdm/enterprisemodernappmanagement-csp.md b/windows/client-management/mdm/enterprisemodernappmanagement-csp.md index 6d9a0e4458..65466b03e1 100644 --- a/windows/client-management/mdm/enterprisemodernappmanagement-csp.md +++ b/windows/client-management/mdm/enterprisemodernappmanagement-csp.md @@ -7,7 +7,7 @@ ms.topic: article ms.prod: w10 ms.technology: windows author: MariciaAlforque -ms.date: 07/24/2018 +ms.date: 08/21/2018 --- # EnterpriseModernAppManagement CSP diff --git a/windows/client-management/mdm/firewall-csp.md b/windows/client-management/mdm/firewall-csp.md index 2a75d65c24..4d654c47d2 100644 --- a/windows/client-management/mdm/firewall-csp.md +++ b/windows/client-management/mdm/firewall-csp.md @@ -266,9 +266,9 @@ Sample syncxml to provision the firewall settings to evaluate
  • "DNS"
  • "WINS"
  • "Intranet"
    • -
  • "RemoteCorpNetwork"
    • +
  • "RmtIntranet"
  • "Internet"
    • -
  • "PlayToRenderers"
    • +
  • "Ply2Renders"
  • "LocalSubnet" indicates any local address on the local subnet. This token is not case-sensitive.
  • A subnet can be specified using either the subnet mask or network prefix notation. If neither a subnet mask not a network prefix is specified, the subnet mask defaults to 255.255.255.255.
  • A valid IPv6 address.
    • diff --git a/windows/client-management/mdm/images/provisioning-csp-enterprisemodernappmanagement.png b/windows/client-management/mdm/images/provisioning-csp-enterprisemodernappmanagement.png index 95d2fcf840..6c5472995b 100644 Binary files a/windows/client-management/mdm/images/provisioning-csp-enterprisemodernappmanagement.png and b/windows/client-management/mdm/images/provisioning-csp-enterprisemodernappmanagement.png differ diff --git a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md index f3ab379a5e..1234f5199b 100644 --- a/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md +++ b/windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md @@ -1414,6 +1414,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s
  • Experience/AllowClipboardHistory
  • Experience/DoNotSyncBrowserSettings
  • Experience/PreventUsersFromTurningOnBrowserSyncing
    • +
  • Kerberos/UPNNameHints
  • Privacy/AllowCrossDeviceClipboard
  • Privacy/DisablePrivacyExperience
  • Privacy/UploadUserActivities
    • @@ -1478,6 +1479,10 @@ For details about Microsoft mobile device management protocols for Windows 10 s [TenantLockdown CSP](\tenantlockdown--csp.md)

    Added new CSP in Windows 10, next major version.

    + +[Office CSP](office-csp.md) +

    Added FinalStatus setting in Windows 10, next major version.

    + @@ -1763,6 +1768,10 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware +[Office CSP](office-csp.md) +

    Added FinalStatus setting in Windows 10, next major version.

    + + [RemoteWipe CSP](remotewipe-csp.md)

    Added new settings in Windows 10, next major version.

    @@ -1801,12 +1810,14 @@ The DM agent for [push-button reset](https://msdn.microsoft.com/windows/hardware
  • Browser/UnlockHomeButton
  • Experience/DoNotSyncBrowserSettings
  • Experience/PreventUsersFromTurningOnBrowserSyncing
    • +
  • Kerberos/UPNNameHints
  • Privacy/AllowCrossDeviceClipboard
  • Privacy/DisablePrivacyExperience
  • Privacy/UploadUserActivities
  • Update/UpdateNotificationLevel

    • Start/DisableContextMenus - added in Windows 10, version 1803.

    +

    RestrictedGroups/ConfigureGroupMembership - added new schema to apply and retrieve the policy.

    diff --git a/windows/deployment/update/device-health-monitor.md b/windows/deployment/update/device-health-monitor.md index 6e78e96a31..e8341b6fea 100644 --- a/windows/deployment/update/device-health-monitor.md +++ b/windows/deployment/update/device-health-monitor.md @@ -45,7 +45,6 @@ Use of Windows Analytics Device Health requires one of the following licenses: - Windows 10 Enterprise E3 or E5 per-device or per-user subscription (including Microsoft 365 F1, E3, or E5) - Windows 10 Education A3 or A5 (including Microsoft 365 Education A3 or A5) - Windows VDA E3 or E5 per-device or per-user subscription -- Windows Server 2016 and on You don't have to install Windows 10 Enterprise on a per-device basis--you just need enough of the above licenses for the number of devices using Device Health. diff --git a/windows/deployment/update/servicing-stack-updates.md b/windows/deployment/update/servicing-stack-updates.md index 16dd909dd8..23321eb5ad 100644 --- a/windows/deployment/update/servicing-stack-updates.md +++ b/windows/deployment/update/servicing-stack-updates.md @@ -34,6 +34,6 @@ Typically, the improvements are reliability, security, and performance improveme ## Installation notes -• Servicing stack updates contain the full servicing stack; as a result, typically administrators only need to install the latest servicing stack update for the operating system. -• Installing servicing stack update does not require restarting the device, so installation should not be disruptive. -• Servicing stack update releases are specific to the operating system version (build number), much like quality updates. +* Servicing stack updates contain the full servicing stack; as a result, typically administrators only need to install the latest servicing stack update for the operating system. +* Installing servicing stack update does not require restarting the device, so installation should not be disruptive. +* Servicing stack update releases are specific to the operating system version (build number), much like quality updates. diff --git a/windows/deployment/windows-autopilot/TOC.md b/windows/deployment/windows-autopilot/TOC.md index 13ef2ce85b..ac183ef6d1 100644 --- a/windows/deployment/windows-autopilot/TOC.md +++ b/windows/deployment/windows-autopilot/TOC.md @@ -17,7 +17,6 @@ ### [Administering Autopilot via Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/add-profile-to-devices#manage-autopilot-deployment-profiles) ### [Administering Autopilot via Microsoft Intune](https://docs.microsoft.com/intune/enrollment-autopilot) ### [Administering Autopilot via Microsoft 365 Business & Office 365 Admin portal](https://support.office.com/article/Create-and-edit-Autopilot-profiles-5cf7139e-cfa1-4765-8aad-001af1c74faa) -### [Administering Autopilot via Partner Center](https://msdn.microsoft.com/partner-center/autopilot) ## Getting started ### [Demonstrate Autopilot deployment on a VM](demonstrate-deployment-on-vm.md) ## [Troubleshooting](troubleshooting.md) diff --git a/windows/deployment/windows-autopilot/windows-10-autopilot.md b/windows/deployment/windows-autopilot/windows-10-autopilot.md index 794e515940..e73d7727a0 100644 --- a/windows/deployment/windows-autopilot/windows-10-autopilot.md +++ b/windows/deployment/windows-autopilot/windows-10-autopilot.md @@ -1,7 +1,7 @@ --- title: Overview of Windows Autopilot description: This topic goes over Windows Autopilot and how it helps setup OOBE Windows 10 devices. -keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune +keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, msfb, intune ms.prod: w10 ms.mktglfcycl: deploy ms.localizationpriority: medium @@ -9,7 +9,7 @@ ms.sitesec: library ms.pagetype: deploy author: coreyp-at-msft ms.author: coreyp -ms.date: 05/09/2018 +ms.date: 08/22/2018 --- # Overview of Windows Autopilot @@ -89,7 +89,6 @@ For guidance on how to register devices, configure and apply deployment profiles * [Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/add-profile-to-devices#manage-autopilot-deployment-profiles) * [Microsoft Intune](https://docs.microsoft.com/intune/enrollment-autopilot) * [Microsoft 365 Business & Office 365 Admin](https://support.office.com/article/Create-and-edit-Autopilot-profiles-5cf7139e-cfa1-4765-8aad-001af1c74faa) -* [Partner Center](https://msdn.microsoft.com/partner-center/autopilot) ##### Configure company branding for OOBE diff --git a/windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields.md b/windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields.md index 9d31869696..3f4c11004e 100644 --- a/windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields.md +++ b/windows/privacy/enhanced-diagnostic-data-windows-analytics-events-and-fields.md @@ -109,7 +109,6 @@ The following fields are available: - **isSystemManagedAccount:** Indicates if the user's account is System Managed - **isUnlockScenario:** Flag indicating whether the event is a Logon or an Unlock -- **PartA_UserSid:** The security identifier of the user - **userType:** Indicates the user type: 0 = unknown; 1 = local; 2 = Active Directory domain user; 3 = Microsoft Account; 4 = Azure Active Directory user ## Microsoft.Windows.LogonController.SignInFailure @@ -251,3 +250,8 @@ The following fields are available: - **WindowFlags:** Flags denoting runtime properties of an app window - **WindowHeight:** Number of vertical pixels in the application window - **WindowWidth:** Number of horizontal pixels in the application window + +# Revisions to the diagnostic data events and fields + +## PartA_UserSid removed +A previous revision of this list stated that a field named PartA_UserSid was a member of the event Microsoft.Windows.LogonController.LogonAndUnlockSubmit. This was incorrect. The list has been updated to reflect that no such field is present in the event. Note that you can use the Windows Diagnostic Data Viewer to review the contents of the event. diff --git a/windows/security/identity-protection/vpn/vpn-profile-options.md b/windows/security/identity-protection/vpn/vpn-profile-options.md index 01948e0ca4..3051e37b8b 100644 --- a/windows/security/identity-protection/vpn/vpn-profile-options.md +++ b/windows/security/identity-protection/vpn/vpn-profile-options.md @@ -304,7 +304,7 @@ After you configure the settings that you want using ProfileXML, you can apply i 5. Choose **Windows 10 and later** as the platform. 6. Choose **Custom** as the profile type and click **Add**. 8. Enter a name and (optionally) a description. -9. Enter the OMA-URI **./user/vendor/MSFT/_VPN profile name_/ProfileXML**. +9. Enter the OMA-URI **./user/vendor/MSFT/VPNv2/_VPN profile name_/ProfileXML**. 10. Set Data type to **String (XML file)**. 11. Upload the profile XML file. 12. Click **OK**. diff --git a/windows/security/information-protection/tpm/trusted-platform-module-overview.md b/windows/security/information-protection/tpm/trusted-platform-module-overview.md index 43699df08e..8b4a54d9f3 100644 --- a/windows/security/information-protection/tpm/trusted-platform-module-overview.md +++ b/windows/security/information-protection/tpm/trusted-platform-module-overview.md @@ -8,7 +8,7 @@ ms.sitesec: library ms.pagetype: security ms.localizationpriority: medium author: brianlic-msft -ms.date: 06/18/2018 +ms.date: 08/21/2018 --- # Trusted Platform Module Technology Overview @@ -68,14 +68,15 @@ Some things that you can check on the device are: - Is SecureBoot supported and enabled? > [!NOTE] -> The device must be running Windows 10 and it must support at least TPM 2.0 in order to utilize Device Health Attestation. +> Windows 10 and Windows Server 2016 support Device Health Attestation with TPM 2.0. Support for TPM 1.2 was added beginning with Windows version 1607 (RS1). ## Supported versions -| TPM version | Windows 10 | Windows Server 2016 | -|-------------|------------|---------------------| -| TPM 1.2 | X | X | -| TPM 2.0 | X | X | +| TPM version | Windows 10 | Windows Server 2016 | +|-------------|-------------|---------------------| +| TPM 1.2 | >= ver 1607 | >= ver 1607 | +| TPM 2.0 | X | X | + ## Related topics diff --git a/windows/security/threat-protection/intelligence/TOC.md b/windows/security/threat-protection/intelligence/TOC.md index 73449a6a2c..86d4f40296 100644 --- a/windows/security/threat-protection/intelligence/TOC.md +++ b/windows/security/threat-protection/intelligence/TOC.md @@ -34,6 +34,8 @@ ## [Safety Scanner download](safety-scanner-download.md) +## [Industry antivirus tests](transparency-report.md) + ## [Industry collaboration programs](cybersecurity-industry-partners.md) ### [Virus information alliance](virus-information-alliance-criteria.md) diff --git a/windows/security/threat-protection/intelligence/transparency-report.md b/windows/security/threat-protection/intelligence/transparency-report.md new file mode 100644 index 0000000000..a89924060f --- /dev/null +++ b/windows/security/threat-protection/intelligence/transparency-report.md @@ -0,0 +1,93 @@ +--- +title: Industry antivirus tests +description: Industry antivirus tests landing page +keywords: security, malware +ms.prod: w10 +ms.mktglfcycl: secure +ms.sitesec: library +ms.localizationpriority: medium +ms.author: ellevin +author: levinec +ms.date: 08/17/2018 +--- + +# Top scoring in industry antivirus tests + +[Windows Defender Antivirus](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10?ocid=cx-blog-mmpc) **consistently achieves high scores** from independent tests, displaying how it is a top choice in the antivirus market. + +We want to be transparent and have gathered top industry reports that demonstrate our enterprise antivirus capabilities. Note that these tests only provide results for antivirus and do not test for additional security protections. + +In the real world, millions of devices are protected from cyberattacks every day, sometimes [milliseconds after a campaign starts](https://cloudblogs.microsoft.com/microsoftsecure/2018/03/07/behavior-monitoring-combined-with-machine-learning-spoils-a-massive-dofoil-coin-mining-campaign/). In many cases, customers might not even know they were protected. That's because Windows Defender ATP's [next generation protection](https://www.youtube.com/watch?v=Xy3MOxkX_o4) detects and stops malware at first sight by using predictive technologies, [machine learning](https://cloudblogs.microsoft.com/microsoftsecure/2018/06/07/machine-learning-vs-social-engineering/), [artificial intelligence](https://cloudblogs.microsoft.com/microsoftsecure/2018/02/14/how-artificial-intelligence-stopped-an-emotet-outbreak/), behavioral analysis, and other advanced technologies. + +> [!TIP] +> Learn why [most enterprises use Windows Defender Antivirus](https://docs.microsoft.com/windows/threat-protection/windows-defender-antivirus/windows-defender-antivirus-in-windows-10). + +



    +![Logo](./images/av-test-logo.png) + +## AV-TEST: Perfect protection score of 6.0/6.0 in the latest test + +**[Analysis of the latest AV-TEST results](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2v60I)** + +The AV-TEST Product Review and Certification Report tests on three categories: protection, performance, and usability. The scores listed below are for the protection category which has two scores: real world testing and the AV-TEST reference set (known as "prevalent malware"). + +**Real-World testing** as defined by AV-TEST refers to protection against zero-day malware attacks, inclusive of web and email threats. + +**Prevalent malware** as defined by AV-TEST refers to detection of widespread and prevalent malware discovered in the last four weeks. + +Note: Microsoft sees a wider and broader set of threats beyond just what’s tested in the AV-TEST evaluation. + +The below scores are the results of AV-TEST's evaluations on **Windows Defender Antivirus**. + +|Month (2018)|Real-World test score| Prevalent malware test score | AV-TEST report| Microsoft analysis| +|---|---|---|---|---| +|January| 100.00%| 99.92%| [Report (Jan-Feb)](https://www.av-test.org/en/antivirus/home-windows/windows-7/february-2018/kaspersky-lab-internet-security-18.0-180557/)| [Analysis (Jan-Feb)](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE27O5A?ocid=cx-blog-mmpc)| +|February| 100.00% | 100.00%|[Report (Jan-Feb)](https://www.av-test.org/en/antivirus/home-windows/windows-7/february-2018/kaspersky-lab-internet-security-18.0-180557/)| [Analysis (Jan-Feb)](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE27O5A?ocid=cx-blog-mmpc)| +March |98.00%| 100.00%|[Report (Mar-Apr)](https://www.av-test.org/en/antivirus/business-windows-client/windows-10/april-2018/microsoft-windows-defender-antivirus-4.12-181574/)|[Analysis (Mar-Apr)](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2ouJA)| +April|100.00%| 100.00%|[Report (Mar-Apr)](https://www.av-test.org/en/antivirus/business-windows-client/windows-10/april-2018/microsoft-windows-defender-antivirus-4.12-181574/)|[Analysis (Mar-Apr)](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2ouJA)| +May|100.00%| 100.00%| [Report (May-Jun)](https://www.av-test.org/en/antivirus/business-windows-client/windows-10/june-2018/microsoft-windows-defender-antivirus-4.12-182374/) **Latest**|[Analysis (May-Jun)](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2v60I)| +June|100.00%| 100.00%| [Report (May-Jun)](https://www.av-test.org/en/antivirus/business-windows-client/windows-10/june-2018/microsoft-windows-defender-antivirus-4.12-182374/) **Latest**|[Analysis (May-Jun)](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2v60I)| + +||| +|---|---| +|![Graph describing Real-World detection rate](./images/RealWorld-67-percent.png)|![Prevalent Malware](./images/PrevalentMalware-67-percent.png)| +

    + +![Logo](./images/av-comparatives-logo-3.png) + +## AV-Comparatives: Perfect protection rating of 100% in the latest test + +AV-Comparatives is an independent organization offering systematic testing for security software such as PC/Mac-based antivirus products and mobile security solutions. + +The **Real-World Protection Test (Enterprise)** as defined by AV-Comparatives evaluates the “real-world” protection capabilities with default settings. The goal is to find out whether the security software protects the computer by either hindering the malware from changing any systems or remediating all changes if any were made. + +The **Malware Protection Test Enterprise** as defined by AV-Comparatives assesses a security program’s ability to protect a system against infection by malicious files before, during or after execution. It is only tested every *six months*. + +Note: Microsoft sees a wider and broader set of threats beyond just what’s tested in the AV-Comparatives evaluation. + +The below scores are the results of AV-Comparatives tests on **Windows Defender Antivirus**. The scores are specifically for the ability to block malware. + +|Month (2018)| Real-World test score| Malware test score (every 6 months)| +|---|---|---| +|February| 100.00%| N/A| +|March| 94.40%| 99.90%| +|April| 96.40%| N/A| +|May| 100.00%| N/A| +|June| 99.50%| N/A| +|July| 100.00%| N/A| + +* [Real-World Protection Test (Enterprise) July 2018](https://www.av-comparatives.org/tests/real-world-protection-test-july-2018-factsheet/) + +* [Real-World Protection Test (Enterprise) February - June 2018](https://www.av-comparatives.org/tests/real-world-protection-test-february-june-2018/) + +* [Malware Protection Test Enterprise March 2018](https://www.av-comparatives.org/tests/malware-protection-test-enterprise-march-2018-testresult/) + +## To what extent are tests representative of protection in the real world? + +It is important to remember that the capabilities within [Windows Defender ATP](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=cx-blog-mmpc) provide [additional layers of protection](https://cloudblogs.microsoft.com/microsoftsecure/2017/12/11/detonating-a-bad-rabbit-windows-defender-antivirus-and-layered-machine-learning-defenses/) that are not factored into AV tests. Using these tests, customer can view one aspect of their security suite but can't assess the complete protection of all the security features. + +There are other technologies in nearly every endpoint security suite that address some of the latest and most sophisticated threats, but are not represented in AV tests. For example, the capabilities such as attack surface reduction and endpoint detection & response help prevent malware from getting onto devices in the first place. + +Microsoft is highly engaged in working with several independent testers to evolve security testing to focus on the end-to-end security stack. In the meantime, customers can evaluate Windows Defender Advanced Threat Protection in their own networks by signing up for a [90-day trial of Windows Defender ATP](https://www.microsoft.com/windowsforbusiness/windows-atp?ocid=cx-blog-mmpc), or [enabling Preview features on existing tenants](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-atp/preview-settings-windows-defender-advanced-threat-protection). + +![ATP](./images/wdatp-pillars2.png)