bonnie201110141's Accepted Solutions

Hi, Will you please enable tools log in your guest operating system as below? 1. Create a folder maybe on your desktop in your guest os to store the tools log. Let 's say C:\users\${USER}\d... See more...
Hi, Will you please enable tools log in your guest operating system as below? 1. Create a folder maybe on your desktop in your guest os to store the tools log. Let 's say C:\users\${USER}\desktop\toolsLog. 2. Added below line in your C:\ProgramData\VMware\VMware Tools\tools.conf (Create the file if not exist) in your guest os [logging] log = true # Enable tools service logging to a file. vmtoolsd.level = debug vmtoolsd.handler = file vmtoolsd.data = C:/users/${USER}/desktop/toolsLog/vmtoolsd.${USER}.log # Enable 'vmsvc' service logging to a file. vmsvc.level = debug vmsvc.handler = file vmsvc.data = C:/users/${USER}/desktop/toolsLog/vmsvc.log # Enable 'dndcp' service logging to a file. dndcp.level = debug dndcp.handler = file dndcp.data = C:/users/${USER}/desktop/toolsLog/dndcp.log # Enable new "vmusr" service logging to a file. vmusr.level = debug vmusr.handler = file vmusr.data = C:/users/${USER}/desktop/toolsLog/vmusr.${USER}.log 3. restart the guest and reproduce the issue 4. Send us the logs in C:/users/${USER}/desktop/toolsLog
Can you disable the shared folder and enable it again from VM > Settings > Options > Shared Folders, and try to access it again in guest OS?
Usually "soft" power operation will trigger the tools to run a script in guest operating system before doing the power operation. For "hard" power operation, no script in guest will be run. You c... See more...
Usually "soft" power operation will trigger the tools to run a script in guest operating system before doing the power operation. For "hard" power operation, no script in guest will be run. You can check the script in tools installation path. I am not sure if you are using VMware tools or open-vm-tools. By default, you should be using open-vm-tools. And you You can modify or customize the script to do anything you want. For suspend, by default the script in soft operation in Linux guest is stopping networking for the virtual machine. When resume, networking restarts. You can take a look at the script. I guess the problem you ran into might be with tools in CentOS guest. Anyway, I would recommend using hard suspend, i.e. VM > Power > Suspend, unless you have specific requirement in which case you can customize the script. Whether the button in Workstation UI is doing hard or soft depends on vm settings > Options > Power > Power controls. Hope this helps.
This issue only occurs if the mouse if grabbed in guest OS. From technical perspective, there is no generic solution to this problem. But we can add below option in /etc/vmware/config: mks.scree... See more...
This issue only occurs if the mouse if grabbed in guest OS. From technical perspective, there is no generic solution to this problem. But we can add below option in /etc/vmware/config: mks.screenSaverTimeout = "..."  # Set to to the number of seconds slightly lower than the host lock setting Then after the specified number of seconds of idle time in guest, the mouse will automatically ungrab from guest, and the host can lock successfully. --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.
Can you add below line to the .vmx file from your VM directory? usb.generic.keepStreamsEnabled = "FALSE" Please let us know if it works.
VMware Workstation will pre-allocate 8GB disk space for Windows 7 or above VM, even though it is is thin-provisioned. It is to improve performance. So I think it is expected.
This issue is fixed internally in VMware. Please be patient for the update.
Hi, The smart card reader is not available in Removable Devices because VMware USB arbitrator cannot connect to hcmon driver and is not running. Please check Windows Services > VMware USB A... See more...
Hi, The smart card reader is not available in Removable Devices because VMware USB arbitrator cannot connect to hcmon driver and is not running. Please check Windows Services > VMware USB Arbitration Service is running. If not, please check if you can start it manually it. If starting usb arbitration service triggers error, please do the following to cleanup and reinstall: 1. remove Vmware Workstation 2. Restart host 3. Remove C:\Windows\System32\drivers\hcmon.sys. If you cannot remove it, stop it firstly by "sc stop hcmon" 4. Restart host 5. Install VMware Workstation again. Please let me know if it works for you.
Let me understand your requirement. You add a serial port to a VM, and tries to map the serial port to COM3 on the host. Is it successful when you do it from vm settings? If above step is ... See more...
Let me understand your requirement. You add a serial port to a VM, and tries to map the serial port to COM3 on the host. Is it successful when you do it from vm settings? If above step is successful, the guest should have a serial port available. The port number depends on whether you have thinprint enabled in Workstation menu Edit > Preferences > Devices. If you have thinprint enabled, you should be using com2 mapped to COM3 on the host. If not, you should have COM1 mapped to COM3 on the host. I think you can do an echo to the COM port in guest to see if the com port works.
I tried a computer with a touch screen, but not the same as your touch computer. Without connecting the touchscreen device to VM (i.e., stay connected to my Windows 10 host), it works the same in... See more...
I tried a computer with a touch screen, but not the same as your touch computer. Without connecting the touchscreen device to VM (i.e., stay connected to my Windows 10 host), it works the same in guest as on host, i.e. whenever I click somewhere using my finger, the mouse vanishes and the destination is focused. Maybe there is some issue in Workstation with  your type of machine. Can you please try to add below option in your vmx file (from your VM directory) and see if it works? Please try it without connecting the touch panel device to VM. touchscreen.vusb.present = FALSE touchscreen.vusb.enable = FALSE mks.enableTouch = FALSE
Can you try the following? In Edit > Preferences > Shared VMs, disable sharing and enable sharing again. If error happens, please attach screenshot and hostd-*.log from %programdata%\VMware\ho... See more...
Can you try the following? In Edit > Preferences > Shared VMs, disable sharing and enable sharing again. If error happens, please attach screenshot and hostd-*.log from %programdata%\VMware\hostd. Thanks a lot!
Do you mean your wired UBS devices does not show up in VM > Removable Devices? What device are you using?
Thanks for reporting the issue! This looks weird, but is however expected. This is because in Workstation 15, the OVFTools bundled supports hardware version up to 14. You need to upgrade the hard... See more...
Thanks for reporting the issue! This looks weird, but is however expected. This is because in Workstation 15, the OVFTools bundled supports hardware version up to 14. You need to upgrade the hardware version using Workstation UI after imported.
Can you verify that in Edit > Preferences > Display "Autofit Guest" is checked? (You can uncheck "Autofit Window"). If this still does not work for you, is clicking "VM > Fit Guest Now" working f... See more...
Can you verify that in Edit > Preferences > Display "Autofit Guest" is checked? (You can uncheck "Autofit Window"). If this still does not work for you, is clicking "VM > Fit Guest Now" working for you? If still not, what is your tools version?
No, it is not a configuration in Player. It is a configuration in your Mint host. I know Ubuntu has such a setting (Settings > Privacy > Usage & History), not sure if Mint has a similar one? If i... See more...
No, it is not a configuration in Player. It is a configuration in your Mint host. I know Ubuntu has such a setting (Settings > Privacy > Usage & History), not sure if Mint has a similar one? If it is enabled, your host system will save recently-used-files.
This might be caused by a broken Workstation upgrade. Please check whether VMware USB Arbitration Service is started in Windows Services. If not, please try to start it manually. If starting it p... See more...
This might be caused by a broken Workstation upgrade. Please check whether VMware USB Arbitration Service is started in Windows Services. If not, please try to start it manually. If starting it produces error, please try to start VMware Workstation Server in Window services. If above does not work, you might need to uninstall Workstation, stop below services from command line with admintrator sc stop VMwareHostd sc delete VMwareHostd sc stop hcmon sc delete hcmon sc stop vmx86 sc delete vmx86 sc stop vmusb sc delete vmusb reboot host os, and install Workstation again. Let me know if it works for you.
I can reproduce the issue locally and have filed an internal bug to track it. Thank you for reporting the issue to us!
2018-04-05T13:04:26.097-04:00| host-13740| W115: USBArbW: Could not connect to HCMON: The system cannot find the file specified (2) So C:\Windows\system32\hcmon.sys is missing. I am sorry you ... See more...
2018-04-05T13:04:26.097-04:00| host-13740| W115: USBArbW: Could not connect to HCMON: The system cannot find the file specified (2) So C:\Windows\system32\hcmon.sys is missing. I am sorry you might need a clean reinstall again. Will you please do the following? 1. Uninstall VMware Workstation without keeping any config files. 2. Remove the following files and folders if any: C:\Program Files (x86)\VMware\VMware Workstation C:\Program Files\Common Files\VMware C:\Program Files (x86)\Common Files\VMware 3. Stop drivers and services from command line (with administrative privilege) sc stop VMwareHostd sc stop VMUSBArbService sc stop hcmon sc stop vmx86 sc stop vmusb sc stop vsock 4. Remove VMware drivers files from C:\Windows\System32\drivers, such as hcmon.sys, vmci.sys, vmx86.sys, vmusb.sys, vsock.sys 5. Restart host OS 6. Install VMware Worstation again. Let me if it works for you.
From the log, the error happen when we install vmusb/netbridge/netadapter/vmci drivers. From setupapi.dev.log, =================================== flq: {_commit_copyfile} flq: CopyFile:... See more...
From the log, the error happen when we install vmusb/netbridge/netadapter/vmci drivers. From setupapi.dev.log, =================================== flq: {_commit_copyfile} flq: CopyFile: 'C:\Users\acs\AppData\Local\Temp\{5f5042b8-f0c3-00c7-ea0b-e401025fd614}\vmusb.sys' flq: to: 'C:\windows\System32\DriverStore\Temp\{431616f7-d661-75d8-1d2d-c8796036d55a}\SET5977.tmp' flq: MoveFile: 'C:\windows\System32\DriverStore\Temp\{431616f7-d661-75d8-1d2d-c8796036d55a}\SET5977.tmp' flq: to: 'C:\windows\System32\DriverStore\Temp\{431616f7-d661-75d8-1d2d-c8796036d55a}\vmusb.sys' !!! flq: MoveFile: FAILED! !!! flq: Error 32: The process cannot access the file because it is being used by another process. !!! flq: Windows could not copy a boot file 'C:\windows\System32\DriverStore\Temp\{431616f7-d661-75d8-1d2d-c8796036d55a}\vmusb.sys' due to the presence of an in-use file. !!! flq: Error installing file (0x00000005) !!! flq: Error 5: Access is denied. ! flq: SourceFile   - 'C:\Users\acs\AppData\Local\Temp\{5f5042b8-f0c3-00c7-ea0b-e401025fd614}\vmusb.sys' flq: TempFile     - 'C:\windows\System32\DriverStore\Temp\{431616f7-d661-75d8-1d2d-c8796036d55a}\SET5977.tmp' ! flq: TargetFile   - 'C:\windows\System32\DriverStore\Temp\{431616f7-d661-75d8-1d2d-c8796036d55a}\vmusb.sys' flq: {SPFQNOTIFY_COPYERROR} !!! sto: Failed to copy file 'C:\Users\acs\AppData\Local\Temp\{5f5042b8-f0c3-00c7-ea0b-e401025fd614}\vmusb.sys' to 'C:\windows\System32\DriverStore\Temp\{431616f7-d661-75d8-1d2d-c8796036d55a}\vmusb.sys'. Error = 0x00000005 sto: File 'C:\Users\acs\AppData\Local\Temp\{5f5042b8-f0c3-00c7-ea0b-e401025fd614}\vmusb.sys' is not in use by any processes. flq: {SPFQNOTIFY_COPYERROR - returned 0x00000000} !!! flq: SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT. !!! flq: Error 2: The system cannot find the file specified. flq: {_commit_copyfile exit(0x00000002)} flq: {_commit_copy_subqueue exit(0x00000002)} ==================================== There have several possibilities to cause this problem. Can you try below? 1.    Check anti-virus software log if you have one, this copy operation failure maybe caused by anti-virus deny this operation. 2.    After uninstall Workstation, goto 'C:\windows\System32\DriverStore\Temp’ folder, for every subdir, which is named as one GUID, find and delete sub-folders  which has these driver files: vmusb/netbridge/netadapter/vmci For example, if you find 'C:\windows\System32\DriverStore\Temp\{431616f7-d661-75d8-1d2d-c8796036d55a}\vmusb.sys' exist, you should delete whole subfolder {431616f7-d661-75d8-1d2d-c8796036d55a} 3.    Check the 'C:\windows\System32\DriverStore\’ security properties, make sure the ‘system’ account have full control for this folder. 4.    It may cause by NTFS ‘alternate data streams’, go to website https://docs.microsoft.com/en-us/sysinternals/downloads/streams download the tool named streams, unpack it and save it to one folder, let’s say c:\temp, then in one administrator console, run this: C:\> cd /d C:\windows\System32\DriverStore C:\Windows\System32\DriverStore> c:\temp\streams -s * If you get output like this (I created test.txt:stream in c:\test for demo): C:\test> c:\temp\streams -s * Streams v1.56 - Enumerate alternate NTFS data streams Copyright (C) 1999-2007 Mark Russinovich Sysinternals - www.sysinternals.com C:\test\test.txt:           :stream:$DATA 8 You need cleanup them, with this command (notice this command run inside C:\Windows\System32\DriverStore): C:\Windows\System32\DriverStore> c:\temp\Streams -s -d * Reinstall Workstation and check the result.
So WinPreVista.iso is mounted when installing tools for Windows 7, which is the reason why tools installer cannot execute in guest. Can you check VM > settings > Options > General > Guest Operati... See more...
So WinPreVista.iso is mounted when installing tools for Windows 7, which is the reason why tools installer cannot execute in guest. Can you check VM > settings > Options > General > Guest Operating System? If it is not Windows 7, can you please change to the correct OS type and try again?