ms16-033

Question

I ran the update but the file did not change and when I try to re-update I get that the update is already applied.

How can I update the usb driver to the new file

Answer 1

I'm having a similar issue.  We did a Nessus scan of our Windows 2008 R2 servers...

This is a Consumer-specific forum. You will find support for Windows Server in these forums: http://social.technet.microsoft.com/Forums/windowsserver/en-US/home

Answer 2

I'm having a similar issue.  We did a Nessus scan of our Windows 2008 R2 servers and it reports MS16-033 as not being installed.

1. Reason – C:\Windows\system32\drivers\usbstor.sys has not been patched.
   1. Remote version            : 6.1.7601.17577
   2. Should be                       : 6.1.7601.19144 (GDR) or 6.1.7601.23344 (LDR)

I downloaded the Windows6.1-KB3139398-x64.msu file directly and when I try to install it I get the same message it's already installed.  Looking in the Installed Updates I find the KB3139398 item as being listed there.  I used the wusa.exe /uninstall command to remove the update and rebooted the server.  After the reboot the update now shows as not installed.  So I then ran the Windows6.1-KB3139398-x64.msu file and it showed successful installation and required another reboot.  After the reboot was complete the C:\Windows\system32\drivers\usbstor.sys file still showed as being from 3/10/2011 and being version 6.1.7601.17577. 

I did a search of the Windows folder structure for usbstore.sys and found it in a couple locations including the new 6.1.7601.19144 version but they just do not seem to actually be being installed into the correct OS location.

C:\Windows\winsxs\amd64_usbstor.inf_31bf3856ad364e35_6.1.7601.19144_none_a68baf39ae8b37fd

C:\Windows\System32\DriverStore\FileRepository\usbstor.inf_amd64_neutral_1eb5ea4d83600226

Answer 3

1. USBSTOR.sys
2. The update shows in the install records and I have deleted and reinstall.
3. All updates have been applied.

This is a master image that has passed all vulnerability checks with the exception of this driver

So does #2 mean that KB3139398 is currently listed in Installed Updates (notUpdate History) or...?

Does #3 mean that KB3154070, KB3156013, KB3156016, KB3156019, KB3155178, KB3153171, KB3153199, KB3156017, KB3142024, KB3150513, KB3138612, KB3123862, KB3035583, KB2952664 and KB2990214 are all listed in Installed Updates (not Update History) or...?

What's the "master image" got to do with it? When was the image created? When was it last used to install Win7 on the computer-in-question? Does the computer-in-question belong to you or your employer (or client)?

Answer 4

The file that should update is USBSTOR.sys

The update shows in the install records and I have deleted and reinstall,. All updates have been applied. This is a master image that has passed all vulnerability checks with the exception of this driver

Answer 5

I ran the update but the file did not change...

1. What file did not change?
2. Is KB3139398 listed in Installed Updates (not Update History)?
3. How about KB3154070, KB3156013, KB3156016, KB3156019, KB3155178, KB3153171, KB3153199, KB3156017, KB3142024, KB3150513, KB3138612, KB3123862, KB3035583, KB2952664 and/or KB2990214?