This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Update KB2862330 repeatedly fails to install on Windows 7.
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.
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.
The sorry is for all of us in the security community. The bad guys work together. The good guys expect someone else to spend the time.
Microsoft built an update that could not and did not take into account all of the third party vendor interactions. So one cannot expect them to magically 'fix this' without at least some effort on your part to provide log files. Since you apparently can repro this, may I please ask that you do take the time to help all of us by working with Microsoft to get a better understanding of what virtual usb provided by VM/Vspehere is interacting with this update.
Please?
Email me at susan-at-msmvps.com and change the -at- to @ and I'll set up a free support case. If you never called Microsoft for a support case you should do that first, not last. Issues with security updates are always a free call.
But if you think that Microsoft will magically be able to fix this without getting log files from your system, this is an unreasonable expectation on your part.
Call support. It will be a free call.
My post was simply for the records and for others to be warned that you can still get into trouble when applying this fix e.g. if you are running VMs on vSphere having virtual USB like in the case of our customers.
To say it with your own words:
We already wasted so much time to track down the root cause for the problem that it is an unreasonable expectation from MS that we will invest additional time getting their software fixed.
Sorry.
You need to open a support case. Microsoft considers it 'fixed' and the rest of the impacted folks will need to open a case to get it fixed for them.
There is obviously some device on your build interacting with this patch.
But if you think that Microsoft will magically be able to fix this without getting log files from your system, this is an unreasonable expectation on your part.
Call support. It will be a free call.
Problem still seems to be unresolved.
2008 R2 Server hangs at 32% on reboot infinitely.
WE will remove the update for all our customers for now until MS fixes the problem (if this ever happens)
