hello, i want to boot with my usb drive windows 10 installer from uefi mode  can someone help me with that i dont want change it to bios i want test it to uefi mode

I have a VmWare workstation client (W2K) that always shows as 25% processor usage in Task Manager on the host (4 core machine, so effectively 100% of one core), but shows as 1 or 2% processor usage in Task manager running on the client. What can I do to diagnose why this is happening and fix ? I have 5 or 6 other Vmware clients on this machine and none of those exhibit this behavior. I've tried all the normal uninstall, reinstall suggestions that VmWare make.

Hello everyone  ,

I'am having a problem that when i'm trying to install VMware WorkStation 15 Pro  on my Win8.1 64bit i got this error (Error "Setup cannot continue. The Microsoft Runtime DLL installer failed to complete installation) i tried so many solutions but its still the same problem.

hope to get help as soon as possible.

thank you all for your time.

Hello. 

I was running Workstation Pro 15.0.2 on a Windows 7 64-bit host with a Windows 7 64-bit guest, and I worked with VMware support to get a Logitech USB headset working properly on the guest.

After upgrading to 15.0.3, I could no longer log into the guest.  I repeatedly got "RPC Service Unavailable" error after entering the password.  I rolled back to a previously working snapshot, and I was able to login again.  The problem is, I cannot get any kind of reliable audio out of the guest now.  The headset is completely useless, but in addition to that, the basic audio from the sound card is choppy and "cut-off" many times.  Normal tones for incoming mail and other notifications are truncated.

It's off topic, but the VM seems to have general lag since the update (and resulting roll-back to a snapshot), too.

Is anyone else experiencing similar issues, or is it just me?

Hi Everyone -

Today I got notice that the 15.0.3 update had been released. In the process of installing it - I got the dreaded vminstallhcmon failed to install the hcmon driver error.

Scouring the web - I tried the suggestions:

- running installer as admin (though this shouldn't matter because the .msi automatically prompts for UAC elevation to admin)

- running install from elevated command prompt

- confirming that hcmon.inf nor hcmon.sys was not cashed in DRVSTORE or elsewhere on disk

- no devices in Device Manager in "Non Plug'n Play devices" - in fact the section doesn't exist (even after displaying hidden items)

from the vminst.log - it seems like the issue might be a revoked certificate on the hcmon.inf file?

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: BaseDriverManager::DifxApiLogCallback: hcmon (Difx): hcmon.inf: checking signature with catalog 'C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.cat' ...

2019-03-19T11:59:14.049-04:00| inst-build-10689111| E1: BaseDriverManager::DifxApiLogCallback: hcmon: Signature verification failed while checking integrity of driver package 'hcmon.inf' ('C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.inf').| winerror code 2148204812 (A certificate was explicitly revoked by its issuer.)

At this point I can't install even the previously available 15.0.2 - I get the same error

larger log section:

2019-03-19T11:59:13.635-04:00| inst-build-10689111| I1: VNLInstallLegacyInf: driverId:hcmon cmd:install hcmoninf args:5;Win7

2019-03-19T11:59:13.635-04:00| inst-build-10689111| I1: launching process for: install hcmoninf 5;Win7

2019-03-19T11:59:13.682-04:00| inst-build-10689111| I1: VNLSpawn64BitVnetlibTask: launched process: pid 7472 tid 4328

2019-03-19T11:59:13.682-04:00| inst-build-10689111| I1: VNLSpawn64BitVnetlibTask: Waiting for process, 0 loops

2019-03-19T11:59:13.901-04:00| inst-build-10689111| I1: VNLInstallLegacyInf: driverId:hcmon cmd:install hcmoninf args:5;Win7

2019-03-19T11:59:13.971-04:00| inst-build-10689111| E2: GetSpecificProductInstallPath: could not find product registry key

2019-03-19T11:59:13.971-04:00| inst-build-10689111| E2: GetSpecificProductInstallPath: could not find product registry key. Try the WoW path.

2019-03-19T11:59:13.971-04:00| inst-build-10689111| I2: Util_FileExistsW: Found "C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.inf"

2019-03-19T11:59:13.971-04:00| inst-build-10689111| I1: LegacyDriverManager::InstallDriver: Determining whether to install the hcmon driver

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I2: LoadSupportFiles: Successfully loaded C:\Program Files (x86)\Common Files\VMware\USB\x64\DIFXAPI.dll

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I2: LoadSupportFiles: Incremented refcount for module DIFXAPI.dll

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I1: DriverVersionInfo::ReadFromRegistry: Did not find info for hcmon driver

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I1: DInfo_GetDriverInfoFromInf: Got provider for inf: VMware, Inc.

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I2: DInfo_GetDriverInfoFromInf: Got catalog file for inf: hcmon.cat

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I2: DInfo_GetDriverInfoFromInf: Got class name for inf: USB

2019-03-19T11:59:13.986-04:00| inst-build-10689111| I2: DInfo_GetDriverInfoFromInf: Got date/version for inf: 08/28/2018,8.11.6.0

2019-03-19T11:59:14.033-04:00| inst-build-10689111| E1: DInfo_GetDriverInfoFromInf: driver C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.inf failed verification| winerror code 2148204812 (A certificate was explicitly revoked by its issuer.)

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverVersionInfo::IsSameAs: File versions don't match or older

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: BaseDriverManager::IsSameDriverAndPresent: Driver file versions don't match

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::EvalUpdateNeeded: Determined that hcmon has changed

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::EvalUpdateNeeded: Prior hcmon info:

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverVersionInfo::Print: Driver version (invalid) 0.0.0.0 is not WHQL (ca ver 0) inf ""

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::EvalUpdateNeeded: New hcmon info:

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverVersionInfo::Print: Driver version (valid) 8.11.6.0 is not WHQL (ca ver 4998961) inf ""

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I2: UnloadSupportFiles: Decremented refcount for module DIFXAPI.dll

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::InstallDriver: Uninstalling a prior version hcmon driver

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I2: LoadSupportFiles: Incremented refcount for module DIFXAPI.dll

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::UninstallDriverImpl: Uninstalling the hcmon driver

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverVersionInfo::ReadFromRegistry: Did not find info for hcmon driver

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverBaseInfo::ReadMultiszFromRegistry: No registry value vwdk.installers

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverInstallerInfo::SetMsiInstallerPresent: Set Msi installer: present

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::UninstallDriverImpl: Query if old style hcmon legacy driver is installed

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I2: Inst_QueryServiceRunningStatus: Attempting to query service: hcmon

2019-03-19T11:59:14.033-04:00| inst-build-10689111| E1: Inst_QueryServiceRunningStatus: Service could not be opened: ERROR_SERVICE_DOES_NOT_EXIST

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I2: UnloadSupportFiles: Decremented refcount for module DIFXAPI.dll

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: LegacyDriverManager::InstallDriverImpl: Installing new version of the hcmon driver

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverBaseInfo::ReadMultiszFromRegistry: No registry value vwdk.installers

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: DriverBaseInfo::DeleteFromRegistry: No info for driver hcmon to delete

2019-03-19T11:59:14.033-04:00| inst-build-10689111| I1: FindVMwareInSystemTrustedPubStore: didn't find certificate in system trusted publisher store

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I2: Util_IsTestSigningEnabled: TestSigning not enabled (no TESTSIGNING token)

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: DriverMgmt_TryAddVMwareCerts: Automated cert installation requires test-signing mode

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: Util_GetKeyValueDWORD: Cannot query key value HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\hcmon\DeleteFlag| winerror code 2 (The system cannot find the file specified.)

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: BaseDriverManager::DifxApiLogCallback: hcmon (Difx): ENTER:  DriverPackageInstallW

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: BaseDriverManager::DifxApiLogCallback: hcmon (Difx): hcmon.inf: checking signature with catalog 'C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.cat' ...

2019-03-19T11:59:14.049-04:00| inst-build-10689111| E1: BaseDriverManager::DifxApiLogCallback: hcmon: Signature verification failed while checking integrity of driver package 'hcmon.inf' ('C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.inf').| winerror code 2148204812 (A certificate was explicitly revoked by its issuer.)

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I1: BaseDriverManager::DifxApiLogCallback: hcmon (Difx): RETURN: DriverPackageInstallW  (0x800B0100)

2019-03-19T11:59:14.049-04:00| inst-build-10689111| E1: LegacyDriverManager::InstallDriverImpl: Install of hcmon failed with| winerror code 2148204800 (No signature was present in the subject.)

2019-03-19T11:59:14.049-04:00| inst-build-10689111| E1: LegacyDriverManager::InstallDriverImpl: Cannot locate installed INF location for hcmon of C:\Program Files\Common Files\VMware\Drivers\hcmon\Win7\hcmon.inf| winerror code 3758097154

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I2: UnloadSupportFiles: Closed module handle for DIFXAPI.dll

2019-03-19T11:59:14.049-04:00| inst-build-10689111| I2: UnloadSupportFiles: Module DIFXAPI.dll wasn't unloaded

2019-03-19T11:59:14.064-04:00| inst-build-10689111| I1: ParseCommand: operation: successful

2019-03-19T11:59:14.064-04:00| inst-build-10689111| I1: VNLSpawn64BitVnetlibTask: Done waiting for process, code 0

2019-03-19T11:59:14.064-04:00| inst-build-10689111| I2: VNLSpawn64BitVnetlibTask: process exit code 4

2019-03-19T11:59:14.064-04:00| inst-build-10689111| I1: VNLSpawn64BitVnetlibTask: process was not successful

2019-03-19T11:59:14.064-04:00| inst-build-10689111| I1: VNLInstallLegacyInf: Launched 64-bit process, result FALSE

2019-03-19T11:59:14.064-04:00| USBDeviceInstUtil-build-10689111| I0: Reboot not required

2019-03-19T11:59:14.064-04:00| USBDeviceInstUtil-build-10689111| I0: ERROR: Failed calling VNL_InstallHcmonInf() for service hcmon

2019-03-19T11:59:14.064-04:00| USBDeviceInstUtil-build-10689111| I1: Util_FreeLibrary: Freeing library: 1453785088

2019-03-19T11:59:14.064-04:00| USBDeviceInstUtil-build-10689111| I0: ERROR: Failed to install hcmon

Hey All,

I have seen a very worrying issue which is not always reproduced.

It seems like my interfaces for NAT/Bridge adapters doesn't get an IP from the DHCP, when I am running 'dhclient eth0/eth1' the command just stuck!

as a workaround, I remove my adapters and create them again... ( in some of time it helps and sometimes not ).

Does anyone know what could cause this issue?

ENV details:

VM workstation 15

Kali as Guest OS.

if you need any more details please let me know.

Thanks,

Ariel. 

Hi,

I am trying to use the VMWare performance counters on my host (Windows 10).

I tried turning on the option Virtualize CPU performance counters.

But no matter what I try nothing seems to register.

Is there some other setting or method I need to do to activate them?

Thanks,

Ward

I run a win 8 guest on vmware workstation pro 12 and i set as network connetion: vmnet2

On the guest I set the network adapter tcp/ipv4 properties to 192.168.192.4 static address

On my windows 10 host I set the network adapter "vmware network adapter vmnet2" property to 192.168.192.2 static address

The ping from my guest to my host works but from my host to my guest does not works.

"vnetsniffer /e VMnet2" on my host sees only the ping requests from my host towards my my guest: no replies

the same with win 7

Hello Guys,

I Installed on my Main System a new Windows 10 OS ( with buyed key nothing is cracked! ), before i did this i used VMware daily and never had any Problems with it. Now it tells me ( after i choosed an iso ) that no OS is installed. When i choose to Install an OS later it says " vmware cannot connect the virtual device sata 0:1 " .

I tryed a Windows 10 Iso + Windows 7 Iso, other Install Places and Google didnt Helped me.

Have someone a tip what i can do?

friendly regards

(when i open a old VM it opens perfectly and i can use it normally, my prob is the creation of a new one)

Author :

URL : http:////docs.vmware.com/jp/VMware-Workstation-Pro/15.0/com.vmware.ws.using.doc/GUID-3749BFCB-5065-476A-BA18-E2EB888FB026.html

Topic Name : 新しい場所への仮想ハード ディスクの移動

Publication Name : VMware Workstation Pro の使用

Product/Version : VMware Workstation Pro/15.0

Question :

vmware-vdiskmanagerのダウンロードサイトを知りたい

VMware® Workstation 15 Pro running on Linux Mint.

There is an update to this software and it keeps on asking for a root password to install the update.

I have typed in every password that I have ever known and it won't work.

Please advise.

When trying to open a Win7 x64 VM, I get the error message specified above.  This vm is on a physical drive (D:) on this machine.  I see the .vmdk file referenced.   I do have snapshots, but if the .vmx file won't open, how can I repair what seems to be a corrupted file?  Thanks please I have read thru the forums but don't know how to fix.  Thanks!

Dear VMWare workers,

I recently updated my VMWare Workstation pro 15 to 15.0.3 and since then copy paste does not work for me. Can you guys please fix it?

Kind regards,

Tornaci

Is there a way to find all linked clones that are based on a parent VM?

Reason I'm asking is that if I want delete a parent I want to know all of the linked clones based on it so that I can convert them into full clones (or just delete them).

I'm using Workstation 12.5.9 build-7535481, running on Windows 2012 x64  R2 standard server. This is hosting a W10 VM, with the latest VMWare tools installed. The VM connects to the host file system using the 'Share Folders' capability. But it fails copying files using any software (explorer, goodsync, total commander...) when the file names exceed ~255 ch. It probably reaches the 260 characters limit. On the other hand, if it uses a network connection (UNC \\<ip addr>\share) then the files copy well. Is this a limitation of the VMWare tools? Is there a fix for this?

Just did a quick install of Windows 10 64-bit in VMware Workstation and I just realized I forgot to switch the Guest OS "Version" from "Windows 10" to "Windows 10 x64", so I'm wondering what if any side effects it will have leaving it like this and whether or not I should just bite the bullet and reinstall. I know that when you have the "Firmware type" set to "UEFI" that changing the "Version" between "Windows 10" and "Windows 10 x64" will actually change what Architecture the UEFI firmware uses, but I'm not aware of any adverse effects it has when using just regular "BIOS" as the "Firmware Type".

TIA

Hello dear community,

I am writing this discussion because I face an annoying problem with my multiple monitors setup and WMware workstaiton 15.

Whevever the program show the information pop up window, this one SPANS on all 3 of my monitors (c.f. screenshot). I found no way to resize it or make it display into only one monitor so far.

Could somebody help ?

Many thanks.

Nicolas

Hi,

Using 15.0.3 build-12422535 with a Ubuntu 16.04 guest the VM will not start.  Screen is black and the VM appears to be hung.  The last portion of the log always looks like this (see below).   If I remove the NIC (bridged) I can start the VM but of course it then serves no function. However,  once I do this I can re-add the NIC and it will start.  I have to do this just about every time I stop and restart the VM.   I also have a WIndows Server 2012 VM that does the same thing and I just had it happen when trying to create a brand new VM.   I realize that the version of Windows 10 may be responsible since's it's not officially released but if anyone has advice or a more graceful workaround I'd love to hear it.

2019-03-24T14:18:25.488-05:00| vmx| I125: USB: Found device [name:Seagate\ RSS\ BUP\ Slim\ BK vid:0bc2 pid:ab26 path:1/1/4/3/1 speed:super family:storage,storage-bulk instanceId:USB\\VID_0BC2&PID_AB26\\MSFT30NA9CYXG8 serialnum:MSFT30NA9CYXG8 arbRuntimeKey:2 version:3]

2019-03-24T14:18:25.488-05:00| vmx| I125: USB: Found device [name:Virtual\ Bluetooth\ Adapter vid:0e0f pid:0008 speed:full family:wireless,bluetooth virtPath:usb:2 deviceType:virtual-bluetooth info:0000001 version:3], connected to usb:1 port 0.

2019-03-24T14:19:24.974-05:00| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2019-03-24T14:20:46.118-05:00| mks| W115: SOCKET 5 (-1) AsyncNamedPipeRecvCallback: failed to get overlapped result: 109.

2019-03-24T14:20:46.118-05:00| mks| I125: MKSControlSocket:  MKSControl Remote Disconnect: socket closed.

2019-03-24T14:20:46.118-05:00| mks| I125: MKSControlMgr: disconnected

2019-03-24T14:20:46.118-05:00| vmx| I125: SOCKET 4 (2140) recv error 10054: An existing connection was forcibly closed by the remote host

2019-03-24T14:20:46.118-05:00| vmx| I125: Vix: [mainDispatch.c:2828]: VMAutomation: Connection Error (1) on connection 0.

2019-03-24T14:21:03.048-05:00| WinNotifyThread| I125: Suspending VM from WM_ENDSESSION: U64_Media

2019-03-24T14:21:03.048-05:00| vmx| I125: SUSPEND: Start suspend (flags=0)

Vmware workstation pro 15

Win10 host, guest win7

Is possible add determined IPs, or any option to control who can connect in my remote server?

I have set up three Linux based Virtual Machines and all three have similar issues.

Linux Mint v19.1

With Linux Mint running, I go to the VM Menu > Settings and/or Removable Devices and enable the Sound Card, but as soon as I try to adjust the sound volume I recieve a small popup error message as displayed in the image. I see this popup error message when starting the VM also.

If I attempt to adjust the settings in the Sound settings in Mint, I recieve the following error message.

VMware tools are installed.

Initially, I had no issues with the Screen Resolution in Linux Mint, but on occasion that must be manually set when I start the VM.

Debian 9.8.0

Same issues with the Sound Card as in Linux Mint.

VMware tools are installed.

Initially, I had no issues with the Screen Resolution in Debian, but on occasion that must be manually set when I start the VM.

There seems to be an issue with the Stop Job message when shutting down Debian though, it is all over the place ... lol

uBuntu v18.04.2 LTS.

VMware tools are installed.

With uBuntu, even though I still recieve the small popup error message, sound will in fact work, but I must manually enable the sound card each time I start the VM, despite having the proper sound settings in the VM settings.

Initially, I had no issues with the Screen Resolution in uBuntu, but on occasion that must be manually set when I start the VM.

I have the following running on:

Asus RAMPAGE V

Intel i7 5930K @ 3.5GHz

16296 MB  (DDR4 SDRAM)

Windows 10 v1809 build 17763.379 running VMware Workstation Pro v15.0.3 build-12422535

The Sound card reports as:

ES1371/ES1373/Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]

I have tried adding these lines to the .vmx file, but alas, they did not help.

     sound.present = "TRUE"

     sound.fileName = "-1"

     sound.autodetect = "TRUE"

Any hints or tips on resolving these issues would be greatly appreciated.