VMware ESXi and vSphere Cluster Management

Change a Virtual Machine Guest Operating System Version in VMware Workstation Player

Learn how to change a VM's configured guest OS type and version in VMware Workstation Player without upgrading the operating system installed inside the VM.

What the Guest Operating System Setting Means

A virtual machine (VM) is a software-defined computer that runs inside VMware Workstation Player. The guest operating system is the operating system installed and running inside that VM.

When you create a VM, VMware asks you to select a guest OS type, such as a Windows or Linux family, and a guest OS version, such as a particular release. VMware stores this selection as part of the VM configuration.

You may need to correct this setting if you selected the wrong operating system profile during VM creation. You may also update it after completing a supported operating system upgrade inside the VM so that the VMware profile matches the newly installed release.

VM Configuration Versus an Actual Guest OS Upgrade

The VMware setting describes the installed guest to the virtualization software. It can help VMware choose suitable default behavior and compatibility assumptions, but it is not an operating system installer.

Action	Where it is performed	What changes	What does not change
Changing the guest OS type or version in Virtual Machine Settings	VMware Workstation Player	The VM's declared operating system profile and configuration metadata	The installed guest OS, applications, user files, and OS version
Installing or upgrading the OS inside the virtual machine	Inside the running VM, using installation media or the OS upgrade process	The actual operating system installed in the VM	The VMware profile does not automatically become correct in every case; verify it afterward

An actual guest OS change requires an in-place operating system upgrade, installation media, or a new operating system installation within the VM. Use the VMware setting to correct metadata or align it with an upgrade that has already been completed.

Before You Begin: Fully Shut Down the VM

The target VM must be powered off before you edit this setting. Powered off means the guest has completed a full shutdown and is neither running nor suspended.

VM state	Can settings be safely changed	Recommended action
Powered off	Yes	Proceed with editing the VM settings.
Running	No	Shut down the guest from inside its operating system, then confirm that the VM is powered off.
Suspended	Do not treat this as powered off	Resume the VM if necessary and perform a full guest shutdown. Do not rely on a suspended state for this change.

Settings may be unavailable while the VM is running, and changing configuration while the VM is active can cause inconsistent behavior. Do not use a forced power-off as your normal shutdown method because it can risk guest file-system damage.

Change the Guest OS Type and Version

Open VMware Workstation Player and select the target VM in the VM library. The VM library is the interface area where registered virtual machines are selected and managed.
Confirm that the VM is fully powered off, not running or suspended.
Open the Player menu and choose Manage, then Virtual Machine Settings.
```
Player > Manage > Virtual Machine Settings
```
In the Virtual Machine Settings dialog, open the Options tab. The Options tab contains general VM configuration choices rather than emulated hardware settings.
Select the General page.
Locate the Guest operating system and Version controls.
Choose the correct operating system family first, such as the appropriate Windows or Linux family.
Choose the release or version that matches the operating system currently installed in the VM. If you completed an OS upgrade inside the VM, select the profile corresponding to the new installed release.
Confirm the change using the dialog's confirmation button, such as OK or the available save control.

The exact list of operating system families and versions depends on your VMware Workstation Player release. Select a profile that describes the actual guest rather than the version you hope to install later.

What Happens to the .vmx Configuration File

VMware records the selected guest OS profile in the VM's text-based .vmx file. This file stores virtual machine configuration values, including guest OS metadata.

The normal GUI procedure updates this configuration automatically. You do not need to edit the file manually.

Verify the Change

With the VM still powered off, reopen Player > Manage > Virtual Machine Settings > Options > General.
Confirm that both the guest OS family and version show the values you selected.
Start the VM and verify that the installed guest operating system boots normally.
Check important devices and applications if the change followed a guest OS upgrade.

A profile matching the actual installed operating system helps VMware apply suitable defaults and compatibility assumptions. It does not repair an incomplete OS upgrade or guarantee compatibility with unsupported software.

Before major guest OS work, consider creating a backup or snapshot when your product edition and workflow support it. A recovery point is especially useful before an in-place upgrade.

When This Procedure Is Appropriate

Incorrect profile during creation: A Linux VM was created with the wrong family or release. Shut it down, select the profile matching the installed Linux distribution and version, and save.
OS upgrade already completed: The guest was upgraded from one supported release to another inside the VM. After confirming the upgrade succeeded and shutting down the VM, update the VMware version field to match.
Metadata correction: The installed OS has not changed, but the VM's declared profile was inaccurate. Correcting the profile does not alter the guest.

Do not present this procedure as a substitute for upgrading Windows, Linux, or another guest operating system. Selecting a newer version in VMware alone leaves the installed OS on its existing release.

Unavailable or Unsupported Versions

If the desired version is not listed, first verify that the operating system family is correct. The VMware Workstation Player release may not provide a profile for that specific release.

When necessary, select the closest appropriate supported profile, then check VMware and guest operating system compatibility information before relying on that setting for a newer or unsupported release. The closest profile is a configuration choice; it does not certify that the guest OS is supported.

Troubleshooting

The Guest OS Controls Cannot Be Changed

Shut down the guest completely. A running VM is not ready for this edit.
Make sure the VM is not suspended. Resume it if needed, then perform a full shutdown.
Verify that you selected the intended VM in the library.
Open the correct page: Options > General, not a hardware settings page.

The Desired Version Is Missing

Check the selected operating system family first.
Confirm whether your VMware Workstation Player release offers that guest profile.
Select the closest appropriate supported version when necessary.
Check compatibility information before treating the profile as support for a newer guest release.

The Installed OS Did Not Change

This is expected. The procedure updates VM metadata in the .vmx configuration; it does not run an operating system installer. Perform the guest OS installation or upgrade separately inside the VM.

The VM Has Boot or Device Problems After an OS Upgrade

Verify from inside the VM that the guest OS upgrade completed successfully.
Power off the VM and confirm the configured guest OS family and version.
Review whether the selected profile matches the installed release.
Use a backup or supported snapshot recovery path if the guest upgrade failed and recovery is needed.

Key Exam Notes

The guest OS type and version are VM configuration settings selected initially during VM creation.
The VM must be fully powered off before editing the setting; suspended is not the same as powered off.
The navigation path is Player > Manage > Virtual Machine Settings > Options > General.
The setting changes VMware metadata stored in the .vmx file, not the installed operating system.
An actual guest OS upgrade requires an OS upgrade or installation process inside the VM.
After saving, reopen General settings and boot the VM to verify the profile and guest behavior.

For related guidance, see changing the guest operating system version.