Security update MS17-010 addresses several vulnerabilities in Windows Server Message Block (SMB) v1. The WannaCrypt ransomware is exploiting one of the vulnerabilities that is part of the MS17-010 update. Computers that do not have MS17-010 installed are at heightened risk because of several strains of malware. This article provides several quick methods to detect whether the computer is updated.
Method 1: Check by installed Knowledge Base number
Use the following table to check for any of the listed updates (except the ones marked as "Does not contain MS17-010 patch"). If any of these is installed, MS17-010 is installed.
Table 1 of 2: Windows 7 SP1 and later. The following rollup KBs contain the fix (except in the "April Security Only 4B" column). Beneath each KB number is the updated Srv.sys version number.
Windows versions
|
March Security Only Update (3/14/17)
|
March Monthly Rollup
(3/14/17)
|
March Preview of Monthly Rollup
(3/21/17)
|
April Security
Only Update
(4/11/17)
|
April Monthly Rollup
(4/11/17)
|
April Preview of Monthly Rollup
(4/18/17)
|
May Security Only Update
(5/09/17)
|
May Monthly Rollup
(5/09/17)
|
Download link
|
Windows 7 SP1 and Windows Server 2008 R2 SP1
|
4012212
6.1.7601.23689
|
4012215
6.1.7601.23689
|
4012218
6.1.7601.23689
|
4015546
Does not contain MS17-010 patch
|
4015549
6.1.7601.23689
|
4015552
6.1.7601.23689
|
4019263
6.1.7601.23762
|
4019264
6.1.7601.23762
|
Windows 7 SP1 and Windows Server 2008 R2 SP1 update history
|
Windows 2012
|
4012214
6.2.9200.22099
|
4012217
6.2.9200.22099
|
4012220
6.2.9200.22099
|
4015548
Does not contain MS17-010 patch
|
4015551
6.2.9200.22099
|
4015554
6.2.9200.22099
|
4019214
6.2.9200.22137
|
4019216
6.2.9200.22137
|
Windows Server 2012 update history
|
Windows 8.1 and Windows Server 2012 R2
|
4012213
6.3.9600.18604
|
4012216
6.3.9600.18604
|
4012219
6.3.9600.18604
|
4015547 Does not contain MS17-010 patch
|
4015550
6.3.9600.18604
|
4015553
6.3.9600.18619
|
4019213
6.3.9600.18655
|
4019215
6.3.9600.18655
|
Windows 8.1 and Windows Server 2012 R2 update history
|
Windows 10 Version 1507
|
4012606
10.0.10240.17319
|
4016637
10.0.10240.17319
|
-
|
-
|
4015221
10.0.10240.17319
|
-
|
-
|
4019474 10.0.10240.17394
|
Windows 10 update history
|
Windows 10 Version 1511
|
4013198
10.0.10586.839
|
4016636
10.0.10586.839
|
-
|
-
|
4015219
10.0.10586.839
|
-
|
-
|
4019473
10.0.10586.916
|
Windows 10 update history
|
Windows 10 Version Windows Server 2016
|
4013429
10.0.14393.953
|
4016635
10.0.14393.953
|
-
|
-
|
4015217
10.0.14393.953
|
-
|
-
|
4019472
10.0.14393.1198
|
Windows 10 and Windows Server 2016 update history
|
Table 2 of 2: Continued for the May and June 2017 updates.
Table 2: Other Windows versions. Use KB 4012598 for the security update.
Table 3: Additional updates that contain the fix.
Windows 8.1 and Windows Server 2012 R2
Windows server 2012
Windows 7 SP1 and Windows Server 2008 R2 SP1
Method 2: Check by %systemroot%\system32\drivers\srv.sys file version
Use the following chart to check the file version of %systemroot%\system32\drivers\srv.sys. If the file version is equal to or greater than the listed version, MS17-010 is installed.
Windows versions
|
Minimum updated Srv.sys version
|
Windows XP
|
5.1.2600.7208
|
Windows Server 2003 SP2
|
5.2.3790.6021
|
Windows Vista
Windows Server 2008 SP2
|
GDR:6.0.6002.19743, LDR:6.0.6002.24067
|
Windows 7
Windows Server 2008 R2
|
6.1.7601.23689
|
Windows 8
Windows Server 2012
|
6.2.9200.22099
|
Windows 8.1
Windows Server 2012 R2
|
6.3.9600.18604
|
Windows 10 TH1 v1507
|
10.0.10240.17319
|
Windows 10 TH2 v1511
|
10.0.10586.839
|
Windows 10 RS1 v1607
Windows Server 2016
|
10.0.14393.953
|
Method 3: Check by WMI and Windows PowerShell
Use WMI and Windows PowerShell to determine whether MS17-010 fixes have been installed.
WMI command
To find a specified KB number, open an elevated Command Prompt window, and then run the following command:
wmic qfe get hotfixid | find "KB1234567"
Notes
PowerShell commands
To check in the local system, run the following administrative PowerShell cmdlet:
get-hotfix -id KB1234567
Notes
To check all computers in an Active Directory domain or OU, run the following administrative PowerShell cmdlet on a domain controller:
foreach ( $n in (get-adcomputer -searchbase ‘OU=workstations,dc=contoso,dc=com’ -filter * -property * | select name )) {get-hotfix -computername $n.name -id KB1234567}
Note The "OU=workstations,dc=contoso,dc=com" part can be changed to point to the root of an Active Directory domain directory partition, such as "dc=contoso,dc=com" to search computers in the entire domain. In this command, replace <KB1234567> with the actual KB number.