Apr 252014

If your keyboard doesnt work after you converted a physical maschine to a virtual one using VMWare Converter, the solution is easy:

– Open the console on the virtual maschine
– Use on-screen-keyboard to log in and open Registry Editor (regedit.exe)
– Goto HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E96B-E325-11CE-BFC1-08002BE10318}
– Change UpperFilters to include only kbdclass
Reboot virtual maschine

I had a Touchpad driver from my Thinkpad still in there, which blocked…..

Found the solution here btw https://communities.vmware.com/message/2248856#2248856

Keyboard Not Working after VMWare Conversion

  7 Responses to “VMware keyboard not working after P2V conversion?”

  1. This lead me in the right direction, thanks!

    More info is needed for more people though

    Can’t log in because of ctrl alt del?
    Mount the vmdk file and use regddit

    Can’t find CurrentControlSet?
    Use control01 and control02 instead

    Can’t find the virtual mounted vmdk disk when attaching a hive in regedit?
    Run both vmware workstation and regedit as admin (if you don’t you don’t have permission to c:\windows\system32\config)

    • CRTL+ALT+DEL can be done using the onscreen keyboard.
      CurrentControlSet could not be found, because you loaded the registry from another computer (using the .vmdk) file. CurrentControlSet is just a symlink to the ControlXX hive.
      There is no need to do it this way, just use the onscreen keyboard and login using CTRL+ALT+DEL.

  2. This fixed my issue, exactly. I mounted the virtual disk on the host computer, used “reg load” to load the system hive, edited out the line that said “SynTP”, unloaded the hive, disconnected the virtual disk, restarted the VM. Viola! Fixed it. Thank you very much.

  3. Thank you very much for the provided information.
    I had the same problem that I couldn’t unlock Windows.
    Sending Ctrl + Alt + Del via the internal keyboard or USB connected keyboard or onscreen keyboard or via the VMware Workstation button/function didn’t work.

    I finally managed to get my VM running by doing the following.

    1. Run “VMware Workstation” as administrator
    2. Map the virtual (.vmdk) disk of the VM with “VMware Workstation” by selecting from the main menu “File” -> “Map Virtual Disks…”, uncheck “Open file in read-only mode (recommended)” and make sure that you select the system partition.
    3. Run “regedit” as administrator
    4. Click “HKEY_LOCAL_MACHINE” and select from the main menu “File” -> “Load Hive…”, navigate to “C:\Windows\system32\config” an load the file “system”
    5. Give a temporary “Key Name” like “Temp” or something else
    6. Go to “HKLM\SYSTEM\CurrentControlSet\Control01\Class\{4D36E96B-E325-11CE-BFC1-08002BE10318}”
    7. Delete the value “SynTP” out of “UpperFilters” so that only the value “kbdclass” remains
    8. Go to “HKLM\SYSTEM\CurrentControlSet\Control02\Class\{4D36E96B-E325-11CE-BFC1-08002BE10318}”
    9. Delete the value “SynTP” out of “UpperFilters” so that only the value “kbdclass” remains
    10. Reboot virtual maschine

  4. Correction:

    10. Unload the hive by selecting from the main menu “File” -> “Unload Hive…”
    11. Disconnect the mapped virtual disk
    12. Boot/Start the VM

  5. Still works!!! Thanks a ton!

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>