Windows Server Summit 2026 | Part 10: From planning to push-button: Windows Server feature updates
Krähe mit Hut
The previous article discussed cloud-based options for migrating Windows Server or deploying the applications running on it in a serverless manner. However, some companies are unable or unwilling to migrate their servers to the cloud. This may be due to technical reasons, but it can also stem from security or compliance considerations.
Nevertheless, these companies also have options for updating and maintaining their server infrastructure. This article discusses how traditional servers can be updated to new versions with minimal effort.
The classic approach
Many companies still follow the traditional migration approach: they set up a new server and move the service or application running on it to the new server. Depending on the scenario, however, this requires careful planning, downtime, user communication, etc.—not to mention errors that may occur after the update. As a result, companies often delay the migration until the very last possible moment or even continue to operate the system beyond the end of the manufacturer’s support.
Inplace Upgrade
Inplace upgrades are already familiar from the Windows client operating system, where they have been working for many years without any significant issues. End devices can be upgraded directly to a new operating system version (provided the hardware supports it). This can be done in several ways:
- Manual installation from an installation medium
- Windows Update
- Use of software distribution/Intune
Inplace upgrades are now also well-established for server operating systems and have been working for many years. However, companies typically do not use this feature because they distrust its functionality. This should come to an end by Windows Server 2025 at the latest!
With Windows Server 2025, you can combine up to four upgrades into one—an inplace upgrade from Windows Server 2012 R2 to Windows Server 2025 is possible!
Almost all server roles support direct updates (for an overview, see here:Windows Server Upgrade - eine Übersicht). And now there's an exciting new installation option for Windows Server as well!
Inplace Upgrade with Windows Update
Some time ago, direct updates via Windows Update were already making headlines. At that time, Microsoft had accidentally enabled the feature and configured it so that servers would automatically install updates.
Microsoft has since corrected this and is now re-enabling the feature as an opt-in process (registry value) with the April 2026 update. This means servers can now be conveniently updated via Windows Update just like end devices! Companies that still want more control need not worry that their servers will update themselves. Existing solutions can still be used.
Windows Server vNext - rollback to previous version
With Windows client operating systems, you can revert to the previous version for up to 10 days after a direct update. This makes it easy to test all applications under the new version, and if problems arise, the device can be rolled back to a working version.
This feature is also coming to Windows Server with the next server version! This means that applications can be tested under the new version for a limited period of time here as well. If problems are detected, you can roll back to the last working server version. This should further alleviate concerns about performing a direct update.
Liked this article? Share it!
3 thoughts on “Windows Server Summit 2026 | Part 10: From planning to push-button: Windows Server feature updates”