Hi,
I am not too new to using VM VirtualBox, but I encountered an error after I changed my monitor.
I have been projecting to a second screen (a bigger one for easier viewing) without any issues until I changed the monitor.
When I connect the new monitor, the main screen will be the bigger monitor instead of the PC and as I tried different options, I couldn't log into windows anymore. The system only boots to a black screen and won't go further.
But I discovered that once I go to settings > Display > Monitor count and change from 2 to one the system boots normally.
What can I do to be able to extend my VM screen to a second monitor without encountering an error?
I have attached the log file
VMBox Won't boot unless I Change Display Monitor Count to 1
VMBox Won't boot unless I Change Display Monitor Count to 1
- Attachments
-
- Windows 10-2022-08-03-09-51-40.log
- This is the VM VirtualBox Log file
- (115.75 KiB) Downloaded 3 times
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VMBox Won't boot unless I Change Display Monitor Count to 1
The provided log is truncated. Please zip and attach complete logs.
Re: VMBox Won't boot unless I Change Display Monitor Count to 1
Thanks for the prompt response.mpack wrote:The provided log is truncated. Please zip and attach complete logs.
The zipped logs has been attached.
- Attachments
-
- Logs.zip
- (172.73 KiB) Downloaded 7 times
Re: VMBox Won't boot unless I Change Display Monitor Count to 1
Hi Mpack,mpack wrote:The provided log is truncated. Please zip and attach complete logs.
I am still awaiting. Kindly help me get through this.
Thank you
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VMBox Won't boot unless I Change Display Monitor Count to 1
I didn't say I had an answer for you, all I said was that the info you provided is incomplete.
And in any case the zip you provided had two truncated logs and several older logs. Not the single, current, complete, zipped log needed. Do NOT copy out files while the VM process is still running.
Check if you get the same behaviour with and without 3D acceleration being enabled. If it works with 3D acceleration disabled then it implies that you have different graphics cards for the two monitors, and one has drivers with signing problems. Unfortunately the hardening log was one of the two truncated logs.
And in any case the zip you provided had two truncated logs and several older logs. Not the single, current, complete, zipped log needed. Do NOT copy out files while the VM process is still running.
Check if you get the same behaviour with and without 3D acceleration being enabled. If it works with 3D acceleration disabled then it implies that you have different graphics cards for the two monitors, and one has drivers with signing problems. Unfortunately the hardening log was one of the two truncated logs.