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-29T19:40:24+00:00

I tried the steps shown in this link:

http://social.technet.microsoft.com/wiki/contents/articles/10880.kb2686509-failure-due-to-missing-dll-files.aspx

But my missing .dlls (kbd101.dll , kbd101a.dll , kbd101.dll , kbd101a.dll) can't be found within the registry file.

What else can I do?
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-30T00:37:16+00:00

teopini,

I assume that you are saying that those dll's you name are found in your faultykeyboard.log?

If they are, then you need to make sure they are not on your pc using start right click search, and ***make sure the option to look at system files is turned on in your options.***

If the files are not on your PC, but are in the faultykeyboard.log, then they must be in your registry, so are you using regedit and highlight my computer at the top of the registry, then do edit find, with each name. Go back to the top and highlight my computer each time, or find will only pick up where it left off. Let us know.

I found the kbd101a.dll and kbd101a.dll in a jpn and kor member, but they are in the system32 folder, and the directory says so.

I think these might be on your pc, but you can't see them (is the look at system files turned on)?
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-30T11:11:17+00:00

KB2686509 repeatedly fails with Error code 0x8007F0F4

I am following the instructions to install KB2686509 on a machine that was converted from Windows ME to Windows XP and I have a question. Near the bottom of the instructions there is a paragraph that reads:

"And save the original keyboard layouts file with a different name. You can, for example, add a 1 to the registry file name so you have a backup. Now delete everything under the keyboard layout key. Now save the edited regsitry file of Keyboard Layouts (the original file name) into to the registry. You can click on the file and it will reimport it into the registry replacing the kbd files in the registry."

Is the bold, underlined sentence above correct? Should it be "keyboard layout" key or should it be "keyboard layouts" key? The edit was done to the "Keyboard Layouts" key so why would the instruction say "...delete everything under the "keyboard layout" key? I'm new to the 'regedit' process and want to be sure before I proceed with deleting. Thanks.
Was this answer helpful?

0 comments No comments