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-16T04:05:01+00:00

Like, have you spent a few minutes and seen how many of us XP people got this to go on?

I'm running XP Home SP3, and the fix went on after I took the actions posted previously.

This says XP, too...

http://support.microsoft.com/kb/2686509

No reply is necessary unless I'm wrong, or you have another question. No detriment intended by my post. We all had problems with it or we wouldn't be here. :-)

Good Luck everybody!

By the way, the script that is mentioned just above with the tribute to Christian is on Page 18 of this thread.

Also don't forget - Contact Susan if you need personal help, but somebody said they worked for 3 hours with MS, and finally fixed it using info in this thread.
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-16T04:11:32+00:00

I have tried every solution here, and more. I was hoping the VB script from Cristian a couple of days ago would have been sucessful but that failed to install each time I tried it. Maybe I read wrong and it was ONLY for systems updated from a previous windows version.

What I find rather odd with my system is that since I built it, I have only ever used a Microsoft Multimedia keyboard.

One solution I thought might have helped is that I have a "CurrentControlSet" a "CurrentControlSet 001", "CurrentControlSet 002" and "CurrentControlSet 005", the latter having more entries than the rest. But now, they all have exactly the same number and names of the keyboard layouts, and those layouts are reflected in the System 32 and dll Cache folders.

I now no longer get a faultykeyboard report. But it STILL refuses to alow the update.

I must have spent more than 24 hours on it by now.... Lets hope we get a solution soon.
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-16T04:13:25+00:00

It's applicable to Windows XP and Server 2003. Got a faultykeyboard.log file? Been upgraded from ME or Windows 98?
Was this answer helpful?

0 comments No comments