Install CentOS in VMware Workstation Player on Windows

Learn how to install a supported CentOS release in VMware Workstation Player on Windows, configure virtual hardware, complete Anaconda setup, and validate the guest system.

What you will build

This tutorial creates a virtual machine (VM) on a Windows computer and installs CentOS inside it. Windows is the host operating system, and CentOS is the guest operating system.

A hypervisor is software that creates and runs virtual machines. VMware Workstation Player presents virtual CPU, memory, storage, networking, and devices to CentOS so it behaves like a separate computer while using the physical Windows computer underneath.

Unlike dual booting, virtualization does not require repartitioning the computer or restarting Windows to use Linux. You can run Windows and the CentOS guest at the same time, although both systems share the host's CPU, RAM, storage, and network connection.

Choose a CentOS release carefully

Choose a supported CentOS family release that matches your learning objective or compatibility requirement. CentOS Stream is continuously delivered in the Red Hat Enterprise Linux development flow. It is different from historical CentOS Linux, whose releases have reached end of life.

Do not use an end-of-life release for an internet-connected or production-like workload. It no longer receives normal security updates. If a course, application, or lab specifically requires an older release, isolate it and understand the risk.

Download an installation ISO for the intended architecture. On most modern desktop and laptop computers this is x86_64, also called 64-bit. Do not select a cloud image, container image, minimal boot-only image, or other specialized image unless that is the intended exercise.

Requirements and preparation

Before downloading software, confirm that the Windows host has the following:

A supported Windows version and permission to install desktop software.
A 64-bit processor with hardware virtualization support.
Enough free RAM for Windows and the guest. A practical beginner VM often starts with 4 GB of guest RAM, but the host must have additional memory available.
Enough free disk space for the ISO, VM configuration, virtual disk, updates, and future snapshots.
Intel VT-x or AMD-V enabled in UEFI/BIOS if it is disabled.

Hyper-V, Windows Hypervisor Platform, Virtual Machine Platform, WSL-related virtualization features, and security virtualization can affect VMware Player performance or compatibility on some systems. Do not disable security features casually. If VMware reports that hardware virtualization is unavailable, review the VMware and Windows configuration, then restart Windows after changing firmware or virtualization settings.

After downloading the ISO, verify its checksum or signature using the values published by the CentOS distribution channel. A checksum helps detect an incomplete or altered download before it is used as boot media.

Suggested starting resources

Component — Minimum consideration — Recommended learning configuration — Why it matters

Host RAM — Enough for Windows plus the VM — 8 GB or more is more comfortable — The guest reserves memory from the host.

Host free disk space — ISO plus virtual disk capacity — At least 50 GB free for a modest lab — VMDK files, updates, and snapshots consume space.

CPU virtualization — 64-bit CPU with VT-x or AMD-V — Enabled in firmware — Efficient 64-bit guests depend on it.

Guest memory — Depends on the selected CentOS environment — Start with 2–4 GB — More memory improves graphical and package-heavy workloads.

Guest CPU count — At least one virtual CPU — Start with 2 — More cores help builds but reduce host capacity.

Guest virtual disk — Sized for the software you will install — 40 GB for a typical beginner lab — The installer and updates need working space.

Network mode — A connected virtual adapter — NAT — It normally provides guest internet access without exposing the guest directly to the LAN.

Obtain VMware Workstation Player

Obtain VMware Workstation Player through VMware's current official download channel. Product names, availability, licensing terms, and account requirements can differ by VMware version and region, so follow the current vendor instructions.

Download the Windows installer.
Run the installer and approve the Windows permission prompt.
Accept the required license terms and keep the default installation options unless your organization requires different settings.
Restart Windows if the installer requests it.

Interface labels may differ between VMware versions. Look for equivalent options such as Create a New Virtual Machine, New Virtual Machine, or Virtual Machine Settings.

Download and verify the CentOS ISO

Use the current CentOS download channel appropriate for your selected release.
Select a 64-bit x86_64 installation ISO rather than a cloud, container, or boot-only image.
Save the ISO in a known Windows folder, such as a dedicated Downloads or Linux installation-media folder.
Record the published checksum and compare it with the downloaded file using a Windows checksum utility or PowerShell.

Keep the ISO until installation is complete and basic validation succeeds. The VMware wizard will need its full file path.

Create the virtual machine

Open VMware Workstation Player.
Start the new virtual machine workflow.
Choose installation from an ISO image and browse to the downloaded CentOS ISO.
If VMware detects CentOS, review the detected guest family and version.
If detection fails, choose Linux manually and select the nearest available 64-bit Red Hat Enterprise Linux or CentOS Linux profile. The profile mainly supplies defaults; the CentOS installer still performs the actual installation.
Give the VM a descriptive name such as centos-lab.
Select a host folder with adequate free capacity. A laptop with limited system-drive space can store the VM on a larger secondary drive.

A VM folder normally contains configuration files, virtual disks such as VMDK files, and snapshots or checkpoints if the selected product edition supports them. Keep the complete folder together when moving or backing up the VM.

Configure virtual hardware

Review the hardware summary before finishing the wizard. A conservative starting configuration is 2 virtual CPUs, 2–4 GB of RAM, NAT networking, and a 40 GB virtual disk when the host can spare those resources. Do not allocate so much RAM or CPU that Windows becomes slow or unusable.

Virtual disk choices

Choice — Advantages — Tradeoffs — Appropriate use

Single disk file — Simpler to manage and often convenient for performance — Larger single file can be less convenient to copy — A VM that stays on one host.

Split disk files — Easier to move through file-size-limited storage and some backup systems — More files must remain together — Portable labs or constrained storage systems.

Dynamically allocated storage — Starts small and grows as data is written — Can fragment and eventually consume the declared maximum — Most beginner installations.

Preallocated storage — Reserves space in advance and can provide predictable capacity — Immediately consumes the selected host storage — Fast storage with a stable, well-planned VM.

Choose a disk capacity appropriate for planned packages and desktop components. Dynamic growth does not remove the need for free host space: the file can eventually grow to its configured maximum.

Networking

Mode — Guest internet access — Local-network visibility — Best use case — Security consideration

NAT — Usually available through the host — Generally not directly visible as a separate LAN computer — Default choice for learning and updates — Inbound access is limited by the virtual NAT configuration, but guest software still needs hardening.

Bridged — Available through the local network — Guest appears more directly on the same network as the host — Services that must be reachable from other LAN devices — Treat the guest like another networked computer and protect exposed services.

Host-only — Normally no internet unless separately configured — Communicates with the host and other host-only guests — Isolated labs and host-guest testing — Isolation is useful, but it does not replace guest security.

NAT is the suitable default for most learners. Use bridged networking only when you intentionally need the guest to participate directly on the local network.

Final hardware review

Set the guest OS family to Linux and the closest matching 64-bit CentOS or Red Hat Enterprise Linux profile.
Confirm the downloaded ISO is attached to the virtual CD/DVD device and that the device is connected at power-on.
Review memory and processor count.
Review the network adapter and select NAT initially.
Check display settings and optional removable devices such as printers or USB devices.
Leave firmware at the default unless the selected CentOS release or your configuration requires UEFI.

Install CentOS with Anaconda

Anaconda is the installer used by Red Hat family distributions, including relevant CentOS releases. Start the new VM and confirm that it boots from the attached ISO.

Select the installer language.
Confirm the keyboard layout.
Set the time zone and time settings.
Open the installation destination and select the virtual disk.
For a beginner lab, choose automatic partitioning. Custom partitioning is appropriate only when you understand filesystem sizes, mount points, boot requirements, and the consequences of erasing or reusing storage.
Choose software selection. A graphical environment needs more resources; a minimal environment is useful for command-line practice.
Configure the network if the installer exposes that screen. Connect the virtual adapter and confirm the expected connection.
Set a strong root password if the installer asks for one.
Create a regular user for routine work and choose whether that user is allowed to administer the system through sudo.
Review the summary, begin installation, and wait for it to finish.

VMware Easy Install is a VMware-assisted workflow that can supply installation answers automatically for supported guests. It may prefill identity and credentials, but manual installer screens still require you to review and confirm settings. A regular user's password is not automatically the root password. Depending on the CentOS release and installation method, administrative access may be provided through sudo, a separate root password, or both.

When the installer finishes, reboot the guest. If it returns to the installer, disconnect the ISO from the virtual CD/DVD device or follow the prompt to remove installation media, then boot again from the virtual disk.

First login and validation

Log in with the regular account created during setup. Open a terminal and verify the distribution, kernel, storage, and network:

cat /etc/os-release
uname -r
lsblk
df -h
ip addr
ip route
ping -c 3 <reliable-hostname>

The first command identifies the installed CentOS family and release. uname -r shows the running kernel. lsblk lists block devices, df -h reports filesystem usage, and the network commands show addresses, routes, and name-resolution connectivity.

Use the guest's normal shutdown command or the CentOS desktop shutdown action. Avoid forcibly powering off a running guest because it can interrupt writes and damage the filesystem or application data.

Post-install integration and updates

VMware guest tools improve integration between the host and guest. In Linux, open-vm-tools commonly provides pointer integration, display resizing, time synchronization, and host-guest clipboard features where supported by the desktop session and VMware settings.

sudo dnf install open-vm-tools
sudo systemctl enable --now vmtoolsd

Desktop guests may need an additional desktop integration package depending on the CentOS version and graphical environment. If a feature does not work, check that guest isolation settings, display options, and the relevant service permit it.

Refresh package metadata and apply updates with the package manager for the installed release:

sudo dnf check-update
sudo dnf upgrade

Package-management commands vary by CentOS generation. Review the output rather than treating a nonzero check-update result as an installation failure. Reboot when an updated kernel or core system component requires it.

After reaching a known-good state, make a backup or take a snapshot/checkpoint if your VMware edition provides that capability. A snapshot is useful before experiments, but it is not a substitute for an independent backup.

Security and VM data management

Use strong, unique passwords for the regular user and root account.
Keep the guest on a supported release and install updates regularly.
Do not expose SSH or other guest services to untrusted networks unless you intentionally configure authentication, firewall rules, and updates.
Use NAT for ordinary learning unless direct LAN visibility is required.
Removing a VM from the VMware library does not necessarily delete its files. Deleting the VM folder and virtual disk files permanently removes the guest data, so verify backups before doing so.

Troubleshooting

Symptom — Likely cause — Resolution

64-bit guest unavailable — VT-x or AMD-V is disabled, another virtualization layer controls it, or the CPU is unsuitable — Enable hardware virtualization in UEFI/BIOS, review Windows virtualization features and VMware compatibility, then restart Windows.

VM cannot start because virtualization is unavailable — Firmware or Windows hypervisor conflict — Check firmware settings and Hyper-V, Windows Hypervisor Platform, Virtual Machine Platform, WSL-related features, and security virtualization without disabling protections blindly.

ISO does not boot — ISO is detached, corrupt, or not first in the boot order — Connect the CD/DVD device, verify the ISO checksum, download again if needed, and review firmware and boot settings.

Installer has no network — Adapter is disconnected, mode is unsuitable, or the host or network blocks access — Verify host connectivity, connect the virtual adapter, select NAT, and check the guest IP address and default route.

Guest has insufficient disk space — Virtual disk is too small or custom partitioning used space incorrectly — Increase capacity before installation or recreate the lab VM with more space; do not erase a disk containing data you need.

VMware and Hyper-V conflict — A Windows virtualization layer is controlling processor virtualization — Review the current VMware compatibility guidance and Windows feature configuration, then restart after any approved change.

Other common symptoms

Blank screen, EFI shell, or no bootable device: confirm the expected ISO is attached, validate it, and review firmware mode and boot order.
Windows becomes slow: power off the guest, reduce RAM and virtual CPUs, close host applications, or move the VM to faster storage with sufficient capacity.
Display resizing or copy/paste fails: install or update open-vm-tools, restart the guest or service, and check guest-isolation and display settings.
Regular user cannot administer: use an authorized administrative account and verify sudo policy and group membership. Recover or set the root password only through an authorized administrative process.

Exam-relevant notes

The host is Windows; the guest is CentOS.
A hypervisor runs isolated software-defined computers on a physical host.
An ISO image is bootable installation media represented as a file.
VT-x and AMD-V are processor virtualization extensions.
NAT is the safest simple networking default for many labs; bridged networking gives the guest more direct LAN presence.
Automatic partitioning is the beginner-friendly installation choice.
Root is the all-powerful administrative account; sudo lets permitted regular users run selected commands with elevated privileges.
open-vm-tools provides Linux guest integration features, but support depends on the guest desktop and VMware configuration.