Windows 10: KB4571756 crashes WSL with “Element not found” error for some users

A new cumulative update is now available for Windows 10 version 2004 and version 20H2 with numerous fixes, but it also breaks WSL (Windows Subsystem for Linux) for some users. The patch in the question is “Windows 10 KB4571756” and it’s designed to fix SSD drive debugger bug in Windows 10.

Unfortunately, it’s causing headaches for certain users who use Windows Subsystem for Linux. According to reports from the Feedback Hub and Microsoft’s Github, users have said that they’re getting “Element not found” error when trying to run WSL. Others have noticed general installation issues.

The problem stems from KB4571756, which is a cumulative update that’s available for computers running both version 2004 and version 20H2. At the moment, it looks like the problem is hitting users with version 20H2 only.

“After the KB4571756, 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,” one user noted.



There’s some good news and some bad news. The good news is that you can uninstall this update to fix issues with WSL. The bad news? Microsoft is currently not aware of issues with WSL, so it’s possible the company isn’t working on a fix yet.

If you’re one of the unlucky users with WSL issues, we recommend rolling back the update from the Settings app.

How to fix WSL “Element not found” error


To fix “Element not found” error in WSL after applying recent updates, follow these steps:

1. Go to Settings.
2. Click “Update and Security” from the left sidebar.
3. Click on “View update history”.
4. Click “Uninstall updates” to open Control Panel window.
5. Locate the update and click the uninstall button.
6. Reboot.

If you still have issues with WSL, you should try reinstalling the distribution that you use.

The post KB4571756 crashes WSL with “Element not found” error for some users appeared first on Windows Latest

Weiterlesen...

 

FAILED install: September 8, 2020—KB4571756

I get a page fault error trying to install the KB4571756 (OS Build 19041.508) update either through Windows Update or downloading the msu file directly.

Any suggestions?
Thanks.

 

WSL related crash

I did a repair upgrade and chose to keep only my files. I'm always being worried it might crash, though, because it often gets slow or has a minor pause occasionally. This has been happening since a few days ago.

I don't know what "WWAJSE" stands for, so it'd be great if someone told me. Also, when searching online about the Kernel Mode Heap Corruption error, I saw in the results list someone saying that he/she was told that uninstalling WSL might fix the issue. The person noted that this doesn't apply to him/her because he/she doesn't remember ever enabling that setting, but am I correct in assuming that most of the time this issue only comes up for people who have WSL? And if so, is there a way to prevent it from happening even while you have WSL? I hope there is.

 

Permission error on WSL 2 when trying to setup a nodejs project

TLR;

Code:

Can't use npm global package in /mnt/c/Users.username. It works in WSL home (~) though.

---

Code:

Currently, I have all my web projects in /mnt/c/Users/[username]/dev.

Steps I took:

1. I open the terminal and access the above folder via a symlink.
   
2. Installed p5js-cli package globally but when I get to use it I get the below output:
   

Code:

☁ dev p5 new test+
Creating new p5.js project in test...[Error: failed to mmap. Could not write data: Permission denied] {errno: -1,errorFunction: 'Clone.clone'}

I'm struggling to get my head around file permissions in this case.

Code:

If I run ls -lah in the windows folder I get the below output which I understand it means I should have the correct access to those folders and the output is consistent
 with the files on the WSL side.drwxrwxrwx 1 username username 4.0K Aug 25 23:31...I have installed vue-cli and was able to successfully use it to create a project in /mnt/c/Users/username/dev , could this be an issue with p5js-cli and not the wsl setup?