KB2686509 repeatedly fails with Error code 0x8007F0F4

Anonymous

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

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/

0 comments

Answer accepted by question author

Anonymous

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

To perform steps 1 through 3 in the "Let me fix it myself" section, run Microsoft Fix it 50882. ( http://go.microsoft.com/?linkid=9812279 )
To perform step 5 in the "Let me fix it myself" section, run Microsoft Fix it 50883. (http://go.microsoft.com/?linkid=9812280)

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

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

0 comments

397 additional answers

Anonymous

2012-05-12T04:34:31+00:00

LazerJ, go back and read my posts.

Others make that call to phone number or post to Susan. Good luck!

P.S. The fix is not broken. It fixes a security hole by requiring keyboard items to be in system32 folder. Unfortunately, older (even long ago) updates and viruses, installed keyboard items elsewhere. The fix will intentionally not go on to protect these old entries that might be valid, but in many cases are not any more. So, they have to be cleaned up by hand, including via registry update, which is tricky and if you botch it, your system might be killed. Due to the huge number of keyboard modifications and keyboard software that could have been installed, there seems no automatic way to move the non system32 files and correct/remove non system32 registry entries that do not even have files (leftovers). Looks like its every man for himself, find a buddy that knows how to do it, ask Geek Squad, or call Microsoft (see above).

Just making sure the situation is understood, since I didn't understand until the middle of last night. There surely won't be a fix. The only bypass for the non system32 entries is to not install the fix that is holding itself off, until you resolve the non standard entries (non system32).
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-12T04:30:41+00:00

Susan, another situation is bogus registry entries that can be deleted (see my previous post). You have to delete the entries since there are no files to copy (see my previous post).

And many here might not even be able to do a search for the log file (right click on start, do search on C: ) Then they have to know how to backup and save the registry - ask your friends, etc. Or call 1-866-PCsafety without the y, and they will fix it (you hope - good luck).

There was also a guy earlier in this thread that listed a fixit he ran from the Microsoft website, but it was not always able to fix the problem - probably your situation 2. Would not have fixed the situation I posted about before.

This failure to apply is a feature of the fix, until you can get your system cleaned up.

But, it is true that most people will noi be able to fix the problem, so Microsoft needs to install a tool that can run, and give a real report, and options that the tool can do to fix the problem.'

If you can't fix it, ask a friend or call Microsoft to fix it free at 1-866-PCsafety (without the y)

Maybe the traffic to their number will wake them up.
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-12T04:23:39+00:00

Me too. I'm another XP user that can't install update KB2686509.
Was this answer helpful?

0 comments No comments