Build 22000.282 for Beta and Release Channels

CrazyKats 19,420 Reputation points Volunteer Moderator
2021-10-15T17:03:50+00:00
Windows Insider program | Windows Insider preview | Windows AI

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

131 answers

Sort by: Newest
  1. Anonymous
    2021-10-16T18:03:05+00:00

    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 😞

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-10-16T17:10:22+00:00

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

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-10-16T16:57:55+00:00

    Same Here CK and FG, broken Store

    Hi,

    Thanks for confirming.

    I was in the middle of an update, now I have to wait, but no idea when it will be fixed !🤔

    It's working again perfect this morning. Perhaps it was a server problem 🤔

    I'm not sure what it was 🤷‍♂️

    Hi,

    I had to issue a Reset of the MS Store app to get it to work again on the machines that were failing.

    Clearly MS fixed the problem on their side later yesterday. It was failing on every machine for me.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-10-16T15:51:38+00:00

    Same Here CK and FG, broken Store

    Hi,

    Thanks for confirming.

    I was in the middle of an update, now I have to wait, but no idea when it will be fixed !🤔

    It's working again perfect this morning. Perhaps it was a server problem 🤔

    I'm not sure what it was 🤷‍♂️

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-10-16T13:01:11+00:00

    Image

    FG , so am I on the public build (kb5005537) ?

    I found the answer : https://support.microsoft.com/en-us/topic/windows-11-update-history-a19cd327-b57f-44b9-84e0-26ced7109ba9

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments