Keyboard not working

[AnandaVimal]

Hello Everyone,

I have this VM running Windows 10 Pro 64 bit installed, yet all of a sudden the keyboard does not work.

When I installed Windows 10 the keyboard worked fine.

Virtual Box is running on a Tuxedo computer with Virtual box pre-installed.

The host OS ist a Tuxedo OS based on Ubuntu.

I'll attach a screen shot with the keyboard shown as activated, yet the keyboard does not work.

I've tried everything I could think of. Any advice on how to solve this issue ???

[mpack]

Probably you enabled a blank USB filter in <settings>|USB. Disable them until you learn what USB is for.

Also, if VirtualBox was pre-installed on Ubuntu then it probably isn't VirtualBox. It's the Ubuntu fork based off the open source. Only the official release is supported here, not third party forks.

If you want to continue this discussion then I'll require a VM log. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

[AnandaVimal]

I just deactived USB, but still no keyboard action when trying to enter the password to log in

[mpack]

Please refer to the last paragraph of my previous response.

[AnandaVimal]

I've attached the Log as requested.

If this is a Fork then I'm not aware of it.

Thank you for looking into this! The funcitoning VM will hopefully enable me to install Ableton Live to produce music.

[mpack]

You are not using a fork. The log shows you are using VirtualBox 6.1.12.

I recommend that you install the extension pack, and give the VM 2 cores. The idea of Win10 on a single core makes me shudder! However, don't give it more than two cores.

When you say "no keyboard action", do you literally mean that nothing at all happens, or simply that your password is rejected? I have never heard of the former other than when the host has been robbed of its keyboard by a misjudged USB reassignment, but the latter would be a relatively common newbie error (assuming that the guest somehow knows the host keyboard layout).

Once you get access to the guest OS you need to update the Guest Additions: currently you have v6 features enabled (in particular, the VBoxSVGA graphics controller), and a v5 version of the GAs which has no idea how to use those features properly.

[AnandaVimal]

I recommend that you install the extension pack, and give the VM 2 cores.

What Extension pack? and yes, I was unaware of the fact that it was only running on one processor. I changed the settings accordingly.

When you say "no keyboard action", do you literally mean that nothing at all happens, or simply that your password is rejected?

Nothing at all happens. I can't type in my password.

I have never heard of the former other than when the host has been robbed of its keyboard by a misjudged USB reassignment,

That leaves me with little hope... I've written Tuxedo computer's support as well. Perhaps they know why...

Once you get access to the guest OS you need to update the Guest Additions

How do I do that?

Thank you for taking your time so far!

[mpack]

Where did this VM come from? Was it always created as a VirtualBox VM on this host? It was never a VM on another platform?

See the user manual, chapter 1, for your extension pack question.

[AnandaVimal]

here did this VM come from?

It was preinstalled, as requested, on the Tuxedo laptop I purchased two months ago. - https://www.tuxedocomputers.com/en#

Was it always created as a VirtualBox VM on this host?

Yes.

It was never a VM on another platform?

Yes, it was never used on another platform.

See the user manual, chapter 1, for your extension pack question.

Thank you!

[fth0]

Once you get access to the guest OS you need to update the Guest Additions: currently you have v6 features enabled (in particular, the VBoxSVGA graphics controller), and a v5 version of the GAs which has no idea how to use those features properly.

I'd suggest to temporarily change Display > Screen > Graphics Controller to the old VBoxVGA and try if the problem persists. If the login is successful then, uninstall the GA, reboot, install the GA matching the VirtualBox version, shutdown, and change Display > Screen > Graphics Controller back to the current VBoxSVGA again.

[mpack]

Well, I have no problem doing that, but I can't see why incorrect drivers for the current graphics controller could have any effect on the keyboard.

I'm more interested in the statement:

here did this VM come from?

It was preinstalled, as requested, on the Tuxedo laptop I purchased two months ago.

I.e. the OP did not install this guest OS himself and therefore has no basis for assuring us that this OS was installed properly, from scratch, as a VirtualBox original VM on this host. Because I don't think it was. I think it was created as a VMWare VM and then migrated. That has often in the past resulted in a dead keyboard.

[AnandaVimal]

OK, I followed up on my initial support request to Tuxedo Computers, and will try to get a reply from them to fix this issue.

Thank you so far and have a nice evening mpack.

[fth0]

I think it was created as a VMWare VM and then migrated. That has often in the past resulted in a dead keyboard.

Interesting, I didn't know that. Then of course your assessment has a much higher probability than any wildly constructed idea from myself that errors in the VirtualBox graphics driver initialization (as seen in the VBox.log file) could have an impact on graphical dialog elements.