Incompatible hardware? Expect permanent watermark soon

No worries:

Brink said:

No worries:

Remove "System requirements not met" Watermark on Windows 11 Desktop Tutorial

This tutorial will show you how to remove the "System requirements not met" watermark on the desktop for your account in Windows 11. Starting with Windows 11 Insider Beta and Release Preview channels build 22000.588 and Windows Insider Dev channel build 22557, you will see a System requirements...

www.elevenforum.com

Click to expand...

I just updated my old, unsupported Asus laptop to 22621.1265 and no watermark appeared. I downloaded your reg file just in case it ever does.

It really begs the question - have they not more important things to do?

Fabler2 said:

It really begs the question - have they not more important things to do?

Click to expand...

Emoji16, Emoji17, Emoji18, & Widget 10, Widget11, Widget12 etc.?

cereberus said:

Emoji16, Emoji17, Emoji18, & Widget 10, Widget11, Widget12 etc.?

Click to expand...

I was just going to post that they needed a break from creating new emoji's.

Fabler2 said:

It really begs the question - have they not more important things to do?

Click to expand...

Revenue protection is THE most important thing

Edit: Stricter and stricter measures will follow over time, that's quite predictable

Haydon said:

Edit: Stricter and stricter measures will follow over time, that's quite predictable

Click to expand...

I look for that to happen with Windows 12 or whatever MS decides to call the next version.

It follows no logic whatsoever, 'cept maybe some deeply embedded legalities.
Should be a non-issue!

I'm at 22621.1265 and I have NO watermark either. I also have no SV2 DWORD in HKEY_CURRENT_USER / Control Panel / UnsupportedHardwareNotificationCache either, just the (Default). So I created the SV2 32bit DWORD and gave it a value of 2. Just in case. Or should it be 0??

@Brink's tutorial cited above specifies SV2 = 0 ("SV2"=dword:00000000) for your system, @Lance1.

Wisewiz said:

@Brink's tutorial cited above specifies SV2 = 0 ("SV2"=dword:00000000) for your system, @Lance1.

Click to expand...

Made the change. Thank you.

The W11 system requirements that fit on a small webpage, is most likely the product of at least one million manhours, involving MS, Intel, AMD, a myriad other companies and their respective marketing, legal, and engineering departments, all serving the almighty $.

The one million manhours is not a hyperbole, most likely the second million is being spent.

It's not a mom-and-pop's decision to put up a watermark, it's really a very small cog in a gigantic machinery

Lance1 said:

Made the change. Thank you.

Click to expand...

Always welcome. Brink is always frightfully busy, so I thought I'd jump in and suggest the edit instead of waiting for him to get to it.

So far the watermark is being seen only on a selected few machines as it seems MS is in some sort of testing phase of rolling out the watermark. I knew that getting rid of the watermark is not a new thing, but what IS new is it is appearing on some 100% compatible systems, some which came directly from the OEM with Windows 11 installed.

Those who have installed 11 on incompatible hardware know they are incompatible. They came to forums such as this and found all the workarounds how to make it work and will also run to forums such as this to find out how to get rid of the watermark. It's Grandpa and Grandma who got 11 through Windows Update or who ran out and bought a new PC with 11 on it that will be be panicked unnecessarily when they receive this watermark unexpectedly and not know what to do about it. Mass chaos will ensue if MS doesn't do something about their scanning of hardware PDQ.

glasskuter said:

Mass chaos will ensue if MS doesn't do something about their scanning of hardware PDQ.

Click to expand...

MS should only check for compatibility at the time of the install. If someone had to use one of the work arounds to install Windows 11, I think they already know that the computer doesn't meet the requirments.

@Winuser Exactly what I meant to imply. They KNOW they are incompatible and should have expected all along that MS would at some point start pointing it out.

History shows MS does things in stages so as not alienate their user base in one fell swoop. MS is not designing only for the here and now, but no telling how many years on down the road.

I've long expected MS would start clamping down on incompatible users in one way or another. Win11 is MS fledgling OS when it comes to imposing hardware restrictions. I think the watermark is just their first step. Getting windows updates may be next. IMO, at some point, maybe Win 12 or 13 or 14, the OS will be locked down tighter than a jug so that no workarounds will work to install it if one is not compatible. Who knows. MS could actually make it so that no OS, other than the one the OEM installed, could be installed. I'm not saying it will happen, only that it could.

Folks fail to understand that any workaround works ONLY because MS has left the door open for it.

My point is MS should have measures in place so as not to be rolling out this watermark on fully compatible machines and especially to any machine that has Win11 embedded in its UEFI.

No plan execution is error free, it will likely be corrected the next WU.

No plan execution checking is one-time only, it will be checked on on an on-going bases, likely every WU even.

A user, who is a complete noob, allows their more than capable Windows 10 PC to upgrade to Windows11, through the coercion of MS.
Upon Restart, the PC boots to the Desktop, and the user sees the likes of this on the Desktop...



... what do you think is going through that user's naive mind, about what his or her next steps should be!?!?!?

What's a complete noob doing getting Insider builds?