(On XP, in the event log, this problem will show as "Installation Failure: Windows failed to install the following update with error 0x8007f0f4: Security Update for Windows XP (KB2686509)." in the event log).
There's some help at http://support.microsoft.com/kb/2686509, but on my system there was no Faultykeyboard.log file to examine.
Examination of the relevant registry keys
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts
showed no file reference entries with files outside of System32. However, it did show that I had a "Scancode Map" installed in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout
.
By removing the Scancode Map key from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout
and then rebooting, I was able to install KB2686509 without further trouble, and I could reinstall my Scancode Map later.
I wrote a VB Script to fix two problems while running Microsoft security update KB2686509
HKLM\SYSTEM\CurrentControlSet\Control\Keyboard Layout\Scancode Map
and
HKLM\SYSTEM\CurrentControlSet\Control\Keyboard Layouts
for those who are no registry freaks.
Here you can download my little hotfix as ZIP-file.
What does it do? Nothing magic!
I have a .reg file that disables the Caps lock key. I also have one that restores it back to the default. I saw a reference to re-mapped keys on another site so I tried resetting my caps lock hack back to the default and the Microsoft Security update KB2685609 installed successfully.
Problem solved.
Disable_caps_lock key UNDO remove_all_scancode_mappings.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout]
"Scancode Map"=-
Disable_caps_lock key.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout]
"Scancode Map"=hex:00,00,00,00,00,00,00,00,02,00,00,00,00,00,3a,00,00,00,00,00
Just in case anyone else might benefit from this: after running this "fix-it" (216893), this patch (KB2686509) was able to be successfully applied on my x86 windows sp3 pc.
The advantage of trying this first is that you don't have to muck around in the registry or run some script. I believe I ran the "fix-it" to "enable windows key" (even though I don't think it was ever disabled), rebooted, patch applied, problem resolved (until next time...)
User contributions licensed under CC BY-SA 3.0