Hello i am having a problem with

vmware and i dont have any idea how to fix it. Unable to open kernel device

"
.\Global\vmx86": The system cannot find the file specified. Did you reboot

after installing VMware Workstation?

Failed to initialize

monitor device is the error that it gives me when i try to power on my virtual

machine. and i dont know how to fix it can anyone tell me what the problem is?bq.

so im guessing no one knows how to

fix this problem? also i cannot uninstall the program i havent found a way to

uninstall it yet

Hi all,

I’m using Workstation 12.5.2 and I’m experiencing freezing of my clients which often requires a full reboot of the host. I’ve stopped WIN10 Defender in the host from scanning the *.vmdk files as well as the vmware.exe process. I’ve also stripped the virtual machines back by removing printer, floppy, CD/DVD, network, and USB3 support but it’s still happening. I’m pretty sure it’s some kind of graphics problem. I’m using an intel skull canyon with 32GB ram and two Samsung M.2 drives. The virtual disks are not located on the host OS drive. The host OS is the latest image of WIN10 x64. Is anyone else experiencing problems with Workstation 12.5.2 and Intel’s Iris Pro Graphics? This morning I saw the attached error for the first time. Usually it just freezes with no error. I looked through the log file and noticed this:

2017-01-02T14:04:46.024+11:00| svga| W115: DX11Fence_InsertFenceAndFlush: Failed to create event query hr=-2147024882

2017-01-02T14:04:46.024+11:00| svga| W115: DX11Renderer: ID3D11Device_CreateQuery: hr=E_OUTOFMEMORY

2017-01-02T14:04:46.024+11:00| svga| W115: DX11Fence_InsertFenceAndFlush: Failed to create event query hr=-2147024882

2017-01-02T14:04:46.024+11:00| svga| W115: DX11Renderer: ID3D11Device_CreateQuery: hr=E_OUTOFMEMORY

2017-01-02T14:04:46.024+11:00| svga| I125: DX11Renderer_HasFencePassed: Dropping fence, query did not complete with state=0.

2017-01-02T14:04:46.024+11:00| svga| W115: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----

Thoughts?

my vmware machine was running and suddenly my PC shutdown due to power problem. when i turn on my pc again and try to open my vmware machine it show me this error "

Unable to open file "C:\Users\JUWEL\Documents\Virtual Machines\pc8\pc8.vmdk":

The system cannot find the file specified. " after all check, i saw some files are missing from the folder and I don't know how those get deleted. i attached some screenshots. 

Hi,

When i type in the iceweasel browser with the kali-linux OS https://kali:8834 under vmware;i got server not found

I try to launch nessus-home

I am connected to internet by ethernet.

Somebody knows what it could be ?

I am trying to get Workstation / Player (tried both, no different) working on a Win 10 Enterprise build 1607 host with the ability to bind USB devices to the guest.  (Ignoring USB devices, everything else works fine).

I am using 12.5.6 - didn't try so much with 12.5.5  but

I've read loads of different posts, and tried loads of things (over and over again) including:

• uninstall and reinstall
• uninstall, reboot, remove vmnet* network adapters, uninstall /clean, prevent vmware services from starting, reboot, run the vmware full uninstall steps, remove registry entries, delete files, reboot, reinstall (I knew those old Win95 experiences would come in useful again some day!)
• repair install, and repair install again

I've got past the failure to install vmusb and hcmon, and the usb arbitration service not starting.

I am now stuck with it simply saying 'the connection for the usb device "xxx" was unsuccessful' with a reason of "driver error".

The logs for the vmware USB arbitration service have this to say:

2017-06-12T21:45:16.048+01:00| vthread-4| I125: VTHREAD initialize thread 4 "vthread-4" host id 3856
2017-06-12T21:45:16.049+01:00| vthread-4| I125: USBArb: Starting VMUSBArbService args:'VMUSBArbService'
2017-06-12T21:45:16.053+01:00| vthread-4| I125: USBGW: Host controller #0 hc= "\\?\HCD0"
2017-06-12T21:45:16.053+01:00| vthread-4| I125: USBGW: Host controller #0 rootHubName="USB#ROOT_HUB30#4&2138960&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}"
2017-06-12T21:45:16.053+01:00| vthread-4| I125: USBGW: Host controller #0 rootHubDevInst="USB\ROOT_HUB30\4&2138960&0&0"
2017-06-12T21:45:16.054+01:00| vthread-4| I125: USBArbW: Connected to HCMON version 3.12
2017-06-12T21:45:16.135+01:00| vthread-5| I125: VTHREAD initialize thread 5 "vthread-5" host id 3892
2017-06-12T21:45:16.152+01:00| vthread-4| I125: VTHREAD initialize thread 4 "vthread-4" host id 3980
2017-06-12T21:45:16.152+01:00| vthread-4| I125: USBArb-BT: Beginning inquiry thread
2017-06-12T21:45:16.212+01:00| vthread-5| I125: USBArb: VMUSBArbService Started.
2017-06-12T21:45:18.184+01:00| vthread-5| W115: USBGW: WMIWin32_Wake failed for USB\VID_05C8&PID_0383\5&A6A6D4&1&9:1
2017-06-12T21:45:30.387+01:00| vthread-5| I125: USBArb: Num instances:2, user:SYSTEM client:vmware-hostd.exe
2017-06-12T21:45:30.387+01:00| vthread-5| I125: USBArb: Client 4488 connected (version: 7)
2017-06-12T21:46:12.542+01:00| vthread-5| I125: USBArb: Num instances:3, user:USER client:vmplayer.exe
2017-06-12T21:46:12.542+01:00| vthread-5| I125: USBArb: Client 9912 connected (version: 7)
2017-06-12T21:46:19.224+01:00| vthread-5| I125: USBArb: Num instances:4, user:USER client:vmware-vmx.exe
2017-06-12T21:46:19.224+01:00| vthread-5| I125: USBArb: Client 3556 connected (version: 7)
2017-06-12T21:46:19.224+01:00| vthread-5| I125: USBArb: Registered target 'vmware-vmx:C:\Users\USER\Documents\Virtual Machines\Ubuntu 64-bit\Ubuntu 64-bit.vmx' for client 3556.
2017-06-12T21:47:19.148+01:00| vthread-5| I125: USBArb: Connecting device 0x305c80383 to client 3556
2017-06-12T21:47:26.523+01:00| usbArb| I125: USBArb: Service being interrogated....
2017-06-12T21:47:27.274+01:00| usbArb| I125: USBArb: Service being interrogated....
2017-06-12T21:47:27.677+01:00| usbArb| I125: USBArb: Service being interrogated....
2017-06-12T21:47:35.116+01:00| vthread-5| W115: USBArbW: Connect failed: The semaphore timeout period has expired 0x(79)
2017-06-12T21:47:35.116+01:00| vthread-5| W115: USBArbW: Failed to connect device:305c80383 to 'dummy', status:4
2017-06-12T21:47:35.151+01:00| vthread-5| I125: USBArb: Client 3556 trying to close id 305c80383 it doesn't own.

It is on a laptop so there are loads of different USB devices to play with, and all of them fail the same way.

If I run the arbitration service manually (as listed in the first post below) I see this in the debug output when I try binding a new device:

C:\WINDOWS\system32>"C:\Program Files (x86)\Common Files\VMware\USB\vmware-usbarbitrator64" -f --verbose --debug 10
...
USBArb: USBArb_SendMsg op:4 len:4
USBArb: USBArb_SendMsg2 op:5 len:188
USBArb: USBArb_SendMsg2 op:5 len:227
USBArb: USBArb_SendMsg2 op:5 len:190
USBArb: USBArb_SendMsg op:4 len:4
USBArb: USBArb_SendMsg2 op:5 len:188
USBArb: USBArb_SendMsg2 op:5 len:227
USBArb: USBArb_SendMsg2 op:5 len:190
USBArb: USBArbCompletePipeRead: Asyncrhonously read the message from client:2C59970 len:8 readPos:8 isHeader:1
USBArb: USBArbInferMsg: Client 2C59970 wants to perform op:7 len:8
USBArb: USBArbPipeRead: Received request to read from client:2C59970 len:8 readPos:0 isHeader:0
USBArb: USBArbPipeRead: Synchronously read the message from client:2C59970 len:8 readPos:8 isHeader:0
USBArb: client:2C59970 op:7 len:8
USBArb: Client 1076 trying to close id 305c80383 it doesn't own.
USBArb: USBArbPipeRead: Received request to read from client:2C59970 len:8 readPos:0 isHeader:1

(Before I tried workstation, I was seeing the arbitrator fail with "error 31 a device attached to the system is not functioning" although all devices were correctly running in device manager - but I can't recreate that situation now).

What to try next?  I've spent many hours to get to this point and still no joy with something that should work out of the box like it has done for many years until now..

(One remaining question - I have vsphere client and client integration plugin installed - do they make a difference here?)

Some useful topics I've followed to no avail:

VMWare Workstation 12.5.5 / VMWare USB Arbitration Service

VM Removable Devices does not detect all USB devices under Workstation 12.5

The VMware USB Arbitrator returned error code 4(9)

VMware USB Arbitration service fails to start in VMware Workstation (2043656) | VMware KB

Error 31: A device attached to the system is not functioning, Windows 7 host, v. 7.1.4

Cleaning up after an incomplete uninstallation on a Windows host (1308) | VMware KB

Remove WorkStation Completly & Reinstall

Can't install Workstation Pro 12 because of virtual network driver

sanbarrow.com ~ Index

Getting  some information about the host  from virtual machine to verify a virtual machine is unqiue

i am running workstation on windows 7 with 16G RAM and i5 processor ,i need to test some network functionalities between two vms and because of that i changed MTU to 6000 in both the NICs and also the driver from e1000 to vmxnet3(By editing conf file manually).But as soon as i send out packets with size above 1500,vm crashes

Guest: ubuntu 16.04 64bit with Kernel 4.4.0-31-generic with 2 VCPU,3Gb RAM,3 Interfaces (all with vmxnet3 and one with jumbo frame enabled --> eth1)

Workstation Version : 12.5.6, build-5528349 with all the updates.

eg:

ping -Mdont 192.168.211.200 -s 1800

PING 192.168.211.200 (192.168.211.200) 1800(1828) bytes of data.

ERROR

VMware Workstation unrecoverable error: (vcpu-0)

VERIFY bora\devices\vmxnet3\vmxnet3_hosted.c:719

A log file is available in "C:\VM\k8storage1\vmware.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.

Update

if i don't change MTU of interface (ip l set eth1 mtu 6000) and then there is no crash with  "ping -Mdont 192.168.211.200 -s 1800 "
How ever
if i change MTU of eth1 to 6000 then same issue is happening again.

A few months back on Workstation 10 ,same test case was working fine .Not sure whats wrong in workstation 12.se

Any idea what could be wrong here?

Hi,

Currently VMware Workstation Pro 12.5.6 is installed in my desktop computer.

Windows 10 Enterprise is installed in my desktop computer.

Including Windows Server 2016, other OS are installed as guest OS in VMware Workstation.

VMware Workstation is working fine.

And I would prefer VMware Workstation as a virtualization application.

If I enable Hyper-V role, VMware Workstation doesn’t work.

I don’t want to run both; VMware Workstation and Hyper-V; same time but I want both should work in my desktop computer. I’ll run or use one application at a time.

Therefore, please let me know the way so that both should work in my desktop computer.

GnVm

Hi

I cant run x64 hosts on my Windows 10 Pro x64(Lenovo P50). x32 works without any problems.

Any ideas?

Hello,

Every time I upgrade my VmWare Workstation it is a real nightmare with errors such as "vmware authorization service could not be installed" and "workstation server is not available" and so on and so forth.

Each time I search online and finally get my system running again after half a day wasted. So, this time after upgrading to 12.5.6 I decided to write some notes down for myself, and to share them with the community.

1. Don't use the built-in updater, but go to the vmware website and download the full updater using your credentials (if you try to use the built-in updater you will not find the updater file after step 2 fails and steps 4 and 6 will be impossible).
2. Run updater once as admin, UPDATER WILL FAIL AND ITS SO-CALLED ROLLBACK WILL TOTALLY THRASH YOUR INSTALLATION (this is "normal").
3. Reboot.
4. Run updater again as ADMIN (will not obviously fail, but the Workstation Server will be damaged)
5. Reboot
6. Go to windows add/remove programs and REPAIR VmWare Workstation (fixes problems with a few services that still do not get installed properly even after steps 2 and 4)
7. Reboot
8. Go to C:\ProgramData\VMware\VMware Workstation\config.ini and change 903 to 902 in the line authd.client.port = "902"
9. Reboot.
10. Use VMware

Hope this helps,

Olivier

I just finished installing Kali linux on Vmware Workstation 11 and my after the installtion my kali is not launching showing " Cannot connect the virtual device ide0:0 because no corresponding device is available on the host. "

I have checked the IDE 0:0, it is failing.

Please anybody help me.

Hi,

For dual-boot to Windows Server 2016 within Windows 10, I have gone through the link

https://blogs.technet.microsoft.com/blainbar/2012/09/25/step-by-step-4-methods-to-dual-boot-microsoft-windows-8-and-windows-server-2012-with-or-without-windows-7/

One of the ways is “Dual Boot to Windows 8 or Windows Server 2012 from within the Windows 7 Operating System using an existing .VHD”.

In this way, a VHD is selected i.e. Server2012RTM.vhd.

Currently Windows Server 2016 is installed as a Guest OS on VMware Workstation 12.5.6 and because of VMware Workstation; the VHD is created with an extension .vmdk.

In this dual-boot process, may I use this VHD (.vmdk) as Attach VHD?

Apart from the way (mentioned in the link), is there another way so that .vmdk can be used as a Dual-boot within Windows 10?

Regards

GnVm

Hi. I have a problem with my virtual machine. WMDK files a split on 5 files and take a lot of disk space.

Host system is Windows 10, guest system Ubuntu 14.04

How I can join disks into one and reduce the size?

Creating a vsocket using socket() function on the host machine returns INVALID_SOCKET and WSAGetLastError() returns WSAEAFNOSUPPORT.

Same thing if executed with elevated privileges. VMCI device is present in Device Manager, "working properly". Didn't find any relevant records in log files, but I can provide all log files needed.

VSockets worked on Win10 before the Creators Update.

Tried on 3 different machines, same result.

"netsh winsock show catalog" output does not include any mention of vsocklib.dll

VMware Workstation version: 12.5.6.

I've got some VMs and they're all doing the same thing and I think everything is configured right. I have multiple monitors and am running multiple VMs, each maximized on their own monitor. When I move my mouse from one VM to another, it doesn't seem like it's getting captured automatically. I have to always click twice initially when switching from VM to VM. I see "grab cursor when enters window" is on. Shouldn't that allow me to just move back and forth and not have to click to actually enter a VM?

I'm getting a little desperate here.

I'm trying to install WIndows 10 64-bit as a virtual machine within VMware Workstation 12.

Every time I do that I'm getting stuck at 'Getting files ready for installation' and VMware Workstation is stated as 'Not Responding'.

I even cannot shutdown VMware with task manager or taskkill. When rebooting my machine I need to force stop the system (press power button for seconds) to quit VMware.

The past few days I tried almost everything to make it work but I'm not able to.

Things I tried:

• Update bios
• Update drivers (Graphics/Chipset)
• Update VMware Workstation 12 to latest version
• Watched videos how to install
• Downloaded multiple windows 10 Iso files to try with
• Update firmware on SSD drives
• Disabled security programs and set exclusions to VMware folders
• Tried various virtual hardware configurations

After trying and trying it is still not working.

Hardware/Software:

• Lenovo Thinkpad x230
• Samsung T1 SSD on USB3
• Windows 7 x64 (updated)
• VMware Workstation 12 (latest release)

Last resort here, what else can it be?

This might be obvious to people that have used the tool before, but the documentation is not clear to me.

       -r <source-disk>     : convert the specified disk; need to specify

                           destination disk-type.  For local destination disks

                           the disk type must be specified.

My questions is how to specify the -r parameter.  Obviously if I am doing a merge then I already have multiple .vmdk files.

There are a series of .vmdk files in the form of "Windows XP-s001.vmdk", "Windows XP-s002.vmdk", and "Windows XP-s00n.vmdk".  Then there is Windows XP .vmdk which is a text file.  Is it that file with the references to the others that should be supplied as the -r parameter?

I am converting from a vista  host to a win10 host. The vista host runs 2 microsoft VPC machines which I used an evaluation version of workstation pro to convert. Version 12 does not work on vista so I installed version 10. The evaluation period is up on version 10 which required me to get a license key. I installed the same evaluation version of workstation pro on the win10 host about a week after the vista host. My question is when  I am completely finished with the vista host can I use the same key on the win10 host? I suspect not since it has already been used which is only fair. Can I uninstall the vista version and then transfer that key to the win10 host?

Thanks for you help

Dennis

I am in the process of converting my microsoft virtual pc VMs (xp and vista) from a vista host to a win10 host. I downloaded an evaluation copy of workstation pro version 10 because 12 will not install on vista. I got the VPC VMs converted (the vista VM is my laptop vista host which I used workstation pro to convert the physical machine and it worked great).

My issue is this: it was necessary to reboot the host so I suspended both VM machines. I rebooted the host immediately but did not resume the VM machines until 3 hrs later. Both VM machines had lost their IP address and it was necessary to use ipconfig/release and renew to get them connected. I am using the default  networking that workstation pro uses when creating a VM. Is this going to happen each time I suspend a VM? Is it maybe related to version 10 and will work differently in version 12?

I'm sure there is additional info that may be needed to sort this out.

Thanks in advance for your help.

Dennis

Creating a new initrd boot image for the kernel.

update-initramfs: Generating /boot/initrd.img-4.9.0-kali4-686-pae

WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead.

Job for vmware-tools.service failed because the control process exited with error code.

See "systemctl status vmware-tools.service" and "journalctl -xe" for details.

Unable to start services for VMware Tools

Execution aborted.