4.3.20 VM window keeps squeezing into smallest possible size

[wroot]

I have tried upgrading 4.3.12 to 4.3.16 (on Windows 7 x64). I have also done uninstall and install of 4.3.16. Whenever i start a VM its window squeezes itself into a smallest possible size and jumps into left highest corner of the screen. If i try to drag the border down it jumps back again. The only way to work with VM is to maximize a window and work in a scaled stretched mode. Going back to 4.3.12 fixes the issue. Maybe 4.3.16 missing something from the previous version? But 4.3.14 wasn't working for me at all.

Updated the title as this is the same for 4.3.20 (was same with 4.3.18).

[OliverOne]

Same issue here! Downgraded to 4.3.12.

[mpack]

@Oliver: Downgraded to 4.3.12... and what?

@wroot: IME It's a common problem caused by a corrupted registry - nothing at all to do with the VirtualBox version.

The usual fix is to pick a display size other than the one it's using - i.e. force it to update the registry with new size information. Then reboot the guest. Then change display size back to where you want it to be, and reboot again.

The well known hardening issues with 4.3.14, and less so with 4.3.16, can affect graphics, but I've not heard of it causing these symptoms. Still, you can easily try downgrading to 4.3.12 and report the results.

[OliverOne]

If I downgrade to 4.3.12, all is correct. With 4.3.16 all Guests have the problem.

[wroot]

@wroot: IME It's a common problem caused by a corrupted registry - nothing at all to do with the VirtualBox version.

Yet, if i install 4.3.12 it is back to normal. How come this registry "corruption" only happens when i install 4.3.16? Or do you mean this is a client's registry corruption? This is happening to all even read-only boot from live cd clients. So this is not a possible cause either.

The usual fix is to pick a display size other than the one it's using - i.e. force it to update the registry with new size information. Then reboot the guest. Then change display size back to where you want it to be, and reboot again.

The well known hardening issues with 4.3.14, and less so with 4.3.16, can affect graphics, but I've not heard of it causing these symptoms. Still, you can easily try downgrading to 4.3.12 and report the results.

This fix doesn't change anything. As i said, going back to 4.3.12 fixes the issue. I can provide logs or registry entries if that helps.

@Oliver, do you also use it on Win7 x64? Maybe we have something in common. What video card and driver do you use, what antivirus? Mine are: GTX 550 Ti with forceware 314.22 and i use AVG 2015 (same issue with AVG 2014).

[OliverOne]

For the test I use Windows 7 32 bits and Nvidia GT 8600 + pilote 337.88. No antivirus installed.

[mpack]

As i said, going back to 4.3.12 fixes the issue.

Not having reliable data, I gave you a range of possible solutions, including a suggestion to revert to 4.3.12. So, I'm puzzled why your subsequent posts adopt an adversarial tone, and an implication that reverting to 4.3.12 was despite my advice?

[wroot]

Because i said that in the first post. And Oliver's first post was clear enough to make the conclusion that downgrading to 4.3.12 fixed the issue.

Adversarial.. more like skeptical about the registry corruption cause. To me it looks more like some stuff in VM settings (file or registry) is in 4.3.12 format and 4.3.16 Host works differently. But as this doesn't affect all users, it maybe also be related to some specific stuff on my and Oliver's machine (OS, settings, drivers, etc.).

I have tried your proposed fix with changing the resolutions and rebooting and as i said it didn't change anything.

So, we are using 4.3.12 for now. But we want to be able to update eventually. I understand that the information is limited, so i ask what else can we provide to help pinpoint the cause (debug, config files, registry keys).

[Systech]

I have the same problem.
Host is Windows 7 Prof 64 bits
All guests
Videocard: Radeon X300/X550/X1050 series with latest drivers
I tried all posible settings for resolutions and screem modes but nothing helps
Back to version 4.3.12 and all is ok again

[OliverOne]

Welcome to the club!

[mariolino]

Same here.

4.3.12 works 4.3.16 keeps resizing to one screen.

Windows 7, 3 screens attached to NVIDIA NVS 310

Tried to reinstall Guest additions many times, no difference.

I can try to resize the window to any size, but as soon as I stop the mouse movement, it goes back to a single screen.
It looks like the guest display is at the desired size, inside the host window, behind scrollbars, but using the scrollbars is a real pain.

[nut75]

Same problem (4.3.16) and same solution (reinstalling 4.3.12), but I have to add another strange behavior of the guest's window that could be related with this:
when I try to minimize the guest windows with RBTray (used to minimize window in the system tray instead of the task bar), I obtain the context menu and guest windows doesn't minimize.
RBTray worked well since VB 4.3.12.

My host PC: Intel Core2Duo 8400, Geforce 9600GT, Windows 7 x64

Bye

[EarthCrash]

exactly same problem. It maybe associated with windows registry.

[wroot]

FYI, i'm not using rbtray. I'm using Classic Shell though (a few settings for Windows Explorer).

[volkans80]

I am using clean Win7 x64 host and first installation of VirtualBox 4.3.16 r95972.
I tried WinXP and Win7 guests but same problem.