Guidance for in-place upgrade of Windows Server 2012/2016/2019/2022/2025

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

In-place upgrade of the guest operating system (between major OS release versions, such as Windows Server 2012, Windows Server 2016, Windows Server 2019, Windows Server 2022 or Windows Server 2025) is not recommended. The best practice is to install a new major OS release in a new VM.


Support considerations:

• Read OS vendor's documentation to ensure the specific upgrade scenario and method are supported, e.g.: Overview of Windows Server upgrades.
• If the OS vendor does not support a particular upgrade scenario, then VMware will not be able to provide support for such scenarios due to lack of ability to collaborate with the OS vendor.
• In-place upgrade is a feature of the operating system, if problems are encountered, it is best to first contact the OS vendor for assistance. If the OS vendor has narrowed down problem to be specific to VMware software, then VMware can provide assistance.
• Some VMware products do not support in-place upgrade of the guest operating system in a VM. For more details, see VMware support for guest operating system upgrade (2018695).
• Check VMware Compatibility Guide to ensure new operating system version is supported as guest on the VMware product.
• Check the configuration of VM to ensure that it meets requirements to run new OS release. New major OS releases sometime increase the minimum require amount of memory, video ram, disk space, etc. In addition, performing OS upgrade consumes disk space, so ensure VM has adequate storage to complete the upgrade. It may be necessary to power off the VM to make some of these adjustments before starting the upgrade.
• For all applications running in the OS, contact the application vendor to determine their support policies and guidance for conducting operating system upgrades.
• After upgrading, the change will not reflect in the "Guest OS Version" field on the VM until it has been powered off and the option is changed in settings:
  • Actions > Edit Settings... > VM Options > General Options > Guest OS Version

Environment

VMware vSphere ESXi 8.0.x
VMware vSphere ESXi 7.0.x
VMware vSphere ESXi 6.7

Resolution

Before guest OS upgrade, upgrading VMware tools to the latest version available for current Windows release, test installation on a cloned VM firstly, taking snapshot of the VM or saving backup of the VM are recommended.
If you have a Windows Server 2022 ISO image used for Windows Server 2022 installation, you can follow below procedure:

1. Mount this ISO file to the VM, select “Virtual Machine -> Edit Settings -> CD/DVD drive -> Datastore ISO file”, click “Browse” to select the Windows Server 2022 ISO file from datastore as CD/DVD media.
2. Logon to the guest OS and double-click CD-ROM from the File Explorer.
3. Follow the installation prompts to complete the OS upgrade.
4. Upgrade or reinstall VMware tools after OS upgrade is done.
5. Shutdown VM, select “Virtual Machine -> Edit Settings -> VM Options -> General Options”, change “Guest OS Version” to “Microsoft Windows Server 2022 (64-bit)”, “Microsoft Windows Server 2019 (64-bit)” or “Microsoft Windows Server 2016 and later (64-bit)”.

For Windows Server 2022 guest operating system option see this KB84239

Additional Information

Known issues:

1. The VSock library DLLs for the VSock protocol are registered during vsock install by VMware Tools installer, this VSock protocol registration gets broken and lost over the OS upgrade, causing the socket creation requests fail.

Workaround:
Uninstall and reinstall VMware tools after OS upgrade.

Resolution:
This issue is resolved in VMware tools 11.3.0.

2. Uninstalling VMware Tools after Windows upgrade from Windows Server 2016 or Windows Server 2019 to Windows Server 2022 causes loss of access to storage and network - KB Article

3. Guest OS in-place upgrade to Windows Server 2022 or Windows 11 failed after upgrading VMware Tools to 12.0.5 or later on vSphere - KB Article