Skip to content

"Element not found" after install KB4571756  #5880

Closed

Description

Environment

Windows build number: Microsoft Windows NT 10.0.19042.0
Your Distribution version: Ubuntu 20.04 (WSL 2)

Steps to reproduce

Install KB4571756
Reboot PC
Launch Windows Terminal with WSL

WSL logs: https://aka.ms/AA9kmq5

Expected behavior

WSL just works

Actual behavior

Element not found.
Process exited with code 4294967295
image

Activity

  1. changed the title [-]"Element not found" after [/-] [+]"Element not found" after install KB4571756 [/+] on Sep 8, 2020
  2. Mystic8b commented on Sep 8, 2020

    @Mystic8b
    Author

    Now i got a WSL update via update center but it didn't help.

  3. dvv101111 commented on Sep 8, 2020

    @dvv101111

    image
    Same problem

  4. relliv commented on Sep 9, 2020

    @relliv

    After the KB4571756 windows update I also got this error. I deleted the docker folders in AppData, then uninstalled and reinstalled docker but it didn't fix. It finally worked when I uninstalled the latest windows quality updates. (docker is associated with wsl in this case.)

    Caution: If you're not sure what you're doing, check out the tutorials on the web!

    • Sign out and hold shift while clicking restart button on lock screen
    • After restart, select Troubleshoot>Advanced options>Uninstall Updates>Uninstall latest quality update
    • Then enter related Microsoft account credentials and when all done > select Continue option.

    This is not a real solution but you can keep working at least until Microsoft fixes the problem.

  5. therealkenc commented on Sep 9, 2020

    @therealkenc

    Ref #5002 #5631. Appreciate the OP logs, thanks.

  6. cl1933404370 commented on Sep 9, 2020

    @cl1933404370

    I have the problem too. And i won't to remove KB4571756.
    I had to transfer this Distribution from wsl2 to wsl1.
    hoping fixing this bug quickly.
    log.zip

  7. dafoxuk commented on Sep 9, 2020

    @dafoxuk

    Removing the KB4571756 Windows update has fixed the problem for me as well

  8. francescarpi commented on Sep 9, 2020

    @francescarpi

    Me too. I have had to remove the KB4571756 update. I'll wait a few days for try to update again.

  9. AnMaillard commented on Sep 9, 2020

    @AnMaillard

    I can confirm that the workaround of EgoistDeveloper (uninstalling the KB4571756 update) solved the problem for me too.

  10. Smallthing commented on Sep 9, 2020

    @Smallthing

    when I turn off my computer ,docker report error and wsl s exited with code
    ....
    I'm really stupid.then I uninstalled my wsl2 ..when I install them back .

    click the ubuntu icon.and it said:

    Installing, this may take a few minutes...
    WslRegisterDistribution failed with error: 0x800706be
    Error: 0x800706be ?????????
    
    Press any key to continue...
    

    I don't know where to get logs.
    hope this bug solve faster...

  11. francescarpi commented on Sep 9, 2020

    @francescarpi

    when I turn off my computer ,docker report error and wsl s exited with code
    ....
    I'm really stupid.then I uninstalled my wsl2 ..when I install them back .

    click the ubuntu icon.and it said:

    Installing, this may take a few minutes...
    WslRegisterDistribution failed with error: 0x800706be
    Error: 0x800706be ?????????
    
    Press any key to continue...
    

    I don't know where to get logs.
    hope this bug solve faster...

    Please, check this issue #5768

  12. malkia commented on Sep 9, 2020

    @malkia

    Hmm.. I'm with "2004" e.g. "10.0.19041.508" and both wsl2 (kali-linux) and docker (through wsl2) work fine. Maybe my update got updated (Just did an update)

    image

  13. therealkenc commented on Sep 9, 2020

    @therealkenc

    I don't know where to get logs.

    WSL logs

  14. chungweileong94 commented on Sep 9, 2020

    @chungweileong94

    Facing the same thing, uninstall the update doesn't help.
    I ended up reinstall the Windows.

  15. sozercan commented on Sep 9, 2020

    @sozercan
    Member

    With KB4571756 update (19042.508), was getting this error:

    The remote procedure call failed. 
    [process exited with code 4294967295]
    

    After uninstalling KB4571756 and reverting to 19042.487, WSL2 starts again.

  16. 114 remaining items

  17. markexperience commented on Oct 2, 2020

    @markexperience
  18. baracunatana commented on Oct 2, 2020

    @baracunatana

    Might be. But, at the same time, what's de point of keeping the issue open if all that is left is for the KB4577063 patch to run its curse?

  19. coxchris859 commented on Oct 2, 2020

    @coxchris859

    They have release a standalone KB patch that isn't apart of the 20H2 feature update

  20. markexperience commented on Oct 2, 2020

    @markexperience
  21. v-emman commented on Oct 3, 2020

    @v-emman

    LOL guys, the bug was on the insider builds anyway. If you are not an insider you don't have it, plain and simple.

  22. malkia commented on Oct 6, 2020

    @malkia

    To fix, install this update KB4577063 (Windows 10 Build 19041.546) launched 10/01/2020, this issue has fixed in this update.

    I've found certain apps not to be working with this one (and had to revert it). One of them is AppVerif - the command-line still works, but the UI needs "EdgeGDI.dll" which is not present (seems to be loaded by newer gdi32.dll, but not so sure). Searching for "EdgeGDI" reveals other apps that maybe missing it. It might not affect you, or what you do daily, but it affected me, and had to revert.

  23. o1x3 commented on Oct 16, 2020

    @o1x3

    Юрий Зубарев (@Mystic8b) Totally unrelated question, but can you share your Windows Terminal profiles.json 😅

  24. Mystic8b commented on Oct 16, 2020

    @Mystic8b
    Author

    Юрий Зубарев (@Mystic8b) Totally unrelated question, but can you share your Windows Terminal profiles.json 😅

    Sure 😉Take it
    Oh yeah, and icons

  25. o1x3 commented on Oct 16, 2020

    @o1x3

    Юрий Зубарев (@Mystic8b) Totally unrelated question, but can you share your Windows Terminal profiles.json 😅

    Sure 😉Take it
    Oh yeah, and icons

    Юрий Зубарев (@Mystic8b) Thanks dude, appreciate it ✌

  26. Stlturkey commented on Dec 28, 2020

    @Stlturkey

    Edition Windows 10 Home
    Version 20H2
    Installed on ‎12/‎10/‎2020
    OS build 19042.685
    Experience Windows Feature Experience Pack 120.2212.551.0
    WslRegisterDistribution failed with error: 0x80070490
    Error: 0x80070490 Element not found.

    wsl2 version is installed and i don't have the insider package. wsl1 works just fine for kali. When i update and set version 2 as default error message happens. I figured out after downloading the kali package from windows app store, rootsf files are missing in app data/local/packages/kali/local state. When I checked on wsl version1 folder is available.
    C:\Program Files\WindowsApps\KaliLinux.54290C8133FEE_1.6.0.0_x64__ey8k8hqnwqnmg has the data file install.tar.gz {276 MB } as gz file format which is not recognized by the windows. I don't know if any of this information helps to figure out the bug but I'm stuck on a loop between wsl1 with no gui interface or not working wsl2

  27. ajkessel commented on Dec 15, 2021

    @ajkessel

    I've been unable to launch wsl2 recently - "element not found" every time. I've tried restarting lxssmanager and rebooting. I don't have KB4571756 in my list of updates, but I believe this started after some recent patch, possibly KB5007253 or KB5007289 which were both installed last week. Tried to install KB4577063 but the OS told me it was not installable. I'm unable to access the filesystem at \wsl$\ubuntu . Any workarounds for getting wsl2 to launch again?

    Also posted to #3785 as it seems to describe the same problem.

  28. ajkessel commented on Dec 15, 2021

    @ajkessel

    Update: the resolution described here fixed this problem for me. Specifically, downloading and running the https://aka.ms/easyfix20159 easy fix, followed by a reboot. Hopefully this will help others.

  29. gbasile17 commented on Feb 3, 2022

    @gbasile17

    This issue seems to have surfaced again. None of the solutions in this thread are relevant. Any suggestions? So far I have tried:

    1. Completely reinstalling WSL2
    2. The solution provided here "Element not found" after install KB4571756  #5880 (comment)
  30. bui commented on Feb 11, 2022

    @bui

    I've started getting this error today after installing KB5010386. Anyone else?

    Edit: Running the above-linked easyfix and rebooting fixed the issue for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions