Fix by Christian S. – Moers for “KB2686509 repeatedly fails with Error code 0x8007F0F4” (via: Microsoft Community)
Posted by jpluimers on 2014/05/07
I’ve used it as the Microsof FixIt offered at You may receive a “0x8007F0F4” error code when you try to install updates from the Windows Update Web site or from the Microsoft Update Web site did not work on several systems. The fix by Christian did work on all those systems.
Note: it is possible you get the same error for KB2676562: MS12-034: Description of the security update for Windows kernel-mode drivers: May 8, 2012, as it is related to KB2686509: MS12-034: Description of the security update for CVE-2012-0181 in Windows XP and Windows Server 2003: May 8, 2012.
One of the symptoms is that your system contains the file
%windor%\faultykeyboard.log containing a list of missing keyboard layout DLL files or KBD files (one of my machines had these missing: kbdjpn.dll and kbdkor.dll).
The cause is that KB2686509 can have problems with registry keys stored here:
- HKLM\SYSTEM\CurrentControlSet\Control\Keyboard Layout
- HKLM\SYSTEM\CurrentControlSet\Control\Keyboard Layouts
Christian wrote a batch file to fix it (named
BatchFixKB2686509.cmd) which works splendid on the systems I had this error.
The batch file uses regedit /e to export parts of the registry, then writes a small .reg file to clear the keys and imports them with regedit /S, waits for you so you can install the update, then writes back the saved registry data.
So basically, it automatically performs the manual steps described at KB2686509 – Failure Due to Upgrade from Windows ME or 98 to Windows XP – TechNet Articles – United States (English) – TechNet Wiki.
Christian S. – Moers replied on May 15, 2012
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/
There is also an alternative Microsoft Fix It solution you can try, but this batch file worked very well for me on the machines that failed.