KB2686509 repeatedly fails with Error code 0x8007F0F4

Anonymous
2012-05-08T19:14:06+00:00

KB2686509 repeatedly fails with Error code 0x8007F0F4

Windows for home | Previous Windows versions | Windows update

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-15T03:18:54+00:00

This is obsolete

I wrote a VB Script to fix two problems while running microsoft security update KB2686509

HKLM\SYSTEM\CurrentControlSet\Control\Keyboard LayoutandHKLM\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!

1. Makes a registry backup

2. delete entries in Keyboard Layout

3. checks every keyentry in Keyboard Layouts against existing file in %SystemRoot%\System32

Hope I help someone with this script.

Regards

Christian from Germany

Update 2012/06/03

I have written a batch file too. So you can use this instead the vbs solution.

It's a little bit harder, because the batch file exports the two keys, deletes them, creates blank entries. Then you have to run the KB2686509 again! After doing this do not reboot, press continue in the command window (restoring old entries) and then reboot.

If one of the (bad) keys does not exists, the batch file creates a blank entry, so KB2686509 should work.

Here you can download the batch file http://www.vivus.net/dl/

Was this answer helpful?

3 people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2012-05-08T22:52:59+00:00

New instructions OF 6/19/2012

The FIX-IT’s for this KB have been released today for this Security update. They are available for download at : http://support.microsoft.com/kb/2686509

========================

Since we’ve figured it out, can you see if any of these solutions fixes you up?

Edit on Sunday 5/13 - I figured out the problem.  I had remapped a keyboard key.

If you are hitting this error and do NOT have a faultykeyboard.log file see if you can follow this post and get the patch installed:

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

If you upgraded from Windows ME or 98 to XP (you see nothing but .kbd files listed in your faultykeyboard.log file) -- follow this post:

KB2686509 - Failure - due to upgrade from Windows ME or 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-me-or-98-to-windows-xp.aspx

If you have DLLs noted in the faultykeyboard.log file but can't find them on your PC follow this post:

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**

IF NONE OF THESE WORK, email susan-at-msmvps.com and I'll have someone from Microsoft call you back to fix your system.

==========

Freudi always posts great analysis:

2686509 (MS12-034) - Vulnerability in the keyboard layout handling on Windows XP SP3 - 8:05:12 - patch-info.de:

http://translate.googleusercontent.com/translate_c?hl=en&ie=UTF8&prev=_t&rurl=translate.google.com&sl=de&tl=en&u=http://patch-info.de/artikel/2012/05/08/1324&usg=ALkJrhgcu5tcIlkGoRk0XYjsGBlgYvLePw

Was this answer helpful?

0 comments No comments

397 additional answers

Sort by: Newest
  1. Anonymous
    2012-05-20T00:03:43+00:00

    Glad everyone found a fix.  So did I.  However, I cancelled getting emails for this thread 3 times.  How do I stop getting emails.  Thanks,

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-05-19T19:22:13+00:00

    You know, I'm not much for conspiracy theories but it's a bit tempting to conclude that Microsoft is deliberately forcing this problem on us so we can just eventually give up and ditch our XP machines in favor of a Windows 7 system.  At this point I'm ready to ditch Windows altogether and just learn Linux. <grin>  Seriously, one of the things I didn't mention is that my particular machine was upgraded from Windows 98.  Lo and behold I found an article just for this particular situation at

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

    To make a long story short ... it didn't work.  I exported the keyboard layouts registry key and opened it in Notepad.  I opened my faultykeyboard.log file into Notepad as well.  I did a search for the entries containing the *.kbd files contained within faultykeyboard.log and deleted them from the exported registry key.  I saved the key, reimported it and Windows said "Horray, the key is imported."  (My paraphrase.)  Restarted system ... update fails.  Did the same thing again and the rogue .kbd files were back.  Did the same steps, restart and no success.  Does anyone have any insights as to what I could do at this point?  

    I'd also like to say that I called Microsoft this past week and was routed to a call center and spoke with a gentleman with an Indian accent.  While he did spend nearly four hours trying to tweek my system he encountered the same failure.  He did not give me an incident number and also concluded that the update was not compatible with my machine.  When I tried to ask him to explain why this was the case he just gave me vague and rather generic answers and I know this just isn't the case.  Look, a security update for Internet Explorer 9 wouldn't be applicable or compatible with my XP system and it also wouldn't be offered as an important update.  I told him I was not satisfied with the resolution of the call and wanted to speak with another technician: nobody from Microsoft has called me back.  The way Microsoft is handling this situation is extremely disheartening.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-05-19T16:34:54+00:00

    Can you check the solutions on page one and see if any fix you up?

    Was this answer helpful?

    0 comments No comments