Talk about unsupported configurations.

Right , FG ! The Point is " my machine won't support Dev updates "

@WoldfBoy,

Even less chances of getting updates on the Public Release Build 22000.xxx next month with an unsupported box !

If you can do System Image Backups you can easily try both 22000xxx and 22xxx.xxxx any time you like, just restoring one build or the other.

Apparently you don't do backups either. 😉

No. 😥

Maybe you can open a "Go fund me" and find a way to get a PC that meets the hardware requirements ?

Maybe trade yours to somebody not interested in Windows 11. 😎

I have 4 machines in the Red Zone, so you are not alone, those 4 machines will be fine with Windows 10 at least till 2025. 😊

By that time, who knows ? I could be dead, in the US we are surrounded by antivaxxers imbeciles.... 😜

Where are you located ?

Right , FG ! The Point is " my machine won't support Dev updates "

@WoldfBoy,

Even less chances of getting updates on the Public Release Build 22000.xxx next month with an unsupported box !

If you can do System Image Backups you can easily try both 22000xxx and 22xxx.xxxx any time you like, just restoring one build or the other.

Apparently you don't do backups either. 😉

No. 😥

Right , FG ! The Point is " my machine won't support Dev updates "

@WoldfBoy,

Even less chances of getting updates on the Public Release Build 22000.xxx next month with an unsupported box !

If you can do System Image Backups you can easily try both 22000xxx and 22xxx.xxxx any time you like, just restoring one build or the other.

Apparently you don't do backups either. 😉

First he wanted to go to Dev 22454, then when he was almost there he changed his mind.

He just doesn't know what he really wants.

With a red zone box (legacy BIOS), I've gone from a 19043.1202 public build, (Non insider) to 22000.184 and then from 22000.184 to 22454.1000 R.P. and then changed to Dev.

There are tricks to work around the obstacles (for now) and do all this, but what's the point if the machine is not supported ?

Right , FG ! The Point is " my machine won't support Dev updates "

I believe the jury is still out about that, and most likely there will be witty users coming up with tricks to bypass MS blocks just as they did this time around.

@Sibro.o,
I'm on a red box in Dev channel and getting all the updates, but I'm sure talking about it on this thread will cause MS to put some more nails on the road and close the holes.

Probably much more strict once the public release is out.

WolfBoy needs to make up his minds and decide what he wants to do.

Can be fun for a while, but I think I'm done with this game. 🤣

First he wanted to go to Dev 22454, then when he was almost there he changed his mind.

He just doesn't know what he really wants.

With a red zone box (legacy BIOS), I've gone from a 19043.1202 public build, (Non insider) to 22000.184 and then from 22000.184 to 22454.1000 R.P. and then changed to Dev.

There are tricks to work around the obstacles (for now) and do all this, but what's the point if the machine is not supported ?

Right , FG ! The Point is " my machine won't support Dev updates "

I believe the jury is still out about that, and most likely there will be witty users coming up with tricks to bypass MS blocks just as they did this time around.