Build 22000.282 for Beta and Release Channels

Yes, you get updates also on non compliant boxes, but not the beta updates because you cannot join the Beta insider, only the public build updates.

As for .NET 5.0.11 I have not seen it on any of my Beta boxes yet.

I don't use VM, my Beta machines are compliant boxes.

Isn't 22000.258 a Beta update?

That's where I'm at after KB5006674 shown above

I think an app installed 5.0 runtime and that's why I'm getting updates, but I don't know which one

The Raspberry has me confused

The complication is just with Beta. It is easier with Development Builds because I can still be on Development channel even with an unsupported box, but cannot do that for Beta channel, it just kicks it out to non insider, which works fine for public build, but cannot get the Beta W.U. directly and have to use some of the known tricks. 😎

Why confused ? Looks like you are non insider public windows 11 build.

I see now that your .NET 5.0.11 is for ARM processors, that could be why I don't see it, I only have Intel Processors x64, I don't have any ARM machines.

Confused because I'm getting updates.

Are you saying that Public gets updates even if hardware is not compliant?

Not just the Raspberry, I get .NET 5.0 on my Beta VM x64 as shown on page 8

https://answers.microsoft.com/en-us/insider/forum/all/rs-prerelease-build-224781012-kb-5007328-is-out-to/c483c51c-1159-4691-b088-c4625d3645f4?page=8

Yes, you get updates also on non compliant boxes, but not the beta updates because you cannot join the Beta insider, only the public build updates.

As for .NET 5.0.11 I have not seen it on any of my Beta boxes yet.

I don't use VM, my Beta machines are compliant boxes.

The Raspberry has me confused

The complication is just with Beta. It is easier with Development Builds because I can still be on Development channel even with an unsupported box, but cannot do that for Beta channel, it just kicks it out to non insider, which works fine for public build, but cannot get the Beta W.U. directly and have to use some of the known tricks. 😎

Why confused ? Looks like you are non insider public windows 11 build.

I see now that your .NET 5.0.11 is for ARM processors, that could be why I don't see it, I only have Intel Processors x64, I don't have any ARM machines.

Confused because I'm getting updates.

Are you saying that Public gets updates even if hardware is not compliant?

Not just the Raspberry, I get .NET 5.0 on my Beta VM x64 as shown on page 8

https://answers.microsoft.com/en-us/insider/forum/all/rs-prerelease-build-224781012-kb-5007328-is-out-to/c483c51c-1159-4691-b088-c4625d3645f4?page=8

The Raspberry has me confused

Why confused ? Looks like you are non insider public windows 11 build.

I see now that your .NET 5.0.11 is for ARM processors, that could be why I don't see it, I only have Intel Processors x64, I don't have any ARM machines.

I guess you didn't see my edit before posting 😁

I used to use the appreiserres.dll hack on all the non-compliant machines but my yellow zone laptop allows me to clean install and update so I don't need to do it anymore, the other PCs all went back to W10 since.

On the Beta VM I was also using the hack until we learned of TPM and encryption, now it's possible with the flag Johnny discovered.

@Sibro.o,

I have build 19044 on non compliant boxes normally, but I still check with Windows 11 to see how far it let me go. 😉

The complication is just with Beta. It is easier with Development Builds because I can still be on Development channel even with an unsupported box, but cannot do that for Beta channel, it just kicks it out to non insider, which works fine for public build, but cannot get the Beta W.U. directly and have to use some of the known tricks. 😎