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 No 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 No 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 No 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 No comments

70 additional answers

Sort by: Newest
  1. Anonymous
    2012-06-27T21:44:09+00:00

    I had a home user with this issue and i troubleshot over join.me.

    could not install the update, even manually. So i took one of our XP machines here, selected every dlll file in system32 that started with KB (so kb*.dll) and copied them over to the remote machine using one of our webservers.

    i unzipped in the windows/system32 dir overwriting all files. He originally had about 40 kb* files and from the other machine I took 89 of them. So clearly he was missing some DLL's.

    I believe that a colleague had built this machine with ninite several years ago. I read something else that said that might be the problem, and we were doing machines with nLITE at that time.

    I cant attach the files here as this forum does not have attachments, but all you need is another windows xp machine to fix this. they are getting rarer these days, but should still be available somewhere!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-06-08T23:11:49+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

    IT WORKED For ME !!! Delete that entry if it still didn't work for you after having deleted (in the registry) all references to the dll contained in the "faultykeyboard.log"... THX A LOT

    Was this answer helpful?

    0 comments No comments