Page 1 of 1
Win 10 Dual Monitor fail with VB6.1.26
Posted: 10. Aug 2021, 13:11
by craig100
Upgraded to VB 6.1.26 on Linux Mint 20.2 Cinnamon, Kernel 5.11.0-25, now Win10 guest hangs on boot when 2nd screen initialised. Will boot on single screen. GA installed ok. Have been using dual screen for years. Log attached at time of hang.
Any clues would be appreciated.
Re: Win 10 Dual Monitor fail with VB6.1.26
Posted: 10. Aug 2021, 17:52
by fth0
VirtualBox 6.1.24 had a regression regarding mouse pointer positioning on the second screen, which was fixed in VirtualBox 6.1.26. Which version did you use before 6.1.26?
W10%20VS2019%20Comm-2021-08-10-12-07-21.log wrote:00:00:01.282764 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 2560x0 x 2560x1402
00:00:01.293487 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 1 work area is actually resized to: 0x0 x 2560x1440
It looks like your primary screen is right to your secondary screen. Is that correct? Please post the
W10 VS2019 Comm.vbox file.
Re: Win 10 Dual Monitor fail with VB6.1.26
Posted: 11. Aug 2021, 11:19
by craig100
fth0 wrote:It looks like your primary screen is right to your secondary screen. Is that correct? Please post the W10 VS2019 Comm.vbox file.
Correct, the main screen 1 is on the right, second screen on the left. Copy of W10 VS2019 Comm.vbox attached with MAC addresses redacted
Thanks
Re: Win 10 Dual Monitor fail with VB6.1.26
Posted: 11. Aug 2021, 23:35
by fth0
I don't know if this will solve your problem or not, but I'd suggest to eliminate the memorized screen-related information from the VM's configuration file using the following commands, while the VM is not running:
Code: Select all
VBoxManage setextradata "W10 VS2019 Comm" "GUI/LastGuestSizeHint"
VBoxManage setextradata "W10 VS2019 Comm" "GUI/LastGuestSizeHint1"
VBoxManage setextradata "W10 VS2019 Comm" "GUI/LastNormalWindowPosition"
VBoxManage setextradata "W10 VS2019 Comm" "GUI/Last LastNormalWindowPosition1"
VBoxManage setextradata "W10 VS2019 Comm" "GUI/LastScaleWindowPosition"
VBoxManage setextradata "W10 VS2019 Comm" "GUI/Last LastScaleWindowPosition1"
VBoxManage setextradata "W10 VS2019 Comm" "GUI/LastVisibilityStatusForGuestScreen1"
If this didn't help, can you switch the roles of your two monitors on the Linux host for a test? BTW, you didn't answer my question regarding the previous VirtualBox version.
Re: Win 10 Dual Monitor fail with VB6.1.26
Posted: 11. Aug 2021, 23:49
by craig100
BTW, you didn't answer my question regarding the previous VirtualBox version.
Sorry, had to do a bit of digging to find out. It looks like it was 6.1.24.
I'll try your suggestion as soon as I get back home and let you know. Should be tomorrow. I'm just travelling with a laptop right now.
Thanks.
Re: Win 10 Dual Monitor fail with VB6.1.26
Posted: 31. Aug 2021, 15:30
by craig100
As suggested I managed to temporarily switch my primary screen round on Mint. It didn't make any difference. So reverted to normal.
I then tried switching off "3D Acceleration". This allowed Windows 10 to boot to 2 screens and allowed me to log in. However, everything happened on VB Screen 2 leaving VB Screen 1 totally black. Interesting enough the background on VB Screen 2 is the correct background for the Windows screen 2 but the foreground content of the VB Screen 2 was that of the missing Windows Screen 1 (i.e. taskbar and desktop icons, albeit in the wrong places).
It appears to be completely screwed up like never before. I've updated VB many, many times over the last decade and never had such a problem. I've been using 2 screens with VB for about 4 years now without a hitch.
If there's anything else I can do to troubleshoot, please let me know.
TIA
Re: Win 10 Dual Monitor fail with VB6.1.26
Posted: 31. Aug 2021, 22:59
by fth0
I have no new ideas, but since you didn't mention it explicitly: Did you eliminate the memorized screen-related information as suggested? Before each experiment?
Re: Win 10 Dual Monitor fail with VB6.1.26
Posted: 20. Sep 2021, 14:12
by simondcoleman
Not sure from the posts as to whether this applies to your case.
If I start my dual monitor vbox in full screen both displays go black.
Switching to windowed & then back to full-screen shows it's a graphics issue, not a vm one.
The displays redraw & all is ok.
A soft reboot of the vm has the same effect.
I occasionally forget (not many restarts) & worry about a crash for a few minutes until I remember to come out of fullscreen.
This applies to all guests [win11 & ubuntu], vbox 6.1.26 running on an ubuntu 20.04 host.
Re: Win 10 Dual Monitor fail with VB6.1.26
Posted: 20. Sep 2021, 20:16
by craig100
Finally fixed it. It was a Windows 10 issue rather than a VB issue. I ran it up with 3D Accel off. Set up both screens again in Windows then rebooted with 3D Accel back on again. It's been fine ever since.
HTH
Re: Win 10 Dual Monitor fail with VB6.1.26
Posted: 21. Oct 2021, 13:08
by craig100
The exact same thing happened with the upgrade from VB6.1.26 to VB6.1.28. Though an additional item was initially, before guest additions where added, there were two mouse cursors, one for the host and one for the guest. The guest one didn't cover the whole window which caused a bit of worry. Once again, had to reduce down to 1 display with 3D Accel off to install GA. Then switch on 2nd display, set the displays up in Windows again then switch on 3D accel. Now ok.
Upgrading used to be a non-event, the last two have had issues, but at least I now know what to do about it. Hope this helps others that come across this as it's quite a shock when Windows stalls on boot.