I am trying to push update MS17-010 in my environment but unfortunatly it is not showing in WSUS.

I am targeting it for Win 7 devices.

Win 7 is selected in product category but this update is not showing.

Download Security Update for Windows XP SP3 (KB4012598) from Official Microsoft Download Center. A security issue has been identified in a.

Please advise what kind of category needs to selected or any alternate method to deploy this update from WSUS.

1. Patching your machines for MS17-010 will do quite a lot to stop the spread of this malware. If you can't get the update through Microsoft update you can go to the update catalog and download and install it manually. I have just fixed Windows Update so it doesn't take forever and a day to check for updates (I had shut off.
2. Ms17-010 is not showing in WSUS (WannaCry Ransomware) Ask Question 3. I am trying to push update MS17-010 in my environment but unfortunatly it is not showing in WSUS. The rollups include MS17-010 Security update for Windows SMB Server according to the link in my last comment.
3. WannaCry ransomware attack currently spreading across the globe and every one is busy working to patch the machines for MS17-010. There has been a doubt on which updates covers this Vulnerability. Patches That Fix the Vulnerability For MS17-010. Security Update for Windows Server 2003 for x64-based Systems (KB4012598).
4. What is Microsoft's MS17-010 Windows patch? Never click on links you don't recognise or download files from people you don't know or trust. The Sun website is regulated by the Independent.

Here is the microsoft link https://support.microsoft.com/en-us/help/4013389/title

I think it would be wise to create a powershell script to check the status on machine. At least we would have report or i can say confirmation.

migrated from superuser.comMay 14 '17 at 6:44

This question came from our site for computer enthusiasts and power users.

2 Answers

Here's the MS bulletin page for MS17-010:

Which does indeed point you to KB4013380:

However, that article in turn lists several other KB articles covering various products effected or patches addressing this vulnerability:

• 4012598 MS17-010: Description of the security update for Windows SMB Server: March 14, 2017

• 4012216 March 2017 Security Monthly Quality Rollup for Windows 8.1 and Windows Server 2012 R2

• 4012213 March 2017 Security Only Quality Update for Windows 8.1 and Windows Server 2012 R2

• 4012217 March 2017 Security Monthly Quality Rollup for Windows Server 2012

• 4012214 March 2017 Security Only Quality Update for Windows Server 2012

• 4012215 March 2017 Security Monthly Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1

• 4012212 March 2017 Security Only Quality Update for Windows 7 SP1 and Windows Server 2008 R2 SP1

• 4013429 March 13, 2017—KB4013429 (OS Build 933)

• 4012606 March 14, 2017—KB4012606 (OS Build 17312)

• 4013198 March 14, 2017—KB4013198 (OS Build 830)

Any one or several of those may show up for you in WSUS, depending on which products are found in your environment.

In my own systems, that means I need to check for both 4012215 and 4012212. However, I don't have to manage any Windows 8 or Server 2012 machines. If those operating systems matter to you, the list is a bit longer.

Additionally, the monthly quality rollups really are rollups. I have machines that failed the March update, but succeeded in April or May. These machines still show 'Failed' when I look at the WSUS reports for these KB#'s, but they're okay because they have the later updates.

It's MS17-006 / KB 4012215 (4012212) for Windows 7 / 2k8

Windows Ms17-010 Patch Download

Not the answer you're looking for? Browse other questions tagged windows-7windows-8wsus or ask your own question.