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

Anonymous
2022-01-12T18:00:15+00:00

Live in W.U.

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

164 answers

Sort by: Newest
  1. Anonymous
    2022-01-14T07:21:41+00:00

    Hi IanRG,

    All I have to do here to solve the problem is by removing the latest version 22535.1.1.0 and reinstall older version 22534.1.1.0. and then stop the update from the MS Store.

    I use the following PowerShell commands; you can probably change these to match the Pack and version for your Zone Language, I don't know which one you use, your snapshot showed Camberra,Melboune,Sydney.

    Mine is for en-US and the problem goes away if I reinstall the older version 22534.1.1.0.

    Get-AppxPackage Microsoft.LanguageExperiencePacken-US -AllUsers | Remove-AppxPackage

    Add-AppxPackage -register "C:\Program Files\WindowsApps\Microsoft.LanguageExperiencePacken-US_22534.1.1.0_neutral__8wekyb3d8bbwe\appxmanifest.xml" -DisableDevelopmentMode

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-01-14T06:20:55+00:00

    FWIW, I do not have this issue.

    Try to investigate what I can that has been mentioned in the thread.

    Cheers,
    Drew
    Image

    Which issue? We discussed many different ones.

    If you are referring to the Time & Language screen screwup, it only shows with the latest version of the App English (United States) Local Experience Pack Version 22535.1.1.0, no problem with previous Version 22534.1.1.0.

    You may not even have the English Local Experience Pack installed, and in that case, you will not see the bug.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-01-14T05:49:48+00:00

    FWIW, I do not have this issue.

    Try to investigate what I can that has been mentioned in the thread.

    Cheers,
    Drew

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-01-14T05:39:36+00:00

    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.

    I suspected it was language settings based as it affects other things like keyboard settings and networks. The funniest confused description is:

    Image

    Ian,

    In my case it is the new version of the English (United States) Local Experience Pack.

    The old version 22534.1.1.0 works fine, the new one 22535.1.1.0 screws up the Settings screen.

    I can reproduce the problem at will just removing and reinstalling the latest version of that App.

    I have seen only the one screen screwed up, not any of the other ones you mentioned, but you are in a different zone and local language.

    Image

    Added feedback with recording:

    https://aka.ms/AAfh4l3

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2022-01-14T05:29:29+00:00

    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.

    I suspected it was language settings based as it affects other things like keyboard settings and networks. The funniest confused description is:

    Was this answer helpful?

    0 comments No comments