Windows 11: Microsoft enforces TPM 2.0 on virtual machines

Windows[German]That's it for Windows 11 – at least with older hardware, if I'm right. If the hardware requirements already caused head shaking and unstoppable enthusiasts were looking for ways to install the operating system on machines that did not meet the requirements, this will now be blocked. In the latest Insider Build, Microsoft makes a TPM 2.0 and secure boot mandatory for virtual machines to run Windows 11.


I've begun omitting mention new Windows Insider Preview builds within my blogs (unless there are earth-shattering new features). A good week ago, on 9/9/2021, Microsoft had released Windows 11 Insider Preview build 22454 in the Developer Channel (see Announcing Windows 11 Insider Preview Build 22454). On Twitter, users reported that their upgrade to this Insider build failed because TPM 2.0 was missing.

Windows 11 Build 22454 requires TPM 2.0

The colleagues from MSPU had mentioned this here. On September 16, 2021, Microsoft then released the Windows 11 Insider Preview build 22000.194 in the Beta Channel (see Announcing Windows 11 Insider Preview Build 22000.194). So far so bad, because the following statement can now be found in the announcement:

This build includes a change that aligns the enforcement of the Windows 11 system requirements on Virtual Machines (VMs) to be the same as it is for physical PCs. Previously created VMs running Insider Preview builds may not update to the latest preview builds. In Hyper-V, VMs need to be created as a Generation 2 VM. Running Windows 11 in VMs in other virtualization products from vendors such as VMware and Oracle will continue to work as long as the hardware requirements are met. For more details on the Windows 11 system requirements – see this blog post here.

In a nutshell: Virtual machines also need the same hardware requirements as bare metal instances. This also includes support for TPM 2.0. Microsoft is already making 2nd generation VMs mandatory for Hyper-V. The hypervisors from VMware and Oracle Virtualbox should still work as long as the Windows 11 hardware requirements are met. 


I had already seen it in various tweets throughout the night – the colleagues at Techdows addressed it in the above tweet and in this article. Without TPM 2.0 and Secure Boot, upgrading a guest with Windows 11 a feature upgrade in virtual machines no longer works. While reinstalling a Windows 11 build in a VM might still work, it doesn't make sense to reinstall your OS every year to get the next feature update. So I have to say, bye, bye, that's it.

Similar articles
Yes, Microsoft introduced Windows 11
Windows 11: Hardware requirements
Windows 11 Compatibility tests (PC Health Check, WhyNotWin11)
Windows 11: These features disappear
Windows 11: No TPM required?
Windows 11: First Insider Preview Build 22000.51
Microsoft defends the minimum Windows 11 system requirements
Has Intel revealed the October 2021 release date and name for Windows 11?
Microsoft explains the Windows 11 context menu and the Share dialog
Windows 11: Microsoft talks about the centered start menu
Windows 11: Microsoft AMA , the HW requirements, app updates and other insights
Windows 11 ISO install image file released (August 2021)
Windows 11: Microsoft specifies hardware requirements, no blocking on incompatible devices
Windows 11: PC Health-App updated, release date and no updates for non-compatible systems?
Windows 11: Rollout is the starting October 5, 2021
Windows 11: Microsoft breaks start menu/taskbar with teams promo
Windows 11 News (Sept. 2021)

Cookies helps to fund this blog: Cookie settings

This entry was posted in Virtualization, Windows and tagged , , . Bookmark the permalink.

2 Responses to Windows 11: Microsoft enforces TPM 2.0 on virtual machines

  1. Raphael Groner says:

    Release Notes für VCSA 7.0 Update 2c:
    "Discontinuation of Trusted Platform Module (TPM) 1.2 in a future major vSphere release"

  2. EP says:

    from Bleeping Computer – Windows 11 is no longer compatible with Oracle VirtualBox VMs:

Leave a Reply

Your email address will not be published. Required fields are marked *