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

CrazyKats 19,415 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 No comments

210 answers

Sort by: Most helpful
  1. Anonymous
    2021-08-13T12:05:21+00:00

    Hi CK,

        Thanks for the heads up. I installed the 22000.132 Beta with only a couple hiccups. But other than that works Great.
    

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-08-13T12:00:53+00:00

    Hi fg2001,

          I was having the same problem as your reply post to Davy-Delliott was having. I followed your suggestion on using Power shell as administrator and typing :
    

    Get-AppxPackage Microsoft.SecHealthUI -AllUsers | Reset-AppxPackage

    This Worked perfect for me and fixed the problem.

    Thank-You for this suggestion

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-08-13T09:20:48+00:00

    The search with a screen-shot is still not available. I wonder is this will be brought back. Use it in Windows 10 to extract text from pictures several times a day. All other methods (the ones I know) are much more cumbersome

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-08-13T08:09:34+00:00

    Hi.

    Hidden icons flyout has sharp corners. Switch themes and sharp corners get rounded.

    Log out of my account and log back in. Sharp corners resume.

    So I keep waiting for another build.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-08-13T06:40:50+00:00

    Thanks for the help fg2001.

    It is apparent that the fault is NOT patched in 22000.132 which is strange when you read what APPAULS has to say here.

    So, it’s obviously worrying that a core element of Windows is giving the same error as a third-party file might, an element as crucial as security. Fortunately though, this issue is not prevalent on a large-scale as only a few users are reportedly facing this error. However, that number is still large enough that this has become a glaring issue that Microsoft will likely patch in the next update.

    I looked for this problem in Fixes and Known Issues and was surprised by its omission.

    Davy.

    Was this answer helpful?

    0 comments No comments