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.
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!).
@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.)
@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
They forgot the "control" in the KB.
Delete any registry entry that references the keyboard layout file in the following registry subkey:
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 ;-)
@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.
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.
Thanks to whoever found this fix. It worked like a charm. Maybe this should be included in the Microsoft Fix It solution centre?
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!
Well, tried every thing and it will not install....