Build 22000.282 for Beta and Release Channels

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.

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 🤔

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 😞

I've got the Diagnostics & feedback settings the same as yours, Sibro, but WU still says I'm up to date at 22000.258. ???

Hi,

I tried to update my non-compliant PC, which is obviously neither on beta nor on RP, from build 22000.278 to build 22000.282 using an ISO compiled from a known, reputable source. As expected, I couldn't do it. The Windows installer gave me a frowned look: "This PC can't run Windows 11."

Therefore, I went back one step after I got scolded by Windows installer while it was still running and deleted some files that were giving me that frowned look.

Now I have Windows 11 build 22000.282.

As you can see, I am trying very hard to help Windows take a better shape and look.

Hi Suat,

Looks like you don't know know about appraiserres.dll trick in the sources folder ?

I updated my non compliant Legacy Bios Laptop from 22000.258 using the downloaded .282 ISO, (offline update).

The only problem I see is that the I don't get the latest Apps from MS Store because I'm not in the Insider Beta on that machine.

It will probably update when MS releases .282 to the public. 😉