Share via

WorkloadsSessionHost using 4GB RAM on Copilot+ PC

Chris Arneson 20 Reputation points
2026-05-14T23:46:02.7833333+00:00

I have Windows 11 Pro on a HP OmniBook X. Still relatively new.

  1. WorkloadsSessionHost consuming 3-4GB RAM on startup 14 processes
  2. Intel Core Ultra 7 256V, Windows 11 Pro 25H2 build 26200.8457
  3. WSAIFabricSvc registry set to Value 4 (Disabled) but service still starts
  4. You do not use Recall, Click to Do, or any Copilot+ AI features
Microsoft Copilot | Windows Copilot | Copilot+ PC
0 comments No comments

Answer accepted by question author

  1. Lychee-Ng 19,620 Reputation points Microsoft External Staff Moderator
    2026-05-15T12:08:13.3766667+00:00

    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:

    1. Press Win + X > open Device Manager
    2. Expand Neural processors (name may vary)
    3. Right‑click the Neural Processing Unit > Disable device
    4. 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 WorkloadsSessionHost is 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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Q&A Assist
    2026-05-14T23:46:16.1+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    WorkloadsSessionHost and related Windows AI components on a Copilot+ PC are part of the on-device AI stack that supports features such as Recall, Click to Do, and image/semantic processing. On Copilot+ PCs, these components are present and active at the platform level even if the user does not actively use Recall or Click to Do.

    Key points from the available information:

    1. Copilot+ PCs ship with dedicated Windows AI components
      • Windows 11 24H2/25H2 on Copilot+ PCs includes AI components such as the Image Processing AI component and other Windows AI components that run on the NPU and CPU to support features like Click to Do, Recall, and improved Windows search.
      • These components are delivered and updated via Windows Update as separate AI component packages (for example, the Image Processing AI component updates in KB5061853 and KB5065500).
    2. AI components are updated and maintained via Windows Update
      • AI components for Copilot+ PCs are serviced independently of normal cumulative updates. For example:
        • KB5061853 / Image Processing AI component update (version 1.2505.838.0) for Intel-powered systems.
        • KB5065500 / Image Processing AI component update (version 1.2507.797.0) for Intel-powered systems.
      • These updates are automatically downloaded and installed when running Windows 11 24H2/25H2 on a Copilot+ PC with the latest cumulative update.
    3. Copilot+ features and services are platform-level, not only user-invoked
      • Features unique to Copilot+ PCs in Windows 11 24H2/25H2 include:
        • Click to Do
        • Recall (preview/GA depending on build)
        • Improved Windows search with semantic indexing
        • Agent in Settings
      • Even if Recall or Click to Do are not used, the underlying AI components and services that support them can still be present and running as part of the platform.
    4. Policy and manageability
      • For Recall specifically, there is a policy setting to control whether Windows saves snapshots and analyzes user activity: DisableAIDataAnalysis in the WindowsAI policy CSP. When enabled by policy, Recall’s data collection and analysis are disabled, but the platform components can still exist on the system.
      • Click to Do and other AI features are also governed by hardware and OS prerequisites and may still have supporting services loaded even when the feature is not actively used.
    5. WSAIFabricSvc and similar services
      • The context provided does not document WSAIFabricSvc behavior or how it interacts with WorkloadsSessionHost.
      • It also does not document a supported method to fully disable WorkloadsSessionHost or WSAIFabricSvc on Copilot+ PCs when running Windows 11 Pro 25H2.

    Given the available information:

    • On a Copilot+ PC running Windows 11 Pro 25H2, it is expected that AI-related components and services (including those that support Recall, Click to Do, and image/semantic processing) are installed and maintained by Windows Update.
    • These components can be active at startup as part of the Windows AI platform even if the user does not explicitly use Recall or Click to Do.
    • The context does not provide a supported procedure to stop or remove WorkloadsSessionHost or WSAIFabricSvc beyond standard policy controls such as DisableAIDataAnalysis for Recall.

    For managing AI features themselves (not the underlying host process):

    • Use the documented management controls for Recall and Click to Do (for example, Recall can be disabled and removed on managed devices, and Click to Do has hardware and usage limitations). This affects feature behavior and data collection, but not necessarily the existence of the platform services.

    References:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.