CRLF in /etc/wsl.conf silently fails to use config

[ahupp]

Windows Version

Microsoft Windows [Version 10.0.26100.2894]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 24.04.1 LTS

Other Software

n/a

Repro Steps

Create an /etc/wsl.conf with CRLF line endings, enabling systemd. Boot WSL, it will skip the config and use /init. The offending wsl.conf file:

$ xxd < /etc/wsl.conf
00000000: 5b62 6f6f 745d 0d0a 7379 7374 656d 6420  [boot]..systemd
00000010: 3d20 7472 7565 0d0a 0d0a                 = true....

If I replace the line endings with just LF, it will use systemd as expected:

$ xxd < /etc/wsl.conf
00000000: 5b62 6f6f 745d 0a73 7973 7465 6d64 3d74  [boot].systemd=t
00000010: 7275 650a 0a                             rue..

I have not checked if this just effects systemd, or all config.

Expected Behavior

WSL would either accept CRLF identically to LF, or fail with an explicit error at startup if the config could not be parsed.

Actual Behavior

adam@DESKTOP-R4CAFH5 ~> xxd < /etc/wsl.conf
00000000: 5b62 6f6f 745d 0d0a 7379 7374 656d 6420  [boot]..systemd
00000010: 3d20 7472 7565 0d0a 0d0a                 = true....
adam@DESKTOP-R4CAFH5 ~> ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0   2616  1760 hvc0     Sl+  22:18   0:00 /init

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• .wslconfig doesn't work: Unknown key ... (#10510), similarity score: 0.75
• wsl.conf silently ignored if DOS line endings. (#8002), similarity score: 0.70
• Incorrect line ending values in wsl console output (#9748), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[ahupp]

WslLogs-2025-01-26_19-16-55.zip

[github-actions]

Diagnostic information

Detected appx version: 2.3.26.0

[benhillis]

Fixed with https://github.com/microsoft/WSL/releases/tag/2.5.1