Hi,
I just updated to version 6.0.6 in Windows 10 host and also updated Guest Additions in Windows 2012 R2 guest, but after rebooting screen is monochromatic and resolution is 640x480 with no way to make it better, do you have any recommendations? Thanks in advanced.
[Resolved] Windows 2012 guest resolution downgraded after 6.0.6 update
[Resolved] Windows 2012 guest resolution downgraded after 6.0.6 update
Last edited by socratis on 24. Apr 2019, 08:14, edited 1 time in total.
Reason: Marked as [Resolved].
Reason: Marked as [Resolved].
-
cameron_hayne
- Posts: 1
- Joined: 23. Apr 2019, 23:51
Re: Windows 2012 guest resolution downgraded after 6.0.6 update
I had this problem (with a Windows 10 guest on OS X host in 6.06) after doing a Windows 10 update.
I solved the problem by taking the suggestion that I saw elsewhere on these forums to change the vGPU setting (in VirtualBox's Display settings) to VBoxVGA
instead of VBoxSVGA which it was before.
I solved the problem by taking the suggestion that I saw elsewhere on these forums to change the vGPU setting (in VirtualBox's Display settings) to VBoxVGA
instead of VBoxSVGA which it was before.
Re: Windows 2012 guest resolution downgraded after 6.0.6 update
Thanks a lot, this solved the problem.
Last edited by socratis on 24. Apr 2019, 08:11, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
Reason: Removed unnecessary verbatim quote of the whole previous message.
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 2012 guest resolution downgraded after 6.0.6 update
Marking as [Resolved].
@both "omoralesm" and "cameron_hayne",
Next time that you're having an issue, please include a ZIPPED VBox.log. I'll give you the instructions now, so I won't have to give them at a future post, two birds with one stone...
We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
@both "omoralesm" and "cameron_hayne",
Next time that you're having an issue, please include a ZIPPED VBox.log. I'll give you the instructions now, so I won't have to give them at a future post, two birds with one stone...
We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
- Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
- With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
- Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.