Opened 5 years ago
Last modified 5 years ago
#18255 new defect
Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors.
| Reported by: | peddanet | Owned by: | |
|---|---|---|---|
| Component: | guest additions/x11/graphics | Version: | VirtualBox 5.2.22 |
| Keywords: | VBoxGuestAddition installing guest addition update 6.0 | Cc: | peter.wein@… |
| Guest type: | Windows | Host type: | Linux |
Description
Host : Ubuntu 16.04 Host System: NVIDIA Graphics, i7 core, 24 GB RAM VirtualBox Client: Windows 10 worked with VirtualBox 5.2 Issues that the second screen has only 1280x1024 instead of 1600 x1200
That was working before I run the machine today.I have not worked for month with the target.
An update to 5.2.22 was announced. I clicked it away. Then I got the small issue mentioned above. I decided to do the update. On the homepage 6.0 was announced instead of 5.2.22. So I downloaded the deb-File for 16.04. Ubuntu Software Center could not install it. Old version has been still installed at this time. But then followed the instructions on the page and downloaded and installed it by command line adding the repo for it.
After starting my Windows 10 machine, there was only two very small VGA screens left. After trying to reinstall the vboxguestadditions, there was only one screen left at least with 1280x1024 resultion.
There have been errors installing the guest additions they stuck installing some driver fro VBoxVideoW8 for a "hardware that is currently not present". Please see the log.
How can I rescue my windows copy. Because I think something was messed up during installation of VB 6.0 or the guest additions. I meanwhile deleted the vbox in /usr/share/virtualbox but after reinstallation error stays stable. I am not able to continue working on my projects .
In the end I deinstalled 6.0 and get me a copy of 5.2.22.
Please help save my work, because last time it all worked perfectly!
Best regards Peter
Attachments (2)
Change History (5)
by , 5 years ago
| Attachment: | install_drivers.log added |
|---|
by , 5 years ago
| Attachment: | virtualbox-Windows10-2018-12-31-17-53-29.log added |
|---|
comment:1 by , 5 years ago
comment:2 by , 5 years ago
It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
Plus it's really a shame that I'm doing the VBox.log analysis here, where most probably only you, me and a developer might see the answer, as opposed to the forums, where many more users can benefit.
So, if you can, please open a new thread in the VirtualBox on Linux Hosts or the Windows Guests section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.
comment:3 by , 5 years ago
Thanks for posting in the forums!
Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=7&t=91065
At least the guest addition log looked very stable over all changes. So the root cause is maybe the same.