Hi, we have vm workstation version 12, when we tried to connect it to nets-tic ZTE, the vm get freeze, only when disconnect it it back to work. any suggestion?

My PC is Windows 10 64bit.  My VMWare is running XP PRO 32Bit.  VMWare is version 15.1.0 build 13590040. When in VMWare and I select Start,and then shut down, I get the hour glass and it stays there forever.  I have to do a hard reboot.  In the end I have to go to "Task Manager" and stop the application.

What can I do the fix this?

Hello, can you guys please update VMware workstation to work with the new windows 10 1903 update because when you try to open a VM it just hangs and it doesn't open, sometimes it does but most times it doesn't open at all.

I've been going round on this for hours. Hoping someone can help...

I had 15.0 working on 18.04. Upgraded to 19.04. 15.0 won't run, found out there is now 15.1 so I upgraded (actually un-installed and re-installed several times).

I got it to run at first, but there are no network interfaces and any attempt to connect the network interfaces produces the error:

Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'.

Sure enough there are no /dev/vmnet* devices. So I do the MOK stuff that I had to do to get the /dev/vm* devices to appear (under 15.0) in this:

sudo /usr/src/linux-headers-`uname -r`/scripts/sign-file sha256 ./MOK.priv ./MOK.der  $(modinfo -n vmmon)
sudo /usr/src/linux-headers-`uname -r`/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vmnet)
sudo insmod $(modinfo -n vmmon)
sudo insmod $(modinfo -n vmnet)

After a reboot, /dev/vm* looks about right:

crw------- 1 root root  10, 165 2019-07-05 11:39:37 /dev/vmmon
crw-rw-rw- 1 root root  10,  52 2019-07-05 11:39:37 /dev/vmci
crw------- 1 root root 119,   0 2019-07-05 11:39:37 /dev/vmnet0
crw------- 1 root root 119,   1 2019-07-05 11:39:38 /dev/vmnet1
crw------- 1 root root 119,   8 2019-07-05 11:39:38 /dev/vmnet8

So I run 'vmware' from the command line, and this pops up:

Before you can run VMware, several modules must be compiled and loaded into the running kernel.

Click 'Install', and enter my password when prompted. The window goes away and ... nothing. Running 'vmware' again just does the same thing.

Looking in /tmp/vmware-michael/vmware-10027.log:

2019-07-05T12:16:47.299-05:00| host-10027| I125: Log for VMware Workstation pid=10027 version=15.1.0 build=build-13591040 option=Release
2019-07-05T12:16:47.299-05:00| host-10027| I125: The process is 64-bit.
2019-07-05T12:16:47.299-05:00| host-10027| I125: Host codepage=UTF-8 encoding=UTF-8
2019-07-05T12:16:47.299-05:00| host-10027| I125: Host is Linux 5.0.0-20-generic Ubuntu 19.04
2019-07-05T12:16:47.298-05:00| host-10027| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2019-07-05T12:16:47.298-05:00| host-10027| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2019-07-05T12:16:47.298-05:00| host-10027| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2019-07-05T12:16:47.298-05:00| host-10027| I125: DictionaryLoad: Cannot open file "/home/michael/.vmware/config": No such file or directory.
2019-07-05T12:16:47.298-05:00| host-10027| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/michael/.vmware/config": No such file or directory.
2019-07-05T12:16:47.298-05:00| host-10027| I125: PREF Optional preferences file not found at /home/michael/.vmware/config. Using default values.
2019-07-05T12:16:47.327-05:00| host-10027| W115: Logging to /tmp/vmware-michael/vmware-10027.log
2019-07-05T12:16:47.339-05:00| host-10027| I125: Obtaining info using the running kernel.
2019-07-05T12:16:47.339-05:00| host-10027| I125: Created new pathsHash.
2019-07-05T12:16:47.339-05:00| host-10027| I125: Setting header path for 5.0.0-20-generic to "/lib/modules/5.0.0-20-generic/build/include".
2019-07-05T12:16:47.339-05:00| host-10027| I125: Validating path "/lib/modules/5.0.0-20-generic/build/include" for kernel release "5.0.0-20-generic".
2019-07-05T12:16:47.339-05:00| host-10027| I125: using /usr/bin/gcc-8 for preprocess check
2019-07-05T12:16:47.343-05:00| host-10027| I125: Preprocessed UTS_RELEASE, got value "5.0.0-20-generic".
2019-07-05T12:16:47.343-05:00| host-10027| I125: The header path "/lib/modules/5.0.0-20-generic/build/include" for the kernel "5.0.0-20-generic" is valid.  Whoohoo!
2019-07-05T12:16:47.491-05:00| host-10027| I125: found symbol version file /lib/modules/5.0.0-20-generic/build/Module.symvers
2019-07-05T12:16:47.491-05:00| host-10027| I125: Reading symbol versions from /lib/modules/5.0.0-20-generic/build/Module.symvers.
2019-07-05T12:16:47.508-05:00| host-10027| I125: Read 23240 symbol versions
2019-07-05T12:16:47.509-05:00| host-10027| I125: Reading in info for the vmmon module.
2019-07-05T12:16:47.509-05:00| host-10027| I125: Reading in info for the vmnet module.
2019-07-05T12:16:47.509-05:00| host-10027| I125: Reading in info for the vmci module.
2019-07-05T12:16:47.509-05:00| host-10027| I125: Reading in info for the vsock module.
2019-07-05T12:16:47.509-05:00| host-10027| I125: Setting vsock to depend on vmci.
2019-07-05T12:16:47.509-05:00| host-10027| I125: Invoking modinfo on "vmmon".
2019-07-05T12:16:47.510-05:00| host-10027| I125: "/sbin/modinfo" exited with status 256.
2019-07-05T12:16:47.510-05:00| host-10027| I125: Invoking modinfo on "vmnet".
2019-07-05T12:16:47.512-05:00| host-10027| I125: "/sbin/modinfo" exited with status 256.
2019-07-05T12:16:47.512-05:00| host-10027| I125: Invoking modinfo on "vmci".
2019-07-05T12:16:47.513-05:00| host-10027| I125: "/sbin/modinfo" exited with status 256.
2019-07-05T12:16:47.513-05:00| host-10027| I125: Invoking modinfo on "vsock".
2019-07-05T12:16:47.515-05:00| host-10027| I125: "/sbin/modinfo" exited with status 0.
2019-07-05T12:16:47.527-05:00| host-10027| I125: to be installed: vmmon status: 2
2019-07-05T12:16:47.527-05:00| host-10027| I125: to be installed: vmnet status: 2
2019-07-05T12:16:47.539-05:00| host-10027| I125: Obtaining info using the running kernel.
2019-07-05T12:16:47.539-05:00| host-10027| I125: Setting header path for 5.0.0-20-generic to "/lib/modules/5.0.0-20-generic/build/include".
2019-07-05T12:16:47.539-05:00| host-10027| I125: Validating path "/lib/modules/5.0.0-20-generic/build/include" for kernel release "5.0.0-20-generic".
2019-07-05T12:16:47.539-05:00| host-10027| I125: using /usr/bin/gcc-8 for preprocess check
2019-07-05T12:16:47.542-05:00| host-10027| I125: Preprocessed UTS_RELEASE, got value "5.0.0-20-generic".
2019-07-05T12:16:47.542-05:00| host-10027| I125: The header path "/lib/modules/5.0.0-20-generic/build/include" for the kernel "5.0.0-20-generic" is valid.  Whoohoo!
2019-07-05T12:16:47.688-05:00| host-10027| I125: found symbol version file /lib/modules/5.0.0-20-generic/build/Module.symvers
2019-07-05T12:16:47.689-05:00| host-10027| I125: Reading symbol versions from /lib/modules/5.0.0-20-generic/build/Module.symvers.
2019-07-05T12:16:47.705-05:00| host-10027| I125: Read 23240 symbol versions
2019-07-05T12:16:47.705-05:00| host-10027| I125: Kernel header path retrieved from FileEntry: /lib/modules/5.0.0-20-generic/build/include
2019-07-05T12:16:47.705-05:00| host-10027| I125: Update kernel header path to /lib/modules/5.0.0-20-generic/build/include
2019-07-05T12:16:47.705-05:00| host-10027| I125: Validating path "/lib/modules/5.0.0-20-generic/build/include" for kernel release "5.0.0-20-generic".
2019-07-05T12:16:47.705-05:00| host-10027| I125: using /usr/bin/gcc-8 for preprocess check
2019-07-05T12:16:47.709-05:00| host-10027| I125: Preprocessed UTS_RELEASE, got value "5.0.0-20-generic".
2019-07-05T12:16:47.709-05:00| host-10027| I125: The header path "/lib/modules/5.0.0-20-generic/build/include" for the kernel "5.0.0-20-generic" is valid.  Whoohoo!
2019-07-05T12:16:47.710-05:00| host-10027| I125: Found compiler at "/usr/bin/gcc"
2019-07-05T12:16:47.711-05:00| host-10027| I125: Got gcc version "8".
2019-07-05T12:16:47.711-05:00| host-10027| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-07-05T12:16:47.712-05:00| host-10027| I125: Got gcc version "8".
2019-07-05T12:16:47.712-05:00| host-10027| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-07-05T12:16:47.714-05:00| host-10027| I125: Trying to find a suitable PBM set for kernel "5.0.0-20-generic".
2019-07-05T12:16:47.714-05:00| host-10027| I125: No matching PBM set was found for kernel "5.0.0-20-generic".
2019-07-05T12:16:47.714-05:00| host-10027| I125: The GCC version matches the kernel GCC minor version like a glove.
2019-07-05T12:16:47.714-05:00| host-10027| I125: Validating path "/lib/modules/5.0.0-20-generic/build/include" for kernel release "5.0.0-20-generic".
2019-07-05T12:16:47.714-05:00| host-10027| I125: using /usr/bin/gcc-8 for preprocess check
2019-07-05T12:16:47.718-05:00| host-10027| I125: Preprocessed UTS_RELEASE, got value "5.0.0-20-generic".
2019-07-05T12:16:47.718-05:00| host-10027| I125: The header path "/lib/modules/5.0.0-20-generic/build/include" for the kernel "5.0.0-20-generic" is valid.  Whoohoo!

I can't spot any real error in there.

I'm stuck. Can someone coach me on how to get 15.1 to run on Ubuntu 19.04. Thanks.

Hi,

I want to create an existing Win7 Installation

( on a existing Harddisk 1 )

as a VM Ware

into a new Win 10 Installation ( on a new second HardDisk 2 )

on my NoteBook.

So it should be a new Win10 Installation

with concurrent my old Win7 in a VMWare Enviroment.

In which way / steps it is possible and

what kind of VM Ware Tools I need ?

Author :

URL : http:////docs.vmware.com/en/VMware-Workstation-Pro/15.0/com.vmware.ws.using.doc/GUID-41311258-4AAD-42B9-B0DE-CE7457298BFA.html

Topic Name : Prepare for an Upgrade

Publication Name : Using VMware Workstation Pro

Product/Version : VMware Workstation Pro/15.0

Question :

testing

Dear Community Guru's.

I've found posts as old as 7 years old referring to this issue, and I'm having the exact problem now in 2019. I get the errors below in the event viewer each time I plug in our out a USB device. And also at random times ( without actually plugging in anything.)

I'm running VMware Workstation 15 pro, latest version as of today ( 15.0.2 build-10952284 ), on an ASUS ROG GL702V Notebook, on Windows 10 64 bits latest build (17763).

Reading in ASUS' forums, the only solution that actually works is to disable the "VMWare USB Arbitration Service" , but that is not a real solution since it disables the possibility to attach USB devices to VM's.

Any ideas/suggestions?

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\PnpManager).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32111</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\PnpManager</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

 

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\nxusbh).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32110</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\nxusbh</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

 

Log Name:      System

Source:        hcmon

Date:          2/3/2019 11:01:33 PM

Event ID:      0

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      ASUS

Description:

Detected unrecognized USB driver (\Driver\nxusbf).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="hcmon" />

    <EventID Qualifiers="32768">0</EventID>

    <Level>3</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-02-04T02:01:33.388210900Z" />

    <EventRecordID>32109</EventRecordID>

    <Channel>System</Channel>

    <Computer>ASUS</Computer>

    <Security />

  </System>

  <EventData>

    <Data>\Device\hcmon</Data>

    <Data>\Driver\nxusbf</Data>

    <Binary>00000000020028000000000000000080000000000000000000000000000000000000000000000000</Binary>

  </EventData>

</Event>

 

In VMWare Fusion there is the ability to add notes to a VM which I find especially useful to record things like passwords and such.

I have been unable to find any such feature.

In Ubuntu 18.04, in the GNOME shell, when a different keyboard layout is selected than the default of the OS, scrolling in Windows guests (Linux guests not tested) is erratic. This results in randomly scrolling up or down when the mouse is moved in the VM in some scrollable panes, such as the start menu. This occurs on all guests, including those in an ESXi cluster, and even in the installer of the guest OS. This lead me to believe this is a host-guest interaction issue, and unrelated to the VM itself.

I have narrowed this problem down to the keyboard layout selector in the upper right corner. It only occurs in the GNOME shell, which is the default in Ubuntu 18.04, and can be reproduced across several systems using VMware Workstation for Linux 14.1.2. You can reproduce this issue as follows:

1. Install Ubuntu 18.04 as host OS

2. Make sure you login using the GNOME shell (Unity works as expected)

3. Add seven different input methods (one additional would be fine, but we are testing here). It does not matter which exactly you pick

4. Start up a Windows 10 guest OS (again, does not matter, but for testing purposes this is fine)

5. In the Guest OS, go to the Start menu, and try to scroll in the 'All apps' section (not all scrolling is broken, but the start menu is)

When the first option in the keyboard layout selector is chosen, this works as expected.

When the second option in the keyboard layout selector is chosen, when the mouse is scrolled or moved, the menu will scroll UP immediately. Scrolling down using keyboard works, but when the mouse is moved again, it will scroll up immediately.

When the third option in the keyboard layout selector is chosen, the menu will scroll DOWN immediately.

This will repeat: when the fourth option is chosen, it works as expected. The fifth option will scroll UP. The sixth option will scroll DOWN. The seventh option will work as expected, etc.

The workaround is simple: simply set the input selector to the first option when erratic scrolling occurs, but I believe this bizarre interaction bug should be fixed.

Also posting it here in the case someone else encounters this issue.

I've upgraded from workstation Pro V12 to V15 (As windows 10 wouldn't update with version 12!)

Upgrade all went fine but now when I try to access any shared VM on ESXI server I get the error - Unable to connect to the MKS: Internal error

Attached Here the log from a VM

Anything else to try?

Moderator note: Moved pasted log content into an attachment.

Hi all,

I downloaded the Vmware workstation pro 15 and installed it on my computer (Win 10), but I found the computer gets stuck when I try to create a new virtual machine. I have tried several times but the problem always occurs. Is it a bug?

Je suis sous FEDORA 30 et WORKSTATION PRO 15.1.0 ne tourne pas sur ma Distribution...!!!???

Hi,

I'm having an intermittent issue when attaching Huawei mifi devices to my Windows 7 VM's
using Vmware Workstation 15.

Most of time it works fine and the mifi device appears and works with the vm, other times the vm
freezes and cannot be shutdown via the vmware workstation menu.

The only way I've been able to free up the vm again is to restart the host, which is a pain to do
several times a day as I have a host of apps and other vm's working fine.

I have several mifi devices and they all seem to work ok most of the time with the vm's, but
they've all caused the crash at some point. I've tried using different USB
Ports on the PC and a TPLINK USB hub - same intermittent issue.

What usually happens is thje mifi initially connects to the host pc, then I manually select the
connect to vm option. The driver starts installing in the vm, then it freezes.

After googling around it seems I just need to kill off the vmware-vmx.exe process. The
issue is I cannot seem to kill it! Nothing happens when using Task Manager -
just remains there. Tried elevated command prompt, trying to kill using PID an
name. Same with elevated powershell. I can end the Workstation tasks, but when
I relaunch the app, the vm is still running in
a frozen state.

So, I'd be really grateful if someone could help me troubleshoot and
resolve both or one of the following:

1. VM's are sometimes crashing when I attach the Huawei mifi devices
2. I cannot kill the vmware-vmx.exe without having to restart the host each time it happens

Host PC:

Windows 10 Pro

Asus  ROG STRIX X299

I9-9980XE

64GB Corsair Vengeance
DDR4 3000MHZ

Many thanks!

When I try to install the latest Windows 10 updates I get a warning message for the Windows 10 updates installer:

"VMWare Workstation Pro

This app can't run because it causes security or performance issues in Windows. A new version may be available. Check with your software provider for an updated app that runs on this version of Windows."

Has anyone else encountered this and does anyone know if upgrading to the latest VMWare Workstation 15 will fix this issue?.

Thx

Is it a ok to have Multiple VM's with the same hard drive ID as the Host?  I have software that binds itself to the Host Hard Drive ID and want to utilize the same license on my VM's.

A native ESXi driver for the SVGA adapter that appears in a nested instance when 'Accelerate 3D graphics' is enabled to provide Xorg with OpenGL/Mesa acceleration in the same way an Nvidia/AMD/Intel driver does on a physical host.

Such a driver already exists for the SVGA adapter in Linux so this can’t be too difficult. If I had access to SDK/DDK's for ESXi I'd attempt it myself.

I understand this would never be supported but it would improve Horizon View test/demo scenarios and 3D acceleration also has some use at the console for DWM acceleration (if it's Windows, other window managers on other operating systems as well).

Сделать это через параметры VMXили через настройки графического адаптера в виртуально машине.

To do this through the parameters of the VMX or through the settings of the graphics card in the virtual machine.

Hi,

Allow virtual support of monitors. At the moment we are limited by only having the maximum number and resolution limited by the host.

For example if my host has 2 screens allow to to virtually create more then 2.

In addition allow me to simulate having a 4K monitor if my host does not have one.

Thanks,

Ward

Dear All,

This is my configuration:

Host:

  + Hardware: HP Z240 Tower Worktation

         Note:   enable Virtualization Technology( VTx),

                     enable Virtualization Technology for Directed I/O (Vtd)

  + OS: Windows 10 Pro 1709 (64 bit)

            Vmware workstation 15 Pro

            Note:    enable Virtualization engine

Guest:

+ OS: Windows 10 Pro 1903 (64 bit)  (UEFI / BIOS)

First, i setup "Browser_In_The_Box.5.2.2-r711.firefox.Archive.exe" in Guest OS. It is OK.

After that. I run "Browser in the Box" shortcut in the Desktop. I get error:

"A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware Workstation".

I try:

   + enable in BIOS Hp Z240: Virtualization Technology( VTx),

                                              Virtualization Technology for Directed I/O (Vtd)

   + install Guest OS in the both (UEFI/ BIOS)

   + seach google to find solution

   + enable all Virtualization engine of Vmware workstation 15 Pro

But, It is still error.

Do you have any solution ?

Please help me.Thanks!

During the installation of Ubuntu Server 18.04.3 LTS on the MacBook Pro and after the first reboot, I got the following message:

So, how do i fix this?

Thanks