If Settings → System → Recovery → Go back is available, return to Windows 11 25H2 now, because the freezes began with the feature upgrade and Microsoft supports reverting to the previous version for this scenario.
1. Restore the last stable configuration
- Back up important files and ensure the BitLocker recovery key is available.
- Open Settings → System → Recovery.
- Select Go back and follow the prompts.
- After returning to 25H2, pause deployment of 26H2 through your organization’s normal update-management policy until the device’s firmware and driver stack have been validated.
The option is normally available for only 10 days after an upgrade. It retains personal files but removes apps, drivers, and settings introduced afterward.^1^
If Go back is unavailable, do not attempt an unsupported manual downgrade over the existing installation. The supported alternatives are uninstalling a recent update, reinstalling the current Windows version while preserving files/apps/settings, or restoring an earlier restore point.^2^
Is this a confirmed 26H2 regression?
Microsoft’s current Windows 11 26H2 Release Health page does not list a confirmed issue matching WorkloadsSessionHost, ASUS TUF A14, Ryzen AI 9 HX 370, Radeon 890M, hybrid-GPU switching, or these freezes.^3^
There are similar public reports:
- A Microsoft Q&A report describes high CPU/RAM use by
WorkloadsSessionHost.^4^
- An open Microsoft GitHub issue reports multiple instances consuming Radeon 890M resources on a Ryzen AI 9 HX PRO 370 system.^5^
These reports support investigating the Windows AI workload stack, but they do not establish that it causes your freezes or that iGPU/dGPU switching is responsible.
WorkloadsSessionHost behavior
First confirm the exact executable name and signature:
- Open Task Manager → Details.
- Right-click the process → Open file location.
- Open Properties → Digital Signatures and record the signer, path, file version, PID, CPU, memory, and GPU engine.
- While memory usage is abnormally high, right-click it → Create memory dump file.
Task Manager supports user-process dumps; they are normally written under %LocalAppData%\Temp.^6^
Its automatic relaunch means another Windows component or service owns its lifecycle, so repeatedly ending it is only temporary. Available documentation does not identify one permanent switch that safely disables every workload capable of launching it.
If Recall is enabled
On managed Enterprise devices, verify Group Policy → Computer Configuration → Administrative Templates → Windows Components → Windows AI → Allow Recall to be enabled. Disabling that policy removes the Recall component after restart; Microsoft states Recall is disabled and removed by default on commercially managed devices.^7^
An administrator can remove enabled Recall bits with:
Disable-WindowsOptionalFeature `
-Online `
-FeatureName "Recall" `
-Remove
Restart-Computer
This is a diagnostic mitigation only if Recall is actually installed or enabled. It is not documented as a general fix for WorkloadsSessionHost, and it removes Recall functionality.
Replace third-party-installed drivers with the ASUS stack
“Updated by Driver Booster” does not verify that the laptop has the ASUS-qualified hybrid-graphics and power-management combination. Install packages for the exact ASUS model, in this order:
- BIOS/UEFI, following ASUS’s precautions.
- ASUS/AMD chipset and platform drivers.
- ASUS-provided Radeon 890M graphics driver.
- ASUS-provided NVIDIA graphics driver.
- ASUS system-control/interface and power-management packages.
- Restart and test on AC and battery.
For a recently changed display driver, Device Manager → Display adapters → adapter → Properties → Driver → Roll Back Driver is supported. If rollback is unavailable, uninstalling the device and selecting Attempt to remove the driver for this device, followed by restart, is also supported.^8^
Do not apply speculative registry changes for GPU switching, power states, the NPU, or WorkloadsSessionHost; no matching Microsoft-supported registry fix is documented.
Isolate memory usage from the freezes
A freeze occurring at 40–50% memory means the high-memory condition and hard lock may be separate.
Perform a clean boot:
- Run
msconfig.
- Services → Hide all Microsoft services → Disable all → Apply.
- Startup → Open Task Manager and disable enabled startup items.
- Restart and test normal light/idle use.
- If stable, re-enable half the services/items per test until the responsible component is isolated.^9^
If it still freezes in a clean boot with ASUS-qualified drivers, capture:
-
C:\Windows\Minidump, if present.
- A
WorkloadsSessionHost user-mode dump during high usage.
- Event Viewer → Windows Logs → System events around the freeze.
- A Feedback Hub recording with diagnostics; Feedback Hub permits attaching files and retaining a local copy.^10^
Submit those artifacts to ASUS and Microsoft business support with the exact OS build, BIOS version, and driver versions. Dumps can contain memory-resident personal data, so share them only through a trusted support channel.
References
- Go back to the previous version of Windows | Microsoft Support
- Recovery options in Windows | Microsoft Support
- Windows 11, version 26H2 known issues and notifications
- WorkloadsSessionHost High CPU & RAM Usage - Microsoft Q&A
- [Privacy/Thermal] WorkloadsSessionHost silently consumes 90% ... - GitHub
- Task Manager live memory dump
- Manage Recall
- [Windows 11](https://support.microsoft.com/windows/hardware/display-graphics/troubleshoot-screen-flickering-in-windows#fix-your-display-driver)
- [Windows 11](https://support.microsoft.com/windows/experience/startup-boot/how-to-perform-a-clean-boot-in-windows)
- Send feedback to Microsoft with the Feedback Hub app | Microsoft Support