Error code: Wsl/Service/E_UNEXPECTED

[brumle80]

Error message

Error code: Wsl/Service/E_UNEXPECTED

What I tried
Installed local version, also tried Online with same result:
Clean Windows installation, trying to start ArchWSL after installation and got the error message above.

To Reproduce

Install following guide, then try to start Arch.

Enviroment:

• Windows build number: Microsoft Windows [Version 10.0.26120.2705]
• WSL version 2
• System: Copilot+ Snapdragon arm64
• ArchWSL version 24.4.28.0
• ArchWSL Installer type zip/appx clean install on clean Windows
• Launcher version: wsldl2, version 24042000 (amd64)

Running the store Ubuntu 22.04 work, but it's not Arch...

[tomaoq]

It has something to do with systemd.
This issue is a good starting point.

[brumle80]

thanks for the reply, tried that but then I get other error messages, and the stock Ubuntu WSL works fine.

PS C:\Users\dag.notland\ArchWSL> .\Arch.exe
<3>WSL (16 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\WINDOWS\system32
<3>WSL (16 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\WINDOWS
<3>WSL (16 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\WINDOWS\System32\Wbem
<3>WSL (16 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\WINDOWS\System32\WindowsPowerShell\v1.0
<3>WSL (16 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\WINDOWS\System32\OpenSSH
<3>WSL (16 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\Program Files\WireGuard
<3>WSL (16 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\ProgramData\chocolatey\bin
<3>WSL (16 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\Users\dag.notland\AppData\Local\Microsoft\WindowsApps
Processing fstab with mount -a failed.
Failed to mount C:, see dmesg for more details.

[hedgepigdaniel]

I just ran a pacman update, and now I have a similar symptom. I'm able to follow the instructions from microsoft/WSL#10942, but switching off systemd does not solve the problem in my case. Now sure if there is an obvious way to read logs to see more detail on the error?