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: Most helpful
  1. Anonymous
    2012-05-20T00:21:07+00:00

    To stop the thread notifications, log on, click on your user name up by signoff, and...

    select notifications tab, on right is stop emails button for each thread you are monitoring.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-05-20T00:09:34+00:00

    Microsoft has allowed most everybody to do what everybody wants.  That has resulted in exposures, but great flexibility, and a huge tech boom.

    Once an exposure is open, and a lot of code is written based on that lax situation, getting all the bazillion cows back in the barn, results in strays that are in the bushes and swamps being left out.

    Did you read from the front of this thread all the way through?  Try just going back and reading my posts instead of shortcutting and sending to everybody monitoring this thread.

    What I did was just go through the keyboard registry keys, and delete every key that did not contain system32 in it.  BACK IT ALL UP FIRST.  ME to XP left junk that is now checked for security purposes after this fix goes on, so MS does not let it go on to save your a**.  This might not work for you, but you need to try the posts that reportedly help, especially what Susan wrote.

    I don't think importing the entries back in is a good idea.  I came up from ME, and I'm running fine. now (read my posts).  In fact, Microsoft has provided a security fix for a hole to XP at a huge expense to therir support, and risked this happening- strays (I was one) that are outside the system32 folder.  They even prevented the fix from going on, and affecting your system operation by not allowing it to install if there was a possibility it would hurt your system.  It might be that their checking was flawed, but look at all the strange possibilities they had to allow for.  They only allowed it to go on if there was NO possibility it would affect your system.  Do you see complaints about the fix being installed, and it causing problems? 

     If you go back and read my posts, and the others, it should give you good things to check, and if not, email Susan, but do your research first.  I am not all that fond of Microsoft usually, but would you rather they just not put out security fixes for XP because the systems are old and cludged?  I came up from ME, and got my XP to install the fix, so I am glad they did what they did, though it is possible their checking to utterly protect us was not totally correct.  Better that MS err on the safe side, and not install, than install, and kill your PC, right??

    Lets hope this is the way they handle things in the future, as far as ERR on the safe side, anyway, and keep delivering security fixes for XP.  Good Luck!

    By they way, I backed up the keyboard major key that has all the keyboard keys under it, looked at each one, and if a keyboard key did not contain system32 inside, I deleted the whole key - about 10 or more of them, and then rebooted, just in case.  Err on the safe side.

    The fix went on, and I have seen no problems, though I do not have any special keyboards, etc., but I think it was just old ME suff (from Dell?).

    Was this answer helpful?

    0 comments No comments
  3. 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