KB2862330 known issues

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: 100000D1(parameter1, parameter2, parameter3, parameter4)

    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 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) or when a USB port resumes from selective suspend.

    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.  

      Restart the computer one more time after you complete the installation of security update 2862330. The additional restart will make sure that Usbport.sys is updated. 
    • Scenario 2
      A computer has USB companion controllers (for example, a USBEHCI controller together with a USBOHCI or USBUHCI controller) but does not have Windows 7 SP1 servicing stack update 2533552 installed. Update 2533552 should be installed to make sure that the installation of future updates is successful.  

      To resolve this issue, take one of the following actions:
      • Install update 2533552 before you install security update 2862330. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 
        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

        Note Install this update to enable future updates to install successfully on all editions of Windows 7 or Windows Server 2008 R2.
      • Disable all USBEHCI 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 Usb stack reports that there is a third-party driver that has the same name installed. Therefore, the Usb stack does not install the updated driver from security update 2862330. This problem can occur when the user installs an update that has a Usb.inf file, then installs an update that has both Usb.inf and Usbport.inf files, and then uninstalls the second update. 

      Disable all USBEHCI controllers by using Device Manager before you install security update 2862330. The successful installation of security update 2862330 will 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.

3 Thoughts on “KB2862330 known issues

  1. well, today i had several bsod’s with our SBS2008 but it started with this one.
    so will check tomorrow if it was this KB.

    but the most anoying part is, that since a few weeks, several services which are on automatic, will stop after a few seconds after a server reboot which is necessary after a Microsoft update.

    which result in the fact that clients are unable to connect to the AD.
    server services
    secondary logon
    ip helper
    network policy
    are a few of the services that are stopped.

  2. bradley on October 25, 2013 at 6:03 pm said:

    Did you install the update? As the bsod should be immediately after right after reboot after installing the update.

  3. Thank you for your response.
    yes the update was installed and caused the bsod. it was followed by another bsod about memory_manager. So it was murphy’s law for me that evening. Unfortunately after every reboot i need to check the running services due to the fact that several of them will stop for ?no? reason? like secondary log on, network policy server, Server and a few more. Checking with your default-sbs-2008-running-services.aspx i made sure all of them are set correctly. But after restarting them a few are stopped again. So this time i only started the ones that are needed for clients to log on to the domain.
    currently 4 services are stopped: IP Helper, Application experience, Background Intelligent Transfer Service and finally System Event Notification Service.

Post Navigation