VMware Communities
gantzm
Enthusiast
Enthusiast

VMWare Workstation 14 Pro pops out of full screen mode.

I've upgraded from Workstation 12 to 14.  Everything seems to be fine except for one detail.

Here is what happens:

1) I start up a VM, or two.

2) I full screen the VM, or both.  (Multiple monitors)

3) After a few minutes the VMs pop out of full screen mode and revert to a non maximized window.

4) If I full screen the VMs they seem to stay there.

The exception is:

1) Start VM and full screen it, pops out, full screen again.

2) Start another VM and full screen it.

3) Again, after several minutes both pop out of full screen.

4) Full screen everything and seems to be OK.

Host OS: Ubuntu 16.04.3 LTS

I'm not sure what other info to add.  The displays never get garbled or anything, nothing else malfunctions.

Any help would be appreciated.

Message was edited by: gantzm Fixed a typo in the title.

0 Kudos
8 Replies
Banjo4Boys
Contributor
Contributor

I can confirm the same problem.

Host OS: Linux Mint 18.3 64 bit.

0 Kudos
Banjo4Boys
Contributor
Contributor

Just updated to version 14.1.0 build-7370693 and it still got this bug - please solve it, thanks.

0 Kudos
gtrxcb
Contributor
Contributor

I am also running into this issue.  The resolution changes seem to happen at random as I have not yet found any pattern, and the logs do not show any errors that I have found as of yet.

Host: Ubuntu 16.04.3

Guest: Any (Ubuntu, RHEL/Centos, Fedora, Win7k, Win10k, etc...)

Vmware Workstation: 14.0.0 build-6661328 and 14.1.0 build-7370693

0 Kudos
Banjo4Boys
Contributor
Contributor

One more update v14.1.1 build-7528167 and still NOT solved Smiley Sad.

0 Kudos
MikeStutzzzz
Contributor
Contributor

Same issue here... (Virtualbox doesn't have this issue)

0 Kudos
PaulHanson
Contributor
Contributor

I have the same issue.

Workstation 14.1.1 build-7528167

Host OS: Ubuntu 16.04.4 LTS

0 Kudos
Banjo4Boys
Contributor
Contributor

Hi VMware, we are still waiting for an update solving this bug.

0 Kudos
Banjo4Boys
Contributor
Contributor

Yes, with v14.1.2 build-8497320 this bug has been solved, thanks.

0 Kudos