Summary of Windows 11 situation before official release: Windows frontline (1/2 page)

Windows 11 general release is looming on October 5th. As mentioned in previous reports, we basically adopted a rolling update method, and delivered sequentially to devices that were "Eligible" for the hardware requirements of Windows 11 using existing Windows 10. done. In addition, the latest OEM hardware, such as the new Surface products that appeared at the hardware event the other day, will be shipped with Windows 11 preinstalled.

When Windows 11 had just started test distribution to early users through the Windows Insider Program, upgrades were made to PCs that did not meet the minimum operating requirements of the OS through the "PC Health Check" app. was not provided, but it was actually possible to install and run by bypassing the checking program, which was considered a kind of loophole.

This was the same when introducing the ISO via the Media Creation Tool, and it seemed that Microsoft had implicitly prepared a way to install it on non-compatible PCs, but the company itself said, "We will stop updating in the future. It also warns that it will do ", and there is a suspicion that it is necessary to replace the hardware in order to satisfy the two conditions of "secure boot with TPM 2.0" and "CPU that meets the requirements" that many users stumbled upon. was

In conclusion, at the beginning of September, when the Windows 11 test window was expanded to Release Preview, I had already participated in the Windows Insider Program Dev Channel and Beta Channel and introduced Windows 11 Insider Preview. It is reported that users who do not meet the hardware requirements are now being warned to revert to Windows 10. In fact, Microsoft added a statement to that effect in a blog post when Build 22449 was delivered to both channels on September 2 (US time).

Users encountering this message are also effectively unable to receive the latest builds and updates in the Dev Channel or Beta Channel, and have similar problems deploying ISOs via the aforementioned Media Creation Tool. believed to occur.

We will discuss why Microsoft is so strict about hardware requirements on another occasion, but some developers have actually released a program that bypasses the hardware requirements check in the Media Creation Tool. there is

The "wrapper" program for the Media Creation Tool published on GitHub, as described by Neowin, runs Builds 22449 through 22463 on unsatisfactory hardware (a virtual machine on VirtualBox, to be precise). A screenshot from Bleeping Computer shows that the update to .NET is working.

However, this may cause unexpected troubles and instability, and may result in “ It is considered temporary because the "hole" may be blocked, but users of incompatible hardware should continue to use Windows 10 until the end of support in 2025, or buy new hardware. may be wise.