Insufficient system resources exist to complete the requested service.

[ioweb-gr]

Please fill out the below information:

• Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.19041.264]

• What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

Trying to execute kali linux in WSL2 results into an error

• What's wrong / what should be happening instead:

The error is Insufficient system resources exist to complete the requested service. however the instance should run correctly. Rebooting solves the issue

Restarting the HV Host Service seems to work too.

[rescenic]

In explorer, type in address bar: \\wsl$
then enter. It will show linux path.
Then you can click the linux symbol in navigation pane to list the linux path.

I am using Insider 19624.1000. In previous build, there isn't any error like that.
But in the build I am using right now, it will show Insufficient system resources exist to complete the requested service when you click the linux symbol in navigation pane without accessing \\wsl$ first.

[jozsefsallai]

I can confirm this issue with Debian (I don't think it matters what flavor of Linux you have). Same version as the one described in the issue. The only difference is that the only way I can fix it is rebooting or logging out and then back in. Restarting the HV Host Service does not work for me.

Edit: logging out and back in doesn't always work either.

[onomatopellan]

What's your CPU and how much RAM do you have?

[ioweb-gr]

For me it was on Ryzen 1700x and 32Gb Ram

[onomatopellan]

Then 16 threads and 32Gb of RAM. This issue #5240 was very similar. Try creating a .wslconfig file and reduce the numbers of processors and RAM used for the WSL2 VM.

[ioweb-gr]

I guess the main difference is that for me everything works normally ok with the default settings. It was only a temporary issue which got fixed by restarting the service so I can live without cutting down the vm resources but I thought it would be important to report

[jozsefsallai]

What's your CPU and how much RAM do you have?

My specs aren't that great, but most of the time I have no issues with WSL2. Right now I booted into my computer and it didn't work. I logged out and then back in and everything worked fine.

• CPU: AMD Ryzen 7 2700U Quad-Core
• RAM: 8 GB (1 GB is allocated for the integrated GPU)

And I agree with @ioweb-gr. It doesn't always happen. For me, most of the time it works fine. And like I said, for some reason, restarting the service doesn't work for me though, so what I usually do is start WSL2 as soon as I boot into my computer and if it doesn't work, just log in again or reboot until it works. Then I don't close it 😅

[onomatopellan]

How about the Virtual memory? Do you let Windows to manage the paging file size automatically?

[jozsefsallai]

Yeah, that option is enabled!

[onomatopellan]

I'm out of ideas. But it's curious that both CPUs are AMD.

[gabriellovate]

I had the same problem, using WLS 2 on a notebook with AMD processor.

• CPU: AMD Ryzen 7 3700U Quad-Core
• RAM: 8 GB (2 GB are allocated for the integrated GPU)

[jozsefsallai]

I wonder if it has anything to do with the fact that I added \\wsl$\Debian to my Quick Access menu. When I open the File Explorer shortly after logging in, the Debian entry doesn't initially show up in the Quick Access menu (only after a while).

@rescenic mentioned that they can reproduce this issue when they try to access the VM's folder directly, without entering \\wsl$ first. Maybe this happens when the system tries to load the folder in the Quick Access menu too?

I've deleted the entry from the menu now and I'll let you know how it goes!

[elbro]

Same issue once a week or so, ryzen 7 2700x and 16gb RAM. Only way i've found to fix is a windows Restart

[jozsefsallai]

I haven't had this error since I removed the Quick Access entry (granted, it's only been 3 days), however, I did see a different error yesterday (which was also fixed by logging out and in):

It's weird that pretty much everyone who is facing this issue has a Ryzen CPU.

Edit: the original issue happened again.

[GiorgioG]

Same issue - 1950X Threadripper / 32gb of RAM.

[mbledkowski]

The same for me - Ryzen 5 mobile second gen / 8GB ram + virtual memory

[dmayan-ss]

Same issue on 2700x 16gB of RAM

[onomatopellan]

Do you all have Fast Startup enabled? Try turning it off, reboot Windows and see if the issue still happens.

[icorbrey]

Also have this issue, R5 1600 + 16GB RAM

[NogrTL]

Same,

Ryzen 1600+8GB RAM

[inigoml]

Same problem here.
Ubuntu 20.04, upgraded from 18.04 wsl1 to wsl2. Worker for the first time.

• Microsoft Windows [Version 10.0.19041.264]
• 16GB RAM
• Ryzen 5 2600X

[inigoml]

Do you all have Fast Startup enabled? Try turning it off, reboot Windows and see if the issue still happens.

Tested and worked again. Thank you!

[iamnotagentleman]

Same problem
Ubuntu 20.04, switched wsl1 to wsl2 also I added the WSL shortcut to explorer quick access

• Microsoft Windows Version 10.0.19041.329
  -8GB RAM (2 GB are allocated for the integrated GPU) (VM Enabled on NVME disk)
  -Ryzen 5 3550H

[mattrea]

Same issue here started yesterday with WSL2 Ubuntu 20.04.

• Microsoft Windows Version 2004 (OS Build 19041.329)
• Ryzen 5 2600 with 32GB of RAM

Update 2nd July:

• I removed a quick access entry and it started working again for a bit...
• But its just started again today and my Ubuntu 20.04 failing on load with...

"Insufficient system resources exist to complete the requested service.
[process exited with code 4294967295]"

Update July 4th: Add .wslconfig with memory attribute (set to ~1/3 system memory) as per #5231 (comment) below and this worked!

[sonj2]

Same issue happened today for me with WSL 2. I got the error ever since roughly 80% of the RAM was being used. Lowering the RAM usage down to 40% by closing applications didn't fix the issue, nor did restarting HV Host Service. Restarting fixes the problem until it crops up again.

• Windows version 2004 (Build 19041.329)
• Ryzen 5 2600 with 16 GB of RAM

[kiraleos]

Same issue here, started happening yesterday, 21/07/2020. WSL 2 Ubuntu 20.04
It happens when I'm using more than 50% of my RAM or so (4GB). Closing down programs that use that RAM fixes the issue, even if I go up to 50% of my RAM again.

• Windows version 2004 (Build 19041.329)
• Ryzen 5 2600 with 8 GB RAM

[nicscharlau]

Same issue.

• Windows 10 2004 (19041.329)
• Ryzen 5 3500U with Vega 8 Graphics
• 8 GB RAM
• Virtual memory allocation managed by the system
• Used distro: Debian 10 (the Microsoft Store version)
• Exit code 4294967295

Disabling fast startup doesn't fix the problem.

[craysiii]

I have the same issue as well, though I am on an Intel CPU.

• Windows 10 Version 2004 (OS Build 19603.1000) (Fast Ring)
• Intel i7-8750H (6 core 12 thread)
• 32GB RAM
• Using Pengwin
• Fast Startup disabled

I get this error when trying to use the Linux location that was added to explorer by the OS. If I manually type in \\wsl$ into explorer, I can then use the location in explorer without issues immediately.

[xFrann]

Same issue on ubuntu wsl2

• Ryzen 5 2600 6 cores 12 threads
• Microsoft Windows [Version 10.0.19041.329]
• 8GB RAM

[b4ruch]

same dang issue here:

Ryzen 4900HS 8 cores 16 threads
Microsoft Windows 10 [Version 10.0.19041.329]]
16GB RAM
WSL 2
Ubuntu 20.04

[avoidwork]

Hi,

I ran into this issue for the first time today. Using a Ryzen 9 5950x / 64GB RAM / .wslconfig ... after reading this thread I was wondering if it was a soft block, so I tried starting an ubuntu shell in the new windows terminal and it worked where the direct ubuntu terminal failed multiple times.

The direct ubuntu shell started working afterwards. Screenshots around 7 min apart based on file names.

[Mohitkumar6122]

Is there a specific solution to this issue ?

[Noexpert]

Same issue on an AMD Ryzen 2500U laptop with 8GB RAM.
The suggested .wslconfig solution didn't work.

[MoJoE3131]

I also have the problem.

Microsoft Windows [Version 10.0.18363.2158]

Intel Xeon W-2135 CPU @ 3.70GHz with 64 GB RAM

I tested every solutions in this issue and it still doesn't work.

[leandro-toledo-uux]

Same issue here, Ryzen 7 1700 and 8GB, however, after some reboots it finally worked.

[amkhrjee]

I was having the same problem(Ryzen 5 3550H and 8GB memory with Windows 10 21H2). Removing the WSL shortcut from the Files app(not the inbox File Explorer - I didn't have the shortcut enabled there) solved the problem.

Seems like WSL works fine with shortcuts enabled in file explorers in Windows 11, but bugs out for Windows 10, at least that's true in my experience.

[ZYinMD]

Removing from Quick Access instantly solved the problem for me.

[itdevwu]

I suffered from the same problem.

• CPU: AMD Ryzen 6800H
• RAM: 16GB
• Host OS: WIndows 11 21H2 (22000.1042)
• Distro: Ubuntu 22.04

It has happened several times, and the only available solution is to reinstall Windows, which also removed the entire WSL VM.

[Betzabesp94]

Same problem here:

• CPU: AMD Ryzen 5 3500U
• RAM: 12GB
• Host OS: WIndows 10
• Distro: Ubuntu 22.04

After trying a lot of things the solution was:

1. Search Ubuntu on windows explorer
2. Right click and select ⚙️ App Settings
3. On Reset click Repair button
4. Then click on Reset button

[mouafakben]

Disabling my McAfee fixed this problem for me.

the problem happens to me twice and doing that fixed the problem.

[MihailRomanov]

Same problem:

• CPU: AMD Ryzen 7 4700U
• RAM: 16GB
• Host OS: WIndows 10 (10.0.19045)
• Distro: Ubuntu 20.04

My solution:

• Restart Virtual Mashine Magaement service (I just stopped and started it from the Hyper-V Manager MMC console)

[Namlaz]

#5231 (comment)

This worked around my issue, thank you.

For reference :

• CPU : AMD Ryzen 7 PRO 5850U
• RAM : 16GB
• Host OS : Windows 10 (19044.2251)
• Guest OS : Debian 11.5

[treehead]

I have the same issue and the temporary work-around in [comment #5231 resolved it:

1. Open PowerShell (or CMD)
2. notepad $env:USERPROFILE\.wslconfig (or notepad %USERPROFILE%\.wslconfig in CMD)
3. Paste and save the following:

[wsl2]
processors=4

4. Launch WSL distribution.

You can also try 2 or 1 for the value of processors as well, if 4 doesn't work.

System specs:

• CPU : AMD Ryzen 7 5800H with Radeon Graphics
• RAM : 16GB
• Edition: Windows 10 Pro
• Version: 21H2
• OS build: 19044.2364
• WSL Distribution: Ubuntu 22.04.1 LTS

[RivenSkaye]

I just faced this issue on my laptop, Ryzen 7 5800H w/ 16GB mem, Microsoft Windows [Version 10.0.19045.2486]
In my case it was solved by killing off a few processes consuming a lot of memory. If only Windows Taskmanager reported accurate statistics for mem consumption per app, as the highest it reported was 2GB in use for PHPStorm. Yet closing it freed up about 8GB and allowed me to run it again

[toneck]

I also started having problems yesterday.
My laptop has Ryzen 7 PRO 5850U Microsoft Windows [Version 10.0.19044.2486]

[krisavi]

I lowered my memory down from 2GB by halving it until I reached memory=1MB when it was again able to "run" again. I doubt that my computer memory is so fragmented. 32 GB of memory, 17.1 GB available should be well enough to start WSL with at least 2 GB. I would say it is bug with WSL if it simply refuses to allocate memory for VM or issue with MS virtualization layer.
CPU: AMD Ryzen 7 PRO 4750U

The WSL accepted to run it, but of course WSL is unable to start with only 1 MB of memory.

WSL OOM-killer kept killing pacman in Arch, ended up it crashing it while upgrading of glibc... Now have to scrap whole WSL image and recreate from scratch...

[theCrius]

Years later, Ryzen7 5800H, same issue just out of the blue.

Used the wsl 2 (ubuntu 20.04) all day without issue.

[viniciusCamargo]

[tabbea]

I'm unsure as to what went wrong but the very concise fix in #5231 (comment) worked for me.

[ivandustin]

Doing a full shutdown via cmd fixed my issue.

1. Open cmd, run as admin
2. Type and enter: shutdown /s /f /t 0
3. Wait for the shutdown
4. Boot again
5. Try to run WSL

ver: Microsoft Windows [Version 10.0.22000.856]

[mingxxv]

Same issue here.

Ryzen 7 7735HS (8c/16t)
16GB DDR5 RAM
Windows 10 IoT Enterprise LTSC 2021

Was working fine until today.

[ibndias]

Ryzen 9 5900HS, 16GB RAM
Windows 10 Pro

Solved by adding .wslconfig file in the User directory (C:\Users\username)

[wsl2]
processors=4

[ghost]

#5231 (comment)

The comment by ibndias worked for me. I was running Windows 10 Pro with Fedora running in WSL2. I started having this problem out of nowhere. When I looked up the error code, it lead me here. I tried the advice by ibndias and it fixed me right up:

Solved by adding .wslconfig file in the User directory (C:\Users\username}. Contents of file : {wsl2| processors=4

This worked out great for me. Thanks for making it easy guys. Oh, to follow up, yes Ryzen here. Asus ROG Strix.

[SySagar]

Ryzen 7 5800H,
16GB RAM
Windows 10

Steps:
-> Go to your search bar and search : %USERPROFILE%
-> Create a new file .wslconfig , if not there already.
-> Add these and save:
-> Restart your pc. Works fine for me.

[wsl2] processors=4

solved by adding .wslconfig file in %USERPROFILE%

[wendyn-projects]

Same Issue
Specs:

• Windows 10 - WSL2 (Debian)
• Ryzen 5 5600H
• 16 gigs of RAM (I still have like 4 gigs free looking at the task manager)

This is my whole .wslconfig:

[wsl2]
guiApplications=false
processors=4

After adding the last line, I stopped getting the message, but instead I just get a blinking cursor on a new line and Ctrl+C doesn't do anything...

I also tried (processors=2), (processors=1 and memory=1MB) and (removing guiApplications=false)

[MHCooke]

Experienced this when trying to launch WSL after playing a RAM intensive game on a R7 5800X + 16GB RAM. Restarting HV Host Serivce didn't do anything immediately, but after a few minutes it launched successfully. RAM usage was around 50%

[krisrok]

If my memory usage is somewhat high (70+% of 32GB), I have to lower the processor count via .wslconfig significantly (to 16 of 32).
Closing some applications and freeing memory to around 50%, I can use all of my 32 cores again.

What the heck.

[Luky584]

Happened to me as well
Running
taskkill /f /im wslservice.exe
taskkill /f /im explorer.exe
(as administrator)
Fixed it for me

[Vadsher]

Faced with this for the first time. It happens after Win10 was updated (currently 22H2, 19045.4046).
As it was mentioned above, logging out and then back in solve the issue. Didn't try anything else

[Kooks0711]

@ibndias
He is god