Security Update KB2686509 will not install- error code 0xf0f4

Anonymous
2012-05-09T04:25:33+00:00

After download from Microsoft Update Security Update for Windows XP (KB2686509) won't install-what do I need to do?

Windows for home | Previous Windows versions | Install and upgrade

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.

0 comments
Answer accepted by question author
Anonymous
2012-05-21T04:44:27+00:00

Wow you saved me from so much 'update' distress. Indeed I had done a similar thing somewhere in my distant memory. Simply deleting my hacked registry key entry as shown below solved my problem.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout]

"Scancode Map"=hex:00,00,00,00,00,00,00,00,02,00,00,2a,00,3a,00,00,00,00,00,00

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2012-05-20T16:57:10+00:00

I struggled with this for days. Here is what was happening and what I did that worked.

faultykeyboard.log listed 24 entries of the form   kb*.kbd

I searched and no such files exist on my computer.

By running regedit and looking I found 24 abnormal looking subkeys matching the list in:

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Keyboard Layouts

After carefully reviewing the potential for damage I discovered that the operating system automatically restores this section of the registery if a boot failure occurs.

I then boldly deleted all subkeys of the type *.kbd from the registry. I deleted faultykeyboard.log. I rebooted then ran the update KB2686509 and it installed and rebooted the computer.

The problem is gone.  Everything works.

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2012-05-18T17:07:03+00:00

Good tips in this thread. It ultimately led me to my solution. The problem computer here was also running a version of Windows XP modified with NLite.

I was able to resolve this problem by first opening the faulty keyboard log. On the problem computer, it was located in C:\Windows\system32\faultykeyboardlog.log.

The faultykeyboard.log file simply listed these four items:

KBDDV.DLL

KBDUSX.DLL

KBDUSL.DLL

KBDUSR.DLL

I went to a computer that I knew had an unmodified version of Windows XP Professional, copied those four DLL files from C:\Windows\system32. I then transfered them to the C:\Windows\system32 on the problem computer and re-ran the manual installation file for KB2686509 which can be downloaded at http://www.microsoft.com/en-us/download/details.aspx?id=29804.

Problem solved.

Was this answer helpful?

0 comments

70 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2012-05-14T23:35:01+00:00

    KB2686509 - Failure - due to remapping of a key - TechNet Articles - United States (English) - TechNet Wiki:

    http://social.technet.microsoft.com/wiki/contents/articles/10829.kb2686509-failure-due-to-remapping-of-a-key.aspx

    KB2686509 - Failure - due to upgrade from Windows 98 to Windows XP - TechNet Articles - United States (English) - TechNet Wiki:

    http://social.technet.microsoft.com/wiki/contents/articles/10876.kb2686509-failure-due-to-upgrade-from-windows-98-to-windows-xp.aspx

    KB2686509 - Failure due to missing DLL files - TechNet Articles - United States (English) - TechNet Wiki:

    http://social.technet.microsoft.com/wiki/contents/articles/10880.kb2686509-failure-due-to-missing-dll-files.aspx

    See if these help anyone, holler back if they do not.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-05-15T00:22:29+00:00

    Yes, I will email you the file, and this is how we fixed it, from a neophytes prospective:

    1. Search C:/  for a file named faultykeyboard.log.  It will lead you to a .txt file with a list of .kbd file names, mine looked like this:

    kbdsp.kbd

    kbdsp.kbd

    kbdno.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdus.kbd

    kbdla.kbd

    kbdus.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdla.kbd

    kbdycl.kbd

    2. explore C:/  to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts

    3.Using regedit (From the run place at start button) export the Keyboard Layouts registry file somewhere that you can easily find, I used the desk top. 

    1. Use the edit feature, and use cntl F to find each of the files listed in the faultykeybord.log, and delete them. Notice that some are there multiple times, and you have to delete each instance

    5.Go back to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts

    and save the original keyboard layouts file with a different name, I just added a 1 to the file name.

    1. Save the file you have on your desktop with the name Keyboard Layouts (the original file name) back to the registry.
    2. Reboot
    3. Reinstall the annoying patch
    4. If it worked, then you are done.  I left the original registry file with the name change out there just in case, but all seems well so far, probably delete that file in a few days.

    Thanks so much to Susan for her help, if I can do it, anyone can, I don’t know registry files from horse apples!

     

    I believe this is missing a step.

    After backing up the the original HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts at Step 5, I had to delete the old registry key before saving the edited registry key back at Step 6.

    If I didn't delete the existing registry key it left the bad entries in there when I merged the edited registry file back into the registry. All of the kbd???.kbd, etc sub-keys were still in the registry and the update continued to fail.

    After I deleted the existing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts and imported the edited registry file, I double checked to make sure all the kbd???.kbd references were removed.

    I then rebooted and the update installed successfully.

    Was this answer helpful?

    0 comments