the screen/display/monitor is super broken on linux host

have tried player 14 and 15 but got the same glitch artifact

the host has nvidia 418 driver installed on it dont know if that might a problem

workstation player is not working even showing the bios screen but as the screen shot shows the thumbnail shows the vm is actually running

try to disable/reenable the accelerate 3d graphics option and nothing change

Selecting Accelerate 3D graphics bugs the program. No matter what i do afterwards, an error pops up.Observation 2: This error wasn't happening on previous versions (15.0.2, 15.0.3, 15.0.4).

I do not know why but VMWare Workstation Player 15 is not supporting 64-bit virtual machines on a host machine with 64-bit Windows system. It installs into Program Files (x86) by default (I've already tried to switch to 64-bit Program Files, it installs but gives the same error). Other emulators work normally. As shown the photo is a core i3. And the installation file was downloaded from the official vmware website in 64-bit version. I believe that through a regedit file it might be possible to resolve.

Please consider it as a dumb question from a Non-IT guy who has just moved into IT. I am from India. I have an Acer Aspire Series 5 laptop. My laptop has both physical as well as a wireless lancard. I have installed VMWare Workstation 15 Player (trial edition). I have hosted a Windows Server 2008 R2 (trial edition) on this machine. Currently the host machine of my wireless lancard is accepting address from a DhcP server (my modem). My ultimate aim is to configure windows Server 2012 as a router and to use both Wireless and physical lancards to connect to two different subnets via this router. I have tried hard, and although it shows the physical lancard installed on my host machine, but somehow it is not accepting it as the 2nd lancard. even if I add a 2nd lancard and use "bridging" option to select the physical lancard from the list, it still goes to the wireless lancard and accept a new IP address from the DHCP server (or may be it is going by I am not being able to understand it). I would greatly appreciate it someone can explain how to add both wired and wireless lan card in virtual machine running on VMWare workstation Player 15. Since I am a dumb person, any step-by-step document would be of a great help. Many Thanks,. .

Real newbie here, so please be gentle.

Originally installed VMWare Workstation Player 15.0.4 running on Win10 a few weeks back, and then created Win7 VM guest, and installed VMWare Tools 10.3.5 in the Win7 VM.  All was fine.

Today I accepted the offer to upgrade VMWare to 15.1.0, and that went fine.

But now when I play the Win7 VM the system tray icon for VMTools has a yellow exclamation mark on it.  When I hover the mouse over it the message "VMWare Tools can be updated" is the flyout. But I thought the latest version of VMWare Tools was 10.3.5.  I certainly wasn't offered an option to upgrade VMWare Tools to a newer version, assuming there might be a newer version that matches 15.1.0 of VMWare itself.  I have no idea what the story it.

I have tried uninstalling VMWare Tools, re-starting Win7 VM, and then reinstalling the same 10.3.5 version. And not surprisingly the yellow exclamation mark is still there.

I have to admit, I have a great deal of difficulty navigating through the VMWare web site. I do not find it user-friendly.  Quite the opposite, to be honest, but maybe I'm just a beginner.  I cannot figure out how to find anything, or search for something, or how to even download the latest version of VMWare tools. Even trying to search this forum was non-intuitive, and I didn't find any "hits" that might have been helpful.  To be honest I can't even remember how I got the 10.3.5 download file in the first place but I certainly can't find it now, a few weeks later.

Can somebody please help me. Is this yellow exclamation mark normal or an indication of something I must do? And if I must do something, what is that?  And please provide me with URL links to whatever page I need to go to to get started, or whatever I need to download.

Any help would be much appreciated.

Note that my Win7 VM is working perfectly, so that's not something I'm asking for assistance with. I only want to address the "VMWare Tools can be updated" message and yellow exclamation mark.

Thanks in advance.

Hello,

I've just received a VMware workstation license from my school and I tried to download it and got this error.

I had VMware in the past but used IObit uninstaller to get rid of it and all the files. Any help would be very appreciated.

Liam

PRODUCT VERSION： VMware® Workstation 15 Player 15.1.0 build-13591040

HOST OS VERSION： 64-bit (x64) MS Windows 7 Home Premium with Service Pack 1 (Ukrainian)

ENDING (KEY) LINES FROM ONE OF THE LOGS (attached)：

I125: Msg_Post: Error

I125: [msg.log.error.unrecoverable] VMware Player unrecoverable error: (vmx)

I125+ VERIFY bora\lib\vmdb\wqpool.c:750

I125: [msg.panic.haveLog] A log file is available in "Q:\VMs\10188968-71731-2240\vmware.log". 

I125: [msg.panic.requestSupport.withoutLog] You can request support. 

I125: [msg.panic.requestSupport.vmSupport.vmx86]

I125+ To collect data to submit to VMware technical support, run "vm-support".

I125: [msg.panic.response] We will respond on the basis of your support entitlement.

I125: ----------------------------------------

I125: VmdbPipeStreamsOvlError Couldn't read: (109) The pipe has been ended.

I125: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (-32)

I125: VUIDialogDequeue: found 0 vmdb ui connections; canceling dialogs

I125: Exiting

The VMs were created several months ago (in one of the earlier Player builds), since when and up until some point had been working just fine...

Everything bad started at some day (perhaps few weeks ago), when I noticed that my Win7 and Win10 VMs stopped playing sound - they both started displaying the following error messages instead (from one of the attached logs):

I125: Msg_Post: Warning

I125: [msg.sound.stream.error.start.generic] Error starting sound stream.

I125: [msg.sound.stream.error.playback] Playback may not work.

I125: ----------------------------------------

E105: PANIC: VERIFY bora\lib\vmdb\wqpool.c:750

The fact of missing sound wasn't too crucial for me, so I was just ignoring this. Then, the first freeze happened, and since that moment such freezes happen with these VMs on a regular basis, even when I'm leaving them running untouched (in front and active or minimized, with some apps running inside or without - doesn't matter). Or everything might freeze on the black screen after the Guest OS shutting down. In any event, I then have to manually ForceKill vmplayer.exe and vmware-vmx.exe processes from the Task Manager, or it will be stuck in that half-frozen state for-ever.

I have the back-ups of these VMs in their initial states (when I'd just installed the Guest OSs from scratch), so I deleted all my current VMs, downloaded the latest VMware-Player installer (it was the last at the moment), completely uninstalled my previous Workstation installation (using Revo Uninstaller and clearing any found leftover) and re-installed it anew, then re-opened the VMs from those clean back-ups (without additionally installing anything new inside)... No avail.

What else might be possibly important is that my VMs are located on an external USB 2.0 drive, which is connected to my laptop using a USB-hub. I don't have enough space on my laptop's internal SSD, as well as don't need my VMs to be very fast, so for me it's pretty much OK.

I have two different USB-hubs: USB 3.0 7-Port Hub TP-Link UH720 (connected to the USB 3.0 laptop port) and USB 2.0 3-port Hub Edimax EU-4230 (connected to the USB 2.0 laptop port) - connecting using either of them doesn't alter the situation. I also tried to change my main external USB-drive itself by another hard-disk in a USB 2.0 enclosure - to no avail as well.

One of the curious moments is that at the same time my WinXP VMs (32-bit SP0 and 64-bit SP2), with similar configurations (including the VMs location on that same external drive), do play sound properly to this day, and as for the freezes - I don't remember anything similar happening with these. Though, it would be fair to say that I don't use them as often and for as long as my Win7 and Win10 ones. However, all my VMs were created almost simultaneously.

Another moment is that I made an experiment：

－ installed VirtualBox

－ created exactly same Win7 and Win10 VBox VMs, putting them on my initial (main) external USB-drive (and leaving my VMware VMs on that second HDD in an external enclosure), with as similar configurations as possible

－ connected both external USB-drives to the same USB-hub (UH720)

－ ran Win10 WMvare and Win10 VirtualBox VMs simultaneously

－ started exactly same actions within the VMs: both OSs were 1703 (Updated March 2017) and needed lots of updates, so I started updating them in the same way at the same time

Shortly (maybe not that much shortly, but still), WMvare Win10 froze, and VirtualBox Win10 keeps working without issues up till now (more than 24 hours have passed).

I even followed these guide to just in case uninstall the Intel® Rapid Storage Technology (Intel® RST) driver... No avail again.

So, how may I get rid of this VMplayer problem? Even under my conditions (such as VMs location on an external USB 2.0 drive), VMware works significantly faster than VirtualBox, but VirtualBox has no crashes.

Two Win10 logs are attached along with their respective dmps. You can also refer to the attached screenshot.

Regards,

Hi all,

I recently expanded the disk in the VM settings from 40 to 80gb. Now, it suddenly won't boot at all. Nothing happened in between those two steps. I expanded the disk then tried to boot and it failed.

I get this error:

The VMware Tools power-on script did not run successfully in this virtual machine. If you have configured a custom power-on script in this virtual machine, make sure that it contains no errors. You can also submit a support request to report this issue

I didn't configure any custom power-on scripts.

and the terminal shows the following errors:

[failed] Failed to start Create Volatile Files and Directories. See 'systemct1 status systemd-tmpfiles-setup.service' for details.

Starting update UTMP about System Boot/Shutdown...

then a bunch of [FAILED] Failed to start network name resolution.

I really have no clue what to try and can't find that file it's referencing anywhere. Any ideas would be a huge help.

Even if I could just get my files off of it, that's fine. I'm just concerned about a few things I don't have backed up.

-Seth

VMware Workstation 15 Player

Windows 10 host 1920X1080, Windows 98 SE Korean guest 1024X768

I added this line in preferences.ini

pref.autoFitFullScreen = "fitHostToGuest"

then at full screen mode I got upscaling. But like this

What could I try to correct this?

Is this VMware's intention? Or is it possible by tweaking preferences.ini, vmx file or config.ini?

Any helps appreciated.

added. Korean 103/106 keyboard not supported. can't change English to Korean (or vice versa). 14 Player with VMware tools an year ago didn't show this problem.

added. guest 640X480 full screen mode display

svga.maxWidth = "1024"     svga.maxHeight = "768"     svga.vramSize = "3145728"

changing these options in windows 98.vmx has no effect, have nothing with my problem.

pref.autoFit, pref.autoFitGuestToWindow lines in preferences.ini are not full screen option.

I guess full screen display field is forced to always follow guest resolution, so if I can fix that vmplayer full screen display field resolution to 1920X1080 (host resolution), this will be solved. but I don't know how.

This is all about vmplayer full screen mode configuration, not guest, I guess.

If this parameter is hidden hard (because of Pro version), I will quit and give up answer. So I want to know VMware's stance.

Or I hope someday they sell less expensive Workstation version with scaling function. Pro's too expensive to buy, just for 90s gaming nostalgia.

I know line pref.vmplayer.fullscreen.nobar = "TRUE"  , so this scaling problem is only left to use Player comfortably.

added. this message was in Workstation Pro group board 3 days. I didn't know this Player group board. It's my mistake.

I hope any response related. For 3 days there was none.

Can't find my physical DVD drive or mount an ISO.

Latest Workstation Pro version (15.1.0 build-13591040) on Win 10 Pro (v.10.0.17763.529).

VM is Win Me.

Forum and Google search reveals many similar issues, but I couldn't find an exact match.

Guest is linuxCNC (a Debian variant); Workstation Player 15.1  When I try to install VMWare Tools Player->Manage->Install VMWare Tools... I get a complaint about locked CD-ROM door.  Some instructions say to right click the CD-ROM icon and choose Eject.  My only choices are Disconnect and Settings...  I see no Eject option.

Hi Team,

I downloaded VMware-player-15.1 and ran VMware-player-15.1.0-13591040.exe file on windows 10 machine,
while installing it got stuck for about 15min and then manually ended vmware service through  windows task manager.
and tried to run VMware-player-15.1.0-13591040.exe again ,but got error (please refer image attached).

when i used VMware-player-14.1.7-12989993.exe got the same issue, ie installation got stuck for about 15 min. and was unable to proceed further

please help me in solving this issue.

Thanks

I am currently running the free download VMware Player V6.0.7 on a Dell laptop which has an O/S - Windows 10 Pro 64 bit. I am in the process of
upgrading to a new Dell Inspiron laptop. So, I'll need to download the free VMWare Player again. However I can not locate it.
I have found a free download for VMWare Workstation Player 15. A version for Windows and one for Linux.

Q1. FOR A FREE DOWNLOAD,  Is VMWare Workstation Player now the replacement for VMWare Player ?

Q2. Dumb as this question  may appear, since my O/S is Windows 10 Pro I assume I need to download the Windows version
    of this product if in fact this is the replacement for VMWare Player , correct ?

many thanks Brian

An attempt to run VMware Player 12.x on Linux Mint 18.3 said that something needed to be present in the kernel, and made an option to install it. However, it errored out, saying to check for further details in the log.

I've attached the log file; it attempts a make and reports failure.

How can I get Player running again?

As I found out VmWare Player v15.1 for Windows offers in VmWare machine settings buttons for defragmentation and compacting of Linux guestOS.

When was this feature introduced?

I remember times in the past when users have to enter some compact commands in guestOS terminal to achieve this.

Furthermore I observed that defragmentation does the jobs completely.

No further compact is needed.

Is this correct?

Matt

I have 64 bit VMware® Workstation 14 Player version 14.0.0 build-6661328 installed on Linux Mint 18.3 x64. My laptop is a Lenovo Ideapad z510 and I've made sure the virtual machine option in BIOS is enabled. The installation of VMware Player 14 on Mint was successful and VMware Player also opens without issues.

Whenever I choose "Create a New Virtual Machine", it lets me go thru all the appropriate steps. It allows me to pick an ISO and goes thru the full installation process without issues. VMware Player confirms that the virtual machine was installed successful and the virtual machine even boots fine after it's done with the initial installation.

However, the minute I shutdown the virtual machine, I can no longer open it again. It's not listed in the Home panel either. I've tried using the "Open a Virtual Machine" option, but nothing happens when I choose the vmx file.

I get the same symptom when using the ISO file of Kali Linux (kali-linux-2017.3-amd64.iso) and when using the virtual machine version of Kali Linux (kali-linux-2017.3-vm-amd64.ova)

Attached is a screen shot of the files found in the vmware folder (I believe these are for kali-linux-2017.3-vm-amd64.ova) . I've also included a screen shot of the empty Home panel.

Can someone please help? Don't understand why this is happening if all signs confirmed the virtual machine was installed.

Dear all,

After we updated one VM Windows 10 to the latest version 1903, every morning we had to restore the VM of 10 days back to get it working.

the issue is Windows 10 is not responding, when we log in to the ESXI see just black screen, even we reboot the Windows / Power off its tries to boot but after we see just black screen.

i dont know what causes this, other VM remains working.

we do have a Daily job of Veeam .

ESXI 6.7

Windows 10 1903 Hardware Version 13 / even updated to 14 nothings happens.

vMware tools 10.3.5.10430147

Thank you for your support

I have this virtual machine running ubuntu 18.04 server. I have worked on it a lot, and this problem infuriated me when I would no longer access my image after I shut it down and started it back up. This problem is very inconsistent, as when I make a virtual machine, this sometimes happens too, but not always. I made the VM from an ISO, installed a bunch of packages and interface things (confirmed that no packages caused the issue). Then I turned off the machine to go do something and came back to launch it again. After clicking play, it is just a black screen. It doesn't even boot. Normally it has a VMware logo that has a loading bar, but it's just black. Is there a way to recover this image? I am running VMware workstation player.

I can't figure out how to do this, and I'm sure it must be possible. So please, somebody, tell me the step-by-step process to accomplish what I know must be possible.

My host Win10 machine has three local drives, with multiple partitions on each drive. So the host machine has local drive letters C-M.  C is the Win10 system partition, and I realize I can't expect to access it as "C" within the Win7 VM guest.  But I at least would like to see D-M in the Win7 VM environment, as "local drives" with those letters.  Ideally they should just appear in My Computer of the Win7 VM as D-M, but I'll do whatever it takes to "map" them that way.

It's not a matter of just getting to the data on those partitions (i.e. drive letters). I can easily do that by MAP NETWORK DRIVE as D-M through NETWORK, since all of the drives on the host are genuinely visible through NETWORK in Windows Explorer, since the host machine itself shows up in NETWORK (as well as all the other desktops and laptops on my LAN, since I've got "bridged network" set so that I can see all the LAN devices within the Win7 VM).  So I know I can easily get to the host partitions with the identical drive letters D-M if only that would be acceptable to my need.  Unfortunately that method of getting drive letters D-M via MAP NETWORK DRIVE is unacceptable to Windows Media Center for "Record Storage", where only genuine true "local drives" are acceptable for recording, not mapped network drive locations.

So when I go into WMC -> Recorder storage, all I see is C, which is the virtual C provided by VMWare Workstation Player to the Win7 VM.  This partition is too small, and is not the drive letter I actually want to set as "recorder storage" target location. That drive is actually F.  So I need to get at least F (true F, from the host) available to Win7 VM as a "local drive" (ideally F).

How do I do this?  I can't use MAP NETWORK DRIVE. And there's no point in using "shared folders", because just getting to the data is not the goal. The goal is providing the drive letter to Win7 VM so that WMC sees it as a local drive, so that it appears usable for "Recorder Storage".

So, can somebody tell me: is this possible or not? Are you telling me the local drive letters of the host are NOT available as "local drive letters" to guests?  Or, if they are and I'm just a rookie who doesn't know how to make this happen, please let me know how to do it and/or point me to a VMWare FAQ document or forum thread or something which will provide me clear and appropriate instructions for what I need to do.

If it's possible, I'm sure it's quite easy... if only I knew the technique. But I'm a true rookie/newbie to VMWare, so any help for experienced gurus is much appreciated.

thanks in advance.

Hello,

I am using VMware-player-15.1.0-13591040 on Windows 10 host to install Ubuntu Linux 19_04.  I have no LEFT mouse click during and after installation. I had to painfully use  “tab” to get to the right “field” to do the install. The mouse pointer moved and focused correctly in the virtual machine, but left mouse click did nothing.  I have tried older versions (14.X, 13.X) of player and numerous Linux distros,  all had the same problem.  The same problem occurred with wireless or wired USB mouse, Bluetooth mouse, and built-in touch pad mouse.

I read many posting in numerous forums about uninstall and reinstall vmware tools to solve similar problems.  I managed to reinstall vmware tools one time using “tab” and the same no Left mouse click problem still there.  However, everything work fine with VMWare Workstation version.

Thank you for your help.