Resources For IT Professionals
Post an article
Wikis - Page Details
  • First published by (MVP, Microsoft Partner)
  • When: 13 May 2012 12:10 AM
  • Last revision by (Microsoft)
  • When: 17 Jul 2012 3:46 PM
  • Revisions: 17
  • Comments: 23
Options
RSSSubscribe to Article (RSS)
Can You Improve This Article?
Positively! Click Sign In to add the tip, solution, correction or comment that will help other users.

Report inappropriate content using these instructions.
Wiki  >  TechNet Articles  >  KB2686509 - Failure Due to Remapping of a Key

KB2686509 - Failure Due to Remapping of a Key

KB2686509 - Failure Due to Remapping of a Key

EDIT OF 6/19/2012:
New Instructions:
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 


For those people posting to the http://answers.microsoft.com/thread/0deeacb6-115c-419d-ac37-03ff8927b79c thread who remember that they remapped a key on their keyboard, but are unsure how to follow the instructions on how to temporarily remove this remapping for purposes of installing KB2686509, I've typed up this visual how-to to make it a bit easier.  Please note this is only one of three different errors types I've seen so if this doesn't fit your exact failure type, I will be attempting to document all three I've seen people report.

I've also seen an issue where Windows ME or 98 upgraded to Windows XP will cause a failure.  This has been documented in this wiki post.  I've seen where DLLs noted in the faulty keyboard log file are no where to be found on the system, so follow this post.

You have a Windows XP that many years ago you changed a key on the keyboard to be some other key.  Or you have a Windows XP that you disabled a key on the keyboard many years ago.  Now when you go to install KB2686509 it fails with 0x8007F0F4 error.




Or you may see a message like this:




You DO NOT have a log file anywhere on your PC called faultykeyboard.log file.  This should be in the c:\windows folder.  You have NO SUCH log file on your XP.

If this is your symptoms, see if following this will get KB2686509 installed.

Step one, go to your Windows XP and click on the start button, then on run


Then in the run box type in regedit.

Now drill down the listing you see there and find a specific registry key.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout

Go to HKEY_LOCAL_MACHINE.  Under there find System and click on the "+" to expand the location.  Now find a key called CurrentControlSet and expand that by clicking the "+" .  Now scroll down and find the registry key Control and again click on the "+".  Now find the key called Keyboard Layout.
See if there is a value called "scancode map" in the right hand side.

This will look similar to this but may not be EXACTLY this same series of numbers.   These numbers correspond to a key on your keyboard.


We'll want to delete this value, but first, let's back this registry key up so we can restore it later.  Right mouse click on the keyboardlayout registry key and click on export.


Save this key in a place where you can find it again, like My documents


Now that you've exported this value, go back to the keyboard layout registry key and delete just the scancode map value.


Once you've deleted the registry key called "Scancode Map", reboot your Windows XP.
Now attempt to install KB2686509 again either via manual download going to http://www.microsoft.com/en-us/download/details.aspx?id=29804 and downloading from there or using Windows update again.  It now should complete successfully.



Now that the patch has installed, lets' put back in the remapping of the keyboard key.  Click on the start button, then on run
Then in the run box type in regedit.


Once you open regedit, click on File, then on import


Find the exported registry key that we saved earlier, highlight the saved registry key and click open.




You should get a response that the registry key info has been reimported.





And you should see what you had in that Scancode Map value earlier back in your registry. 


If these instructions do not work for this particular issue of remapping of a keyboard key, please post back on the http://answers.microsoft.com/thread/0deeacb6-115c-419d-ac37-03ff8927b79c thread with your exact problem.

, , , , , , , , , ,
Sort by: Published Date | Most Recent | Most Useful
Comments
  • 14 May 2012 5:42 AM

    This worked.  I had remapped caps-lock to control to serve my Emacs habit, and this note helped me get past KB2686509's install problem while preserving my remapping successfully.  Thanks, Susan.

  • 14 May 2012 10:39 AM

    Applied to me with Caps Lock disabled. Reckon MS have got it seriously wrong here. If they've found that the update won't install for the re-mapped keyboard reason, update should include a way of doing all this without user-intervention. Must be possible, surely? First time I've heard of this sort of performance having to be done to get an update to install!! Non-techie folk will, no doubt, be completely flummoxed, probably ending up paying someone to sort it (assuming that said someone knows the answer!).

  • 14 May 2012 2:36 PM

    @davolente: I think the difficulty is that the update has no way of telling that you've deliberately modified the registry (in an unsupported way, so far as I can tell) in order to remap a key.  It can tell that the settings aren't the way they're expected to be, but not why, so it has no way of knowing whether installing the update will make something break or not.  In this case, all would probably be well, but I think MS are right to take the cautious approach - updates that break people's computers are really bad news!  (Non-techies should be OK, because they won't have hacked the registry in the first place.)

  • 14 May 2012 2:42 PM

    @Harry Then Microsoft should document with an exact how to with pictures for the Mom and Pops if you expect them to get this update installed.  Also for this particular error the instructions in support.microsoft.com/default.aspx are wrong.  It should read

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout

    They forgot the "control" in the KB.

    Delete any registry entry that references the keyboard layout file in the following registry subkey:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Keyboard Layout

  • 15 May 2012 10:25 AM

    Many thanks for the guide Susan. I was having this problem on a Server 2003 box on which I had mapped Caps Lock to Control. After three reboots I'm back in business. Maybe no one at Microsoft remapped a key on an older OS that they keep updated ;-)

  • 20 May 2012 4:00 PM

    @Susan, thanks for the pointer.

    @Harry, just to dispel any notion that a custom 'Scancode Map' would be some sort of a hack or abuse, but the key has been well documented for ages by Microsoft, as well as its intended functionality. You can still read the description at msdn.microsoft.com/.../gg463447, find it referenced at blogs.technet.com/.../452892.aspx, and download RemapKey.exe with various resource kits like www.microsoft.com/.../details.aspx.

  • 20 May 2012 10:36 PM

    Instead of 'Scancode Map' regisrty key, I had a 'IgnoreRemoteKeyboardLayout' key.  After deleting this key, the upgrade worked, however I had to run the upgrade before a reboot, as a reboot automatically restored my registry key.  

  • 21 May 2012 11:28 AM

    Thanks to whoever found this fix. It worked like a charm. Maybe this should be included in the Microsoft Fix It solution centre?

  • 27 May 2012 9:58 AM

    This worked for me EXCEPT the Scancode Map registry value was in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Keyboard Layout and HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\Keyboard Layout, not in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout. I'm guessing that's due to multiple user accounts on this PC with the keyboard mapping having occurred in two of the other accounts. Once I removed the Scancode Map value from those two accounts and rebooted, the update installed fine. Thanks for pointing me in the right direction!

  • 2 Jun 2012 8:32 AM

    Well, tried every thing and it will not install....

Page 1 of 2 (18 items) 12