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 respectfully disagree. It's not a matter of the complexity of the patch. It's an error in the development of the patch.
I looked over the previous Windows Update patches I installed on my PC and found one from March 2013 that addressed practically the same issue. See Vulnerabilities in Windows Kernel-Mode drivers could allow elevation of privilege, MS13-027. Security Update for Windows 7 KB2807986. I did not get a BSOD after installing it and I have exactly the same drivers now that I had then. In fact I have never gotten a BSOD after installing Windows updates up to now.
Microsoft has a responsibility to develop their patches correctly and test to ensure they work properly and not wreak havoc on their product that people paid them good money for. A BSOD after installing one of their patches is unacceptable.
The list of all update files seem to list two file versions: 6.1.7601.18251 and 6.1.7601.22441
The former is GDR branch, the latter is QFE branch.
If this were the first time Microsoft had problems with an update, but four or five in a row?
How about 23 or more? See MS-MVP Woody Leonhard's http://www.infoworld.com/t/microsoft-windows/another-botched-black-tuesday-kb-2878890-patch-brings-back-two-year-old-kb-951847-repeatedly-228538
The reason I sent you an email with the specs of the four computers involved was to show that this "update" was not platform specific.
The list of all update files seem to list two file versions: 6.1.7601.18251 and 6.1.7601.22441
On the two CAD workstations the .sys files show the aforementioned 18251 files installed on 10/10/2013 or 10/11/2013 and both were (eventually) done manually with no two restart required. Neither has Automatic Updates turned on. I never had any problems with the lack of functionality on any USB devices here, just the installation of the update.
All USB file versions (on these two workstations) can be found at: C:\Windows\winsxs\amd64_usbport.inf_31bf386ad364e35_6.1.7601.2241_none_ic4e76773365f282 or under the same set of numbers with 6.1.7601.18251 substituted and you can also view previously installed versions.
NOTE: these are AMD systems.
If this were the first time Microsoft had problems with an update, but four or five in a row? I really don't want my Grand kids learning about Microsoft Corp in a history instead of a business class.
John Tietjen
Please explain how it can be possible to still have logs of the BSOD to pull off after I did a disk image restore of a previous image backup that overwrites everything on the entire hard drive. In other words, everything on the hard drive' Windows, programs, and data, was overwritten and restored to a previous state in time before the BSOD happened.
