A PC equipped with advanced AI capabilities and Windows Copilot integration
Hi Chris Arneson,
I understand how frustrating it is to see WorkloadsSessionHost consuming 3–4GB of RAM right at startup. Thank you for sharing that you’re not using Copilot+ features and have tried advanced steps such as disabling the WSAIFabricSvc service.
On Copilot+ builds, this runtime is treated as a core OS component, so in some cases, Windows can re‑enable or bypass disabled services internally. Unfortunately, there’s no confirmed method to reliably stop WorkloadsSessionHost or significantly reduce its memory usage yet. You can try this workaround to see if it helps:
- Press Win + X > open Device Manager
- Expand Neural processors (name may vary)
- Right‑click the Neural Processing Unit > Disable device
- Restart your PC > check if the RAM usage at startup decreases.
Still, the number 3-4GB of RAM is very alarming, this may indicate a regression in your current build. Because this is a user‑to‑user forum, we don’t have backend diagnostics to confirm regressions directly, so the best way forward is to submit a report:
- Press Win + F to open Feedback Hub
- Include a screenshot of Task Manager (Processes + Memory)
- Note that
WorkloadsSessionHostis consuming 3–4GB immediately after startup
This is important because the component isn’t user-controlled today, so any fix would come through a Windows update rather than configuration changes.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.