KB2686509 repeatedly fails with Error code 0x8007F0F4

Anonymous
2012-05-08T19:14:06+00:00

KB2686509 repeatedly fails with Error code 0x8007F0F4

Windows for home | Previous Windows versions | Windows update

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 No comments
Answer accepted by question author
Anonymous
2012-05-15T03:18:54+00:00

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/

Was this answer helpful?

3 people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2012-05-08T22:52:59+00:00

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

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

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

Was this answer helpful?

0 comments No comments

397 additional answers

Sort by: Most helpful
  1. Anonymous
    2012-05-10T22:03:14+00:00

    Mark - this update does not apply to Server 2008, so there's no risk of this update failing on Server 2008 era.

    Are you seeing this on all 80 of the Windows 2003 servers?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-05-10T21:51:36+00:00

    However I found four missing keyboard layouts were required to install this update. These were found by opening 'faultykeyboard.log' in 'C:\Windows' and were, in my case:

    I am sorry, but we have about 80 Windows 2003 servers, and 250 2008 Servers,  and we do not have:

     A 'faultykeyboard.log' in 'C:\Windows'

    I really can't see me removing all of these Servers from de AD-domain, because of GPO settings with Keyboard layouts tru all over Europe WAN via VPN connections, becuase Microsoft can't make a decent hotfix - no way I'm going to do that.

    Is there not a better solution for AD-Networks...?

    Regards,

    MP

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-05-10T21:27:13+00:00

    For now, hide the thing until I can convince someone at Microsoft to build a FixIT tool.

    Just post a "me too" here indicating that you are an XP. 

    With all due respect Bear, I wouldn't do a new thread, I'd pile on this one and showcase the body count.

    I have one here, testing another myself.

    I rather would say:

    Not Windows XP, but better; Windows NT 5.2 kernel instead, while the same error exist on Windows Server 2003 (R2) I386 and x64 versions too, you know.

    Ragards,

    MP

    Was this answer helpful?

    0 comments No comments