Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3476
  • Last Modified:

VmWare Machine's Keyboard will not work. Hardware properties say "Can't start... registry config incomplete or damaged"

Hi All,

I migrated a Windows 7 PC to VmWare Fusion using the migration aid.  All is well except the Keyboard refuses to work.  When I look at Hardware properties the "Standard PS/2 Keyboard" device status reads: "Windows cannot start this hardware because its configuration information (in the registry) is incomplete or damaged (Code 19)".

I've tried the normal stuff like unistalling/re-installing but the problem immediately returns.

Any help would be appreciated.

Thanks in advance,

FBB
0
Firebladeboy1993
Asked:
Firebladeboy1993
  • 16
  • 9
1 Solution
 
John HurstBusiness Consultant (Owner)Commented:
Can you upgrade the hardware in the Guest Machine?  This is a VMware function (at least in VMware Workstation for Windows). Look in the VMware Fusion menu for the VMware machine hardware upgrade.
0
 
Firebladeboy1993Author Commented:
Hi John. Alas, I don't see that option in any of the VMWare Fusion menus.
0
 
John HurstBusiness Consultant (Owner)Commented:
I see it in VMware on the Menu bar as VM, Manage, Change Hardware Compatibility. This is the same menu as Power, Settings, Removable Devices, Snapshots. Choose the Manage option.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Firebladeboy1993Author Commented:
I don't think the menus are the same in Fusion.  The options under the Virtual Machine menu are:   Suspend, Restart, Shut Down, Pause, Settings, Snapshots, Get Info, Send Key, Send Ctrl Alt Del,  Reinstall VMware Tools, Install McAfee....Blah blah blah....No Manage option I'm afraid.
0
 
John HurstBusiness Consultant (Owner)Commented:
What I have done from time to time is copy the VMDK file (main machine file) to a different folder, then make a new machine (custom not wizard) and point the new machine to the VMDK file in the different folder. That may accomplish the same thing.

Here is the VMware Knowledgebase article for VMware Fusion for changing hardware compatibility.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022060
0
 
Firebladeboy1993Author Commented:
Ah, OK, I'll try that.  I can also install a newer version of VMWare I guess and then upgrade the Hardware compatibility as per the link above.  I'll try both and see if it has the desired effect.  Thanks.
0
 
Firebladeboy1993Author Commented:
Hi,
A question on this: I have my VM Machine broken into 2GB chunks.  Thus there's Machine.VMDK and  Machine -S01.vmdk through  Machine -s19.vmdk.   Do I copy them all to a different folder or just the main VMDK? What about all the other VM related files (.VMEM, .VMSD. VMXF etc)?

Thanks!
0
 
John HurstBusiness Consultant (Owner)Commented:
Have you been making Snapshots?  i.e. why the S suffix?  

If no snapshots, try copying the folder to a NEW folder and making a new machine from there. Do not delete anything in case it does not work.
0
 
Firebladeboy1993Author Commented:
Hi,

The S suffix is applied when the VMDK is broken into 2GB chunks.  The total VM machine size is 40GB, thus you get .VMDK and  s01-S19 suffixed VMDKs too.

Anyway, OK, I'll copy the whole folder.

Thanks.
0
 
Firebladeboy1993Author Commented:
OK. That produced a nice new VM Machine with exactly the same problem.  My next move would be to upgrade VMWare and then upgrade the hardware I guess...... Unless you have another idea?
0
 
John HurstBusiness Consultant (Owner)Commented:
I think hardware upgrade is your next step.

If you continue to have problems, do you have the physical machine still? If so what about using VMware Converter to make a VMDK file (all one piece)?
0
 
Firebladeboy1993Author Commented:
The original machine just died (hardware issue) so I no longer have access to it.  I made this VM a while ago when I was planning on decommissioning the old machine (it was Thinkpad T42P so ancient). As it finally gave up the ghost, I thought it would be good to use the VM to replace it but I ran into this problem.

OK. I'll upgrade VMWare to the next release and upgrade the hardware accordingly. Will keep you posted on the outcome.

Thanks,

FBB
0
 
Firebladeboy1993Author Commented:
Hmmm...I was actually able to invoke the Hardware Upgrade functionality by downgrading and then upgrading my VM using  the Compatibility settings.  No luck I'm afraid. Same problem.
0
 
John HurstBusiness Consultant (Owner)Commented:
That is about the only way to repair a machine in that state that I know of. Keyboards are built into Windows. The keyboard on a ThinkPad is (I think) different underneath than a PS2 keyboard, but it is still built into Windows.

If you can do anything in the machine, try running System File Checker. Open an admin command prompt and run SFC /SCANNOW. Allow to complete, run again and restart. If you have no keyboard, I am not sure you can do this.

Can you start the VM in Safe Mode?
0
 
Firebladeboy1993Author Commented:
I actually have access to the machine using the Windows access-assistance on-screen keyboard so I can get into it and play around.  Let me give that a shot.
0
 
Firebladeboy1993Author Commented:
Oh and yes, I can boot into Safe Mode too...
0
 
John HurstBusiness Consultant (Owner)Commented:
Try SFC to see if that fixes the keyboard
0
 
Firebladeboy1993Author Commented:
Did that as instructed but no change I'm afraid.  Is it not possible to correct the corrupted part of the registry for this device?
0
 
John HurstBusiness Consultant (Owner)Commented:
I do not know how or even if you can repair a machine with this kind of malfunction. You may need to build a new machine from scratch.
0
 
Firebladeboy1993Author Commented:
Urg. That's what I was trying to avoid as it's a bunch of work to re-configure. Annoying when it's perfect apart from this ONE problem!
0
 
John HurstBusiness Consultant (Owner)Commented:
I understand. However I know of no other way to fix this.
0
 
Firebladeboy1993Author Commented:
I see.  OK  John, thanks for trying!
0
 
Firebladeboy1993Author Commented:
Oooookay!! Fixed it myself.

Using Regedit and THIS Youtube video https://www.youtube.com/watch?v=i74blHNY_7M I was able to locate the corrupt registry entry and correct it.   As well as the kbdclass entry, it had another driver in there too SynTP.Sys which is the synaptics touchpad driver from the old hardware I guess.  Removed that, rebooted and voila.

Thanks to John and all who may have looked at this.

FBB
0
 
Firebladeboy1993Author Commented:
I'm afraid suggestions on correcting this problem were not in the right direction and the poster gave up at the end.  I researched and found the solution myself.

I gave myself a B for not finding it sooner.
0
 
StudmillGuyCommented:
I had the EXACT same problem and this fixed it.  I've been Googling for days.  Thank you so much for following up and posting.
0
 
Firebladeboy1993Author Commented:
Yay! :-) So gkad it helped!
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 16
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now