Are you using Windows 11 on an “un-upgraded” system? You could soon have a nasty surprise

With the 22H2 version of Windows 11Microsoft intends to make it clear to users that they do not have the required configuration.

Some users of build 22621 have indeed reported the harmful presence of a clearly visible inscription on the screen indicating that the system requirements for proper functioning of the operating system are not satisfied.

The mark of shame

It had started more subtly, with the addition last year of a command in the Windows 11 system settings. This was intended to remind users that Microsoft’s new OS was running on an incompatible machine, with the possibility of learn more “.

Things have since taken a much less subtle turn. Some indeed now deplore the presence of such an indication directly on the Desktop, accompanied by the Windows version and the build installed.

This new development came with build 22621 of the already unloved Windows 11 version 22H2, partly due to numerous performance issues. Especially since the list of processors supported by the OS has only seen a few minor adjustments since the deployment of version 21H2.

How to hide this mark that we cannot see

Fortunately, in case such a red-hot brand comes to torment you, there are various steps to follow to make it disappear. The first, however, requires editing the registry, which calls for some caution in execution:

• Search “Regedit” in the search box;
• Find “UnsupportedHardwareNotificationCache” in HKEY_CURRENT_USERControl Panel path;
• Change the value of SV2 DWORD in this folder from 1 to 0;
• Save and refresh.

To anticipate protests from other users, Microsoft also offered a less risky solution:

• Type “Group Policy” in the search bar;
• Click on “Edit group policy”;
• Go to the Local Computer Policy > Computer Configuration > Administrative Schemes > System category;
• Enable the “Hide messages when Windows system requirements are not met” option.

In both cases, the terrible mark should no longer bother you… at least until a future update which would “inadvertently” reactivate it.

Source : Deskmodder