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-24T00:49:25+00:00

Bill Sessoms,

If you still get the faultykeyboard.log, you didn't get rid of all the keyboard registry members that don't have system32 showing in the file name in them, i.e., the ones still being listed.

They can and in my case did, have same .kbd in multiple registry members. Be sure to back up registry entries in case for some reason, you have a problem later.

Try above, but I saw this in a post. Don't know if system restore might get you back, but I saw this by doing a google about the microsoft update location error...

"You just need to reinstall windows automatic updater. aka. wuapi.dll, its in the Windows root ini right click au and click install, you'll need the file or the windows disk."

Don't know if that will work, and make sure you do a create checkpoint and/or backup before you try it. You might want to just do some googles of your own, or call 1-866-pcsafety without the y to have microsoft fix your microsoft update (windows update) for free. Good luck!
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-24T00:35:41+00:00

Statlaz

i think the fix checks the registry for compliance, even though there are no files any more, which was the best protection Microsoft could give. They might not be able to access files during the install checks, and if they did, virus packages might get mad, etc.

I suggest you back up the registry entries with those dll's and delete them. Should be no problem unless you have Japanese or Korean keyboard. (I googled those dll's)

I started to suggest this in the first place. Sory I didn't, but I err'ed on the safe side, I guess.

If it fixes it, welcome to the other side!
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-23T22:53:59+00:00
Have you tried the script in the 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!

Makes a registry backup

delete Scancode Map if exists

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

Hope I help someone with this script.

Regards

Christian from Germany
Was this answer helpful?

0 comments No comments