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-26T22:27:53+00:00

    Reposting...

    Have you tried the script in Christian's ANSWER post on Page One yet?...

    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!

    1. Makes a registry backup
    2. delete Scancode Map if exists
    3. checks every keyentry in Keyboard Layouts against existing file in %SystemRoot%\System32

     

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-05-26T20:30:24+00:00

    [upgrade path this computer: 1. win95. 2.win 98 upg. 3.win xp pro full installed clean to new drive then personal files moved to new drive and old drive unplugged long ago]

    I tried all three solutions without success and I tried clean boot too.

    Noteworthy: the faultykeyboard.log was in non-latin font. So I searched for kbd*.dll and found no such files on my hard drive. I then deleted all "layout file =kbd*.dll" lines from registry. Update is still a no go.

    Unexpected contents of faulty...log are listed below.  DOH! the text won't cut and paste so its not listed below! Text looks like k  b  d  numbers, tall thin zeroes, little squares, and dots. About three pages worth.

    What next?

    B.

    ps

    never remapped a key.

    B.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-05-26T02:05:50+00:00

    Is there no down side to re-install of SP3?

    How long does it take?

    How many Microsoft update cycles do you have to go through,

    including reboots, etc., to get back up to current level?

    Do you have to rerun manual updates that are not critical, etc.?

    Any problems with virus packages, other software, or settings?

    Just wondering if SP3 re-install is a solution without any downside?

    Does it cause system restore considerations?

    Also, when was that disaster that prevented boot (after SP3?) of a PC using AMD CPU's because HP and others OEM's created their AMD system images on an Intel PC?

    Beware reinstalling SP3 if you have AMD processor still, and had problems before.  The corrections might be required again to be able to get past bootup.

    Was this answer helpful?

    0 comments No comments