Recently, I migrated a Windows 10 Virtual Machine, to a host laptop also running Windows 10, and VMware Workstation 12.   When I attempt to power on the VM, I get an error popup that states:  VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Workstation.

At one point I must have turned on Hyper-V within the Windows 10 Virtual Machine.  But I am unable to remove the role, because I must power on to do so, and VMware Workstation is not allowing the VM to power up. 

Anyone know how I may resolve this issue?

Thanks,

GeoB

Could someone help with the following?

I am running Workstation Pro v.15.5.0. Both the VM that I use and my host run Windows 10. Whenever I do not have an internet connection, Workstation tells me that a host clock skew has been detected and it suspends the VM. I've previously used Windows 8 VMs (possibly with Workstation v.15, but for sure with v. 14) and this did not happen. Can anyone tell me how I can use my VM offline?

HI

I have VMWare workstation 14 pro installed in windows 10 laptop  and created new virtual machine and given the Windows Server 2019 ISO path to create Windows server 2019 VM

but as seen in the picture i face problem

please help to solve this issue and how to create VM sucessful.

Host and guest are Windows 10 x64 1903.  Using VMware Workstationg v15.5.1

I turned on AutoProtect and continued working in the comfortable knowledge that I had some extra protection against some host stability problems that I am still trying to resolve.  But it turns out it does nothing on one particular guest.

I am guessing it is not working because this guest has an extra volume that is set as a persistent disk.  Normal snapshots happily take snapshots of the main (C:) volume and ignore the persistent, but (it seems that) for some reason AutoProtect won't do this ... which might be forgivable if it told me.

Is anyone able to confirm this is expected behaviour, or should I be looking for some other reason?

In virtual machine settings I browse for an ISO image file but there is nothing that is an iso. I tried putting in setup, setup64, autorun (but its just an icon) but nothing works. I go to "My Computer" and I am not seeing the vmware tools icon and clicking on the disc drive is empty.

Imgur: The magic of the Internet

Hello,

I am having a problem with remote VMs running on ESXi server after upgrading my host resolution to 4K 3840x2160.

I use vmware Workstaion to connect to a remote ESXi server to console into vms. Recently after switching my resolution to 4K, AutoFit guest resolution seems not to be working. If I switch back to 1080p or even 2560x1600 (on the host) the AutoFit function works again. I went through the ui-log file and I can see some errors with the guest resolution.

The following is when the host resolution is 2560x1600 (also with 1080p):

2020-01-30T20:14:48.665+04:00| vmui| I125: CVMUIApp::MenuButtonClicked: 10204 12
2020-01-30T20:17:39.714+04:00| vmui| I125: CVMUICmdbar::OnButtonClicked: 6
2020-01-30T20:17:39.714+04:00| vmui| I125: CVMUIApp::MenuButtonClicked: 10300 12
2020-01-30T20:17:39.726+04:00| vmui| I125: cui::IsTopologySupported: Topology: 2560x1600 @ 0,0.
2020-01-30T20:17:39.726+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:17:39.727+04:00| vmui| I125: cui::IsTopologySupported: Topology: 2560x1600 @ 0,0.
2020-01-30T20:17:39.727+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:17:39.749+04:00| vmui| I125: cui::IsTopologySupported: Topology: 2560x1600 @ 0,0.
2020-01-30T20:17:39.749+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:17:39.749+04:00| vmui| I125: cui::IsTopologySupported: Topology: 2560x1600 @ 0,0.
2020-01-30T20:17:39.749+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:17:39.782+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Render full screen.
2020-01-30T20:17:39.909+04:00| vmui| I125: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2020-01-30T20:17:39.909+04:00| vmui| I125: CVMUIFrame::OnGuestTopologyChanged: Passing main UI rect: 2560x1600 @ 0,0
2020-01-30T20:17:39.909+04:00| vmui| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: main UI rect: 2560x1600 @ 0,0
2020-01-30T20:17:39.909+04:00| vmui| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: Found 0 present screens
2020-01-30T20:17:39.909+04:00| vmui| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: Windows for extra guest monitors will be shown
2020-01-30T20:17:39.909+04:00| vmui| I125: cui::IsTopologySupported: Topology: 2560x1600 @ 0,0.
2020-01-30T20:17:39.909+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:17:39.913+04:00| vmui| I125: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2020-01-30T20:17:39.921+04:00| vmui| I125: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2020-01-30T20:17:39.922+04:00| vmui| I125: CVMUIFrame::OnGuestTopologyChanged: Passing main UI rect: 2560x1600 @ 0,0
2020-01-30T20:17:39.922+04:00| vmui| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: main UI rect: 2560x1600 @ 0,0
2020-01-30T20:17:39.922+04:00| vmui| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: Found 1 present screens

When I switch my host to 3840x2160 :

2020-01-30T20:17:47.014+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Render full screen.
2020-01-30T20:19:00.407+04:00| vmui| I125: cui::FullscreenMgr::UpdateResizedVMs: vm Windows Server 2016 has invalid topology.
2020-01-30T20:19:00.407+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:00.407+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:00.408+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:00.408+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:03.257+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:03.257+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:03.280+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:03.280+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:03.331+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:03.331+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:03.397+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:03.397+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:03.443+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:03.443+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:03.479+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:03.479+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:03.509+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:03.509+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:03.546+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:03.546+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:03.737+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:03.737+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:05.275+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Render full screen.
2020-01-30T20:19:07.171+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Render normal window.
2020-01-30T20:19:07.171+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Source: 2560x1600 @ 0,0 Target: 2560x1600 @ 0,0.
2020-01-30T20:19:07.232+04:00| vmui| W115: CVMUIFrame::FitGuest failed: vim.fault.GenericVmConfigFault
2020-01-30T20:19:07.238+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Render normal window.
2020-01-30T20:19:07.238+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Source: 2560x1600 @ 0,0 Target: 2560x1600 @ 0,0.
2020-01-30T20:19:09.855+04:00| vmui| I125: CVMUICmdbar::OnButtonClicked: 6
2020-01-30T20:19:09.855+04:00| vmui| I125: CVMUIApp::MenuButtonClicked: 10300 12
2020-01-30T20:19:09.870+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:09.870+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:09.871+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:09.871+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:09.884+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:09.884+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:09.884+04:00| vmui| I125: cui::IsTopologySupported: Topology: 3840x2160 @ 0,0.
2020-01-30T20:19:09.884+04:00| vmui| I125: cui::IsTopologySupported: Not a local VM. Returning true.
2020-01-30T20:19:09.903+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Render full screen.
2020-01-30T20:19:12.760+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Render normal window.
2020-01-30T20:19:12.760+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Source: 2560x1600 @ 0,0 Target: 2560x1600 @ 0,0.
2020-01-30T20:19:12.831+04:00| vmui| W115: CVMUIFrame::FitGuest failed: vim.fault.GenericVmConfigFault                            ## HERE
2020-01-30T20:19:12.844+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Render normal window.
2020-01-30T20:19:12.844+04:00| vmui| I125: CMksCtl::LayoutGuestWindow: Source: 2560x1600 @ 0,0 Target: 2560x1600 @ 0,0.

Local vms work fine with all resolutions.

Any idea?

Thanks

Workstation 15 Pro 15.5.1 build-15018445

I'm close to giving up on this but thought I'd ask about it here to see if anyone could help.  I have a Windows XP guest VM on a VMWare Workstation 9 installation on a Windows 7 Pro host.  I'm upgrading my Windows 7 Pro host machine to Windows 10 Pro.  Workstation 9 won't run on Windows 10 so I'm seeing if I can convert my Windows XP guest VM to a Hyper-V VM. 

I was able to convert the guest virtural drive to a .vhd.  I've been able to mount the .vhd on a Windows 10 Pro machine so I know that the .vhd drive was correctly created.  Here's where I've run into a wall:

On my Windows 10 Pro machine I'v created a new virtual machine in Hyper-V Manager using the "Use an existing virtual hard disk" option specifying the .vhd file I created. I've done this twice now first specifying Generation 2 VM and then specifying Generation 1.

• When I try to start the generation 2 VM I see ">>Start PXE over IPv4."  If I wait, I eventually get a white screen display stating:
  Virutal Machine Boot Summary
  1. SCSI Disk (0,0)
     The boot loader did not load an operating system.
  2. Network Adapter (00155D018B00)
     A boot image was not found
• When I try to start the generation 1 VM I get nothing but a black screen and flashing cursor. 

Both are set to boot from the hard drive (the Gen 1 seems to think it has a SCSI drive while the Gen 2 is IDE)

Any suggestions?

Hi All,

      I'm not sure if I'm in the right place to ask this question, so please redirect me if required.

I am running WMWare Pro 15.5 and on my old computer with OS = Win 7 I had no problems when I attached an external USB Drive to either the host or the guest.

I have since purchased a new Laptop, Lenovo Legion with OS = Win 10 Pro Build 1809.  My issue is every time I attach a USB Drive the computer stalls (temporary freeze) for up to 10 minutes when VMWare is running.  If VMWare is not running, there is no issue with external USB Drives.  I have multiple VM's with different operating systems and all are affected.  I have tried configuring USB options to only connect to the Host (my perfered selection) Ask before connecting etc.  I have also tried changing the USB compatibility from 3.0, to 2.0 and 1.1 without resolving the issue.

The difference between my old laptop and new laptop

Old:  OS = Win7 16GB Ram  1 only 1TB HDD,  but only had USB 2 ports

New: OS = Win10 Build 1809 16GB Ram 1only 256GB SSD (where VMWare Pro 15.5 is loaded) and 1 only 1TB HDD where the different Virtual Machine files reside) only has USB 3 ports.

Can anybody suggest some suggestions that will allow me to connect an External USB to the Host machine whilst running a Virtual Machine with freezing the computer for a long time.  If I am patient enough, the system will recover and everything works as it should.

Thank you.

Woolie161

Hi, I tried to install win 10 X64 in actual WS Pro 15.5

I create a vm and the setup starts from iso (i have tried different images) or dvd and after a few seconds i have to choose the image i want to install but it is empty and only shows: no image. What´s wrong?

When I created this virtual machine today I had no problems being able to click the generate button, now all of a sudden the button is grey and im unable to click on it. Why? I never changed anything...

- Can't even change hard disk advanced settings anymore, its all grey lol

Nach vmware installation tastatur geht nicht auf meinem hauptbetriebssystem was tun (ich schreibe mit bildschirmtastatur)

After vmware installation keyboard does not work on my main operating system (I write with the on-screen keyboard)

Windows Server 2012 virtual machines will not start (BSOD error 0xC000021A) or loop through the recovery menu in WMware Workstation 15 Pro version 15.5.1 build-15018455!

The virtual machines were copied from VMware ESXi, 6.7.0, 15160138 are in version 14 and with VMTools version 11265.

did anyone experience this problem?

Thanks,

Zé Madaleno

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!

Hello,

I used VmWare WKS 14.1.7

I added a second drive (as persistent) in my win7x86 and it works fine. Windows see it and im able to format it and use it.   thats great!

now my issue :   I did the same setup in my Win10x64 vm(100go HD SCSI Persistent) ,  but in Windows im unable to see that HD in disk management.

even i mark it as independant or not its not working.    why in win10x64 im unable to add a second HD ?

Did a lot of test but i can not find the issue...

any help will be appreciate,  thanks

Yannick

MTL , Quebec

Hello.

When shared folders is enabled and guest creates a file in the shared folder (\\vmware-host\Shared Folders\myshare\file.txt), the owner of the file is the user under which the VMWare itself is running on the host, not the user of the guest's.

Is there a way change the user who access/creates files in shared folder?

Thank you.

I currently own VMware Workstation Pro 14. I am aware that VMware Workstation Pro 15.5 is out. Would anyone have a clue on when VMware Workstation Pro 16 would be released? I can't decide if I should upgrade to 15.5 now or wait for 16 and then upgrade?

I believe that you can only upgrade from the last 2 major versions so I know that when/if 16 comes out I would want to pay the upgrade price and not full price.

I'll like to configure a new AMD build and like to know or nested VM's possible with a 3xxxX AMD proc (TRX-40 with AMD 3960x) within VMware Workstation Pro 15.

My current (old) Intel build has no problem with nested VM's within VMware Workstation Pro 15.

I'll have read it does have something to do SLAT on the Windows OS that is only available for the Intel platform.

So is there anyone who can confirm if nested VM's will work with an AMD 3960x VMware Workstation Pro 15 version before I'll buy this amazing expensive proc.

A tout les fois que j'essaie de créé une VM, j'ai ce message au lancement?

Each time I want to create a VM, I get this message during launch?

Просьба для разработчикам:

Товарищи разработчики после выхода vmware 14 появилась проблема с частотой обновления иконок в режиме просмотра всех виртуальных машин.

Request for developers:

Fellow developers after the release of vmware 14, there was a problem with the refresh rate of icons in the view mode of all virtual machines.

В vmware 15 так не исправили.

На данный момент частота обновления иконок 1 кадр за 2 секунды!!!  и вот что  происходит с загрузкой процессора с включенными иконками и  отключенными.

Vmware 15 did not fix this.

At the moment, the refresh rate of icons is 1 frame in 2 seconds!!! and that's what happens with CPU loading with icons enabled and disabled.

График загрузки похож на пилу. Исправьте уже это , добавьте настройку где можно самому регулировать частоту обновления вплоть до обновления в реальном времени.

PS: Ждем выхода vmware 16.0.0 (новые возможности vgpu dx11.0)(отключение лимита в  28 vm)

С наступающим Новым Годом всех!!!

The loading schedule is like a saw. Fix this already, add a setting where you can adjust the refresh rate up to the update in real time.

PS: Waiting for the release of vmware 16.0.0 (new features of vgpu dx11.0)(disable limit in 28 vm)

Happy New Year everyone!!!