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.
I finally solved the BSOD problem that KB2862330 was causing on my PC. This is how I did it.
I couldn't find out what was causing the BSOD because my PC kept getting a BSOD after every restart, an endless loop, so I couldn't get the minidump for analysis.
I installed KB2862330 again and of course I got the BSOD. But this time I booted the PC at restart with a WinPE boot disk and inside the WinPE environment I was able to navigate into C:\Windows\Minidump and snag the .dmp file. I copied it to a USB flash drive and then copied to my HP laptop (which strangely enough did not get a BSOD after installing KB2862330) and used BlueScreenView to analyze it.
BlueScreenView stated the BSOD was caused by Driver: hcmon.sys, Address : hcmon.sys+2f4d. I did some research on it and it turns out that hcmon.sys is the VMware USB monitor which is used by VMware Player to detect changes in host USB ports. It is a kernel mode driver that is configured to run when Windows starts. I have VMware Workstation installed on my PC but not on my laptop.
Apparently when KB2862330 is installing and at the same time hcmon.sys is loading, they somehow conflict with each other.
I did a disk image restore of my hard drive, used Autoruns to disable hcmon.sys from auto running when Windows starts, installed KB2862330 and this time it installed successfully, no BSOD. Then I re-enabled hcmon.sys in Autoruns, restarted the PC again and all went well. VMware even works normally with USB support.
In conclusion, the KB2862330 installation causes problems when certain drivers are loaded at the same time the patch is installing. It's a matter of finding out exactly which driver it is and disabling it from running when Windows starts, then re-enabling again after KB2862330 is installed.
Exactly. But they first have to understand the problem. Microsoft doesn't fling these update out on the web and just say "have fun guys, let us know if everything still works!" they send them out after testing. Seriously I know this for a fact they test. When there are issues post release they may not be able to internally repro without log files and understanding from us what we have installed.
True story - a few years back a kernel update was released and people started having bsods. Nothing Microsoft did could repro the issue. They tried everything. Nothing worked to repro the issue. The finally got a guy who had an impacted machine that was closed to a UK support center. Got the laptop in and there was a root kit on the system. Until they were able to get a support case and someone working with an engineer they couldn't fix it. (see http://www.youtube.com/watch?v=3WXlPvmDONQ for that and more behind the scenes stories of Patch Tuesday)
So until someone impacted opens a case, no one can get a perfect and final solution. There is an obvious interaction with something on your system.
May I ask that you help us all by letting me open a case for you?
Hello Susan. Thank you for your important note. I totally agree with you and think everybody should keep this in mind. In this sense my suggestion is to understand only as a temporary workaround to get all other patches installed automatically, also in future.
The perfect and final solution has to come from Microsoft e.g. in an upgraded patch which avoids any problems. Which we don't have yet. Such new patch should/could be installed automatically, even if the old one is hidden I think. So was my experience with an other former patch that caused serious problems.
But of course it's also important to observe the case for upcoming special fixes from Microsoft, which perhaps only address systems with exactly the problems shown. Would be fine, if we could get informed about in this blog.
The problem I'm having is those computers that don't show the update as available, but when manually downloaded, it installs without a problem. The installed update file versions check out and if the update wasn't needed, it would not have installed.
The count is now up to five and all these computers have KB33552 installed, x86 & x64, doesn't seem to matter.
John Tietjen
