KB2686509 and KeyTweak

Topic

New Reply

Install of KB2686509 failed on one of my XP machines. (I know I was advised to hold off – but I didn’t listen). The KB article on files in the wrong place did not apply. But I did have KeyTweak installed to kill the caps lock key.

What I learned. Don’t uninstall KeyTweak – that won’t help. Rather ask it to restore defaults. (reboot) Then apply KB2686509. (reboot) Then restore your settings and, of course reboot! (Oh do I love the update process on my Debian Linux server!)

Reply | Quote

Replies

Regarding: KB2686509; May 2012 Microsoft Updates
File: WindowsXP-KB2686509-x86-ENU.exe
Description: Security Update for Windows XP

This update will usually fail for many Systems, especially on Windows XP machines (although I haven’t tried it on other machines yet).

To find the possible culprits, you need to find and open:

%WINDIR%faultykeyboard.log

On my machine (i.e. without third party keyboard layouts), the log read as follows:
===Log Contents===
KBDDV.DLL
KBDUSX.DLL
KBDUSL.DLL
KBDUSR.DLL
===Log Contents===

Now you need to open the registry and navigate to:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlKeyboard Layouts

For example, on my system, I had:

===Original Registry Entires===
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlKeyboard Layouts0000409]
“Layout File”=”KBDUS.DLL”
“Layout Text”=”US”
“Layout Display Name”=”@%SystemRoot%\system32\input.dll,-5000”

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlKeyboard Layouts0010409]
“Layout File”=”KBDDV.DLL”
“Layout Id”=”0002”
“Layout Text”=”United States Dvorak”

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlKeyboard Layouts0020409]
“Layout File”=”KBDUSX.DLL”
“Layout Id”=”0001”
“Layout Text”=”United States International”

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlKeyboard Layouts0030409]
“Layout File”=”KBDUSL.DLL”
“Layout Id”=”001A”
“Layout Text”=”United States Dvorak for left hand”

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlKeyboard Layouts0040409]
“Layout File”=”KBDUSR.DLL”
“Layout Id”=”001B”
“Layout Text”=”United States Dvorak for right hand”
[/I]
===Original Registry Entires===

I backed-up and deleted the faulty keyboard registry keys for this update to install successfully and correctly.

After deleting only the faulty keyboard layouts (as documented in the faultykeyboard.log, in my case all of the international and DVORAK layouts) with non-existent .DLLs, the update installed successfully.

Of course, your system may vary – especially if you have custom keyboard layouts (and/or drivers). I didn’t have any on my test machine (i.e. these are generic standard layouts with a default installation…)

Reply | Quote

I take you didn’t read or understand “The KB article on files in the wrong place did not apply”

This posting was for a different reason for failure than the one well documented by microsoft that you repeat.

Reply | Quote

I take you didn’t read or understand “The KB article on files in the wrong place did not apply”
This posting was for a different reason for failure than the one well documented by microsoft that you repeat.

Actually, I did read and understand “The KB article on files in the wrong place did not apply”. The support article from Microsoft contains some erroneous information, especially to file locations (i.e. the location of faultykeyboard.log on some systems) and registry key location (i.e. HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlKeyboard Layouts, which leaves out CurrentControlSet in the reg key listed at Microsoft support), which is why I tried to document the actual steps I used to fix the problem successfully.

This update should probably have been tested further before public release, given that it has appeared across many forums.

Update: The Microsoft Article MS12-034 has been revised to fix the erroneous information…

Reply | Quote

jgstanley’s fix was right on for me. I had one listed KBxxx.dll in the faultykeyboard log. I went into the registry and had to do a Find to locate that particular key. I deleted it. Then I was able to install the update using the appropriate KB download from the MS12-034 security bulletin.

Reply | Quote

Long story, happy ending.
I broke the ‘/” key on my old Dell laptop, so I downloaded the Resource Kit just for the remapkey tool and remapped my Caps Lock key (never liked that key anyway.) I eventually replaced the keyboard but didn’t undo the remap. I had no problems until KB2686509 came along. I restarted the remapkey tool, changed the Caps Lock key back to its normal function, rebooted and restarted the KB2686509 update. Problem solved. I used a different tool than Millwood, but it seems to have caused the same problem, so thanks, Millwood, for the heads up.

Reply | Quote

How does one view the faultykeyboard.log file???

I have this file in C:Windows, but it is not a text file (as many – but not all! – .log files are).
It is in some sort of binary format. :confused:

Is there a special viewer for this type of log file?

An inquiring mind wants to know.

DanR

Reply | Quote

I explain how I got this fix successfully installed here:

http://windowssecrets.com/forums/showthread//146387-Patch-Watch-update-Duqu-patch-install-problems?p=853791&viewfull=1#post853791

Reply | Quote