How to Create a New Virtual Machine on VMware Workstation

Fitting a lab onto one physical computer may sound like science fiction. Yet millions of professionals do exactly that today. So what setup makes this possible? The answer lies in the practice of creating a virtual machine with VMware Workstation.

VMware Workstation is one of the most established names in the desktop hypervisor market. However, the license shake-up under Broadcom in 2026 changed the rules of the game.

Now a fully free Workstation Pro exists for personal, educational, and commercial use. This gives anyone who wants to learn the virtual machine creation process a great opportunity. Explore with us how to get the most from this opening.

This guide gives you both theory and hands-on practice in one place. First, we will clarify the core concepts. Next, we will check the prerequisites. Then, we will walk through the wizard step by step. In addition, we have a hands-on section for Windows 10 and 11. Finally, we will close with fixes, performance tips, and advanced scenarios.

Why Choose VMware Workstation to Create a Virtual Machine?

Picture an operating system running inside an isolated box on your main machine. This box has its own CPU, memory, disk, and network. We call this setup a virtual machine (VM).

Creating a virtual machine means setting up that box. Additionally, you place a guest operating system (guest OS) inside it. A software layer that shares the physical hardware makes this process work. We call that layer a hypervisor.

VMware Workstation is a type-2 hypervisor, which means it is a desktop hypervisor. It runs like an ordinary app on your host operating system (host OS). However, it manages a very complex resource pool in the background.

In addition, Workstation provides virtual CPUs (vCPU) and virtual RAM (vRAM). It also delivers resources such as a virtual disk (VMDK) to the guest OS. During this process, it uses hardware virtualization extensions (VT-x/AMD-V).

So why VMware? Because Workstation Pro has key features that set it apart from rivals. For example, its snapshot tree management is very mature.

Also, you can fine-tune virtual switches with the Virtual Network Editor. For example, you can edit switches such as VMnet0, VMnet1, and VMnet8. In addition, tools such as vmcli and dictTool in the 2026 releases open the doors to wide automation.

Virtual Machine (VM) and Hypervisor Concepts: A Short Definition

A hypervisor is the software layer that turns physical resources into virtual resources. Type-1 hypervisors (like ESXi) run directly on hardware.

Type-2 hypervisors (Workstation, Fusion, Player) run as applications inside a host operating system. This split directly affects performance and use cases. The type-2 model gives desktop developers and system administrators practical convenience.

A virtual machine is the isolated workspace this layer produces. Each VM has its own virtual BIOS/UEFI firmware. In addition, each VM carries a virtual NVMe or SCSI controller. Each VM also has a virtual network adapter.

The guest operating system treats this hardware as real. In reality, VMware routes these requests to host OS drivers. During this routing, techniques such as I/O control and paravirtualization come into play.

The Place of VMware Workstation Pro in Desktop Virtualization

Workstation Pro is a reference point in the desktop hypervisor market. The license change after the Broadcom buyout distinguished it completely from rivals.

As of 2026, the product needs no license key even for commercial use. This move affected a wide group, from enterprise labs to solo developers. You no longer need to set aside a budget to build a software test setup.

Workstation Pro is also strong on technical depth. Hardware version 22 (as of 2026) offers new virtual hardware features. In addition, these features support modern operating systems without issues.

Thanks to Secure Boot and virtual TPM 2.0 chip support, Windows 11 installation works without issues. Also, ESXi compatibility makes it easy to move local VMs to enterprise infrastructure. You can get the latest release from our VMware Workstation Pro download page.

Compared with rival VirtualBox, Workstation Pro stands out mainly in 3D graphics acceleration and USB controller management.

However, the real difference lies in snapshot and cloning depth. Linked clone and full clone options let you copy test setups in minutes.

Prerequisites for Creating a Virtual Machine: What to Check Before Setup

Creating a virtual machine with the wizard takes half an hour. Still, if you start with poor prerequisites, you will debug for hours. So you must make sure your host machine is ready before you create a VM.

The first check is CPU virtualization support. Intel VT-x or AMD-V is a must for the hypervisor. The second check is whether this feature is on at the BIOS/UEFI level.

After that, you should look at conflicts on the Windows side. Hyper-V, VBS (Virtualization-Based Security), and WSL2 can reserve the virtualization extensions. In this case, VMware cannot access VT-x/EPT and the VM will not start.

The third check is sufficient disk space and RAM. Set aside at least 4 GB RAM for a modern Windows 11 VM. In addition, leave at least 60 GB free disk space. Remember, the resource pool is shared.

How Do You Turn On VT-x / AMD-V and EPT Support in BIOS or UEFI?

Restart your computer and press the BIOS/UEFI key as soon as the manufacturer logo appears. This key is often F2, Del, or F10. In the interface, go to the Advanced or CPU Configuration section.

On Intel systems, look for the Intel Virtualization Technology or VT-x option. On AMD systems, you will find the SVM Mode or AMD-V entry.

Set the option to Enabled. Then make sure EPT or RVI support is also on. This directly affects memory management performance.

Save the changes and restart the system. When Windows opens, open Task Manager. Under the Performance tab in the CPU section, you should see Virtualization: Enabled.

If this line says Disabled, your BIOS setting may not have saved. On some boards, the security chip (TPM) or Secure Boot can hide the virtualization setting. In this case, first turn off Secure Boot temporarily and try again.

Also, the Windows Core Isolation feature can paint a misleading picture. To see the real state, run the systeminfo command in PowerShell.

Hyper-V, VBS, and WSL2 Conflicts: Windows Features to Turn Off Before the VM Starts

Windows 10 and 11 run their own hypervisor (Hyper-V) in the background for security reasons. This hypervisor reserves resources such as VT-x/EPT.

VMware Workstation, however, wants access to the same resources. Result: the “Virtualized Intel VT-x/EPT is not supported” error. To fix this clash, follow the steps below.

• Step 1: Open the Windows Features window. Clear the Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, and Windows Sandbox boxes.
• Step 2: Open Command Prompt as administrator and run the bcdedit /set hypervisorlaunchtype off command.
• Step 3: In Registry Editor, go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard. Set the EnableVirtualizationBasedSecurity value to 0.
• Step 4: Turn off the Memory Integrity setting under Core Isolation.
• Step 5: Restart the system and open VMware again.

These steps create a dilemma for developers who use WSL2. WSL2 needs the Hyper-V infrastructure. Therefore, you cannot use WSL2 and VMware Workstation at full performance on the same machine at the same time.

The fix: change the hypervisor launch type based on need. I personally turn WSL2 off temporarily in heavy VMware scenarios. You can turn it back on with one command when you finish.

New Virtual Machine Wizard: Step-by-Step VM Creation Process

The prerequisites are ready now. When you open the wizard, two paths appear: Typical and Custom. This choice sets the fate of your VM. Typical is fast but limited. Custom gives you full control.

My experience shows most users pick Typical for their first VM. However, moving to Custom from the second VM onward saves significant time in the long run.

You can start the wizard in three ways. The fastest is the Ctrl + N shortcut. As an alternative, go to File > New Virtual Machine in the top menu. The Create a New Virtual Machine box on the main screen also takes you to the same place. Whichever path you choose, the first screen asks for the setup type.

Starting the Wizard: Ctrl+N Shortcut, Menu, and Main Screen

When you open VMware Workstation, a clean welcome screen greets you. A Create a New Virtual Machine button sits at the top right. The moment you click this button, the New Virtual Machine Wizard starts. The wizard is a set of dialog boxes that guide you step by step. You move on by clicking Next at each step.

However, here is a small tip. You can go back with the Back button as the wizard moves forward. Still, going back on some steps can reset your earlier choices. So read each screen carefully. Do not rush, especially on the disk type and network connection screens. A wrong click can make you set up the VM from scratch.

On the first wizard screen, you see two radio buttons: Typical and Custom (advanced). Typical is the default. If you do not target a special hardware setup, Typical takes you to the result quickly. Even so, knowing what Custom offers helps you make a mindful choice.

What Is the Difference Between Typical (Recommended) and Custom (Advanced) Setup?

Typical mode is for typical scenarios, as the name says. It finds the OS during setup. Easy Install then asks for your username, password, and product key.

It also sets disk size and memory in most cases with sensible defaults. You finish the job in four or five screens in total. This path is ideal if you will build a quick test setup.

Custom mode, however, starts with the hardware compatibility version. You choose which Workstation release your virtual hardware will match. Then the I/O controller type (SCSI, NVMe, SATA) is selected.

You set the virtual disk type (IDE, SATA, SCSI, NVMe) one by one. You also pick the disk allocation policy one by one. For example, there are thick provision lazy zeroed, thick provision eager zeroed, and thin provisioning options. The network adapter type (e1000e or vmxnet3) and firmware (BIOS legacy vs UEFI) are also under your control.

My advice is this: set up your first VM with Typical. That way you learn the process. Move to Custom from the second VM onward. If you want to add an NVMe controller or pick a different firmware, Custom is your only option.

Remember, the earlier you take control when creating a virtual machine, the less you’ll struggle later.

Installing an OS with an ISO File or Creating an Empty VM Without an Install

A key step in the wizard asks for the OS source. If you have an ISO image, check the Installer disc image file (iso) option. Point to the ISO file with the Browse button.

VMware analyzes the ISO content and detects the OS type on its own. If it cannot detect it, you can pick from the list manually.

If you do not have an ISO file, use the I will install the operating system later option. Check this option again if you want to install the OS later.

In this case, VMware builds a VM with an empty virtual disk and basic hardware. You can mount the ISO from the VM settings later. This method is handy especially for people who want to prepare hardware setup separately from the OS.

Easy Install mode starts on its own when it detects an ISO. It asks you for a Windows product key, user name, and password. Then it completes the installation with no human input. However, you do not always want this automation.

You should cancel Easy Install especially if you will do a custom disk partition or pick a different language. To cancel, just check the Do not use Easy Install box in the wizard.

Creating a Virtual Machine for Windows 10 & 11: A Hands-On Step-by-Step Guide

If you want to prepare a VM for Windows 10 or 11, you are in the right place. In this section, we cover each wizard screen one by one. Also, we explain what you do at each step and why you do it.

That way you can create your next VM with your eyes closed. After you install VMware on your Windows computer, you can start preparing a new VM.

Also, you can set up VMware Tools for file exchange between host and guest. Now you can start creating a virtual machine with VMware by following the steps below. Apply each step in order. Do not skip steps, because each one lays the foundation for the next.

Starting the Wizard and Picking Custom Setup

Step 1

Open VMware Workstation Pro. To start the wizard, first click the File menu. Then go to the New Virtual Machine option.

As an alternative, use the Create a New Virtual Machine button on the main screen. That starts the virtual machine creation wizard.

Step 2

The VM wizard asks which setup type you want to continue with. Check the Custom (Advanced) option to see more advanced settings and click Next. This choice gives full control on later screens.

Step 3

On the Select a Virtual Hardware Compatibility window, Workstation 17.0 is selected by default. This is because VMware Workstation 17 Pro is installed on your system.

If you update when a new release ships, you should pick the new version on this window. After you set VMware hardware compatibility, press Next to continue.

Step 4

The Guest Operating System Installation window has three options. Let us go through them in order.

1. Installer Disc: Check this option to install the OS from CD/DVD.
2. Installer disc image file (iso): If you add an ISO file with this option, VMware sets some settings on its own.
3. I will install the operating system later: If you want to add install media later, you set all options manually. Pro users pick this option more often.

Guest Operating System and Firmware Settings

Step 1

On the Select a Guest Operating System window, first check the OS type. Then pick the version you want to install.

If you have a Windows 10 64-bit ISO, pick Windows 10 x64 in the Version part. In the same way, pick the right version for Windows 11.

Step 2

On the Name the Virtual Machine window, type the OS name and version. That makes the VM easier to recall. If your storage device is large, you can go on with the default location.

Still, set up virtual machines on a physical SSD or NVMe disk. That gives you a cleaner and faster setup.

Step 3

On the Firmware Type window, you can set the boot options for the OS. On older Windows 10 builds, the BIOS option was the default.

On newer Windows builds, UEFI is more common. So VMware Workstation picks this option on its own. To make your virtual system safer, check the Secure Boot option too.

Step 4

On the Processor Configuration window, set the CPU and core count for your hardware. As a middle value, you can set one CPU and four cores. For more than that, keep host capacity in mind.

Memory, Network, and Disk Setup

Step 1

On the Memory for the Virtual Machine window, pick the RAM size you will assign to the VM. If your computer has 16 GB RAM and you will use one virtual PC, set 8 GB RAM. More than that strains the host OS.

Step 2

On the Network Type window, you can set the network options for the virtual machine. Changes you make in VMware’s Virtual Network Editor interface affect the network settings of virtual computers. For more on VMware network settings, see our posts below.

• VMware Bridge Configuration
• VMware NAT Configuration
• VMware Host-Only Configuration

VMware often picks NAT as the default because it suits basic use. This option appears as Use network address translation (NAT).

If you will use VMs for different network projects, the Host-Only type will help you significantly here. You can change these settings later.

Disk Configuration: Controller, Type, and Selection

Step 1

On the Select I/O Controller Type window, pick the default LSI Logic SAS option. This type offers broad OS support, so you can also pick it in server scenarios.

Step 2

On the Select a Disk Type window, the NVMe virtual disk type is selected for Windows 10. New VMware releases added the NVMe option. That lets us get a significant speed boost in virtual machines. On the other hand, NVMe is also the right pick for Windows 11.

Step 3

The Select a Disk window has three options, as in the image. These disk options serve very different goals.

1. Create a New Virtual Disk: Creates a clean new disk for the installation.
2. Use an Existing Virtual Disk: Lets you add the disk of an earlier virtual machine.
3. Use a Physical Disk: We suggest this option for advanced users. You get more performance by adding a physical disk to the VM. Also, it is more efficient to install ESXi and create VMs inside it.

Disk Capacity and Virtual Hardware

Step 1

You picked the Create a New Virtual Disk option in the prior step. Now the disk capacity window appears. At this step you set the options for the disk you will create for the VM. There are two key options.

• Allocate all disk space now: It sets aside the disk space for the VM from the host at once. That way the software does not strain your computer when it needs more disk.

1. Store virtual disk as a single file: Keeps the VM disk file as one piece.
2. Split virtual disk into multiple files: Splits the VM disk file into many parts. However, it creates clutter in the installation folder. It gives a small speed boost on a very old computer. But new computers do not need it.

This option matters for performance. Still, we do not suggest checking Allocate all disk space now for test installs. On this window, set the disk size in the Maximum Disk Size (GB) part. Also, check the Store virtual disk as a single file option.

Step 2

On the Specify Disk File window, you can set the disk name. However, leave the default name and click Next. This prevents clutter later.

Step 3

At the last stage of setup, you can do tasks such as CPU virtualization, adding an ISO, or adding hardware. Click the Customize Hardware button for this. This button brings all virtual hardware into one screen.

CPU Virtualization and ISO Adding with Customize Hardware

Step 1

The Processors window has key options for virtual machine performance. Let us go through them in order.

1. Virtualize Intel VT-x/EPT or AMD-V/RVI: Turns on virtualization for the guest on Intel and AMD hosts. This option does not work if the host does not support virtualization.
2. Virtualize CPU Performance Counters: Software developers use this option. According to the VMware documentation, if you turn on this setting, you move the VM only to a host with compatible performance counters. Also, if Fault Tolerance is on in the ESXi BIOS, some virtual counters may not work correctly.
3. Virtualize IOMMU (IO Memory Management Unit): Makes host I/O devices interact with the VM directly. That way powerful hardware such as a graphics card gets direct memory access. It lets you use host devices in guest machines through IOMMU remapping.

Check all options in the image for virtualization and memory management in the virtual machine. This is critical especially for nested virtualization.

Step 2

On the Hardware window, you can delete devices you do not want to use. For example, you can remove the printer and sound card. Now add the Windows 10 ISO file to the virtual machine. To do this, click the New CD/DVD (SATA) device.

Then press Browse under the Use ISO Image File option. Pick the ISO file you downloaded or have on your computer and click Open to add it to the program.

Step 3

Turn on the USB setting for fast file transfer between host and VM. Then change the compatibility mode to 3.1. This small setting makes a big difference in daily use.

Display Settings and Starting the Virtual Machine for the First Time

Step 1

On the Display tab, check that the Accelerate 3D Graphics option under 3D Graphics is on. This feature uses your graphics card’s power to give you a faster VM. It also lets you run software that needs high compute power inside the VM.

In the Graphics Memory part, you see the default 8 GB value. To use this value in full, you must set the VM RAM to 16 GB. Otherwise, this feature does not take effect. If your host machine has 32 GB RAM, you get much more from virtualization.

Step 2

The summary window shows the virtual machine hardware and installation location. Click Finish and move to Windows setup. This screen lets you review all your choices one last time.

Step 3

You can run the VM in two ways. Check the Power on this virtual machine option. Or click the green start button directly. Both ways give the same result.

Step 4

After you click Start, you see the virtual computer boot from the ISO file you added. The Windows 10 setup wizard comes on screen. You now do a normal Windows installation. The difference: everything happens in a virtual box.

VMware Tools Setup and Verification

You should install VMware Tools after you create a new virtual machine and install Windows 10. This tool boosts guest machine performance. If you do not install it, you get a significant performance loss.

Also, screen resolution will not fit the full screen. In addition, you cannot drag and drop files between host and guest. You can get the current release from our VMware Tools download page.

Step 1

To set up VMware Tools on the Windows 10 virtual machine, open the tool menu. Then click VM and the Install VMware Tools option. This mounts the setup package on the virtual CD drive.

Step 2

If the setup wizard does not open at the bottom right, open This PC. Then double-click the DVD drive, as in the image. The User Account Control window opens. Click Yes to let VMware Tools make changes.

Completing the VMware Tools Setup

Step 1

When the VMware Tools Wizard window opens, click Next to continue. On the Select Setup Type window, check the Complete option. That way you can also use the VM in other VMware products.

Step 2

If you want to change setup options, click Back. Press Install to start setup. In the Status part, you see the drivers for host machine devices being installed.

Step 3

After you install guest tools, click Finish. Restart the system so the changes take effect. When you open the VM menu after setup, you see the software is installed.

Also, click View / Full Screen to make the Windows 10 guest machine full screen. Then check that the screen expands.

Step 4

To confirm VMware Tools works, drag a text file from host to guest machine. If a + sign appears next to the mouse pointer, you can copy the file to the virtual machine. This simple test shows the full integration works.

Virtual Hardware Setup: RAM, CPU, Disk, and Controller Settings

A VM’s performance ties directly to the resources you give it. However, you must keep a balance here. If your main machine goes hungry, neither you nor the VMs can work.

Now we will cover ways to share resources with care. Also, you will see the effect of disk type and controller on performance with real examples.

First, remember this basic rule: every resource you give a virtual machine comes from the main machine. So the “more is better” approach is wrong. The right approach is to give the least resource that meets the OS and app needs. More than that is nothing but waste.

Virtual CPU (vCPU) and RAM Assignment: How Do You Set a Safe Ratio with Host Resources?

You set the virtual CPU (vCPU) count for each VM in VMware. But note: the vCPU count must not exceed the physical core count. If it does, the hypervisor has scheduling trouble.

Result: odd slow-downs and uneven performance. My advice is to assign at most 2 or 4 vCPU to each VM. If you do not do heavy builds, 2 vCPU is enough in most cases.

• RAM allocation: I suggest at least 4 GB for a Windows 11 VM and 8 GB for easy use. For Linux server VMs, 2–4 GB is often enough.
• vCPU allocation: 1–2 for light loads and 2–4 vCPU for dev setups is ideal. 8+ vCPU is only for special loads.
• Total resource budget: Do not give more than 50% of main machine RAM to VMs. For example, on a laptop with 16 GB RAM, total VM RAM should not exceed 8 GB.
• Memory overcommit: VMware’s memory overcommit feature lets you hand out more than physical RAM to VMs. However, it brings ballooning and page sharing into play. Be ready for performance swings.

The Lock all guest memory option protects VM RAM. This option stops the main machine from moving this RAM to the swap file.

I suggest you turn on this setting on critical server VMs. Still, this cuts the RAM the main machine can use. You must balance it well.

Also, the Fit memory option sets RAM size on its own. This setting works based on the main machine state when the VM starts. It helps especially on portable devices.

Virtual Disk Capacity, Single File vs. Split Disk Comparison

A virtual disk (VMDK) is your VM’s persistent storage space. You make two key decisions in the wizard: capacity and file layout. Capacity must be sufficient for the OS and apps.

For Windows 11, 60–80 GB; for Linux, 20–40 GB are sensible start values. However, if you do not check the Allocate all disk space now box, the VMDK grows on demand. That means you do not set aside all disk space now.

Dynamic disk allocation (thin provisioning) makes a small file at the start. The file grows as you write data. This saves disk space. However, it brings the risk of disk bloat.

You do not reclaim the space of deleted files at once. Over time the VMDK file bloats and you may need a shrink step. At this point, you can check our increase VMware disk capacity guide.

Which Should You Choose?

The Store virtual disk as a single file option keeps the whole disk in one VMDK file. The Split virtual disk into multiple files option splits the disk into 2 GB parts.

So which is better? A single file needs less file management during copy and move. However, large files can cause trouble on some file systems (for example, FAT32). A split disk offers flexibility especially for backup and portability.

There is no notable difference in performance. The choice depends fully on your move and backup habits. I personally pick the single file because moving the VM folder as a whole creates less clutter. However, do not create a 2 TB disk as one VMDK. A split layout raises your chance of recovery if it becomes corrupted.

SCSI, SATA, and NVMe Virtual Disk Controller Choice: Which One and When?

A virtual disk connects to a controller. VMware offers a few options: IDE, SATA, SCSI (LSI Logic SAS, LSI Logic Parallel, BusLogic), and NVMe.

IDE is now legacy. SATA is good for compatibility but has limited speed. SCSI, especially LSI Logic SAS, is common in server OSes. NVMe offers the highest performance. For scenarios that run old OSes on NVMe, our running Windows 7 on NVMe post may interest you.

Modern OSes (Windows 10/11 and modern Linux distros) support the NVMe controller natively.

So pick NVMe for database tests that need high IOPS. However, old OSes (Windows 7, Windows XP) do not include an NVMe driver. In this case, you must use LSI Logic SAS or SATA. Windows Server 2019 and later detect NVMe without issues.

My pick is NVMe on Windows 11 and modern Linux VMs. If you do database or build work primarily, you feel the difference.

However, if you will move a VM to ESXi, LSI Logic SAS is a safer choice because ESXi does not support the NVMe controller at the same maturity in every release.

Network Setup: NAT, Bridged, and Host-Only Difference and VMnet Choice

How a VM links to the network sets how much of the outside world it sees. VMware offers three main modes: NAT, Bridged, and Host-only. Each mode maps to a different VMnet switch.

You use VMnet8 for NAT, VMnet0 for Bridged, and VMnet1 for Host-only. Also, you can define custom networks between VMnet2 and VMnet7.

NAT mode lets your VM go out through the main machine’s IP address. Inbound links from outside cannot reach the VM directly. This is a safe and handy default.

Bridged mode links the VM directly to the physical network. The VM gets a separate IP on the same network as the main machine. Host-only mode builds an isolated network only between the main machine and the VM.

Which mode you pick depends on your scenario. NAT is ideal for a test VM that needs internet. Use Bridged if other devices on the network must see the VM.

If you build an isolated security lab, Host-only or a custom VMnet is the right pick. Remember, the wrong network mode leads to hours of connectivity issues.

NAT (VMnet8), Bridged (VMnet0), and Host-Only (VMnet1) Comparison Table

As the table shows, NAT is the most balanced option. Default NAT is enough for most developers. However, if you will open a web server to the outside world, you must move to Bridged mode.

Host-only saves the day in scenarios such as malware analysis because the VM cannot reach any place outside the main machine.

Custom VMnet, DHCP, and NAT Port Forwarding Settings with Virtual Network Editor

Virtual Network Editor is one of VMware’s most powerful but least used tools. With this tool you can reconfigure VMnet switches.

For example, in NAT mode you add a port forwarding rule to send inbound links to the VM. Or you can create a new custom VMnet and change the DHCP pool.

To open the editor, go to Edit > Virtual Network Editor in the top menu. It may need administrator rights. In the window, you list current VMnets.

When you pick a VMnet and click the NAT Settings button, the port forwarding screen opens. You define a new rule with the Add button. For example, you can send main machine port 8080 to VM port 80.

Use the Add Network button to create a custom network. Pick an empty switch from VMnet2 to VMnet7. Set the Host-only or NAT type.

Turn on the DHCP server and set the IP range. This way you can build a separate network segment for each VM group. For example, in a pen test lab, placing attacker VMs and target VMs on different VMnets increases isolation.

After You Create the VM: First Boot, Snapshot, and VMware Tools Setup

You created the VM and installed the OS. So what happens now? The first boot is the start of a set of key decisions. Take a snapshot at this stage. Then install VMware Tools. In addition, remove hardware you do not need.

These steps are a must for a healthy VM in the long run. Also, these steps are not the end of creating a virtual machine—they’re the start of ongoing care.

On first boot, complete OS updates. Check drivers. Look in Device Manager for missing drivers. Then take a clean snapshot. That way you can roll back a broken setup in seconds. This tool set offers many gains, from graphics performance to memory management.

Should You Take a Snapshot on First Boot? When and Why?

A snapshot freezes your VM state at a given moment. Disk state, memory content, and settings are saved as one. This way you can return to that moment with the Go To command.

So is it right to take a snapshot on first boot? Answer: Yes, but at the right time. Take the first snapshot right after OS setup ends, before you run updates.

That way you can return to both the clean installation and the updated release. For detailed steps, see our taking a VMware snapshot guide.

Snapshots are not magic. Each snapshot takes extra disk space. As chained snapshots (snapshot tree) grow, performance drops. So treat snapshots as a temporary safety net.

They are not for long-term backup. My rule: at most 3 snapshots on one VM at a time. Delete them from Snapshot Manager when you finish. Otherwise the VMDK file bloats and you need a shrink step.

Snapshot Manager shows all snapshots in a tree view. If you right-click a snapshot and pick Go To, the VM returns to that moment. If you pick Delete, the snapshot is deleted but the current state stays.

Delete All clears the whole chain. Note: if you hit Revert by mistake, you lose changes from that moment. So do not rush snapshot management.

VMware Tools Setup and Removing Unneeded Virtual Hardware

VMware Tools is a driver and utility set that builds the bridge between guest OS and hypervisor. The graphics driver, mouse integration, memory ballooning, and clock sync sit in this package.

We gave detailed setup steps for Windows 10 and 11 in the hands-on section above. Here we will settle for a short recap.

• Setup: With the VM on, go to VM > Install VMware Tools in the menu. On Linux, the open-vm-tools package often installs on its own. On Windows, run the setup wizard from the virtual CD drive.
• Remove unneeded hardware: Remove devices you do not use in the VM settings. For example, the sound card, printer, and USB controller are unneeded in most server VMs. Removing them cuts resource use.
• 3D graphics acceleration: Turn on the Accelerate 3D graphics option on desktop VMs. Keep it off on server VMs because 3D acceleration uses extra memory and GPU resources.

Restart the VM after VMware Tools setup. You will see screen resolution fit the main machine window. The mouse pointer now moves freely between windows. Copy-paste works. These small gains make a huge comfort difference in daily use.

VM Creation Scenarios and Decision Tree

Not every VM follows the same build. A software developer and a security researcher have different needs. Now we will present a decision tree that shows the right setup path for different scenarios. Also, we will touch on advanced topics such as canceling Easy Install and creating a VM from the command line.

The first question in the decision tree must always be: What will I use this VM for? If you need a quick test, Typical is enough. For a production-like lab, Custom is a must. And if you need automation, vmcli is the tool. This simple question heads off needless complexity.

Typical or Custom? A Scenario-Based Decision Tree

The steps below help you decide which setup mode to pick. Answer each step in order. The first branch where you say Yes shows the right path for you.

1. Will you use the VM only to go online and try an app? If yes, go to Typical mode.
2. Do you want to automate the OS installation? If yes, use Typical + Easy Install.
3. Do you have special hardware needs such as an NVMe disk, UEFI firmware, or Secure Boot? If yes, move to Custom mode.
4. Will you move the VM to another computer or to ESXi? If yes, set hardware compatibility to an older release in Custom mode.
5. Are you building a custom virtual network (VMnet2–VMnet7) or an isolated lab? If yes, pick the network type manually in Custom mode.
6. Do you target automation from the command line? If yes, head to vmcli or dictTool.

This decision tree covers most scenarios. However, exceptions always exist. For example, if you will install a Windows 11 VM, do not forget to add TPM 2.0 and Secure Boot in Custom mode. Otherwise, the setup wizard rejects you. Typical mode does not add these settings on its own.

Canceling Easy Install Auto Setup and Moving to Manual Install

Easy Install is an auto setup mode that starts when it detects an ISO. It takes a product key, user name, and password from you. Then it installs the OS with no human input. However, you do not want this automation in some cases. For example, you do not want it if you will do a custom disk partition or pick a different language pack. Or you do not want it if the installation media has more than one release.

To cancel Easy Install, go to the first wizard screen. Then check the I will install the operating system later option. This turns automation fully off.

You mount the ISO manually after you create the VM. You manage all steps during setup yourself. Users pick this method especially for Windows Server installations. Also, they pick it on Linux distros that need special setup. For example, the manual method is more flexible for installing Ubuntu on a VM.

Another way: after you point to the ISO in the wizard, the Easy Install Information screen appears. Here you can check the Do not use Easy Install box. However, this option does not appear in every release. On Workstation 17.x and later, it varies by ISO type. If you cannot see this screen, the I will install later method is the safest fix.

Creating a Virtual Machine from the Command Line with vmcli and dictTool

vmcli, which comes with VMware Workstation 17.6, makes VM creation from the command line possible. This tool is a perfect fit especially for people who want to automate repeat tasks.

With dictTool, introduced in the same release, you inspect VMX config files. Plus, you change these files. These two tools make the virtual machine creation process scriptable.

vmcli vm create --name "TestVM" --guestOS "windows11_64Guest" --memory 4096 --cpus 2 --disk 60GB

The command above creates a basic Windows 11 VM. You can change the parameters to fit your needs. For example, you can add --firmware efi to pick UEFI firmware. You can use an NVMe controller with --diskType nvme. You can open the VMX file you made with dictTool and fine-tune it. This tool saves the day in bulk VM management and template work.

Command-line tools may seem complex at first to users used to the visual wizard. However, once you learn them, you can stand up dozens of VMs in minutes.

vmcli is becoming a must-have tool especially for teams that prepare test setups in CI/CD pipelines. I also made vmcli a standard in my recent projects. It cuts human error to almost zero.

Errors and Fixes When Creating a Virtual Machine: VT-x/EPT, Hyper-V Conflict, and a VM That Won’t Start

Even the best-laid plan sometimes fails. The most common errors in VMware Workstation come from virtualization conflicts. In this section, we cover two annoying errors and their root causes. The fix steps rest on Broadcom’s official knowledge base and my field experience.

Error messages may look cryptic at first. The line “Virtualized Intel VT-x/EPT is not supported” conveys a very simple message: the hypervisor cannot reach the CPU virtualization extensions.

Either BIOS has them off or the Windows hypervisor has reserved these resources. The fix involves turning off the right layer.

Virtualized Intel VT-x/EPT is not supported Error: Root Cause and Fix Chain

When you see this error, first look at the VM log file (vmware.log). Search for the Monitor Mode line. If it says CPL0, VMware has direct hardware access. The problem lies elsewhere.

If it says UML, VMware runs through the Hyper-V API. This means performance loss and nested virtualization problems.

The fix chain has these steps. First confirm VT-x and EPT are on in BIOS/UEFI. Then turn off Hyper-V and related features in Windows. Run the bcdedit /set hypervisorlaunchtype off command. Disable VBS in the registry. Turn off Memory Integrity. Restart the system. These steps fix the problem in most cases.

If you run the VM inside an ESXi server (nested virtualization), VHV must be on. Go to VM settings in ESXi. In the CPU part, check the Expose hardware assisted virtualization to the guest OS box. This lets the nested hypervisor see VT-x/EPT. Otherwise Workstation cannot use the virtualization extensions.

VM Workstation and Device/Credential Guard Are Not Compatible Error

Device Guard and Credential Guard may be on in enterprise releases of Windows 10 and 11. These security features use virtualization-based security (VBS).

VBS reserves the Hyper-V hypervisor and VT-x/EPT. When VMware Workstation cannot reach these resources, it throws the error above. The fix is to turn VBS off.

First go to Core Isolation settings. Turn off Memory Integrity. Then open PowerShell as administrator. Check VBS state with the Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard command.

If the VirtualizationBasedSecurityStatus value is 2, VBS is on. Set the EnableVirtualizationBasedSecurity registry key to 0. Finally, run the bcdedit /set hypervisorlaunchtype off command and restart.

On a company device, central policies may lock these settings. In this case, you cannot change them even with local administrator rights. Fix: ask your IT department for an exception or run the VM on a different machine. Ignoring this error and trying to start the VM does not lead to data loss but wastes time.

As of 2026, Workstation 25H2 and 26H1 releases include gains in Hyper-V detection and compatibility. However, you still need to turn VBS off for full performance.

My advice is to talk to your company security team before you turn VBS off on any machine that will run VMs because VBS is a key layer against phishing and code injection attacks.

Fixing the VM Workstation and VBS Conflict

If the problem continues after these steps, check the vmware.log file in the VM folder. The Monitor Mode: UML line shows VMware uses the slow Hyper-V API.

CPL0 means direct hardware access. During troubleshooting, try running VMware Workstation as administrator. This can fix some rights issues quickly.

Confirming VMware Tools Works and Deleting a Virtual Machine

Checking VMware Tools after installation is a critical but ignored step. Also, cleaning up a VM you no longer need is a skill you should learn. In this section we cover both topics. First, let us start with the check.

VMware Tools is a critical package that builds the bridge between host and guest. Do not skip the check steps after you finish setup. Restart the virtual machine after setup ends.

Then open the Programs and Features list in Windows. VMware Tools showing here means the basic setup worked.

• Look at the VM summary in the VMware Workstation interface. If the state says Running or OK, the services work.
• Run the services.msc command in Windows. Find the VMware Tools service in the list and confirm its state is Running.
• Test mouse moves. If the pointer moves between windows without sticking, the drivers loaded correctly.
• Put the screen in full screen mode. If resolution fits the host screen on its own, the graphics driver is active.

If you shut down the virtual machine before VMware Tools setup ends, you may get driver conflicts on restart. Always restart after setup.

If the setup wizard does not open on its own, go to the virtual CD drive and run the setup.exe file manually. After setup ends, test the drag-and-drop feature.

Safely Deleting a Virtual Machine

You may decide to delete the virtual machine you set up. You should remove it fully especially if you do not want it to take up space on your storage device.

The files of the virtual machine you set up with the steps above sit on the C: drive. In the Virtual Machine Details part, you can see the VM location from the Configuration File label.

In VMware Workstation, you see the VM list in the Library area on the left. Right-click Windows 10 x64. If you pick Remove, you only remove the VM from the Library. However, if you want to add the VM back from the installation location, double-click the .VMX file.

To remove the VM from the host computer fully, right-click Windows 10 x64. Pick Manage from the menu. Then click the Delete From Disk option.

In the warning window, you see a message that this task is important. Click Yes in the warning that says the deletion cannot be undone. Finally, check the installation location. You see all files are gone.

If you want to keep a copy of the VM before you delete it, see our cloning in VMware guide. Cloning is the fastest way to make a safe backup before deletion.

Performance Tuning: VMware Workstation Speed Tips

Your virtual machine works but is not as fast as you hoped? A few simple setting changes can give a clear speed boost. In this section we share handy tips you can apply on both host and guest sides.

First, run VMware Workstation as administrator. If you use Windows 11 24H2, this step alone can add 10–15% speed. Then change the power plan to High Performance. These two small steps give a clear gain in daily use.

What to Do on the Host Side

• Memory setting: Do not give the VM more than half of host RAM. Overcommit leads to main OS hangs.
• 3D acceleration: Check the Accelerate 3D Graphics option on the Display tab. It is critical for graphics-heavy apps.
• Disk defrag: A virtual disk fragments over time. Run VMware’s disk defrag tool on a regular basis.
• Remove unneeded devices: Delete virtual hardware such as a sound card or printer you do not use.

Close needless background apps on your main machine. Antivirus scans that hit disk I/O hard especially cut VM performance significantly.

Consider exempting the VMware folder from antivirus scans. Also, keep Workstation current at all times. For updates, you can follow our upgrading VMware Workstation guide.

Tuning Inside the Guest Operating System

You can also tune inside the virtual machine. Turn off needless startup programs in Windows. Set the power plan to high performance. Do disk cleanup and defrag on a regular basis. Cut visual effects; animations and shadows especially use significant resources in a VM.

If you still experience slowness, think about taking a snapshot of the VM and creating a new VM. Sometimes a clean installation gives a faster result than a broken setup.

Finally, make sure VMware Tools is current. Old tool releases can cause performance loss. For updates, you can use the Install VMware Tools option in the VM menu.

Advanced Setup: Nested Virtualization and Old Release Comparison

In some advanced scenarios you need to run another virtual machine inside a virtual machine. We call this nested virtualization, and VMware Workstation 17 supports this feature. In this section we also cover points to note when you work with old VMware releases.

Nested virtualization is a powerful feature. However, you do not always need it. Remember it increases resource use. Turn it on only if you truly need it. Otherwise you waste resources.

When Do You Need Nested Virtualization?

To turn on nested virtualization, go to the Processors tab in VM settings. Check the Virtualize Intel VT-x/EPT or AMD-V/RVI option. This option lets the guest OS create its own virtual machines.

Note: nested virtualization needs direct access to host VT-x/EPT support. If Hyper-V or VBS is on, this feature does not work. You must turn off these layers with the steps in the prior section. Nested virtualization helps especially in these scenarios:

1. Installing ESXi inside a VM to run virtual infrastructure tests.
2. Trying container tech such as Docker or Kubernetes in a virtual setup.
3. Testing different hypervisors (Hyper-V, KVM) inside VMware.
4. Building isolated and multi-layer setups in cybersecurity labs.

In terms of performance, nested virtualization uses more resources than single-layer virtualization. So your host machine must be powerful.

I suggest at least 16 GB RAM and a multi-core CPU. Use the snapshot feature with care in nested VMs. Snapshot management for each layer can get complex.

Creating a Virtual Computer in Old VMware Releases

You create a new virtual computer in old or new releases of VMware Pro in almost the same way. Only new releases have certain features. If you have an old VMware Pro license, follow the steps in this post. That way you prepare a new VM.

If you use an old release such as Workstation 12 or 16, the basic steps are mostly the same. But some interface differences can confuse you.

In old releases, the NVMe disk type does not appear by default. You must pick SATA or SCSI disk types. Also, the BIOS firmware type may be the default instead of UEFI.

• Workstation 12: Windows 10 support is limited. I suggest you upgrade to the latest release.
• Workstation 16: It does not offer official support for Windows 11 guest OS. But you can run it with community patches.
• Workstation 17: It offers the newest features and the best performance.

Hardware Compatibility and Version Advice for Old Releases

Be careful on the hardware compatibility window when you create a VM in an old release. You cannot open a VM you made in a new VMware release in an old release.

So pick the compatibility level correctly. Security updates may no longer ship for old releases. If possible, always use the latest VMware Workstation release.

Old releases are ideal for legacy Windows OSes. If you want to install Windows 95 or Windows 98, these guides show you the way. Also, we have guides for Windows Me, Windows 2000, and Windows Vista.

We also prepare full guides for newer but still legacy releases. For example, we cover Windows 8 & 8.1 installation in detail.

As a result, if you work with an old release, the steps are similar. However, you miss new features and security patches. I advise you to upgrade for speed and compatibility. In the virtual machine setup process, current tools always mean fewer headaches.

Further Reading Sources for VM Setup

We picked these sources for people who want to dive into the official and technical depth of the topics in this guide. Each one rests on Broadcom or Microsoft documentation.

You may face current issues when creating a virtual machine. Release notes and knowledge base posts are the source of record especially for these issues.

• VMware Workstation Pro 25H2u1 Release Notes — Broadcom official release notes document the free license change and fixed bugs.
• Virtualized Intel VT-x/EPT Error Fix — Broadcom knowledge base official post includes monitor mode and VBS disable steps.
• Microsoft Credential Guard Documentation — primary source to see how VBS and Credential Guard work.

FAQ About VMware Virtual Machines

Conclusion: The Key to Creating a Well-Configured Virtual Machine

The virtual machine creation process with VMware Workstation is much more than following a wizard. The right prerequisites, mindful hardware picks, and a solid network setup determine the life of your VM.

In this guide we covered the difference between Typical and Custom. We also touched on disk controller choice. In addition, we worked through a wide range from snapshot management to VT-x errors. At each step, we focused on understanding the reason behind each decision.

Remember, the best VM is the one that fits your needs. It should be not more and not less. Use resources with care but sensibly. Treat snapshots as temporary insurance. Never ignore VMware Tools. And above all, do not fear error messages. Each error hides a clue about how the hypervisor works.

With Broadcom’s free license move, no barrier remains to try this powerful tool. Whether you build a software test setup or a security lab, whether one VM or dozens, a well-planned start prevents hours of debugging. Now open the wizard and take the first step.

With Broadcom’s free license move, no barrier remains to try this powerful tool. Whether you build a software test setup or a security lab, whether one VM or dozens, a well-planned start prevents hours of debugging. Now open the wizard and take the first step.