virtualbox.org

I've run into some weird Mouse/Keyboard behavior after installing Guest Additions. Before installing them, windows seems to work perfectly (except that I can't make it my full monitor resolution). So to get the full resolution I installed the guest additions via the menu at the top to mount the iso. I mounted and the clicked on the "Vboxwindowsadditions.exe" file. Went through the install. This is where things stopped working. The screen went black for a while and when it came back i couldn't type or use the mouse in the Guest. What would happen is that if there were a button I wanted to click, I would try and click it and nothing would happen. I would then click out of the guest into the host (like select the task bar in the host windows) and all of a sudden my previous actions in the guest would happen. This would happen for typing too. So I can somewhat get around by clicking in the guest and then clicking in the host, or typing in the guest and then clicking in the host so that the words would be typed. It's really strange.

I'm new to VirtualBox so I really have no idea what to do now.

If anyone has any suggestions I'd really appreciate them!

Host OS: Windows 10 64 Pro
Guest OS: Windows 10 64 Pro

For future reference, we need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

But, in your case I think I know the answer without looking at the log. You have selected (this is the default now, you did nothing wrong), the "VBoxSVGA" graphics controller (see https://www.virtualbox.org/ticket/18205). This is known to have issues with refreshing the screen. Try to change it to "VBoxVGA" (without the "S") and see what happens. If that doesn't work, post the ZIPPED VBox.log as directed above.

Thank you socratis! That was exactly the problem. Can't believe I was banging my head against google for so long and couldn't figure that out.

Also, in the future I'll remember to post the log. Thanks for that info.

Grifter wrote:Can't believe I was banging my head against google for so long and couldn't figure that out.

Don't bang your head too hard. I don't think that Google had a chance to index yet everything related to that, it's only 9 days since 6.0.0 came out. Also you got to remember that Google was on vacation this week too...