Opened 10 years ago
Last modified 10 years ago
#14614 new defect
Virtualbox kills keyboard when running on Windows 10
Reported by: | cytam | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.0.4 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Windows |
Description
OS: Windows 10 build 10240 Virtualbox version: 5.0.4-102546 and 5.0.5-102676
Description:
VirtualBox kills my keyboard every time it is run. Note that this happens when VirtualBox is running for some time, even without starting any VM.
I fresh installed VirtualBox in my new Windows 10 machine (it's a newly built PC with no PS/2 port on the motherboard, so I am using a USB keyboard). Since it's a fresh install the first thing I do is to create a new VM. The keyboard suddenly died out when I attempt to specify where to store the VM files. All LED went off, and pressing the NumLock/CapsLock/ScrollLock keys won't trigger any LED back on. At first I thought it may be the cable of my keyboard got loose. So I checked but found no problem. Unplugging and plugging the keyboard to the same or different USB ports didn't help. Windows even didn't play any sound that indicate a device is being plugged in/unplugged.
I was afraid that it is the motherboard having some issues, but luckily the keyboard came back when I reboot the machine. I tried several times and the result is still the same.
It seems that only the USB keyboard is affected. The mouse still works.
In my experience, keyboard dies after about 1-2 minutes of usage in the stable (5.0.4-102546) build. Using the latest test build (5.0.5-102676). keyboard dies out after about 10 minutes of usage.
I found one similar case in the forum [1]. The op is working on a laptop, while I am working on a desktop.
Not sure if related to the issue, my Windows 10 machine also runs VMWare workstation .
[1] https://forums.virtualbox.org/viewtopic.php?f=6&t=70081
also caps lock continuously flickers between host and guest windows and after 1 hr a hard SHIFTLOCK is enabled so you cant type numbers any more
workaround
shutdown all vms shutdown virtbox
restart virtbox restart all vms