| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006766 | Kali Linux | General Bug | public | 2020-10-02 08:22 | 2021-06-24 02:01 |
| Reporter | Wirus | Assigned To | steev | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | kali-dev | ||||
| Summary | 0006766: Uzaktan İşlem Çağırısı Başarısız | ||||
| Description | Kali Linux windows 10 versiyonuna giremiyorum format attım gene olmadı. | ||||
 |
Wsl 2 |
 |
Which version of Windows are you on? There is a known issue with the latest (or iirc, 20221) Insider builds that causes failures, and people had to roll back if they ran into it. Unfortunately, this is something on the Microsoft side, not Kali |
|
|
I am using windows 10 build 20221 and how can i go back to the old build version aa.PNG (1,484 bytes) |
|
|
solved I upgraded from 20221 to 20226 |
|
|
But I get an error saying that the system is not booting to systemd as init system (PID 1). He cannot operate. Could not connect to the bus: Host is down |
|
|
That is correct, systemd is not used as the init system on WSL. If you need to start or use various services, you can typically use "sudo service SERVICENAME start" or "sudo /etc/init.d/SERVICENAME start" (depending on if it has an init script or not). There have been some people trying to get systemd working on WSL, but as far as I know, they haven't fully succeeded yet. |
|
|
I can't shut down the operating system, I get an error root @ DESKTOP-7P1HU3J: / home / kali # shutdown |
|
|
and i get an error when using the apt-get update W: http://http.kali.org/dists/dists/kali-rolling/InRelease Failed to get temporary error resolving 'http.kali.org' |
|
|
Unable to shut down, is completely expected. You simply "exit" the system (this is a Windows thing, not us) As to the the networking issue.... that will be harder to track down. Are you using a VPN? This is known to break networking in WSL (and again, this is something on the Windows side) - your best bet might be to look through the wsl issues on GitHub to see if anything there helps. |
|
|
I get an error in wsl 1 Default device not found: socket: Socket type not supported a.PNG (4,144 bytes) |
|
|
Not all sockets work in WSL1, unfortunately and there is nothing we can do on the Kali side. We highly recommend WSL2 if it's at all possible to upgrade to a build of windows that supports it for this reason. |
|
|
I gave up the Kali linux windows 10 version, instead I created and installed a kali linux virtual machine |
