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: Oldest
  1. Anonymous
    2012-07-06T02:58:03+00:00

    You are guru enough for me!  Thank you.  I did search as you suggested but I don't recall if I had the option to check Keys, value, and data so perhaps I didn't get a full search.  The computer with this problem is at another location.  I will be there on the weekend and will try this.  I sure do appreciate your help.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-07-16T21:15:34+00:00

    Honor is due to Christian! His batch file works like a charm!

    Evan

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2012-07-16T22:33:39+00:00

    I've sent Susan an email (per her instructions) since none of the above solutions worked.  So if anyone else has come across the same issue as me, and figured out a solution, please let me know.  Here's what I have so far:

    • No "FaultyKeyboard.log" file in C:\Windows
    • No remapped keys (checked both Keyboard Layout and Keyboard Layouts)
    • Windows XP Professional x86 (no upgrade from ME/98)
    • Tried Microsoft's Fix Its, no luck
    • Tried Christian's batch file, no luck
    • Tried exporting the keys (Keyboard Layout/Keyboard Layouts), Deleting, Creating blank keys, and reinstall KB2686509, but no luck
    • Running as VM in offline environment
    • Interestingly enough, the patch originally worked when I installed it back in May on top of existing patches that were cumulative through April 2012.  However, from a clean OS build (exact same VM snapshot that the April 2012 patch image was built on), cumulative patches starting in June 2012 fails to install KB2686509.  Weird, eh?

    Here is the KB2686509.log file:

    [KB2686509.log]

    0.453: ================================================================================

    0.453: 2012/07/13 13:21:51.548 (local)

    0.453: c:\87ca20acffb2c6f07016efaff733d3b9\update\update.exe (version 6.3.13.0)

    0.453: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned: 0x7f

    0.453: Hotfix started with following command line: /q /z /n

    0.500: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with error 0x2

    0.500: ProductSuite is Present

    0.500: SYSTEM\CurrentControlSet\Control\ProductOptions\ProductSuite is Not Equal To Specified Value

    0.500: Second Condition in EmbNTPrereq.Section Failed

    0.500: Condition Check for Line 1 of PreRequisite returned FALSE

    0.515: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102

    0.515: KB2686509 Setup encountered an error:  Setup cannot continue because one or more prerequisites required to install KB2686509 failed. For More details check the Log File c:\windows\KB2686509.log

    0.515: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102

    0.515: Setup cannot continue because one or more prerequisites required to install KB2686509 failed. For More details check the Log File c:\windows\KB2686509.log

    0.515: Update.exe extended error code = 0xf0f4

    0.515: Update.exe return code was masked to 0x643 for MSI custom action compliance.

    4.860: ================================================================================

    Any help on this is greatly appreciated.  Thanks!

    Ryan

    Was this answer helpful?

    0 comments No comments