Hello,
I'm trying to run a VMware Conversion of an old laptop as a backup. I've run a VMware conversion and converted it to a vm 9 image file.
When it gets opened in VMware Player everything works except for the keyboard inputs. The only way I can type on the screen is using either the on screen keyboard or connecting in with TeamViewer.
Looking in Device Manager shows that the following error.
Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)
Has anyone come across this before and know if a solution?
Thanks
Peter Sheridan
Update:
I got it working. I followed the steps in the following KB Article and it worked like a charm
No Keyboard or Mouse After Installing Logitech 9.0 Mouseware Drivers on Windows 2000
Update:
I got it working. I followed the steps in the following KB Article and it worked like a charm
No Keyboard or Mouse After Installing Logitech 9.0 Mouseware Drivers on Windows 2000
Had this problem recently converting a Win 8 x64 laptop install using VMWare converter 5.1, only difference was I had extra settings in the keyboard registry section (mouse section was clear and mouse worked ok):
Key in this case was:
SYSTEM\CurrentControlSet\Control\Class\{4d36e96b-e325-11ce-bfc1-08002be10318}
UpperFilters:REG_MULTI_SZ: had mutliple entries as above, removed all but "kbdclass" and rebooted.
Thanks for the tip!
Cheers
Benni
This happened to me. The keys above showed me that Synnoptics (Lenovo Ultranav) was installed. Instead of editing the keys, I used the mouse to remove the Synnoptics (Lenovo) driver and it all cleared up.
A little easier for the novice computer user.
Thanks guys, in my case I used the Virtual Onscreen Keyboard to logon (available from the Accessibility Options in the logon screen) and had to remove "Thinkpad Ultranav Driver" from Lenovo to get it to work. Urbananimal and cojaxx8, thanks for your posts!!
Hey Benni,
I just did the same thing you did -- I converted a Win 8.1 Pro laptop to a VM using the VMWare Converter. My host is an iMac (OS X Maverics), and my mouse is plugged into my keyboard. So I was surprised (heartbroken?) when I booted up the VM and the mouse worked when the keyboard didn't.
I made the registry change you suggested, rebooted, and everything worked fantastically well.
Thanks as well, of course, to cojaxx8, who originally discovered the solution.
Thank you very much for this post. I have been strugling with this issue for a couple days now. Finally Google found this post.
My situation for others.
P2V Lenovo workstation
after conversion the keyboard function was not passing keyboard strokes or even the VM console send ctrl alt del
Using the on screen keyboard I was able to log in to the machine
With the instructions below I was able to get in using normal keyboard functions
Again
Thank you very much for this information
Dana
Thank you folks very much for this solution. I had the same problem, and it saved my life.
I suppose that I was lucky to wander into this forum in exasperation and see this topic, created so long ago, at the top of the discussion. Google did not point my here in 2 days, unfortunately.
Perhaps this issue should be considered by the vmware team because:
* the issue has persisted since at least 4 years ago
* the issue pertains to fairly popular Lenovo hardware
* the issue is a showstopper
* all it takes is a single little needle of key in the registry haystack to throw everything awry
Anyway, much love again to OP for documenting this very elusive solution.
I successfully converted a physical HP laptop with Win 8.1 to a VM. Tried to boot in Workstation 11 by clicking 'Power up this virtual machine'. It looked like it starts up, then it stops 2 seconds later, resetting back to the initial screen.
After some Google searches, it turned out that changing the USB selection from USB 3.0 to either USB 2.0 or 1.1 under Virtual Machine Settings > USB Controller allowed the VM to start up. Yay!
It got to the login screen, and no keyboard! So I used the on-screen keyboard to log in, and it logged in fine. Nothing I did seemed to get the keyboard to work. I thought maybe installing VMware Tools would sort this out. I installed this, and then neither the keyboard nor mouse worked. Bummer!
Mr Google again. The VMware knowledgebase had a support article about plugging in another USB keyboard and mouse and attaching these directly to the VM under VM > Removable Devices. The mouse attached and worked fine, so at least I could drive the cursor again, but still no keyboard.
So I went to Control Panel (in the VM) > Devices, and I noticed that the keyboard driver said 'Driver error'. Hmm, must be a bum keyboard. So I grabbed another keyboard (first was an HP, this one is a Dell, so this gotta work now, right!), but alas, same issue, 'Driver error'
Then I came across this post, so I went to Programs and Features, and found the Synaptics Driver. Uninstalled this, rebooted and unplugged the second mouse and keyboard, and ** hallelujah **, all worked perfectly.
MAN, this has been a mammoth job of many hours getting to this point, but it is worth it.
Thanks heaps. I thought I would post this to say thanks, and hopefully this will help others who are in a similar position. Props to the other posters on this topic.
Cheers, and have fun!
Sean
Thanks for this article, pointed me in the right direction just had to remove the synaptic version in the class to get my keyboard working.
Thanks,
Cecil
Thanks for the tip. Keyboard working now!
Same, problem and solution!
R.
This one worked for me thanks!
I had the added hurdle of Symantec Endpoint Protection being installed on the laptop i was converting (with no access to the Symantec password), which appeared to be blocking RDP into the new network created on boot. However, using VMware Converter I was able to disable the Symantec services on boot which allowed RDP in. Then I was able to "fix" the driver issue and get the keyboard working...
Danny
Wanted to also add that this is true for Windows 10 P2V conversions as well. There are close to a dozen registry entries with the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96b-e325-11ce-bfc1-08002be10318} name. You have to look through them all until you find the one with the UpperFilters string. In my case UpperFilters was a Multi string with both SynTP and kbdclass as data values. I deleted SynTP, restarted the machine, and that resolved my issue. Again Windows 10x64
Additionally, the path to the on-screen keyboard so you don't have to google that separately is "C:\Windows\System32\osk.exe"
I had this same issue and found SynTP in the keyboard entry, removed that as per the instructions above, rebooted the vm and then it worked fine. My machine was also Win 10 x64.
Got this to work with P2V from win10 Enterprise from a lenovo laptop that had synaptics track/point.
The solution was not to edit registry in this case, but to remove the synaptics hardware from the device manager, then image the physical machine. Then, booted up in vmware, CTRL-ALT-DELETE functioned and was able to login and use it.
Removing SynTP worked for me, also.
Thank you, so very much 🙂
It took me many Googles to find this.
Several false starts, before I realized that there were multiple instances of that key.
(And I probably mis-matched the hex a couple of times.)
Anyone have any idea why VMware has not fixed this?
config:
Lenovo ThinkPad W530
Ubuntu Bionic 18.04 LTS x86_64 host
Windows 10 64-bit guest
VMware Workstation Player 14.1.2
For those of you who don't want to edit the registry, I was able to accomplish the same by removing the Synaptics software programs. One is able to click their way to add-remove programs. After removing the Synaptics mouse drive and programs, the keyboard worked as it should. Initial login was accomplished through the accessibility feature of on-screen keyboard. I'm NOT referring to the device in device manager, but the actual software program in add/remove software had to be removed & reboot.
Same here, I used VM Converter but then I could not use my keyboard to type anything. Used all the different browser and all but no luck. However, regkey resolved the issue for me
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96b-e325-11ce-bfc1-08002be10318} name. Look for UpperFilters string. In my case UpperFilters was a Multi string with both SynTP and kbdclass as data values. I deleted SynTP, restarted the machine, and that resolved my issue on windows 10 pro x 64
Hello from 2021! Just want to say that removing SynTP from this key fixed a nonfunctional keyboard caused by a VM Converter conversion of Windows 10 on esxi 7 from a thick to thin harddrive. Thanks for the post, I was going crazy--tried the conversion several times with a broken keyboard on each until I tried to find a workaround.