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

@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:

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 your local time is ...😎

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

@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:

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 🤔

@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:

@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 🤣

Bug report,

Logging into windows causes my default speakers to always start as muted(but only system sounds), but then selecting the sound does not show source as muted. Work around seems to be to mute audio source, and then unmute to return to normal function.

Mine maintains the state that it was when I sign out or shutdown, if it was muted it comes back muted, if it was on it comes back on.

I saw one case on a Laptop that had a Realtek audio manager behaving strange in a similar way as you describe.