Until today I had a good WIN10 virtual machine configuration. I then updated to Virtua lBox 4.3.28.100309 and also updated the WIN10 Guest Additions to the 4.3.28.100309 version. At that point I lost the wide-screen display modes and have been unable to get them back.
If I run “VBoxManage getextradata WIN10 enumerate” I get the result:
Key: CustomVideoMode1, Value: 1366x768x32
Key: CustomVideoMode2, Value: 1440x900x32
Key: GUI/LastCloseAction, Value: Shutdown
Key: GUI/LastGuestSizeHint, Value: 1152,864
Key: GUI/LastNormalWindowPosition, Value: 109,92,1152,906
Key: GUI/MiniToolBarAlignment, Value: bottom
Key: GUI/SaveMountedAtRuntime, Value: yes
Key: GUI/ShowMiniToolBar, Value: yes
So, the wide-screen modes appear to be defined, but never show up when attempting to change the Display settings in WN10.
Can anyone provide assistance in resolving this issue?
WIn10 - Can't use CustomVideoModes with 4.3.28.100309 ?
-
RB@hotmail.com
- Posts: 5
- Joined: 15. May 2015, 23:47
-
loukingjr
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: WIn10 - Can't use CustomVideoModes with 4.3.28.100309 ?
FWIW, the only time I have a working W10 guest is when I do a fresh install when a new build comes out and install the guest additions for the first time.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
-
RB@hotmail.com
- Posts: 5
- Joined: 15. May 2015, 23:47
Re: WIn10 - Can't use CustomVideoModes with 4.3.28.100309 ?
Updated Win10 to Build 1022. Still no wide modes.
Uninstalled WIN10 Guest Additions to the 4.3.28.100309. Can now use video wide modes.
What's up Oracle????????
Uninstalled WIN10 Guest Additions to the 4.3.28.100309. Can now use video wide modes.
What's up Oracle????????
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: WIn10 - Can't use CustomVideoModes with 4.3.28.100309 ?
Lets see every time MS releases an update it brakes something and that takes time to fix, but by the time it would have been fixed they changed something else and guess what? We are right back to where we were before with it being broken again. Don't expect anything until MS releases the product and then it will be worked out.RB@hotmail.com wrote:Updated Win10 to Build 1022. Still no wide modes.
Uninstalled WIN10 Guest Additions to the 4.3.28.100309. Can now use video wide modes.
What's up Oracle????????
-
loukingjr
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: WIn10 - Can't use CustomVideoModes with 4.3.28.100309 ?
FWIW, I have Windows 10 (Build 10122 now) guests installed on OSX, Linux and Windows 8.1 hosts running on VB 4.3.28 and VB 5.0 Beta4 and the guest additions. I have no trouble with wide screen modes with any of them. Maybe the OP means something else?
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
-
loukingjr
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: WIn10 - Can't use CustomVideoModes with 4.3.28.100309 ?
and just because I can, Windows 10 in 900 x 1440 mode.
- Attachments
-
- Windows 10.jpg (98.03 KiB) Viewed 10626 times
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
Re: WIn10 - Can't use CustomVideoModes with 4.3.28.100309 ?
To add special mode simply use VBoxManage setextradata
On OSX hosts (in terminal)
On Windows hosts :
On OSX hosts (in terminal)
Code: Select all
VBoxManage setextradata "Your Win10 machine name" CustomVideoMode1 1920x1080x32Code: Select all
VBoxManage.exe setextradata "Your Win10 machine name" CustomVideoMode1 1920x1080x32Re: WIn10 - Can't use CustomVideoModes with 4.3.28.100309 ?
I've wasted most of the day on this and think I now have everything working.
I'm running CentOS 6.5 and VB 4.3.30 (tried version 5.0.2 but that just seg faults).
Had a perfectly happy Windows 8.1 with a screen resolution of 1920x1200. Used Microsofts upgraded media to move to Windows 10. After the upgrade I immediately installed Guest Additions.
The maxiumum screen resolution offered was 1600x1200.
A common suggestion "vboxmanage setextradata "Windows 8.1" CustomVideoMode1 "1920x1200x32"" - this has no effect at all (reading section 9.8.1 of the manual though: "When using Windows guests with the VirtualBox Guest Additions, a custom graphics driver will be used instead of the fallback VESA solution so this information does not apply" suggests this was never going to work when using guest additions.
Next - setting 'vboxmanage setextradata "Windows 8.1" GUI/MaxGuestResolution "any"' - this added 1920x1440 to the list of options (ignored with auto because bigger than the physical resolution available).
Uninstalling guest additions gave me the full 1920x1200 resolution.
** Solution that worked for me **
+ With the guest running open a 'cmd' window as administrator.
+ Change to Guest Additions directory (for me c:\Program Files\Oracle\VirtualBox Guest Additions
+ List custom modes "VBoxControl.exe listcustommodes" - empty list
+ Add the new resultion: "VBoxControl.exe addcustommode 1920 1200 32"
+ I then did "VBoxControl.exe setvidmode 1920 1200 32 1" - but this seemed to have no effect at all. Mentioning here in case this is the critial step!
+ Reboot Windows - and go to the display properties and I now have the screen resolution I want.
I've been using VirtualBox for something like 5 years on many OSes and never had to do this so some problem with Guest Additions automatically detecting available hardware resolution in Windows 10?
I'm running CentOS 6.5 and VB 4.3.30 (tried version 5.0.2 but that just seg faults).
Had a perfectly happy Windows 8.1 with a screen resolution of 1920x1200. Used Microsofts upgraded media to move to Windows 10. After the upgrade I immediately installed Guest Additions.
The maxiumum screen resolution offered was 1600x1200.
A common suggestion "vboxmanage setextradata "Windows 8.1" CustomVideoMode1 "1920x1200x32"" - this has no effect at all (reading section 9.8.1 of the manual though: "When using Windows guests with the VirtualBox Guest Additions, a custom graphics driver will be used instead of the fallback VESA solution so this information does not apply" suggests this was never going to work when using guest additions.
Next - setting 'vboxmanage setextradata "Windows 8.1" GUI/MaxGuestResolution "any"' - this added 1920x1440 to the list of options (ignored with auto because bigger than the physical resolution available).
Uninstalling guest additions gave me the full 1920x1200 resolution.
** Solution that worked for me **
+ With the guest running open a 'cmd' window as administrator.
+ Change to Guest Additions directory (for me c:\Program Files\Oracle\VirtualBox Guest Additions
+ List custom modes "VBoxControl.exe listcustommodes" - empty list
+ Add the new resultion: "VBoxControl.exe addcustommode 1920 1200 32"
+ I then did "VBoxControl.exe setvidmode 1920 1200 32 1" - but this seemed to have no effect at all. Mentioning here in case this is the critial step!
+ Reboot Windows - and go to the display properties and I now have the screen resolution I want.
I've been using VirtualBox for something like 5 years on many OSes and never had to do this so some problem with Guest Additions automatically detecting available hardware resolution in Windows 10?