Hi and thanks for looking in.

PC Ugrade. Originally installed and running Windows 7 Home Edition on HP Pavillion Elite 140f.  8GB RAM.

Upgraded HD to SAMSUNG 850 EVO 1TB SSD and using Magician Software completed transferrance of OS without indicdent.

Over the years, have installed much and used as office work machine.  I have tax return preparation packages installed from 2009 forward and a number of different year versions of QuickBooks all still used in support of clients.  While applicablity of these annual packages diminishes every day, I wish to keep all of the Windows 7 installation and environment "as is" in the event I have to go back and do something.

Desired installation environment is a VMWARE WORKSTATION PRO 15 world where I can simultaneously run both Windows 10 and Windows 7 as stand alone instances.

My data drive is not contained on the same drive now running Windows 7.  I intend to allow Windows 10 & 7 access to the data drive so files are accessible when using either instance in a shared fashion.

Windows 7 is now contained in a 400 MB primary partition to which I boot.

I intend Windows 10 to be installed in a new 550 MB partition on the same SSD.

My question is this.

Is the existing Windows 7 installation 'mounted' so to speak in the VMWARE world as a separate instance running on its own partition or,

is the original installation actually moved onto the Windows 10 partition as a separate instance to be run there?

Do I create a dual boot environment?

cj

The issue is regarding the installation and use of VMWARE, W10 & W7.

First I suspect is a clean installation of W10 in the new partition.  Then VMWARE.

Then what?  What happens next?

Your info, configuring suggestions and advice appreciated.  thanks.

Application - VMWare Workstation 12 Player

Version - Build Number: 5813279 (latest version)

A couple of days ago, Windows 10 installed the Fall Creators Update on my PC.  Since then VMWare Player throws an error every time I attempt to Power On the VM.

Here's the error:

Could not get snapshot information: Insufficient permission to access the file.

Module 'Snapshot' power on failed.

Failed to start the virtual machine.

Here's what's in the vmware.log.

2017-10-20T10:14:58.438-04:00| vmx| W115: FILE: FileLockCreateEntryDirectory stat failure on 'C:\Users\VM1234\Documents\Virtual Machines\WIN_7_PRO\WIN_7_PRO.vmsd.lck': Permission denied

2017-10-20T10:14:58.439-04:00| vmx| I125: SNAPSHOT: SnapshotConfigInfoReadEx: Failed to lock 'C:\Users\VM1234\Documents\Virtual Machines\WIN_7_PRO\WIN_7_PRO.vmsd': 'Insufficient permission to access the file'.

2017-10-20T10:14:58.439-04:00| vmx| I125: SNAPSHOT: SnapshotConfigInfoReadEx failed for file 'WIN_7_PRO.vmx': Insufficient permission to access the file (3)

2017-10-20T10:14:58.439-04:00| vmx| I125: Module 'Snapshot' power on failed.

I've given the all users administrative ("Full Control" ) rights to the C:\Users\VM1234\Documents\Virtual Machine folder.  I even copied the virtual machine folder to a root folder - same error.

Any insight would be greatly appreciated.  Thank you.

I found an answer at the following blog:

Dixin's Blog - Run Hyper-V and VMware virtual machines on Windows 10

Thanks Dixin!

Finally, after pulling my hair out, what is left of it, I found a work-around.  When you reboot, it will ask you two security questions, you must respond with F3 for both.  After rebooting Workstations works..  (For some reason, I had to take ownership on one of my VM's, because I couldn't get in to it.

TasP

When I  try to start a VM machine the vm machine crashes.  According to the error log the first problem is cannot find the config.ini file.  It looks in the wrong directory. 

There is a config configuration setting file in Program Data/VmWare/Vm Workstation directory

According to the log, the program is looking for the config.ini file  in Program Data/VmWare/VmWare player directory which does not have the config.ini file

What do I do?  Thanks.

Last week the final Windows 10 1903 was released via MSDN for developers. Needless to say, many of us are upgrading to test / develop with that new feature update.

I've had to migrate all my VMs to Hyper-V in order to be productive but I really prefer VMware Workstation.

Any estimated timeframe for getting an update that works with the new feature update?

From VMware VMware Knowledge Base , open-vm-tools-desktop supports files drag_and_drop between Host and Guest. But partial success.

1. Host bare metal machine installs a RHEL7.5 and installs a Linux VMware Workstation Pro 15.0.4.

2. Create a VM with RHEL7.6 in this VMware Workstaion, enable its "drag and drop" and "copy and paste".

3. Boot this VM successfully.

4. Drag a file from a Host folder to Guest VM desktop, it works well.

5. Plan to drag a file from a Guest folder to Host desktop, but it fails.

6. From /tmp/VMwareDnD in Host, has built the fCQf65 folder, it is link to /home/tester1/.cache/vmware/drag_and_drop/fCQf65. It is null.

7. NO idea to find somewhere stores useful log.

Thanks.

Hi All,

I installed VMware Workstation 15 Pro (version: 15.1.0 build-13591040) in Elementary OS Juno 5.0 (Linux 4.15.0-55-generic, GTK+ 3.22.30) and also connected my ESXi Server to the VMware workstation.

The ESXi virtual machine is running but its console window in the VMware workstation shows a black screen with VMware logo and "Waiting for connection".

Appreciate any help/suggestion.

Thank you.

Raj

This has been brought up several times before...

https://communities.vmware.com/thread/606608

https://communities.vmware.com/thread/602468

To name a couple. It was mentioned that the next release of Workstation 15 Pro would resolve. The latest release is 15.1.0 build-13591040 (released on 05/14/2019), which is what I have installed. I have 3 Guests... 1) Windows 10 LTSB, 2) Windows 10 Pro, 3) Windows 7 Ultimate. They all have the same behavior. I've made several attempts at changing VMware Host settings to no avail.

When working in Guest, I commonly use keyboard shortcuts. I use ALT-F4 to close Windows almost exclusively. Why waste time trying to click on the X when I simple key press will work? Well, this results in VMware Workstation completely shutting down. Typically without warning. Sometimes (and I'm not sure what warrants the change) it will warn me that Guests are still running. I have not changed the settings for this except for testing... the inconsistent behavior is consistent across settings.

Another annoying side effect of this glitch is that an ALT-TAB, which I use nearly as much as ALT-F4, puts the ALT key in "phantom pressed mode" for the Guest. I have to press ALT in the Guest before I accidently hit some other key that results in an undesired ALT-key function.

Thanks.

Hello,

the usual app dialogs are way too large on a 3 Monitor system.

The dialog comes up with 7832x129 pixels

     Monitor 2 is a 4K Monitor, but set to 2560x1440 / 100 %

     Monitor 1 is a 4K Monitor,  3840x2160 / 100 % ( Main Display )

     Monitor 3 is a 4K Monitor, but set to 2560x1440 / 100 %

I'm running Windows 10, latest patch level, VmWare 15.0.2 build-10952284

Any ideas how to fix this?

Hi

While installing VMware-workstation-full-15.0.4-12990004 i am getting stuck long at the stage of VM virtual adapter installation process.

while parallely checking device manager i found the CODE31 error- windows cannot load the driver.

After installation of VM workstation after long time,the VM adapter which was showing error in device manager got disappeared.

Need assistance in resolving the issue.

thanks

i was searching trying to solve this problem but nothing, the problem is that i cant copy any file from the guest and paste in the host.

I try to uninstall the vmware tools and install it again and nothing, reinstall vmware tools and nothing.

it happens when i try to copy text or files, any text and any size/type of files.

but, when i try to copy any file/text from de host to the guest it copy in the VM.

it is a problem of my host? vmwaretools? vmware workstation?

Host: Windows 7 64bits

Guest 1: Windows 7 64bits

Guest 2: Windows XP.

Is there a way to get the automatic bridging settings window to show the network card names that I set and not the names displayed in the device manager?

The device manager (and the virtual network editor) lists the network cards with almost identical names, the only difference being a number at the end. At Windows' network connections window I set different names to make it easier to distinguish the nic's, but VMware Workstation isn't using those names.

I am attempting to install VMware-Workstation-Full-14.1.3-9474260.x86_64.bundle on my freshly updated Ubuntu 18.04 system. I am running the installer from my Downloads directory.

When I run the installer, it gathers some information, then runs for a bit, then asks me if I want to keep the configuration data, then rolls back and says the installation failed.

When the installer first starts up, I see the following warnings...

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-installer.py:8436): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

Then the installer starts up and appears to work fine, until it fails and rolls back the installation.

I tried the installation in console mode using the --console switch, and like with the graphical installer, it stops before it is finished and says, "Deconfiguring". then asks if I want to save my configuration files. Then fails...

All configuration information is about to be removed. Do you wish to

keep your configuration files? [yes]:

Uninstalling VMware Installer 2.1.0

    Deconfiguring...

[######################################################################] 100%

Installation was unsuccessful.

I have checked the libcanberra-gtx-module and am told by apt that it is the most current version. Same with the Murrine files.

Any ideas?

I have looked through all the existing posts and have not been able to find any solutions -- VMWare is crashing every time I try and clone a VM.

I have attached the log file, the dmp file, and the collected support info.

Here's the errors from the log:

2019-08-06T13:09:40.268-04:00| vthread-9| I125: Msg_Post: Error

2019-08-06T13:09:40.268-04:00| vthread-9| I125: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vthread-9)

2019-08-06T13:09:40.268-04:00| vthread-9| I125+ VERIFY bora\lib\disklib\sparseUtil.c:1245

2019-08-06T13:09:40.268-04:00| vthread-9| I125: [msg.panic.haveLog] A log file is available in "C:\Users\cgibb\AppData\Local\Temp\vmware-cgibb\vmware-ui-11796.log". 

2019-08-06T13:09:40.268-04:00| vthread-9| I125: [msg.panic.requestSupport.withoutLog] You can request support. 

2019-08-06T13:09:40.268-04:00| vthread-9| I125: [msg.panic.requestSupport.vmSupport.windowsOrLinux]

2019-08-06T13:09:40.268-04:00| vthread-9| I125+ To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.

2019-08-06T13:09:40.268-04:00| vthread-9| I125+ You can also run the "vm-support" script in the Workstation folder directly.

2019-08-06T13:09:40.269-04:00| vthread-9| I125: [msg.panic.response] We will respond on the basis of your support entitlement.

After configuring the networks in Virtual Network Editor such that the 'Type' is 'Host-only' and clicking on 'Apply', it takes a couple of minutes for the configuration changes to be applied. But it immediately automatically changes to 'Custom' as shown below. Tried multiple times. What could be the reason for that? (Version: 14.0.0 build-6661328)

Hi

I am using Workstation Pro to connect to a virtual machine which is running on a local esxi server. So far no problems

Now I wanted to set up Workstation Pro to be able to connect from a different location, outside the local network. Which ports need to be forwarded in order to get this working?

Thank you!

I'm using Workstation 14 Player and it's popping out the window:

"error while powering on: Unable to find the VMX binary 'C:\Program Files (x86)\VMware\VMware PLayer\vmware.exe'.

Author :

URL : http:////docs.vmware.com/en/VMware-Workstation-Pro/15.0/com.vmware.ws.using.doc/GUID-88DEDB12-D1C6-4D99-80B9-DA8899081E72.html

Topic Name : Assigning IP Addresses in a Bridged Networking Environment

Publication Name : Using VMware Workstation Pro

Product/Version : VMware Workstation Pro/15.0

Question :

I recently upgraded from VMware Workstation Player to Pro. On player, under Network Adapter Settings, when the network connection was set to Bridged I was able to configure adapters. With Pro I do not see a way to do that now. How can I configure specific adapters to use from the base machine?

I am running Vmware Workstation 14.5 on a Linux box with a Windows 10 VM. I’ve connected my laptop to an external 25-inch monitor. The Linux desktop comes up full-size and fills the monitor screen. But the VM only comes up looking like the laptop screen size, and I cannot figure out how to get it to expand to fill the monitor screen. I have tried the “usual suspects,” both in the Windows settings and in the Linux settings. I’d be very grateful for any suggestions.

I Have a unique issue with Windows 10 and the latest Workstation Pro 15, I have a USB keyboard that supports a Firmware download mode both within Linux and for Windows, to build the firmware Linux is needed so I usually use a copy of Debian and run it in the VM, when it comes time to flash the built firmware onto the keyboard I have to put the keyboard itself into a firmware update mode, windows sees it as a Bossa Programming Port (COM3) the keyboard has a SAMD51j18a MCU and Linux usually sees the the keyboard (when in firmware mode) as /dev/ttyACM0 or /dev/ttyUSB .. anyway I'm uncertain if this belongs to a windows driver or vmware issue but in the  past i'd start the firmware mode and vmware would recognize the device and forward it to Linux, now when i go into firmware mode windows will make the connect/disconnect noise, VMWare will ask if I want to connect to the Host or Debian VM, after picking Debian, the icon shows up as connected but Linux itself never sees the device, this exact setup including the Linux build worked about a week ago, windows did an update now I can't get this to work, I can provide further technical details as well as gather any logs if needed, just wondering how to fix this, i have looked at windows device manager, tried to track down the driver used in vmware that handles USB devices all to not here, any advise or help would be much appreciated, I even went as far as downloading the latest copy of windows installed it fresh as well as the latest VMware pro directly off vmware to ensure nothing was corrupted, drivers, registry setting or files used all yielding the same result, the USB "connects" im prompted to attach keyboard to running vm machine but Linux no longer sees the device (only) while in firmware mode, while its acting like a keyboard it works as expected