KB2862330 fails to install

You lost me?  It should be offered up to systems.  I've seen it unchecked (still) but it is being offered up.

if...

"KB2862330 is not a USB driver update, it's a security update for USB drivers"

then...

It should not install manually? should have informed that it is not required on this system?

and... working on one of these systems down the road, how would you know except by checking the .sys file numbering?

Respectfully,

jrt

If "the USB drivers are up to date" - how could they be without this update?

KB2862330 is not a USB driver update, it's a security update for USB drivers.

If KB2862330 has not been installed, is not hidden, and is not currently offered by Windows Update, don't worry about it.

This one is a toughie, there's no one silver bullet fix here.

If you have avast a/v disable it during the update.

If you have unusual usb devices, remove them during the update.

they are wrong in that if you have up to date usb devices, you still need this update.

The updated KB2862330 notes the issues found in investigation:

Known issues with this security update

• Symptoms

After you install this security update on a computer that is running Windows 7 or Windows Server 2008 R2, you may receive a D1 or 100000D1 Stop error message that resembles the following:

*** STOP: 0x000000D1(parameter1, parameter2, parameter3, parameter4)

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Note The 0x000000D1 error is also known as a "0xD1" error.

Cause ****Security update 2862330 should update all the drivers for the USB 2.0 core stack. However, in some specific computer configurations, the Usbport.sys driver is not updated. The binary version mismatch occurs even when the drivers all belong to the same component. After the component is in a partly updated state, a D1 or 100000D1 Stop error may occur.

The stop error is observed when the computer is transitioning to or from a lower power state (Sleep or Hibernation) when a USB port resumes from "selective suspend" mode or during the installation of the update itself.

Affected scenarios and resolution
Three scenarios are identified in which a partial update of a component might occur. - Scenario 1

Third-party software such as antivirus software locks down Usbport.sys. The software prevents Usbport.sys from being updated by the installation of security update 2862330.

Resolution

Restart the computer one more time after you complete the installation of security update 2862330. By restarting the computer, you make sure that Usbport.sys is updated. - Scenario 2

A computer has USB companion controllers (for example, a USB Enhanced Host Controller together with OpenHCD USB Controller or USB Universal Host Controller) but does not have Windows 7 servicing stack update 2533552 installed. Update 2533552 should be installed to make sure that the installation of future updates is successful.

Resolution
To resolve this issue, take one of the following actions: - Install update 2533552, and then restart the computer before you install security update 2862330. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2533552

(http://support.microsoft.com/kb/2533552/ )

An update that prevents a "0xC0000034" error message when you try to install Windows 7 SP1, Windows Server 2008 R2 SP1, or Windows Embedded Standard 7 SP1 is available

Notes - Install this update to enable future updates to install successfully on all editions of Windows 7 or Windows Server 2008 R2. - We recommend that you restart the computer after you install update 2533552. Then, you can install security update 2862330. - Disable all USB Enhanced Host Controllers by using Device Manager before you install security update 2862330. You can re-enable the controllers after you complete the installation of security update 2862330. - Scenario 3

The USB stack is corrupted. For example, the servicing stack reports that there is a third-party driver that has the same name installed. Therefore the servicing stack does not install the updated driver from security update 2862330. This problem can occur when the user first installs an update that has a Usb.inf file, next installs an update that has both Usb.inf and Usbport.inf files, and then uninstalls the second update.

To verify whether scenario 3 has occurred after you install 2862330, examine the %windir%\inf\setupapi.dev.log file for any of the following entries: - Cannot reflect over existing driver file 'C:\Windows\system32\drivers\usbport.sys' - Cannot reflect over existing driver file 'C:\Windows\system32\drivers\usbehci.sys' - Cannot reflect over existing driver file 'C:\Windows\system32\drivers\usbuhci.sys' - Cannot reflect over existing driver file 'C:\Windows\system32\drivers\usbohci.sys'

Resolution

Disable all USB Enhanced Host Controllers from Device Manager before you install security update 2862330. By successfully installing security update 2862330, you make sure that the USB 2.0 core stack is no longer corrupted. You can re-enable the controllers after you complete the installation of security update 2862330.

• Installing security update 2862330 does not update USBCCGP.SYS or HIDPARSE.SYS on virtual machine guests.

This behavior is by design on eligible Windows-based computers that are configured as virtual machine guests.

• After you install security update 2862330, your computer may restart two times. For more information about updates that require multiple restarts, click the following article number to view the article in the Microsoft Knowledge Base:

2894518

(http://support.microsoft.com/kb/2894518/ )

Task sequence fails in Configuration Manager if software updates require multiple restarts