From a99b43c80b6be875ae33c3ff072c9f4f733d86af Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Tue, 17 Apr 2018 09:13:13 -0700 Subject: [PATCH] added wmic --- .../steps-to-deploy-windows-defender-application-control.md | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/security/threat-protection/device-guard/steps-to-deploy-windows-defender-application-control.md b/windows/security/threat-protection/device-guard/steps-to-deploy-windows-defender-application-control.md index bd80c090ce..459bdc15be 100644 --- a/windows/security/threat-protection/device-guard/steps-to-deploy-windows-defender-application-control.md +++ b/windows/security/threat-protection/device-guard/steps-to-deploy-windows-defender-application-control.md @@ -60,6 +60,7 @@ Unless your use scenarios explicitly require them, Microsoft recommends that you - rcsi.exe - system.management.automation.dll - windbg.exe +- wmic.exe [1]A vulnerability in bginfo.exe has been fixed in the latest version 4.22. If you use BGInfo, for security, make sure to download and run the latest version here [BGInfo 4.22](https://docs.microsoft.com/en-us/sysinternals/downloads/bginfo). Note that BGInfo versions earlier than 4.22 are still vulnerable and should be blocked.