We speak about using WSL2, or Windows Subsystem for Linux 2, the improved model that enables Linux distros to be run natively in Windows 10, with their corresponding terminals from which we will use the system to program, compile, carry out checks, and many others. This is achieved due to together with the Linux kernel natively in Windows 10.
WSL2 damaged with KB4571756 patch on Windows 10
WSL2 was launched with May 2020 Update (2004), can also be lately accessible for 1903 and 1909. However, the patch KB4571756 launched two days in the past, which updates the system construct to the model 19041.508, has damaged this performance fully. When attempting to run any Linux distro below WSL2, I get an error saying “course of exited with code 424967295”.
Many customers have tried every part to attempt to get it working once more, however the one resolution that works in the meanwhile is to uninstall the newest patch launched by Microsoft for Windows 10.
Uninstall the patch, the one resolution
If now we have encountered this drawback, we should go to Control Panel> Programs and Features> View put in updates. There we must always see the KB4571756 patch put in. We choose it, we give it to uninstall, and we restart the pc. Thanks to this, the bug appears to be mounted.
Microsoft has not but acknowledged the existence of the bug, and due to this fact it appears that evidently the answer will wait a minimum of a number of weeks, so we advocate that you simply uninstall the patch till then. Of course, take into account that this month’s patch solves 129 vulnerabilities, 20 of them important, so you must prioritize for those who want to go away your laptop susceptible to all these bugs, or if quite the opposite you need WSL2 to work appropriately once more .
Microsoft has a really unhealthy streak of misguided updates for Windows 10, with fixed crashes and errors, breaking functionalities that ought to not have been damaged at first. A number of days in the past they mounted the bug that used up the SSD drives excessively by defragmenting them each time we restarted the pc, though they did not want it. Thus, they may all the time have a pending bug within the system.