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-11T20:25:04+00:00

Malcolm and Maybury, above, are right, but my 2 cents for completeness...

As far as I can tell, KB2686509 requires all keyboard layouts, etc., to be in the system32 folder to install, since it enforces that as a security requirement after it is installed.

This is a built in protection to protect you from possible destruction by this fix (see above).

See http://support.microsoft.com/kb/2686509

If it finds layouts, etc. that are not able to be verified as being in system32, it puts their names in a log - Faultykeyboard.log

In my case, the files named in the log did not actually exist, but there were registry entries that did not contain system32. Looks like the install verifies the registry entry to have system32, but does not actually look for the files. My own searches never found any.

I found in the many layouts entries in the registry, that several (10?) had no system32 in them, and seemed to be for old Spanish, Norwegian, etc., but 1 or 2 with US101, so I exported the registry item that is above these entries, did a system restore create, and went to each registry keyboard entry that did not have system32 visible inside, and deleted the several (10?) entries. THEN I RESTARTED just in case, and to make sure I was still running, and had full keyboard operation. I STRONGLY RECOMMEND A RESTART, just in case - I err on the side of caution, instead of argument. Time well spent.

Then, I executed Microsoft Update, and it installed KB2686509 correctly. Violla!

Of course, other changes to layouts, keys, and other related files might vary, and possibly depending on what aftermarket, old, keyboards were installed previously. My XP system that had the problem, was an actual upgrade from Windows ME on a Dell 8000 laptop, to Windows XP, and copied over to a Dell 8200, then to a Dell E1505, so who knows where the bogus entries came from. (Runs fine, by the way.) My other E1505 that was cloned from an HP Desktop did not have the problem at all. Good Luck!
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-11T19:46:35+00:00

Based on an earlier posting from rmgalley (thanks by the way). I checked the entries in the registry with what was in the system 32 folder. The following were in the registry but not in the system32 folder. As I'm using a UK keyboard I deleted the US entries from the registry -

KBDDV.DLL

KBDUSX.DLL

KBDUSL.DLL

KBDUSR.DLL

Restarted and reran the update and all is well!
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-11T18:46:10+00:00

same here - removed re-mapping (by keytweak) and worked well,
Was this answer helpful?

0 comments No comments