Changes between Version 1 and Version 2 of Ticket #14409, comment 15
- Timestamp:
- Dec 31, 2015 3:06:21 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14409, comment 15
v1 v2 1 I confirm the above reports: this bug, which appears to be in the Win8/Win10 display driver installed by Guest Additions, still exists. I first encountered it after I transitioned from a Win7 Guest to a Win10 Guest, recently. When I first saw the bug, the display went to 800x600. I was able to increase the size in Win10, and currently my system changes the display from 1920 or 2560 pixels wide to 1600x1200. The system is usable, but it is a frustrating loss of functionality.1 I confirm the above reports: this bug, which appears to be in the Win8/Win10 display driver installed by Guest Additions, still exists. I first encountered it after I transitioned from a Win7 Guest to a Win10 Guest, recently. When I first saw the bug, the display went to 800x600. I was able to increase the size in Win10, and currently my system changes the display from 1920 or 2560 pixels wide to 1600x1200. The Win10 system is usable, but this is a frustrating loss of functionality. As others have reported above, I confirm that normal full-screen operation can be restored by either restarting Win10 or by re-installing the Guest Additions. 2 2 3 3 I briefly thought that I had found a workaround, by always saving the state of the VM when not using it, but then I witnessed the bug occur immediately after restoring the state of the saved VM. I saw Win10 change to the reduced machine display size, and pop up a small temporary window informing me that the display driver was not responsive, and had been replaced. That failure of my hoped-for workaround prompted me to file this report. … … 5 5 My Host is a MacBookPro running El Capitan 10.11.2, running VirtualBox 5.0.10 r104061, and my Guest is a 64bit 1cpu Win10pro v1511. I expect that the bug only depends on running a Win10(or Win8) Guest under VirtualBox 5, with the (faulty) VBoxVideoW8 display driver installed by VB5 Guest Additions. 6 6 7 As others have reported above, I confirm that normal full-screen operation can be restored by either restarting Win10 or by re-installing the Guest Additions.7 NOTE: the ticket for this bug, as filed five months ago, says that it is for Mac hosts; that is probably wrong -- the bug probably occurs for ALL HOSTS.
