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-03-06T20:55:43+00:00

Hi,

I have a faultykeyboard log that has nothing but kb*.kbd files listed in it. I followed your instructions for the upgrade from ME to XP. But after I re-booted and tried to manually load the security update for kb2686509, I got the same exact error. below is a copy of the kb2686509 log in notepad after modifying register, re-booting and trying to install kb2686509 update.

[KB2686509.log]

30.674: ================================================================================

30.674: 2013/03/06 02:16:37.278 (local)

30.674: c:\8914b9d500b89f86bc9c\update\update.exe (version 6.3.13.0)

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

30.794: Hotfix started with following command line:

30.794: In Function GetReleaseSet, line 1211, RegOpenKeyEx failed with error 0x2

30.804: In Function GetReleaseSet, line 1240, RegOpenKeyEx failed with error 0x2

30.894: CreateUserInterface: GetProcAddress for DefineInstallCustomUI failed: 0x7f

32.847: Return Value From IsMachineSafe = 0

32.847: IsMachineSafe returned 441092

32.847: Fist Condition in Prereq.IsMachineSafe.Section Failed

32.847: Condition Check for Line 1 of PreRequisite returned FALSE

32.857: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102

32.857: 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

32.897: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102

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

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

1272.960: User Input: OK

1272.960: Update.exe extended error code = 0xf0f4

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

10.185: ================================================================================

10.195: 2013/03/06 03:05:44.928 (local)

10.205: c:\d54cb989cbf12f4e4b9c137cf72a\update\update.exe (version 6.3.13.0)

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

10.275: Hotfix started with following command line:

10.275: In Function GetReleaseSet, line 1211, RegOpenKeyEx failed with error 0x2

10.275: In Function GetReleaseSet, line 1240, RegOpenKeyEx failed with error 0x2

10.335: CreateUserInterface: GetProcAddress for DefineInstallCustomUI failed: 0x7f

12.639: Return Value From IsMachineSafe = 0

12.639: IsMachineSafe returned 441092

12.639: Fist Condition in Prereq.IsMachineSafe.Section Failed

12.639: Condition Check for Line 1 of PreRequisite returned FALSE

12.649: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102

12.649: 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

12.679: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102

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

Any help would be greatly appreciated.

Thanks,
Was this answer helpful?

0 comments No comments
Anonymous

2013-03-07T09:22:38+00:00

Nick,

Go to the thread, and scroll down to the bottom.

You will see at least 37 pages of stuff about this thread.

Put like say 36 in the box, hit enter, and read pages 36 and 37. Many people say what worked for them most recently on these pages.

Hope that gets you what you need. Otherwise, read all 37 pages to see what works, and come back if that does not work. Or you could go through it all looking for the posts I made telling how I got my system that was an old ME to XP conversion that had the problem, but...

Others might post you something to try, but this is sort of an old thread, and you don't mention anything you tried as far as the stuff on page 36 and 37, which I think mention automated methods to get this fix on. Good Luck!
Was this answer helpful?

0 comments No comments
Anonymous

2013-03-10T04:46:36+00:00

Hello Susan:

The Microsoft Fix It items never work for me or for most people that I know that try them, too many bugs in them I guess?

This did "not work at all," just to let you know I tried.

I did call Microsoft and they said to give up on it, and just forget about using that computer.

And they charged me $75 to tell me that.

Thanks again Susan, but think I'm giving up and moving to Apple OS computers or Linux one's from now on.

Sincerely,

Steve
Was this answer helpful?

0 comments No comments