Windows 10: Query on Defender versioning Details for Defender Security Update version or Engine Version

Hi,


Myself Aniket, I have started working recently on MS Defender. I would like to understand how the Security Update Version or Engine Versiondoes the versioning gets a name?


AMProductVersion - 4.18.2003.8

EngineVersion - 1.1.16900.4

AVSignatureBaseVersion - 1.313.0.0

AvSigVersion . - 1.313.906.0


Please find the below example:

Like for the OsBuild 10.0.18305.1003, I have read on MS Docs that this string is formed has it subparts like

• Major version 10
  
• Minor version 0
• Build number 18305
• Build revision 1003

Thanks & Regards,


Aniket Chakraborty

:)

 

Query on Defender versioning Details for Defender Security Update version or Engine Version

Hi,

Myself Aniket, I have started working recently on MS Defender. I would like to understand how the Security Update Version or Engine Version
does the versioning gets a name?

AMProductVersion - 4.18.2003.8

EngineVersion - 1.1.16900.4

AVSignatureBaseVersion - 1.313.0.0

AvSigVersion . - 1.313.906.0

Please find the below example:

Like for the OsBuild 10.0.18305.1003, I have read on MS Docs that this string is formed has it subparts like

• Major version 10
  
• Minor version 0
• Build number 18305
• Build revision 1003

Thanks & Regards,

Aniket Chakraborty

 

Query About Windows Defender Versioning

Thanks for your very very quick reply!

But i was wondering as to how they are named by MS?

Like for the OsBuild 10.0.18305.1003, I have read on MS Docs that this string is formed has it subparts like

• Major version 10
  
• Minor version 0
• Build number 18305
• Build revision 1003
  

- So i was wondering if something similar applies to Windows Defender releases as well ?

- And also anywhere where MS displays what's the total count that MS Defender's can detect?

Thanks Again!

 

Windows Defender issues following Windows10 Creator Update Version 1703

Hello,

There may be a few possible reasons why Windows Defender would suddenly have performance issues. To further assess on this, kindly provide the information listed below:

• Did this issue occur only after the Creators Update?
• What are the troubleshooting steps you have done so far?
• Are you getting any error message when trying to launch Windows Defender Security Center?
• does this issue also happens to other Windows app or programs?
• What's the status of your CPU and Memory performance (Task Manager) when this issue starts to happen?

In the mean time, we suggest checking if your Windows Defender is currently on the latest version, and update it if otherwise. You can find more information about Windows Defender updates
here.

Keep us posted for any changes or outcome.