Microsoft is cracking down users upgrading to Windows 11 on unsupported hardware

Figure 1, view larger image


Microsoft removes support for dodging Windows 11's TPM 2.0 requirement.


Flyby11 is now flagged as malware by Microsoft Defender.


Flyby11's developer is working to resolve this issue.


In just over eight month's time, Windows 10 will fall out of support. Once this happens,


Microsoft is giving people still using the operating system a choice:

Either continue using Windows 10 without any future support, upgrade to Windows 11, or buy a new PC if their hardware can't support Windows 11's TPM 2.0 requirement.



Microsoft removes its documentation about dodging Windows 11's TPM 2.0 requirement

Figure 2, view larger image

In the first instance of Microsoft stopping people performing unsupported upgrades, Neowin spotted that the company had removed a block of text from its "Ways to install Windows 11" page


Previously, the page stated the following:

Microsoft recommends against installing Windows 11 on a device that does not meet the Windows 11 minimum system requirements.


If you choose to install Windows 11 on a device that does not meet these requirements, and you acknowledge and understand the risks, you can create the following registry key values and bypass the check for TPM 2.0 (at least TPM 1.2 is required) and the CPU family and model.



Microsoft Defender now flags Flyby11 as potential malware

Figure 3, view larger image


Two days after Neowin reported the change, the website spotted a new post on Flyby11's GitHub page. The update claims that Windows Defender now identifies the app as potential malware.


Flyby11 is a popular third-party tool that allows people to dodge the TPM 2.0 requirement and install Windows 11 on any machine, so Defender suddenly taking a dislike for the app does raise a few eyebrows.


It's unsure if other antivirus apps have the same reaction, but hopefully, the developer can get things worked out with Microsoft


Source - XDA 


Signing off

@Rahul S


@iQOO Connect@NITIN@Aojesh@woahyash@JStreetS


Figure 4, view larger image

Tech