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-15T07:01:16+00:00

Excuse me. I have said over and over again to email me at susan-at-msmvps.com so I can set up a support case for people that stil can't get this update installed.

What am I chopped liver?
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-15T06:56:02+00:00

Susan. thank you! Both my impacted (sic) boxes are Dells with Dell installed xp & drivers in case that could be part of the issue.

The affected computer in my case is also a Dell. Dimension 4600 to be exact, just in case its being a Dell has anything to do with the problem. There is no faultykeyboard.log file on my C, and no Scancode Map registry key to delete. So far, I am up a creek with no paddle on this bug, despite all the good advice in this thread.

It *is* shocking that MS would allow this to go unfixed. I suspect that they are letting us suffer on purpose to drive us off XP. But until W7 stabilizes further and stops its forced reboots, I'll stay on XP, thank you.
Was this answer helpful?

0 comments No comments
Anonymous

2012-05-15T04:30:59+00:00

The 98 upgraded method does say in it's doc that it includes systems upgraded from Windows ME. I had upgraded from ME as I had posted previously, and the method I posted previously that fixed my problem is the same...

except I just took out all keyboard entries that did not have system32 in them, by looking in each one, then deleting the whole key if no system32 was in it, and I'm fine now, as I said. No register finds necessary, and no looking at the log file, except to see that some were listed.

As y'all can see, this secuity fix can have complications all the way back to windows 98, so it was shipped to fix as many as it could, while protecting all exceptions (by not installing). Looks like if you can't get the fix on, you are no worse off than you were. At least they tried to plug the hole in the future by making the system32 requirement in the future, but if MS had let the fix go on your system, with your exceptions, the new restriction might render your keyboard or other software useless. It was a d if you do/d if you don 't for MS. It is a bummer, though, for the exceptions.
Was this answer helpful?

0 comments No comments