Hello,

I was trying to see, how simplified UI in Workstation Player 14 looks like.

According to knowledge base, it should hide preferences settings of Virtual Machines.

I have edited config.ini on several places:

C:\ProgramData\VMware\VMware Player\config.ini

C:\Users\XXX\AppData\Roaming\VMware\config.ini

C:\ProgramData\VMware\VMware Workstation\config.ini

with value

installerDefaults.simplifiedUI = "yes"

But actually I do not see any changes when starting Player again.

Does someone has experience with this simplified GUI?

Thanks for any hint

Martin

As of recently I've been getting the following error (Workstation 11.1.0, Windows) when starting the UI.

---------------------------

VMware Workstation Error

---------------------------

VMware Workstation unrecoverable error: (vmui)

Exception 0xc0000005 (access violation) has occurred.

A log file is available in "C:\Users\mgill\AppData\Local\Temp\vmware-mgill\vmware-ui-3224.log".

You can request support.

To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.

You can also run the "vm-support" script in the Workstation folder directly.

We will respond on the basis of your support entitlement.

---------------------------

OK 

---------------------------

Nothing obvious in the logs. I've repaired the install. Uninstalled and Re-installed. Upgraded PowerCLI (which is also installed) and nothing changes.

Ironically, I've discovered that if I ignore the error and just keep working, everything seems to work correctly. The moment I hit ok on the windows though the UI is gone.

Any help for removing this error is greatly appreciated.vm

Here's part of the log:

2015-05-26T13:43:01.969+02:00| vmui| I120: cui::ComponentMgrCDS::RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product player-linux

2015-05-26T13:43:01.969+02:00| vmui| I120: CDS: CdsUtil_QueryMsiByProductCode: {A53A11EA-0095-493F-86FA-A15E8A86A405} is unknown in the MSI database.

2015-05-26T13:43:01.969+02:00| vmui| I120: CDS: CdsUtil_QueryMsiByProductCode: {313C6E9F-180C-46C3-8CB1-A2AFB34DF643} is unknown in the MSI database.

2015-05-26T13:43:01.970+02:00| vmui| E105: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2015-05-26T13:43:01.971+02:00| vmui| E105: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2015-05-26T13:43:01.971+02:00| vmui| E105: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2015-05-26T13:43:01.972+02:00| vmui| E105: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2015-05-26T13:43:01.973+02:00| vmui| E105: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2015-05-26T13:43:01.973+02:00| vmui| E105: CDS error: CdsUtil_QueryMsiPropertyByProductCode: MsiViewFetch failed: 259.

2015-05-26T13:43:01.974+02:00| vmui| I120: cui::ComponentMgrCDS::RefreshComponentListWithDefaults: CDS_UNKNOWN_PRODUCT_ERROR for product ws-linux

2015-05-26T13:43:01.974+02:00| vmui| I120: CDS: CdsUtil_QueryMsiByProductCode: {A3FF5CB2-FB35-4658-8751-9EDE1D65B3AA} is unknown in the MSI database.

2015-05-26T13:43:01.974+02:00| vmui| W110: cui::ComponentMgrCDS::RefreshComponentListWithDefaults: Install database empty! Overriding install state of ws-windows

2015-05-26T13:43:01.979+02:00| vmui| I120: LOCALE windows-1252 -> NULL User=809 System=409

2015-05-26T13:43:02.220+02:00| vthread-6| I120: VTHREAD initialize thread 6 "vthread-6" host id 10700

2015-05-26T13:43:02.262+02:00| vmui| I120: VMMgr::OpenVM (cfgPath=C:\Virtual Machines\mgil-mint\mgil-mint.vmx)

2015-05-26T13:43:02.272+02:00| vmui| I120: CVMUIApp::OpenTabInt: opened

2015-05-26T13:43:02.273+02:00| vmui| I120: BasicHttpOnSent: xmlStrcmp

2015-05-26T13:43:02.273+02:00| vmui| W110: Unhandled Win32 SEH exception

2015-05-26T13:43:02.273+02:00| vmui| W110: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----

2015-05-26T13:43:02.273+02:00| vmui| W110: ExceptionAddress 0x5caf42aa eflags 0x00010282

2015-05-26T13:43:02.273+02:00| vmui| W110: rwFlags 0 badAddr 0

2015-05-26T13:43:02.273+02:00| vmui| W110: eax 0 ebx 0x1 ecx 0x35f1d8

2015-05-26T13:43:02.273+02:00| vmui| W110: edx 0xa70048 esi 0x35f1d8 edi 0x35f158

2015-05-26T13:43:02.273+02:00| vmui| W110: eip 0x5caf42aa esp 0x35f0c0 ebp 0x35f14c

2015-05-26T13:43:02.273+02:00| vmui| W110: The following data was delivered with the exception:

2015-05-26T13:43:02.273+02:00| vmui| W110:  -- 0

2015-05-26T13:43:02.273+02:00| vmui| W110:  -- 0

Hello!

I have carried out several installations of different versions of VMware player, it keeps on indicating a hardware problem. I have tried reading on the internet, the exact properties of the computer to buy to host the VMware player versio 15.5.1, but they are not specific.

Please help me with the specifics of a computer that can serve as my server to run VMware player version 15.5.1. The error message i used to get is attached here

Thank you in advance for the help!

Hello!

I have installed VMware 15.5.1 (VMware-Workstation-Full-15.5.1-15018445.x86_64.bundle) on a CentOS 7 server with the following properties;

Memory: 3.6GiB

Processor: Intel Core i3-4000M CPU @ 2.4GHz x 4

Graphics: Intel Haswell Mobile

GNOME: Versin 3.28.2

OS Type: 64-bit

Disk: 315.7 GB

Server is up to date and kernel-devel and kernel-headers installed. The system HSNM hotspot manager i run in it, runs for some time and then freezes (The web interface does not respond after some time). i get this message that shows up (image of problem is attached). I have spent time trying to figure out why but i can't still get it fixed.

Please any help will be appreciated!

Hello!

I am trying to install VMware 8.0.6 (VMware-workstation-full-8.0.6-1035888.86_64.bundle) on a CentOS 7 server with the following properties;

Memory: 3.6GiB

Processor: Intel Core i3-4000M CPU @ 2.4GHz x 4

Graphics: Intel Haswell Mobile

GNOME: Versin 3.28.2

OS Type: 64-bit

Disk: 315.7 GB

Server is up to date and kernel-devel and kernel-headers installed. When i launch the VMware using the the command # vmware on the command line, i get this message that shows up (image of problem is attached). I have spent time trying to figure out why but i can't still get it fixed.

Please any help will be appreciated!

Hello,

is there an automated way to add shared folders to an virtual machine that is powered off (I am aware it is possible to use vmrun.exe for machines that are powered on)?

Thank you!

Hello,

I have a issue related to file attributes change occured when I copy file from guest machine to host machine.

- Host PC -

CPU : Intel Core I5-8400

RAM : 16GB

O/S : Windows 10 1909 x64 (UAC ON)

VMware : VMware Workstation Pro 15.5.1 build-15018445

- Guest PC -

CPU :  2 core

RAM : 2GB

O/S : Windows 10 1909 x64 (UAC ON)

Etc : other options are by default

- Details -

I just copied file guest machine to host machine by using 2 methods.

1.  Guest -> Host using "Mouse Drag n Drop"

Guest Path : C:\Program Files (x86)\Windows NT\TableTextService\TableTextService.dll

Host Path : User - Desktop

2. Guest -> Host using "Ctrl+C and Ctrl+V"

Guest Path : C:\Program Files (x86)\Windows NT\TableTextService\TableTextService.dll

Host Path : User - Desktop

I noticed that file from guest machine using Drag n Drop has "read only" file attribute.

But when I use Ctrl+C and Ctrl+V, file from guest machine does not have "read only" file attribute.

So I used SysInternals Process Monitor to find out why that happend.

If I try to copy file using Drag n Drop, the host process which name is "vmware-vmx.exe" tries SetBasicInformationFile with ReadOnly flag.

This does not happen if I try to copy file using Ctrl+V and Ctrl+V.

Is this VMware team's intended operation? or bug?

I'm really wondering why this happens.

Thanks.

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

Hi there,

I’m running Ubuntu 19.10 on my host machine, and I do not wish to downgrade for the time being.

I tried to install VMware Workstation 12.5.9 on my computer, but it just refused to start at all. I did a little digging, and I found that Workstation 12 isn’t compatible with kernels above 4.x.x.

The thing is, I can’t upgrade to Workstation 15 because my computer has one of the older processors that it dropped support for. So my question is, is there any way I can run Workstation without downgrading my distribution or upgrading my processor?

Hello,

I'm trying to install VMWare Workstation (VMware-workstation-full-15.5.1-15018445.exe) on Windows 10 Pro for Workstation (naturally 64bit) but when I run the installer, it crashes.

I've tried to install also VMWare Player (VMware-player-15.5.1-15018445.exe), and i'v got the same restult.

In the vminst.log I can see that there is an error during the file extraction.

2020-02-12T14:31:17.309+01:00| BootStrapper-build-15018445| I0: Selecting "C:\Users\MATTEO~1\AppData\Local\Temp\{C975449F-C205-4CBF-9911-680F2E5F810B}~setup\" for unpacking temp files

2020-02-12T14:31:17.309+01:00| BootStrapper-build-15018445| I0: Extracting setup files to "C:\Users\MATTEO~1\AppData\Local\Temp\{C975449F-C205-4CBF-9911-680F2E5F810B}~setup\"

2020-02-12T14:31:17.309+01:00| BootStrapper-build-15018445| I0:   --> VMwareWorkstation.msi [535973888]

2020-02-12T14:31:17.309+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.309+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.310+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.310+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.310+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.310+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.310+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.310+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.311+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.311+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.311+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.311+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.312+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.312+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.312+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.313+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.313+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.313+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.314+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.314+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.314+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.314+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.314+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.314+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.314+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.315+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.315+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.315+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.315+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.315+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.315+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.315+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.315+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.315+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.315+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.316+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.317+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.318+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.318+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.318+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.318+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.318+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.318+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.318+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.318+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.318+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.318+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.319+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.319+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.319+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.319+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.319+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.319+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.319+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.319+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.319+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.320+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.320+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.320+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.320+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.320+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.320+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.320+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.320+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.321+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.321+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.321+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 0.

2020-02-12T14:31:17.321+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 1.

2020-02-12T14:31:17.321+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 2.

2020-02-12T14:31:17.324+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 3.

2020-02-12T14:31:17.327+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 4.

2020-02-12T14:31:17.330+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 5.

2020-02-12T14:31:17.333+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 6.

2020-02-12T14:31:17.336+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 7.

2020-02-12T14:31:17.339+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 8.

2020-02-12T14:31:17.342+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 9.

2020-02-12T14:31:17.345+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 10.

2020-02-12T14:31:17.347+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 11.

2020-02-12T14:31:17.349+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 12.

2020-02-12T14:31:17.352+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 13.

2020-02-12T14:31:17.355+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 14.

2020-02-12T14:31:17.358+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 15.

2020-02-12T14:31:17.361+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 16.

2020-02-12T14:31:17.363+01:00| BootStrapper-build-15018445| I0: SetupProgressDlgProc: Current progress 17.

Thank everyone for your support.

Greetings, Matteo.

After switching to Workstation 15, my virtual machines have started switching to black screen if they idle for a few minutes. As they're all Linux servers running in text mode, and didn't blank the screen with Workstation 9, I don't think this is a feature of the guest OS, but something the virtual machine does.

How can I turn this off, or at least change the amount of time before the screen blanks? I am watching the output of the machines, and having to select them and press a key to see the output is driving me nuts.

I searched the docs and googled, but while I found one other user with the same problem, I didn't find any solution.

Hi,

I've installed Workstation Pro 15.5.1 three days ago and every day since loading the software I see that the Windows Reliability Monitor lists vmware-hostd.exe stops working. The error message shows up regardless whether or not I used vmware on that day. When I did launch and use Workstation Pro it ran a VM without any issues.

I'm using the software on a machine with a cleanly installed latest Windows 10 Home build with basically only Chrome, MBAM, vmware Workstation, and the drivers used to run the device, so I'm hoping that it's can't be a software incompatibility/conflict issue.

Is this a known issue or does anyone else see the same error in their Reliability Monitor? Should I be concerned?

Thanks

Hi

I need the display to take up les room. Plz look at pictures for a better explanation.

[url=https://postimg.cc/vDdSLH4M][img]https://i.postimg.cc/vDdSLH4M/New-Bitmap-Image-2.png[/img][/url]

i create the virtual linux,and physical net can catch the packets include vlan but in linux dump the packets ,the vlan disappeared.

is there any configuration to set vlan behavior in VMware?

Hi

I'm wanting to use 2 of the same mouse's. I want to ask this due to I heard it cant be dune. One on host and other on gust. I am using windows 10 on both gusst and host. But I can use any os if it helps setup 2 of the same mice !

I am runing vmware workstation 15 player non-commercial

My Environment:

VMWare Workstation 15 Pro

15.5.1 build-15018445

on Windows 10 Pro (v1903)

Several times I have problems using VMware Workstation recently.

I normally lock the host OS (Windows 10 Pro) when I go home while I run several Guest OSs using VMware.

Sometimes, in the morning of the next day, I find the VMware shutdown with all of the guest OSs shutdown.

It seems those guest OSs boot up normally (without a message of abrupt shutdown).

In one case, that happened about 1 hour after I lock the host OS. For other cases, I didn't record the time of the problem.

This happened five times by now.

I hope the developper solve this problem.

Hello everyone,

I have been doing some research and was wondering if anyone could help point me in the right direction.

I have a system that needs to be setup to support multiple users accessing several virtual machines.

The one thing I am struggling with is setting up the Shared Virtual Machine with "specific users/service accounts?" and actually exposing it on a specific port.

I think I need to use the HOST's IP and somehow VMWare Workstation resolves the request with the RDP protocol to a specific VM? I am unsure about this so if I could get some help in getting this setup that would be great!

I am MOST concerned with:

A.) Users accessing the remote shared virtual machine and being able to reach into the Host operating system

B.) Restricting users to only USING the virtual machine, but not making changes against it.

Thanks to all in advance for any help and supporting in getting me pointed in the right direction!

V/R

Robert

I’m looking for some help and advice with regards to Vmware. I’m completely new to using this software and I am already running into a few problems. I’m using Vmware pro workstation 14 in trial mode. I have successfully installed Windows 10 within the virtual PC and a few other programs. Everything seemed to be going just fine until all of a sudden, I was faced with a black screen within Vmware. I’m not sure if I’ve pressed something or done something to cause this to happen. I have noticed that there is suddenly, a thumbnail bar at the bottom which seems to show my virtual PC powering on and off. If I try to click it to open it up on the main screen it doesn’t work, I just get a black screen. I’m also having problems now connecting to the update server. I have uninstalled and reinstalled Vmware 4 times now without it making any difference. Is there any advice you can offer with regards to what the problem may be? I guess worst-case scenario is I would need to reinstall Windows 10 within Vmware, however this will take a fair bit of time and I still would not be aware of what I did that caused the problem in the first place.

I have attached a screenshot to show you what I’m looking at now when I open Vmware.

Thanks again.

Regards

Christopher

Hello.

I would appreciate it if anyone can help

I have a virtual machine on a vmware player 12 my data got hit by a ransomware ryuk and the vmdk file was encrypted .ryk extension added and all data for the virtual machine profile was deleted.

I was wondering if anyone has any idea about recovering the vmdk file.

I read something about recreating the virtual  machine disk discriptor file using esxi host.

If anyone can help me if this can or might work or worth trying

Note that I have a copy of vmdk file same machine and  a copy of the virtual machine configuration if this might help (backed up years ago).

Appreciate your help

Thank you

VMware 14 Launch Virtual system black screen

Log file