Build 22000.282 for Beta and Release Channels

Perhaps it may be easier to get the ISO file for 22000.282 and update with that ?

Hi fg,

I find it easier, faster and safer to downland the ISO without the updates and let WU do the rest.

Remember, it will update only once to the latest build plus the .NET updates.

W.U. will not update to 22000.282 the non compliant laptop because it cannot enroll in Beta.

The ISO is doing the Update right now from 22000.258 to 22000.282 without insider channel.

This is a legacy BIOS machine 😉

oh yeah, in that case your choices are limited to full ISO or manual update.

curious why you downloaded .258 instead of .282? you wanted to update on purpose?

Finally got a few hours of sleep but I went to bed thinking about this.

How about the registry hack MS is promoting?

• Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup
• Name: AllowUpgradesWithUnsupportedTPMOrCPU
• Type: REG_DWORD
• Value: 1

Never mind, it doesn't work on legacy bios. I guess a few hours wasn't good enough 😞

Perhaps it may be easier to get the ISO file for 22000.282 and update with that ?

Hi fg,

I find it easier, faster and safer to downland the ISO without the updates and let WU do the rest.

Remember, it will update only once to the latest build plus the .NET updates.

W.U. will not update to 22000.282 the non compliant laptop because it cannot enroll in Beta.

The ISO is doing the Update right now from 22000.258 to 22000.282 without insider channel.

This is a legacy BIOS machine 😉

oh yeah, in that case your choices are limited to full ISO or manual update.

curious why you downloaded .258 instead of .282? you wanted to update on purpose?

Finally got a few hours of sleep but I went to bed thinking about this.

How about the registry hack MS is promoting?

• Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup
• Name: AllowUpgradesWithUnsupportedTPMOrCPU
• Type: REG_DWORD
• Value: 1

I saw that last week, but it never worked for me. It is actually already set to one and I never manually changed it, but the updates were still blocked.

I have to hide appreiserres.dll on the sources folder of the Installation Media or when doing W.U. in the one created by W.U. in $WINDOWS.~BT sources folder and then retry the update, it pops out the option to "fix" the problem and then resumes the download if the appreiserres.dll is hidden. (I just rename it as appreserres.dll.bak in case I want to unhide it for the compliant boxes).

Either way I can complete the installation.

The registry entry in MoSetup looks useless in my case because I miss more than just the TPM or the CPU model.

Only my working Desktop is UEFI and no TPM and a Generation 4 Processor.

I don't mess with that machine because it is my production box, all my other old boxes are legacy BIOS.

My 2 compliant machines are a DELL XPS 8930 Desktop and a Lenovo Yoga 920 Laptop.

Both work fine with any insider channel.

I keep public build Windows 11 on the Lenovo.

The XPS 8930 has Dual boot for Public Build Windows 11 and Development Windows 11.

If I want to try Beta I just enroll either box, and then restore the public build after I'm done testing.

MS is not making things easy 🤔

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.

The Raspberry has me confused

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. 😎