Botched Windows Patch KB 3000061 Gets a Working Fix

Reading time icon 2 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

A few days back, we told you about some annoying problems related to the recent Patch Tuesday update, and now it seems that Microsoft has confirmed a fix that seems to be working. What’s interesting to take into account is that it has been offered by a users and not a Microsoft employee.
botched update kb 3000061
Almost with every Patch Tuesday release, Microsoft is bound to make something wrong and issue botched updates. And what’s even worse is that Windows users are being left with them for quite a good while before an official working fix is release.

Such is the case with botched updateĀ KB 3000061 that seems to have received an working fix, as InfoWorld informs us. The KB 3000061 kernel mode driver patch has been said to repeatedly fais to install on many machines, but a Microsoft support engineer has recentlyĀ confirmed a workaround for the problem. And here’s how the fix sounds like:

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}

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.

It wasĀ a regular Windows user whoĀ came up with the original answer on Oct. 17,Ā but only now, more than two weeks since the problem has been reported, Microsoft has acknowledged the solution.

READ ALSO:Ā Windows 10 Gets New DISM Options ā€“ Handles .ffu Files and Multi-volume Images