unable to display console

[goher2000]

I am running VirtualBox 7.0.8 on window 10 pro, after the upgrade from pervious version 6, the vms are running in background but I am unable to display console, I have reinstalled VirtualBox along with extension with no luck, I have even deleted .virtualbox folder in order to get rid of any old settings but it didn't work.

[scottgus1]

the vms are running in background but I am unable to display console,

How are you starting the VMs, and is this the same process you were using before?

[goher2000]

vm are auto starting on boot and currently set to headless , I tried manual with new/exsiting vms, i tired with --defaultfrontend default and --defaultfrontend headless with no luck

[CJM7]

I'm having the same issue having upgraded my Windows10 host from 6.1.38 to 7.0.8. Now, when starting any VM (I tried Normal and Detachable Start from the GUI Manager), no console window appears on screen nor in the taskbar. The guests do actually run: they show as "Running" in the GUI Manager and the current console screen can be seen in tiny Preview window.

In an effort to identify the version where this may've started, I took another host which was running an older 6.1.4, upgraded it to the same version as my first host (6.1.38), then proceeded to install the latest 6.1 version (6.1.44), then installed the following in order, testing the guest start on each:

7.0.0
7.0.2
7.0.4
7.0.6
7.0.8

and low-and-behold it never failed! The guest started and console appeared correctly on each of these versions on my 2nd host.

At this point, I can't identify what is materially different on my first host compared to my second, except that the second host went through installing each subsequent version while the original host (as with the OP) was directly updated from 6.1.38 to 7.0.8.

[CJM7]

Update: This issue persisted on my first host after upgrading it 28Jul2023 from 7.0.8 to 7.0.10 and the subsequent reboot. However, the problem stopped happening on that same system in late Aug2023, possibly after a Windows Update came along. Regrettably, I'm unable to confidently identify what solved the problem which I can no longer recreate at this point.

I'm curious if the OP still has this problem.

[thexixx]

I did some investigation and replied to another tread here viewtopic.php?p=545452#p545452