RS-Prerelease build 21343 is out to Dev Channel

CrazyKats 19,585 Reputation points Volunteer Moderator
2021-03-24T17:00:21+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

105 answers

Sort by: Most helpful
  1. Anonymous
    2021-03-27T06:58:23+00:00

    Once again I cannot get Windows updates after installing 21343.1000. The error I get is Ani-virus update 1.333.1370.0) -Error 0x80070643

    I have run ?WU reset and .net repair.

    David

    @SpiderG,

    Interesting!

    I saw the same problem on build 19043.906 today and it kept failing earlier with 1.333.1349.0.

    So I decided to check for updates directly from windows defender and that finally downloaded and installed the update . Maybe you can try that, see third snap shot below:

    Image

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-03-27T06:56:20+00:00

    Do you have a 3rd party antivirus program installed?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-03-27T06:37:22+00:00

    Once again I cannot get Windows updates after installing 21343.1000. The error I get is Ani-virus update 1.333.1370.0) -Error 0x80070643

    I have run ?WU reset and .net repair.

    David

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-03-26T21:26:27+00:00

    Eddie, why do you create these service names and it doesn't even have a description ?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-03-26T17:42:00+00:00

    The known Start menu search bug is an interesting one.

    On one system, search in Start mostly works, searchapp.exe doesn't crash often, and when it does it restarts and mostly stays running (and working).

    On another system, search in Start is never available because searchapp.exe crashes and basically stays that way. Sometimes there is a flurry of crashes in quick succession, but searchapp.exe is never in memory long enough for search in Start to ever work. Fortunately, it's not a case where it's in an endless searchapp.exe crash loop.

    It's hard to explain why two systems with the same build experience the bug so very differently, but does anyone else think that the Start menu maybe shouldn't be tied in any way to an app?

    This seems to be another inconsistent one, I have 4 machines at build 21343 and I did not see this bug at all yet.

    Was this answer helpful?

    0 comments No comments