Trying to get VMWare working On W11

[Thom Martz]

I installed the latest VMWare on W11 brand new Dell computer.

VMware-workstation-full-17.6.3-24583834.exe was the install package.

After installation, lots of blue screens. 

The only thing I installed.

Thought it was computer related.

It was not. Had a Dell tech show up at my office.  No hardware issues.  

Turns out to be software related.  The only thing installed was VMWare,

I went back to my W10 computer and found I am running 15.5.7 build 17171714

I installed that version on the Dell W11, after a complete wipe of windows on the Dell.

No issues running 15.5 on the Dell.  No blue screens. All positive.

Last step.  Copy over the VM directories.  I should be on my way.

I tried one VM copy first.

Everything appears the same under the VMWare Workstation under windows 11 and window 10.

When I try to start the VM, I get Failed to start the virtual machine in a message box.

I am going to include a zip file with support data.

Any help appreciated.

Attachment(s)

vmsupport-2025-05-01-07-59.zip   3.39 MB 1 version

[RaSystemlord]

If you can run the old VM version on that computer with new Win11 VM, then everything is fine. I suggest to use 17.5.2. which is the last vmware-team version before Broadcom, but that might not be necessary, if everything works now.

The problem is with your copying. Two possibilities, or both:

0. 

You need to deselect those VMs from Pro GUI, or leave Pro closed. Some files are occupied otherwise.

1.

Use a reliable copy method. Windows GUI copy is not one.

Use robocopy which is within Windows, like "robocopy /e /v /Z d:\myVMs\VM1 e:\ssd1\VMs\

It copies directories and is fool-proof.

This step is not necessary, if you are sure about your hardware/network or whatever you have there.

2.

Open up the VMs in the new place by saying "I copied". Failure to do so, does not work, if the computer architecture is different, like from Intel to Ryzen. You need to copy again, if you made this mistake.

I know, after "I copied" some activation (or even a new license, which are really cheap, if you know where to to buy) may be required to some Microsoft stuff. Cannot be helped - this is not exact science though.

3.

I said two, well, the individual VM configuration might have problems when the environment changes. Take everything unnecessary out, at first, read the VMware prompts and go on from there.