Forum Discussion
Storage service StorSvc in Win 10 multi-session causing high CPU
Hello,
in AVD host of Windows 10 multi-session that has FSLogix installed, stroage service (StroSvc) sometimes causing very high CPU and it stay like that for few hours.
This also happen immediately when open Storage settings by any user.
I have checked the setting to "Configure Profile Container to roam the Windows Search database" in MS docs https://docs.microsoft.com/en-us/fslogix/configure-search-roaming-ht but this setting is not applicable for Windows 10 multi-session.
any advice on how to solve this issue please ?
Thanks,
Bachar
- I found the problem. it is when using FSLogix app masking. when creating the rules files we should not depend on the automatic scan that the tool does. we need to modify this scan and remove hiding unneeded registry keys.
9 Replies
This just happened to me. All 8 cores had 100% cpu from the storage service. What is that service for, anyway? Disabling it didn't seem to affect anything. We have the app masking too.
I narrowed it down to an app masking rule for Adobe Acrobat that was causing the high CPU usage. I recreated the masking rule on a reference computer with Adobe Acrobat Pro DC and the problem never returned. I can just speculate that I built the (problematic) rule on an old version, and FSlogix was puking on something.
To test - just remove all the rules from the folder - then add one at a time back in and see what happens.
- I have discovered that the issue is related to FSLofix app masking. when I add .fxa and .fxr files to "C:\Program Files\FSLogix\Apps\Rules". storage service will not be able to calculate the sizes in the user's profile folders and the process will consume high CPU.
Any advice ?- I found the problem. it is when using FSLogix app masking. when creating the rules files we should not depend on the automatic scan that the tool does. we need to modify this scan and remove hiding unneeded registry keys.
- I'm trying to understand what you've written as a reply as I'm seeing similar issues, this time in Citrix VADS and I'm using both FSLogix Profiles and App Masking. The rules were already created in a reference image. Are you saying that you remove the registry entries that are being hidden by the rule set? Leaving just directories that get hidden by the rule set?
