RS-Prerelease Build 22533.1001 is out to Dev Channel + ISO

Certainly, would think there is no relation, but

1. Yes, flags can/do change, but that is not the same as ALL one had suddenly gone and left with NONE enabled and having to replace any & all one had (that are still available, of course. This is 'out of the blue', except for JUST going to a new IB.
2. The point here has to do with receiving new Builds and discovering nay & all flags one had having to be re-enabled. It never happens with Edge in Win10 (and likely not in regular Win11s. However, this is far from the 1st time that immediately with a new Build find NO flags set, as they were, in Edge... normally, with new Builds & or Edge updates this ISNOT the case. But, as stated, this is not the 1st time I had it happen after going to a new Build. I mention it because of how odd it is, since there should be no relation, at all. Have always found it weird, really peculiar & inexplicable when it does or has happened.

From the past times, I was directed to report it, which I did, yet it happen, yet, again.

Cheers,
Drew![](https://learn-attachment.microsoft.com/api/attachments/8964d0bf-c43b-480c-bdc3-378f061d0d21?platform=QnA

Mine looks to be all fine & normal

Mine too

I just restored the backup from yesterday and it looks fine on this machine too.

I have a suspicion that it is related to the Settings app crashing when trying to select HDR which is another reported bug that they did not fix yet. Not a coincidence that this box also has that bug which I don't see on two other older machines.

https://aka.ms/AAfh9uy

https://aka.ms/AAfgkpc

I had the error prior to any HDR setting crash

Hi Ian,

Sorry at that time that was a suspicion, read my following posts, I figured out what is causing the bug. I assume the same is true for your case.

Local experience language pack, whatever that means, I installed the same on another box and got the same bug.

I don't have that App, never seen it before.

I think I just proved my point, rather than restoring the backup from yesterday, I used PowerShell to remove the last package that was updated from the MS Store and that eliminated the problem of the incorrect Time & Language page, which now looks normal again.

Hi fg, good 🕵️‍♂️ job!

What is that App for? some language add-on?

Local experience language pack, whatever that means, I installed the same on another box and got the same bug.

Not sure why it was on automatically on the failing box.

In my case it is en-US, so it should be pretty normal.

I think I just proved my point, rather than restoring the backup from yesterday, I used PowerShell to remove the last package that was updated from the MS Store and that eliminated the problem of the incorrect Time & Language page, which now looks normal again.

Hi fg, good 🕵️‍♂️ job!

What is that App for? some language add-on?