This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
After download from Microsoft Update Security Update for Windows XP (KB2686509) won't install-what do I need to do?
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.
Wow you saved me from so much 'update' distress. Indeed I had done a similar thing somewhere in my distant memory. Simply deleting my hacked registry key entry as shown below solved my problem.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout]
"Scancode Map"=hex:00,00,00,00,00,00,00,00,02,00,00,2a,00,3a,00,00,00,00,00,00
I struggled with this for days. Here is what was happening and what I did that worked.
faultykeyboard.log listed 24 entries of the form kb*.kbd
I searched and no such files exist on my computer.
By running regedit and looking I found 24 abnormal looking subkeys matching the list in:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Keyboard Layouts
After carefully reviewing the potential for damage I discovered that the operating system automatically restores this section of the registery if a boot failure occurs.
I then boldly deleted all subkeys of the type *.kbd from the registry. I deleted faultykeyboard.log. I rebooted then ran the update KB2686509 and it installed and rebooted the computer.
The problem is gone. Everything works.
Good tips in this thread. It ultimately led me to my solution. The problem computer here was also running a version of Windows XP modified with NLite.
I was able to resolve this problem by first opening the faulty keyboard log. On the problem computer, it was located in C:\Windows\system32\faultykeyboardlog.log.
The faultykeyboard.log file simply listed these four items:
KBDDV.DLL
KBDUSX.DLL
KBDUSL.DLL
KBDUSR.DLL
I went to a computer that I knew had an unmodified version of Windows XP Professional, copied those four DLL files from C:\Windows\system32. I then transfered them to the C:\Windows\system32 on the problem computer and re-ran the manual installation file for KB2686509 which can be downloaded at http://www.microsoft.com/en-us/download/details.aspx?id=29804.
Problem solved.
Solution for me: Delete all subkeys from HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Keyboard Layouts not containing "@" in the path of the .dll reference(I've noticed that some layouts have a "Layout Display Name" value not starting with the @ character.)****
Thanks fly out to Bob for mentioning the delete option and for Clark mentioning nLite!
Similarities:
-use of nLite
-There was KB2686509.log babbling about prerequisites, which were already installed. (KB2676562)
Differences:
-There was no C:\Windows\system32\faultykeyboardlog.log.
More details for the curious:
The root cause in my case was:
-removing keyboard layouts never in use by me and installing all the exotic languages/code pages to display everything as it should look like.
-I guess the XP SP3 installer was never intended to cope with this combination, so it installed/registered some layouts.
I then boldly deleted all subkeys of the type *.kbd from the registry.
Does this mean deleting the folders in the registry under the Keyboard layouts folder? I have 5
