3 ms·
Details from Microsoft: https://technet.microsoft.com/en-us/library/security/4022344 https://technet.microsoft.com/en-us/library/security/4022344
by booleandilemma 10y ago
Details from Microsoft:
https://technet.microsoft.com/en-us/library/security/4022344 https://technet.microsoft.com/en-us/library/security/4022344
- nailer 10y agoHrm. Microsoft article says: > For more information on how to verify the version number for the Microsoft Malware Protection Engine that your software is currently using, see the section, "Verifying Update Installation", in Microsoft Knowledge Base Article 2510781. But the link points to https://technet.microsoft.com/en-us/library/security/4022344 https://technet.microsoft.com/en-us/library/security/4022344 which doesn't include Windows 10. Edit: guessed and found it: Start -> Windows Defender Security Centre -> (cog icon in bottom left) -> About -> Engine Version
- johnhattan 10y agoAnd if your engine version is equal to or less than 1.1.13701.0, then you still have the vulnerability and need to update ASAP.
- 0xfeba 10y agoAnd for Microsoft Security Essentials, Click the down arrow next to the Help link, and select about.
- dsp1234 10y agoFrom powershell (on Windows 10/Server 2016, possibly others): (Get-MpComputerStatus).AmEngineVersion Also, from powershell: Update-MpSignature to just go ahead and run the update process
- nailer 10y agoThanks! I wish Microsoft would throw the powershell one liner in their document, most poeple interested in this stuff would just rather do: Get-MpComputerStatus | select 'AmEngineVersion' Than read a longwinded set of commands. PS. Cool technique with the parens.