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

2013-07-10T19:37:17+00:00

You look now => This is a Consumer-specific forum. You will find support for Windows Server in these forums: http://social.technet.microsoft.com/Forums/en/category/windowsserver

Dear Mr. Dyer,

First let me apologies for breaking the Microsoft Community code of conduct by going off topic a little and not replying to the original poster; something I see you do not have an issue doing. Having read the FAQ and the code of conduct, I have failed so see anything that states that this is not a forum for server users. My apologies if this is stated elsewhere but, if this is the case then I suggest that you petition Microsoft to make this information more prevalent.

Further, by saying that I must go to another forum to find support, you suggest that server administrators should not be allowed use the information within this forum for formulate solutions. I find it conceivable that you would try to impose such a concept. I can only suggest that again you petition Microsoft and see if they can implement some sort of technical solution to assist you in your desire to deny support to server support staff.

By sharing my experience and solution (although covered under other suggested solutions as well), I simply aimed to aid the community that you are clearly so fond of. However, I will continue to use Microsoft forums as I see fit until requested by someone affiliated with Microsoft requests that I stop.

Once again I apologies for breaking the code of conduct and I will endeavor not to do so again.

Thanks and regards,

Simon Laird
Was this answer helpful?

0 comments No comments
Anonymous

2013-07-10T18:36:07+00:00

Look, I know this is an old topic but I'm just getting round to fixing this on our Windows 2003 R2 Citrix boxes...

You look now => This is a Consumer-specific forum. You will find support for Windows Server in these forums: http://social.technet.microsoft.com/Forums/en/category/windowsserver
Was this answer helpful?

0 comments No comments
Anonymous

2013-07-10T14:31:33+00:00

Look, I know this is an old topic but I'm just getting round to fixing this on our Windows 2003 R2 Citrix boxes. None of these fixes worked directly for me but I did fall in to the last category. I had the faultykeyboard.log and dod not have the DLL files. The extra problem for me here was that the KeyboardLayouts reg key did not referance the file name in my faultyloggythingy.

I used the following extra steps to get round the problem.

My faultkeyboar.log contained one entry - kbd101a.dll

I seacrhed my registry for it and it showed up under :

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\KeyboardType Mapping\KOR]

and

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\Terminal Server\KeyboardType Mapping*KOR*]

I then manually checked all of the KeyboardLayouts entries and found that the last one was for Korean

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts\E0200412]

"Ime File"="IMEKR70.IME"

"Layout File"="kbdkor.dll"

"Layout Display Name"="Microsoft IME 2003"

"Layout Text"="Microsoft IME 2003"

I made the somewhat tenuous link between the two and exported and deleted the Korean keyboard layout.

I ran the hotfix again and it installed as if nothing had ever gone wrong.

EDIT: Confirmed this on my second Cserver as well. The file name was differant but it was still listed under

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\KeyboardType Mapping\KOR]

Removing the KOR Keyboardlayouts reg entry fixed this for me.
Was this answer helpful?

0 comments No comments