Microsoft endorses workaround for botched Windows patch KB 3000061

Microsoft endorses workaround for botched Windows patch KB 3000061

Two weeks after users offered a fix for the MS 14-058/KB 3000061 kernel mode driver installation problem, Microsoft confirms it works

This month's Black Tuesday crop of patches held more than a few surprises. True to form, my choice for the "most likely to splat," the KB 3000061 kernel mode driver patch, repeatedly fails to install on many machines. Although the Knowledge Base article hasn't been updated, Microsoft support engineer joscon confirmed a workaround for the problem on Thursday afternoon.

Poster CountryKING on the Technet thread on the topic came up with the original answer on Oct. 17, and it was refined by poster lord_vader later that same day. The trick is to manually delete a Registry key, HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{e7ef96be-969f-414f-97d7-3ddb7b558ccc} , reboot, and reinstall KB 3000061. The KB 3000061 installer recreates the key (with a different GUID), so you don't need to restore it.

Here's the official word from Microsoft:

To alleviate this problem on Windows 8 and Windows Server 2012 based systems, please export and delete the following registry value, reboot your system and then re-attempt the update: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{e7ef96be-969f-414f-97d7-3ddb7b558ccc}

If deleting the above registry value does not resolve the issue for you, please ping this thread as I'd like to see your follow-up CBS.logs from the system...

This is the supported method to resolve this issue (and as others have noted above, this works).  This occurs when servers have been upgraded from 2008R2 to 2012 (or WinVista to Win8).  The key is being carried over in these scenarios and not being set to the proper value.  We're investigating why this occurred but deleting the key and rebooting the system will resolve the problem.  If you see something otherwise, please let me know.

Surprisingly, it looks like the culprit is an in-place upgrade. If you performed an in-place upgrade from Vista to Windows 8, or Server 2008 R2 to 2012, your tail may be wagging in the wind. Apparently those who performed clean installs, or are running Windows 8.1 or Server 2012 R2, will have no problem applying KB 300061. At least, they won't have this problem.

I have no idea why it took Microsoft two weeks to confirm CountryKING/lord_vader's suggestion.

Follow Us

Join the newsletter!


Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.

Tags Microsoftoperating systemssoftwareWindowsMicrosoft WindowsKnoforum

Show Comments