virtualbox.org

I'm having problems controlling Visual Studio on a remote computer using my new Logitech MX keyboard.

This has worked just fine with my Logitech MK710 keyboard for several years. I can use F5 (Start Debugging) and F10 (Step Over) keys.

I login to my VirtualBox VM.
I create a VPN to the remote computer.
I then create an RDC connection to the remote computer through the VPN.
I then run Visual Studio and debug projects.

I received my new Logitech MX keyboard a few days ago. I set it up and was able to do most normal tasks, such as reading email, creating VPN connection, connecting RDC, writing Word documents.

When I debug using Visual Studio on the remote computer I can type characters into code files, etc.

However, when I press F5 (Starting Debugging) or F10 (Step Over) keys the key press doesn't get to the remote computer. The F5 causes all windows to minimize on the host machine.

Just tested: If I bring up Visual Studio on my host computer and then type F5 (Start Debugging), the screen minimizes. I'm guessing that means the MX keyboard has overridden the normal F5 function. So perhaps it's not a VirtualBox problem, but perhaps I have to reconfigure MX Keys.

VirtualBox Version 6.0.4.
Host Computer: Windows 10 Pro, 64GB RAM
Guest: Windows 10 Home, 8GB RAM
Remote Computer: Windows 7,
Insert Guest Additions: I selected the menu item but then nothing happens. I'm sure I've installed it in the past.

I couldn't find: VBoxStartup.log or VBoxHardening.log. I looked in C:\Program Files\Oracle\VirtualBox\

Thanks, Ed

SoulTraveler wrote:This has worked just fine with my Logitech MK710 keyboard for several years....I received my new Logitech MX keyboard a few days ago. I set it up

Logitech is known for having extra apps and drivers to control their keyboards and mice, which apps & drivers sometimes are incompatible with other programs.

This site: https://www.computerhope.com/issues/ch000306.htm reports the common results for F# keys on Windows. F5 doesn't report minimizing all windows as common behavior. It does report modern web browsers as using F5 to reload the page, which in my test caused me to have to type this all again . Do you have such apps, perhaps an old setting, or an old app that should have been changed or deleted when you changed keyboards?

Better still, as a test, uninstall any keyboard/mouse control apps & drivers, and use the no-fast-boot complete shutdown command, in a command window or the Run... box:

shutdown -s

to completely reboot your host PC. Try the F# keys again with a basic HID keyboard, no bells & whistles, and see what happens.

SoulTraveler wrote:Insert Guest Additions: I selected the menu item but then nothing happens.

This menu choice only inserts the GAs ISO CD image into the guest OS's virtual CD drive. If your guest OS has Autoplay turned off, nothing will happen. Open the guest's CD drive and run the GAs launcher appropriate to the guest OS.

SoulTraveler wrote:I couldn't find: VBoxStartup.log or VBoxHardening.log.

'VBoxStartup.log' is the old name for 'VBoxHardening.log'.
Easiest way to get at the 'VBoxHardening.log' is to right-click the guest in the main Virtualbox window and choose Show Log. These are actually kept in the guest folder, in the subfolder 'Logs': see the right-click menu 'Show in Explorer' choice.

SoulTraveler wrote:So perhaps it's not a VirtualBox problem, but perhaps I have to reconfigure MX Keys.

This ^^^.

I don't see how a different keyboard can affect what scancode is sent, unless the keyboard itself is "translated" at a lower level. Are there any keyboard-specific drivers/software installed? You should take a look at that...

Hi,

Seems funny I ran into the same problem a few years later and funny that I'm answering my question.

My Logitech Unifying Receiver failed to maintain a connection to my Logitech mouse.

I could use the mouse for an hour or two. Then, if I went away from my computer and returned, the connection was lost. I'd have to use the mouse pad on my laptop to reconnect the Logitech mouse.

I ordered and received a new Logitech Unifying Receiver on Sunday. I plugged it in. Initially,
MX Keys and Logitech mouse connected and stayed connected to the receiver on my laptop.
So, I thought everything was good.

When I started to debug code through my VirtualBox and RDC connection to a remote computer
I noticed pressing F10 in Visual Studio didn't do anything.

I started the Logitech Options app. Selected MX Keys device and noticed under the GENERAL section:

Use F1, F2, etc. Keys as standard function keys function.

This feature was toggled off.

I toggled it on.

And, Shazam! I was able to use F10, F11, etc. in Visual Studio on the remote computer.

Ed

Thanks for posting your finding.