wslconfig file being ignored

[Joanthan17]

So, I've compiled WSL2-Kernel, copied bzImage to %USERPROFILE% and created a .wslconfig file there pointing to this bran new kernel. However, WSL seems to be ignoring my .wslconfig file as uname -r still shows the original version. Any clues on this?

PS I'm running version 20H2 (OS Build 19042) on windows home edition

[Biswa96]

What is in the .wslconfig file?

[Joanthan17]

[wsl2]
kernel=c:\\wslkernel\\bzImage
memory=4GB # Limits VM memory in WSL2 to 4 GB
processors=2 # Makes the WSL2 VM use two virtual processors

[Joanthan17]

the wslconfig file location - C:\Users\Jonathan Elkabas.wslconfig

[hoang-himself]

The wslconfig file location should be C:\Users\Jonathan Elkabas\.wslconfig

[Joanthan17]

yeah I know, it was a typo ><

[Reignable]

I'm having the same issue but not trying a different kernel.
The only setting I have is:

[wsl2]
memory=4GB

Same Build and Version as @Joanthan17 but Pro rather than Home

[Joanthan17]

I fear that the whole .wslconfig file thing is a feature available only on Pro edition although i didn't find any mention about it in the documentation

[therealkenc]

The kernel= feature is not limited to Pro.

[benhillis]

@Joanthan17 - are you running x64 or arm64?

[0xbadfca11]

Make sure you are definitely using WSL2.
So far there is no evidence that you are using WSL2. You may be using WSL1 by mistake.

• wsl.exe -l -v
  Is the VERSION column 2?
• uname -r
  Isn't the kernel version 4.4? It's WSL1.

[Joanthan17]

@benhillis im using x64-based processor
@0xbadfca11 please have a look:
on debian:

on PS:

[hoang-himself]

@Joanthan17 I'm not sure about the kernel, but memory and processors definitely requires WSL2. You can find more information here.

[Joanthan17]

[hoang-himself]

@Joanthan17

wsl --set-version Ubuntu-20.04 2

[Joanthan17]

turns out i was running wsl1 and not wsl2 ><

now the wslconfig file work!

guys thanks a lot for your help (:

[Reignable]

So I am on WSL2 and the wslconfig file is still being ignored

[hoang-himself]

@Reignable Are you using version 19041? .wslconfig is only available on build 10941 and later.

[Reignable]

@Smithienious I'm currently on 19042

But have just gotten insider builds available

[hoang-himself]

@Reignable can you show the content of wslconfig?

[Reignable]

[wsl2]
memory=4GB
swap=0

[hoang-himself]

@Reignable how do you know the file is being ignored? Excessive ram usage?

[Reignable]

Yeah, especially when using Docker although when running other node applications it gets sucked up and doesn't get freed again

[hoang-himself]

@Reignable try running the program given here. If WSL is still using more than 4GB, shut down WSL completely then try again. If it still doesn't work, delete and create a new .wslconfig, shutdown WSL then try again. If these don't work, you should create a new issue.

[Reignable]

Thanks @Smithienious, I've managed to limit it by updating Windows to 21343 which brings in the changed default WSL memory to 8GB which is fine for me. I've done with you suggested and .wslconfig still isn't recognised but it's not a problem anymore
Thanks for your help.

[ThiloFink]

You have to make sure that the .wslconfig is not a txt file but a wslconfig-file type.

Create the .wslconfig not with a text-editor, but inside the C:\Users\<user> with:
code .wslconfig

[starkblaze01]

Make sure when you create a .wslconfig file the type of the file is WSLCONFIG File, not TXT Document:

[moon548834]

You have to make sure that the .wslconfig is not a txt file but a wslconfig-file type.

Create the .wslconfig not with a text-editor, but inside the C:\Users\<user> with: code .wslconfig

you save my life!!

[MerlijnBusch]

Hello can some help me, I have followed all the steps here. But the issue is still there

Its saved as an WSConfig so not a text what should be correct the insides of the files are as follows

But some1 how the memory goes to 8k what is the default max setting for windows but it just ignore the file?

If some1 can let me know what I'm doing wrong it would be amazing