Usually, it comes back for a while, but sometimes, after doing the previous procedure, it keeps on freezing. The issues persist, but I have new information to share, although I'm not sure if it will be helpful.įirst, when the VM freezes, most of the time, I press RCTRL + P to pause it and the same button again to unpause the VM. Thanks in advance.Hello, I'm still facing the same issue after following all the steps discussed before, including reinstalling the WIN 10 on a fresh VM. Why this is the case I'm not sure, and I was wondering if someone could help me. This made me suspect that VirtualBox is somehow allocating lower memory when run (using VBoxManage for instance) from the terminal, as compared to when it's started using the GUI.

Graphics-intensive programs crash as expected (but not when the VM is launched from GUI). On a Windows 7 guest, when remotely connected from the terminal, Aero is disabled but it otherwise works fine, which I put it down to Windows 7's basic mode requiring less graphics memory (as compared to Windows 10, where DWM is forced).

If the VM is started headless from the GUI, things work as expected even if the VM is remotely connected later on. The machine in both cases is the same - the only difference is how the VM is initially started. How the VM was started remotely doesn't matter (I tried VBoxHeadless -startvm vmname and VBoxManage) when started from the command line, the graphics driver crashes and one has to work with the built-in Windows 10 display driver (which does not resize and works poorly).things work fine when the VM is started from the GUI.

Consider the scenario as follows: a virtual machine is created (on the latest version of VirtualBox 6.1), and 256 MB (the maximum) of graphics memory is assigned.

Windows 10 virtualbox hangs