| | cobes on June 25, 2008 | RE: code 39 keyboard win XP
BE VERY CAREFUL DOING THIS!!!
I did this and now I have NO mouse and NO keyboard!!!
BUT... I read the article on Microsoft about doing this and ran the "Automatic Guide" and it didn't fix my problem (which was my
CD-Rom couldn't read my X-Plane Game CD). Anyway, I deleted THREE of the UpperFilters manually and now I'm totally screwed with NO input device(s) at all!!
I only wish I NEVER messed with this setting. I have NO idea how to fix this now and it was a perfectly good working PC except for the CD-Rom issue. Damn, this REALLY sucks...
At this point, I think it would be cheaper to buy a NEW "barebones" system WITH the FULL Operating System XP SP2 CD.
I will NEVER, EVER, buy an HP (what I have now), Dell or any other OEM "mainstream" PC BECAUSE they don't give you the operating system CD and if you have a problem (AND YOU WILL HAVE A PROBLEM TOO!!), their ONLY SOLUTION is to do a FULL RECOVERY back to the state it was in when you first removed it from the box!!! That means you LOSE ALL YOUR DATA!!!!!!!!!!! IMPORTANT EMAILS, ALL DOWNLOADED SOFTWARE, ETC... GONE FOREVER!!!!!
Sorry for getting slightly off topic here with my rant but everybody needs to know what kind of CRAP OEM systems REALLY are and what you CAN EXPECT when you buy one of these POS. You've been WARNED!!
cobes |
|
| | godswen on June 29, 2008 | RE: code 39 keyboard win XP
bas!! thank you man!! it worked! hugs and thanks!! :)) |
|
| | winter on July 12, 2008 | RE: code 39 keyboard win XP
BAS13, thank you very much. The problem bores me...because no one can't help me. Thanks again!! |
|
| | BrianC on July 18, 2008 | RE: code 39 keyboard win XP
Thank you creaturex and Bas13. This worked for me the first try and I did not have to re-start. I have no idea why this crapped out in the first place and I struggled with this for about a day until I discovered your solution. I even did a windows repair which did not touch the problem at all. I've always avoided messing with regedit before for obvious reasons (like previous post) but this worked fine. Thanks again! |
|
| | Dean on July 30, 2008 | RE: code 39 keyboard win XP
worked just fine for me too!! there were 3 upperfilter entries with the syswin added and just deleted them.. |
|
| | clem on August 23, 2008 | RE: code 39 keyboard win XP
Thanks bas13! Great advice! I had this error obviously after deinstalling vmware, and never had expected this NICE side effect. And, as another side effect, the touchpad worked until the first key of the keyboard was hit, and blocked afterwards. To hell with vmware (and the error info in device manager)! It took me half a day until I found your hint!
Thanks again!! |
|
| | Shawn Till on August 30, 2008 | RE: code 39 keyboard win XP
bas13's fix & creaturex's clarification of how to implement it
got my Dell Dimension 3100 rolling again.
Thanks so much guys. You saved me from a total re-install. |
|
| | showst0pper on August 30, 2008 | RE: code 39 keyboard win XP
Thanks to the person who found this fix it helped out great if you wanna make your life easy if you have remote setup on the affected pc just remote into the machine then run find the Upperfilter values it seems to be put there by some type of virus or spyware. |
|
| | MAX on September 5, 2008 | RE: code 39 keyboard win XP
BAS13 - I echo what the rest have said....Great Solutions, Easy to follow steps and works like a charm....Thanks you saved me from having to buy a USB keyboard. |
|
| | 4EVRgrateful on September 8, 2008 | RE: code 39 keyboard win XP
KUDOS to bas13's fix & creaturex's clarification. I recently installed SAM 2003 and had the Keyboard problem, I only needed to fix one instance of the Upperfilter and was fine after I unistalled the keyboard driver and then reinstalled it. Ryan Adams,I found your fix on Computing.net and then on this website which is simular to Bas13's, so that gave me the confidence to try it. Thanks to all for sharing your wisdom. |
|
| | Nic on September 14, 2008 | RE: code 39 keyboard win XP
BAS13 you are a star, thank you very much. Your solution worked perfectly :)
Just for reference i'm running MS Win XP 64-Bit edition with SP2. |
|
| | _steph on September 15, 2008 | RE: code 39 keyboard win XP
First off thank you to BAS13, I was also a victim of VMWARE uninstall leaving lots of bad stuff in the registry. While the fix resolved my issue with my PS2 keyboard, my wireless keyboard still does not work.
Any ideas? |
|
| | Robbie on September 23, 2008 | RE: code 39 keyboard win XP
This was a huge help
big thanks to BAS13. couldnt have done it without you.
I was about to lose my mind with this issue.
again..big thanks. ;) |
|
| | Scolds on October 8, 2008 | RE: code 39 keyboard win XP
Thanks to Bas of course I am using the keyboard to type this. Also to creaturex who made the instructions easier to follow. I am my daughter's hero again for fixing her laptop. :) |
|
| | Jane on October 22, 2008 | RE: code 39 keyboard win XP
thank you bas 13!!
u r a life saver :) |
|
| | Eri on October 30, 2008 | RE: code 39 keyboard win XP
Oh My God.
Thank you all so much for providing this easy solution. I'm an international student from Taiwan currently studying in Australia. And guess what, this happened to my notebook just right before the deadlines of my assignments. It was intolerable and extremely frustrating, considering the fact that I only have this one PC. And, let's not forget, the costly repairment-fee they'll charge me.
I'm using my keyboard right now. You never know just how valuable these little things are until you lost them. Thank you again^_^ |
|
| | chester on November 4, 2008 | RE: code 39 keyboard win XP
OMG i wasnt able to use my keyboard for 2 whole weeks and was without my precious anti-drug (games). I was tempted to turn to crack. HAHA WELL THANKS BAS13!!! THANK U SO MUCH!!!! tried everything but wow... |
|
| | airman on November 5, 2008 | RE: code 39 keyboard win XP
Big thanks to bas. You are the man |
|
| | JHL on November 26, 2008 | RE: code 39 keyboard win XP
Bas 13,
You are amaging !!!!!!!!!!!
It worked for me and I thank you very much. |
|
| | OldSoftware on November 26, 2008 | RE: code 39 keyboard win XP
WOW!! I had this problem VERY suddenly. Could not recognize a wireless bluetooth, PS/2 or USB keyboard. I followed BAS 13 instructions and found three keys with TFKbmon in addition to kbdclass. I removed TFKbmon and I now have my keyboards back.
Thank you, thank you.
Does anyone know how this could have happened? |
|
| | vis on November 28, 2008 | RE: code 39 keyboard win XP
registry editing has been disabled by administrator
how to solve this problem 1st? plz help.. |
|
| | Ed H on November 28, 2008 | RE: code 39 keyboard win XP
THANKS to Bas13 and CreatureX!! I have struggled with this for 3 evenings at home, before finding this solution (searched from my work pc). A lifesaver - I too was going to buy a usb keyboard.
I don't have vmware, but I do have MS LiveMeeting (installed recently). |
|
| | David on November 29, 2008 | RE: code 39 keyboard win XP
Dude, Bas13 and CreatureX, you guys are awesome. I'm a writer and not having my keyboard/PC working was really affecting my work for the past week and a half now. Thanks again! |
|
| | Abhinac on November 29, 2008 | RE: code 39 keyboard win XP
Thank you again bas13. Your help was really appreciated. I was saved from being shouted at by my parents and full formatting. Thanx again! |
|
| | mbroom1 on November 30, 2008 | RE: code 39 keyboard win XP
I have the same dead keyboard problem in XP Pro SP2 -- with 1 added obstacle. My usual account is an administrator account with a log-in password. Since the keyboard is already dead at the log-in screen, I can't use that account. I also have a Guest account with no password, so that I can log in just by clicking its log-in screen entry, but it's a limited account without administrator privileges. I can access (and edit, I assume) the registry from that account (which is weird), but cannot run the Device Manager keyboard troubleshooter or uninstall the keyboard. Also, I hadn't thought to install Remote Desktop. Assuming I can infact change registry entries from the limited accout, is it possible to safely uninstall the keyboard by deleting the registry entries that give its name? (It's a Microsoft Natural Keyboard.) |
|
| | invalidchars on November 30, 2008 | RE: code 39 keyboard win XP
thank you very much bas13 |
|
| | Lomax on December 1, 2008 | RE: code 39 keyboard win XP
If you screw up by deleting the wrong types of "kbdclass" registry keys then just import them from another computer and wham it should work.
WARNING: ONLY WORKS IF BOTH COMPUTERS USE "C:" AS WINDOWS ROOT
1. Find the "kbdclass" key
2. Click on it
3. File -> export
4. Export each file to anywhere, an empty folder preferably.
5. Put on a usb memory or somehow else get it over to the other computer
6. Double click each file and add to registry
7. Restart |
|
| | dongMD on December 1, 2008 | RE: code 39 keyboard win XP
thanks for the help bas13 and creaturex!
also got tftmon on 4 of my kbdclass searches.
what's the possible source?
thanks again! |
|
| | Bob on December 4, 2008 | RE: code 39 keyboard win XP
Thank you. It worked for me too. |
|
| | Adam on December 4, 2008 | RE: code 39 keyboard win XP
Yea, not so sure why it started all of the sudden, but this works if you have ThreatFire installed and your keyboard suddenly stops working AND you have to login to get to the registry...
So I had to use this boot cd to access the registry:
http://home.eunet.no/pnordahl/ntpasswd/bootdisk.html
And edited these keys...but had to change the controlset to the ones I had:
http://blog.ryantadams.com/2008/01/18/keyboard-not-working-due-to-missing-or-corrupt-drivers-code-39/
Removed TfKbMon from two keys....stupid ThreatFire...
Good luck everyone and thanks for the help!!! |
|
| | /b/tard on December 14, 2008 | RE: code 39 keyboard win XP
you sir are legend and a scolar
I got confused with some steps though, simply use the on screen key board to search for 'kbdclass' and look to see if they have anything next to them such as 'abc kbdclass' if so click modifiy.
F3 with on screen keyboard through all of the search results till it says done, then follow the rest of the instuctions. Happy days!! |
|
| | long on December 18, 2008 | RE: code 39 keyboard win XP
BIG THANKS TO BAS13................ YOU HAVE SAVE ME FROM A BIGGEST HEADACHE...........NOW I AM TYPING (AGAIN (:)WITH MY KEYBOARD........THANK YOUUUUUUUUUUUUUUU |
|
| | Stephanie on December 24, 2008 | RE: code 39 keyboard win XP
Thank you, creaturex and Bas13! You guys are life savers. The problem started about a week ago. Since I had no clue what happened, I had no clue where to start searching. On screen keyboard, and my trusty mouse in hand, I went to searching..for the past three days.. and finally found this thread about 30 minutes ago. Seriously. Thank you. My problem came from the string 'TfKbMon'. The thing is, I didn't EVEN UNINSTALL Threatfire. Just closed it down for a while. Hey, it was annoying the sxit out of me. Anyway, it was only on 2 different strings. Funny, huh? Thanks, again. |
|
| | Eddi Mayfield on December 27, 2008 | RE: code 39 keyboard win XP
I_searched-the-registry-but-all-of-the-entries-contained-only-kbdclass-nothing-else.--My-keyboard-still-won't-work.--Also,-if-I_try-to-use-the-keyboard-a-clicking-sound-starts-that-almost-sounds-like-the-hard-drive-is-stuck.--This-issue-started-after-my-grandson-was-playing-a-game-online-and-he-kept-pressing-on-the-shift-key.-He-says-he-got-a-warning/error-message,but-disregarded-it.--Does-anyone-have-any-solution????--I-hate-to-have-to-take-it-somewhere-to-get-it-"fixed".--------Eddi-in-Tampa. |
|
| | Frustrated on December 28, 2008 | RE: code 39 keyboard win XP
creaturex - love the simplification of your directions...I was off to the races within minutes...problem solved.
Love it...keeping it simple is an art form - well done! |
|
| | ananthaks on December 30, 2008 | RE: code 39 keyboard win XP
Thanks to Bas13, I had two Threatfire TfkbMon entries along with kbdclass, which I eliminated to get my keyboard up & working. Wasted over 3 hours over this stupid Threatfire bug.
Even I had to login into my account with a password, which I could not with my dysfunctional keyboard. So I went into safe mode, logged on as Administrator & did the needful. |
|
| | Xenon2000 on January 4, 2009 | RE: code 39 keyboard win XP
This registry fix worked to get my PS2 keyboard working again. Both my PS2 keyboard and PS2 mouse stopped working in Vista x64 Ultimate after uninstalling VMware Workstation 6.0
While this fix got my PS2 keyboard back, I am still without my PS2 mouse and am using a USB mouse in the meantime, but I don't want to give up on fixing my PS2 mouse issue. Anyone have the PS2 mouse missing? And if so, did you get it fixed without just moving to a USB mouse? |
|
| | Xenon2000 on January 4, 2009 | RE: code 39 keyboard win XP - fixed ps2 mouse
I finally fixed my PS2 mouse via the registry. Since both my PS2 keyboard and PS2 mouse stopped working after uninstalling VMware Workstation 6. I did try many things. But the registry change that I think fixed it for me in Vista x64 was HKLM\System\CurrentControlSet\Services\i8042prt\ the key named Tag, was a hex 6 and changed it to hex 5. Rebooted with the USB mouse unplugged (important I think here) and the PS2 mouse was working again. |
|
| | Major Tom on January 10, 2009 | RE: code 39 keyboard win XP
I run HyperOS wtih x3 XP Home and x1 XP Pro on one machine. I waslucky to have not set passwords in all accounts so I could at least get into windows using mouse and then on screen keyboard (Accessories/Accessability ---). The problem I had was only on one Home and the Pro XP therefore I could discount hardware. I was still on PS/2 keyboard and mouse and found on these 2 systems that the mouse was using keyboard memory resoures where it should only use an IRQ (12). As soon as a key was pressed both keyboard and mouse would lock though other services appeared to carry on. Struggled with this and decided to fit a USB mouse but even then the keyboard drivers would not load, giving the code 39 error. Thanks to bas13's info I checked the registry and found some of the upperfilters had a string for PC Tools Threatfire before keyboard string. Placed it after kbdclass on all entries at first but problem still persisted therefore deleted TfKbMon on each upperfilter and then uninstalled keyboard driver entry in device manager, went straight to 'Add new hardware' and did auto search and it loaded sucessfully, requiring a restart.
Although VMware rang a bell as I'm sure a recent update was for this, nothing showed up relevant and as far as I can see it it is not installed
I,m not convinced Threatfire is the culprit as the problem seemed to coincide with the November 08 patch Tuesday updates so I held off updating the two systems that weren't affected which also have Threatfire installed.
Now i know there is a solution I can have a play and try to pinpoint the cause - thats a big advantage of using HyperOS, being able to sacrfice a system to tests etc and also keeping one install free to gain access to files in any that become unbootable and carry out repairs. |
|
| | Bewo on January 26, 2009 | RE: code 39 keyboard win XP
thanks alot to BAS!!!!!! much kudos. you the man or woman! thanks alot yo. smart guy or girl |
|
| | Ariesco on February 12, 2009 | RE: code 39 keyboard win XP
Thanx Bas 13 & creaturex 4 solvin my problem (code 39). I was really pissed off 4 using on-screen keyboard.
U guys r gr8.
PEACE.......... |
|
| | JC on February 27, 2009 | RE: code 39 keyboard win XP
I was certain this problem was stemming from some nasty virus. Spent hours searching for the wrong stuff and coming up with questions to which there were no real answers on all types of forums. Was on the verge of reinstalling...
Finally found out how auto logon with my backup OS, but still could not use the keyboard or understand what caused it to happen. A nasty virus? No, dammit, no!
Thank you Bas 13 for your registry mastery and creaturex for a simplified explanation. Also, thank you Adam for confirming ThreatFire as the source of the TfKbMon keys. I had already had ThreatFire installed and had had no problems. Updating it was what screwed me over.
Thanks again. |
|
| | Astralon on March 2, 2009 | RE: code 39 keyboard win XP
Guys i cant find any upperfilter.I found only one but is the name is kbdclass.So i dont have to delete something.What can i do guys?Pls help |
|
| | Michaelangelo on March 3, 2009 | RE: code 39 keyboard win XP
Bas 13 saved my butt. Directions could have been clearer but got the job done and restored corrupted keyboard upperfilters. If you have XP Pro go to Start-Accessories-Accessiblilty and open On Screen Keyboard. Use this to "type in and modify reg. keys, gives you full access to keyboard with mouse clicks. Great job BAS 13 for finding this fix. |
|
| | CHRISk on March 5, 2009 | RE: code 39 keyboard win XP
thank you Bas 13. thank you for your help . my keyboard works great now :) amazing. |
|
| | anel on March 13, 2009 | RE: code 39 keyboard win XP
help pls.i had a problem with dvd rom and ihad delete the lowerfilter and the upperfilter.and now my key board is dead.but dvd works ;) pls help :((:( |
|
| | fmanz_99 on May 5, 2009 | RE: code 39 keyboard win XP
Man youre great ive been doin this for 4days and for as little as about 15 minutes i'm done with the once been thought to be reformatted hard disk, thank you very much!!!!!! |
|
| | brUcE_g on June 17, 2009 | RE: code 39 keyboard win XP
Dude, you are the cool!
Virus added extra entries to this reg on a client machine, and after doing what you said, everything went teh cool!
I lost 1 week with this problem.
MS is some bad piece of crap. Long live linux! |
|
| | abuadam97 on August 19, 2009 | RE: code 39 keyboard win XP
Great post - Saved me a lot of time.
Thanks a million |
|
| | Andrew on August 24, 2009 | RE: code 39 keyboard win XP
Hi all, I'm having the same problem as TS. I know the solution from Bas13 is 100% working. But what my problem is, I have logout from user account, I can't type my password in. And I tried boot in safe mode, my Administrator account is also passworded. Anybody can help me? |
|
| |
