CO-Release Build 22000.132 is out to Dev & Beta Channel

CrazyKats 19,330 Reputation points Volunteer Moderator
2021-08-12T17:00:19+00:00

Live in W.U.

Windows Insider program | Program announcements and registration | Communications and announcements

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

210 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Sumit 44,306 Reputation points Volunteer Moderator
    2021-08-13T04:15:32+00:00

    Anyone got Mail and Calendar app? I got the other two, but not Mail.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-08-13T04:09:31+00:00

    @Sibro.o,

    F.Y.I.

    The (Shift + Restart) Process1_Initialization_Failed is now gone with 22000.132.

    The 22000.132 ISO looks OK from a couple of tests I tried.

    I downloaded the ISO and tried a repair in-place, the bug is non-existent as you found out but my installation got messed up. Restored a .120 backup image, updating again within active hours but look at this nonsense 🤣

    I've updated 4 machines with .132 ISO, I have not seen the red message you show. Who is setting your policies ? The Insider channel ?

    My active hours are set like this:

    Image

    I set the policy, I don't let WU download drivers. I was pointing out that Windows wants to restart within active hours against settings in place to specifically avoid it.

    edit: and btw, I'm still missing Windows terminal from Start context menu after the second update. Maybe is time for a clean install 🤔

    From the screen shot , I have no idea what you local time is ...😎

    And that screen shot look like a windows 10 settings..

    I'm in the West Coast, close to 9pm now. You're correct, it looks like W10 because I used build .120 but without updates, call it 22000.1 if you will

    OK, we are on the same time zone, good to know. 😉

    I noticed one thing, with .120 and .132, When I go to restore my Windows 10 Image on the machine that was updated to Windows 11, I have to use the reformat option, or the restore gets stuck when trying to restore the second volume on my SSD.

    Never had that issue staying within the Windows 10 family.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-08-13T04:03:25+00:00

    Further to the .132 blog & specific to Dev Channel...

    First set of Windows app updates rolling out to Windows Insiders for Windows 11

    She posted that already on page one 😉

    Image

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-08-13T03:57:08+00:00

    @Sibro.o,

    F.Y.I.

    The (Shift + Restart) Process1_Initialization_Failed is now gone with 22000.132.

    The 22000.132 ISO looks OK from a couple of tests I tried.

    I downloaded the ISO and tried a repair in-place, the bug is non-existent as you found out but my installation got messed up. Restored a .120 backup image, updating again within active hours but look at this nonsense 🤣

    I've updated 4 machines with .132 ISO, I have not seen the red message you show. Who is setting your policies ? The Insider channel ?

    My active hours are set like this:

    Image

    I set the policy, I don't let WU download drivers. I was pointing out that Windows wants to restart within active hours against settings in place to specifically avoid it.

    edit: and btw, I'm still missing Windows terminal from Start context menu after the second update. Maybe is time for a clean install 🤔

    From the screen shot , I have no idea what you local time is ...😎

    And that screen shot look like a windows 10 settings..

    I'm in the West Coast, close to 9pm now. You're correct, it looks like W10 because I used build .120 but without updates, call it 22000.1 if you will

    Was this answer helpful?

    0 comments
  5. Drew - 810 Reputation points
    2021-08-13T03:49:10+00:00

    Was this answer helpful?

    0 comments