KB2862330 fails to install

Anonymous
2013-10-08T23:44:09+00:00

Update KB2862330 repeatedly fails to install on Windows 7.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2014-01-15T22:36:31+00:00

EJM888, the OP of this thread, wrote:

This update [i.e., KB2862330-V2] was installed successfully on Jan 14, 2014 (Yesterday)

Excellent!  Thanks for your follow-up.

Marking one or more of the posts in this thread as ANSWER will officially close your thread.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

248 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-01-16T05:39:37+00:00

    Please to anyone reading this, email me susan-at-msmvps.com (change the -at to @) and I'll set you up with a free support case.  We can't solve this any other way.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-01-16T05:20:31+00:00

    I

    I have a dell Studio XPS Desktop 435MT with an older I7 that was bought from Costco several years ago.  I am running Win 7 Pro 64 bit, service pack 1.

    First round installed this update in October, USB ports, all of them, did not work.  Booted with F8, restored, researched all updated found this one stat referred to USB and hid it. Reinstalled all other updates, no problem.  Until today. 

    Downloaded updates, saw another reference to USB (I now scan Everything from Microsoft, cant trust them anymore), said to myself "They must have fixed the thing" and included it with the approved updates. Same as before, no USB.  Did the F8 thing, restored, USB works again. Then I removed this twice cursed update from list, reinstalled updates, no problem.

    Researched again, read all this thread, and "MS13-081: Description of the security update for USB drivers: October 8, 2013". installed just the update by itself as suggested, restarted windows, unplugging all USB items from sockets.  No USB again.  Did the F8 restore but this time after the restore I clicked on the effected hardware/programs button before continuing:(see pic above also)

    Programs and drivers that will be deleted:

    Description                                                     Type

    Microsoft (USB) 06/21/200 6. 1.7601. 18328       Driver

    Microsoft (USB) 06/21/200 6. 1.7601. 18328       Driver

    Programs and drivers that might be restored. these programs might not work correctly

    after restore and might need to be reinstalled:

    Description                                                     Type

    Microsoft (USB) 06/21/200 6. 1.7601. 17586       Driver

    Microsoft (USB) 06/21/200 6. 1.7601. 17586       Driver

    Don't think this is solved quite yet, do you?  Any ideas?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-01-16T03:02:40+00:00

    This morning, installing updates was stuck at 32% for less than two minutes. 2862330, alongside with 2913602, 2913431 and 890830, installed successfully on the first try. I paid absolutely no attention to what updates were going to be installed beyond knowing that I would get an MSRT scan.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-01-16T02:43:29+00:00

    Firstly, are you serious, Microsoft, to re-release this patch? I had enough trouble with it the first time!

    In my experience, the V2 patch affects systems in the same manner as the original patch. Most of our systems installed the patch without issue, but a few got stuck at 32%. The resolution has been wait 10 minutes, then hold in the power button. On the second boot, the system is stuck at 32% again, but finally initiates a shutdown after about 10 minutes. But the shutdown freezes, so hold in the power button again. On the third boot, the update finally finishes after about 5 minutes.

    Update history shows a successful install, but I'm doubtful. At least this process has gotten the systems past this terrible patch (for the second time) after about 30 minutes.

    Was this answer helpful?

    0 comments No comments