Change a Virtual Machine’s Guest Operating System Type and Version in VMware Player

Learn how to change a VM’s guest OS family and version in VMware Player, understand what the setting changes, and validate the VM afterward.

VMware Player stores an expected guest operating system type and version for each virtual machine (VM). The guest operating system is the OS installed inside the VM, while the host operating system runs on the physical computer that runs VMware Player.

This profile is configuration metadata. It helps VMware choose suitable default virtual hardware and compatibility behavior, but it is not the operating system itself. You can correct the profile without reinstalling the guest, provided the VM is completely powered off.

What the Guest Operating System Setting Means

The guest OS setting contains two related values:

Guest OS family: the broad category, such as Windows or Linux.
Guest OS version: the particular release profile associated with that family.

VMware uses this information when applying or recommending virtual machine defaults. The profile can also help VMware select compatibility behavior suitable for the expected guest.

Common reasons to change it include:

The wrong family or release was selected when the VM was created.
The installed guest operating system was upgraded in place.
An imported VM has an inaccurate guest OS label.
The exact guest profile was unavailable when the VM was originally configured.

Metadata Is Not an Operating System Upgrade

Saving a new guest OS profile updates the VM’s configuration, including its .vmx file. The .vmx file is a text-based VMware virtual machine configuration file.

The setting does not change the contents of the virtual disk. It does not modify installed operating system files, applications, user data, activation status, or the actual guest OS installation.

An actual guest OS change requires a separate operation performed inside the VM, such as:

Running an in-place upgrade supported by the installed operating system.
Booting from supported installation media.
Installing a new operating system on a new or existing virtual disk.

For example, changing a Windows profile to a newer Windows release does not perform the Windows upgrade. You must boot the guest and run the supported upgrade process separately.

Before Changing the Profile

Identify the installed guest. Confirm the operating system family and release currently installed inside the VM.
Decide the intended profile. If the guest was upgraded, choose a profile that represents the installed or intended release, as appropriate for your VMware Player version.
Power off the VM completely. A running or suspended VM may prevent these settings from being edited.
Protect important data. Create a backup or snapshot if the VM contains important work and your VMware product supports snapshots. Profile selection is normally a small configuration change, but a backup is still sensible before editing an important VM.
Close active VM windows and processes. An open console or another VMware process may keep the VM locked.

Powered off means the VM has fully shut down. Suspended means its execution state has been saved for later continuation; suspension is not the same as a full shutdown.

Change the Guest OS Type and Version in VMware Player

Use the VMware Player graphical interface. No command-line command is required for the standard procedure.

Open VMware Player and locate the VM in the VMware Player library.
Select the target VM.
Open the Player menu.
Choose Manage, then choose Virtual Machine Settings.
In the settings dialog, open the Options tab.
Select General.
Locate the guest operating system family selector and the version selector.
Choose the correct family first, such as Windows or Linux.
Choose the matching release or the closest suitable version available.
Click OK to save the change.
Start the VM and verify that the installed guest boots normally.

The navigation path is:

Player > Manage > Virtual Machine Settings > Options > General

Choose the Closest Appropriate Profile

Match the selected family to the operating system actually installed in the VM. A Windows guest should use a Windows profile, and a Linux guest should use a Linux profile.

If the exact release is not listed, choose the closest available release from the correct family. A nearby supported profile is generally preferable to selecting an unrelated family merely because its version name looks newer.

Older VMware Player versions may not include profiles for newer operating systems. If a newer guest release is missing, update VMware Player to a compatible newer release if that option is available. Otherwise, select the closest appropriate family and version, then check the guest’s operation carefully.

Do not use this setting to claim that a VM contains a different operating system. For example, changing a Linux profile to Windows does not make the Linux installation boot as Windows.

What Changes and What Does Not

Guest OS family and version metadata: changed to the values you select.
.vmx configuration: updated when you save the settings.
Installed operating system files: not changed.
Applications and user data: not changed.
Virtual disk contents: not changed by this setting.
Actual OS installation or upgrade: not performed.
Virtual hardware compatibility: not automatically upgraded by changing this profile.

The setting also does not change VMware Player itself, firmware mode, disk controller type, CPU architecture, or the fundamental virtual hardware configuration. A major guest OS upgrade may require separate changes to virtual hardware, available disk space, firmware, or other requirements.

Validate the Change

Reopen Virtual Machine Settings.
Go to Options > General.
Confirm that the new family and version remain selected.
Start the VM.
Verify that the guest operating system starts normally.
Test networking, display behavior, shared folders, and device access if you use those features.
Check VMware Tools if the VM depends on improved display behavior, pointer integration, shared folders, or other guest integration features.

If you changed the profile in preparation for an OS upgrade, perform that upgrade as a separate task inside the running guest. The profile change does not replace the guest installer or upgrade tool.

Common Scenarios

Wrong profile selected at creation: power off the VM, select the correct family and closest matching release, save, and boot the same installed system.
Guest upgraded in place: update the VMware profile if appropriate, then perform and validate the actual guest upgrade separately.
Imported VM has inaccurate metadata: correct the profile without altering the virtual disk or reinstalling the guest.
Different operating system required: changing the profile is insufficient. Use supported installation media or create a separate VM for the new operating system.
VM is suspended: resume it and perform a complete shutdown before changing settings.
Exact version is unavailable: update VMware Player if possible or select the nearest suitable profile from the correct family.

Troubleshooting

The selectors cannot be edited

Confirm that the VM is not running.
If it is suspended, resume it and shut it down normally.
Close active VM consoles and retry.
Check whether another VMware process still has the VM open.

The desired version is not listed

The VMware Player release may predate the target operating system, or it may only provide broader guest profiles. Install a newer compatible VMware Player release if available. Otherwise, select the closest appropriate family and version. Do not select an unrelated family just to obtain a newer-looking version label.

Changing the setting did not upgrade the guest

This is expected. The change updates VMware metadata only. Boot the VM and use supported installation media or the guest operating system’s upgrade tool to perform the real upgrade.

The VM has boot or device problems after a major upgrade

Verify that the selected profile matches the installed guest.
Review the virtual hardware and firmware requirements of the upgraded guest.
Check networking, display, shared folders, and other affected devices.
Update or reinstall VMware Tools if guest integration features no longer work.
Restore from a backup or snapshot if the guest OS upgrade itself failed.

Limitations and Exam Notes

The guest OS profile is metadata, not an installer.
The VM must be fully powered off before changing the setting.
Choose the OS family first, then the closest matching version.
The saved change is written to the VM’s .vmx configuration file.
Virtual disk contents, applications, user files, and activation are not changed by the profile update.
The setting cannot migrate Windows to Linux, Linux to Windows, or one CPU architecture to another.
Changing the profile does not automatically change firmware mode, disk controller type, CPU architecture, or VMware Player’s own version.
Major guest upgrades may require installation media, free disk space, supported virtual hardware, and separate VMware Tools updates.

For related reading, see Change the Guest Operating System Version.