-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting WSL causes "Service host: network store interface service" to have high CPU usage #11948
Comments
View similar issuesPlease 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! Open similar issues:
Closed similar issues:
Diagnostic information
|
My WSL2 has the same problem. It took a long time to start and then that service consumed 100% CPU. It was really difficult to even reboot the PC. |
Same issue here in my company (among developers using WSL2 on Windows 11) - since we made the 2 cumulative Updates KB5042099 and KB5041585. |
I’m encountering this exact issue on WSL 2 with Windows 11 after recent updates. The service "Network Store Interface Service" is causing high CPU usage as soon as I start wsl, and unfortunately, the service can't be stopped - only a full reboot temporarily resolves the problem. This is making the system almost unusable. |
Same issue on WSL2 version 22H2 (22621.4037). In my case I narrowed it down to a Citrix gateway installation (Citrix Secure Access 23.5.1.3) clashing with WSL networking setting. I found two ways of making my computer not reach 100% utilization:
While both of these resolve the CPU utilization problem completely, unfortunately neither of these then allow me to use the VPN inside WSL that I need for work so neither of these solutions work for me. For a temporary fix I am able to kill the service from Processes under Task Manager. This only lasts until the service restarts, which can be any amount of time, I have observed the range to be from seconds to days. |
I have Citrix Secure Access 22.2.1.103. And I can't uninstall it either. |
Hey @rijulg how'd you narrow it down to Citrix out of curiosity? as there are some people on my team that use it, but it can not be running and still have that service start and cause issues. Interested in your findings as would make sense if it is the cause. Yeah killing that service seems to be the best fix now, even though it warns of causing the PC to shutdown (It doesn't) I normally don't have it starting up that often again, maybe twice more during the work day |
It was a bit of a ride, but I originally just noticed the networking services spike when I started WSL. Proceeded with changing WSL to mirrored mode and spikes stopped. But since now citrix stopped working reverted to NAT mode. Knowing that networking was an issue I just had a hunch that it was one of the networking devices/drivers. Since I didn't find any updates for any of my networking devices, I just started deleting networking devices one at a time and did full system reboot and check. That final step revealed Citrix as the culprit. As of today just ending task on the networking service is working fine for me, it is annoying when it restarts and spikes but it does not really happen frequently so after I have started everything I just end task on the networking service which is spiking. I suspect the impact of this will be that change in networking adapters won't be propagated but I don't need that to happen anyway as I am not hotswapping networking stuff. |
I see interesting, sounds like quite a journey, I want to use mirrored mode as well, but since there is an issue with docker in that mode we have to use NAT. Thanks for the investigations, but I do hope there is something in WSL/windows that can be fixed, or if it is Citrix that a patch comes out soon, as it doesn't affect windows 10 at all. Yeah that's the main thing it's annoying and basically kills the PC till the service stops |
I had the same issue that happened after August 13th, KB5041585 update. Something that worked for me was running this command in admin mode:
Credit to: |
In our case, uninstalling “Citrix Secure Access” did the trick. Many thanks for the tip! |
Damn, I was scratching my head for the past few weeks.. but finally found the solution for why NSI Service was seething. |
Works for me, thank you @Usayd for sharing! @Usayd can you check the url to fileshare? Wasn't able to access, only from source url in docs.netscaler.com and searched for "clean" :) |
@stalk3rr Yup that's the correct link for the Citrix Secure Access clean up tool :) - I've updated the URL on my original reply. |
Had the same issue and it was resolved by uninstalling Citrix Secure Access via Settings. Did not require the additional clean-up tool. Windows Version: 10.0.22631.4037 |
had the same issue and can confirm it resolved by uninstalling Citrix Secure Access or by ending process task that contain "network". |
I need Citrix Secure Access for my work, so I can't just uninstall it. Is there another solution/fix? |
@happyswiss same for me, the current workaround for it to work with WSL is to put it in mirrored networking mode, but that only will work for win 11. That stops the service from using a lot of CPU. I hope that helps |
we are also observing the same issue with Network Storage Interface Service on clients without Citrix Secure Access Client. |
UPD 23.09.2024: |
I had the similiar issue on Windows 11 and Hyper-V Services enabled combined with Citrix Secure Access installed. |
Windows Version
Windows version: 10.0.22631.4037
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Start WSL which takes a while to start up, but that's because the service spins up and causes high CPU usage to take place
Expected Behavior
WSL to start up without causing high CPU usage with other services
Actual Behavior
Service host: network store interface service starts up and takes up a huge chunk of CPU usage, and that causes the computer to slow down drastically, until I force stop the service.
Diagnostic Logs
WslLogs-2024-08-22_08-38-13.zip
The text was updated successfully, but these errors were encountered: