Win Update KB5083631 Windows 11 Cumulative Update Preview build 26100.8328 (24H2) and 26200.8328 (25H2) - April 30

cute two · May 3, 2026

Microsoft has not yet rollout a Dark Mode in Folder option in RP/General builds. However, you can manually enable these experimental features in 26200.8313/8328.

Code:

Windows Registry Editor Version 5.00
# Undo - Delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14 Registry Key and restore default values.
# You will need to open CMD as administrator. Type the following command in CMD to Undo:
# REG DELETE "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14" /f

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14]

## Insider Experimental Preview feature
# CFR Toggle Key, Windows Insiders Preview Channel feature requirements. ViVetool ID: 48433719 (CFR RKey: 1853569164)
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14\1853569164]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000

# CFR Toggle Key, Windows Insiders Preview Channel feature requirements. ViVetool ID: 49453572 (CFR RKey: 156965516)
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14\156965516]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000

# Dark Mode dialog prereq. ViVetool ID: 58383338 (CFR RKey: 3587705487)
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14\3587705487]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000

# Dark Mode Run. ViVetool ID: 59270880 (CFR RKey: 3231968911)
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14\3231968911]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000

# Dark Mode Folder Options. ViVetool ID: 59203365 (CFR RKey: 1255272590)
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14\1255272590]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000

Dark Mode Run also enable Dark Mode Folder Options, so I didn't neet to use 1255272590, but require: 1853569164, 156965516.

FIREMEDIC2700 · May 3, 2026

well this update killed the new start meun and the drag tray . ran the dism commands sfc and check disk and nothing, wish ms would get there crap together. i am to the point of just waiting to patch tuesday enough is enough.

FrancoDT · May 3, 2026

Just a heads up for ARM PC users on this build, the WorkloadsSessionHost.exe for the new Windows AI/Recall infrastructure will accumulate a lot of memory usage on ARM machines. Mine was using over 2GB even though Recall is not installed. Apparently it's part of this build and is designed to spawn multiple “workload” processes that run AI/semantic tasks in the background and has been enabled by default.

After seeing what a huge memory hog it was I did some digging and discovered to reclaim that memory I would one have to disable the feature package that enables it vivetool /disable /id:58989070 and two go into Services and disable WSAIFabricSvc which kills WorkloadsSessionHost. Had to reboot after each and the downsides are searches may take 1–2 seconds longer to initialize and some Settings pages may load slower.

Mark K · May 3, 2026

FrancoDT said:
Just a heads up for ARM PC users on this build, the WorkloadsSessionHost.exe for the new Windows AI/Recall infrastructure will accumulate a lot of memory usage on ARM machines. Mine was using over 2GB even though Recall is not installed. Apparently it's part of this build and is designed to spawn multiple “workload” processes that run AI/semantic tasks in the background and has been enabled by default.

After seeing what a huge memory hog it was I did some digging and discovered to reclaim that memory I would one have to disable the feature package that enables it vivetool /disable /id:58989070 and two go into Services and disable WSAIFabricSvc which kills WorkloadsSessionHost. Had to reboot after each and the downsides are searches may take 1–2 seconds longer to initialize and some Settings pages may load slower.

When I researched something similar to AI/Copilot/Recall, I found all AI features are tied together.

For one WindowsWorkLoad has many Appx packages installed with many services:

Code:

Get-AppxProvisionedPackage -Online |
  Where-Object { $_.DisplayName -like "WindowsWorkload.*" } |
  Select-Object DisplayName |
  Sort-Object DisplayName

Copilot generated this script to disable majority of AI features:

Code:

######################################################################
# Microsoft Copilot AI generated script
#
# What this script actually stops
# These are the components that normally keep re‑launching:
#
# WorkloadsSessionHost.exe
# WorkloadsSessionManager.exe
# CoPilotLibraryBroker.exe
# AI Fabric background tasks
# Semantic indexing tasks
# Recall snapshot triggers
# Copilot background workloads
#
# After running the script + rebooting, these processes no longer respawn.
######################################################################

# Disable Windows AI Fabric Service (main trigger)
Get-Service -Name WSAIFabricSvc -ErrorAction SilentlyContinue | Stop-Service -Force
Set-Service -Name WSAIFabricSvc -StartupType Disabled

# Disable Recall / AI background tasks if present
$tasks = @(
    "\Microsoft\Windows\Recall\*",
    "\Microsoft\Windows\AI\*",
    "\Microsoft\Windows\Workload\*",
    "\Microsoft\Windows\Shell\Copilot\*"
)

foreach ($t in $tasks) {
    Get-ScheduledTask -TaskPath $t -ErrorAction SilentlyContinue | Disable-ScheduledTask
}

# Kill running workload processes
$procs = "WorkloadsSessionHost","WorkloadsSessionManager","CoPilotLibraryBroker"
foreach ($p in $procs) {
    Get-Process $p -ErrorAction SilentlyContinue | Stop-Process -Force
}

# Disable Activity History (semantic triggers)
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\System" /v EnableActivityFeed /t REG_DWORD /d 0 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\System" /v PublishUserActivities /t REG_DWORD /d 0 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\System" /v UploadUserActivities /t REG_DWORD /d 0 /f

# Disable Windows Search AI indexing (if present)
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Windows Search" /v EnableDynamicContentInWSB /t REG_DWORD /d 0 /f

Write-Host "WindowsWorkload background components disabled. Reboot recommended."

What I heard, and not sure if this is true or correct, is that the Windows 11 26H1 for ARM64/Snapdragon processors you cannot disable or turn off Recall because it is integrated within Copilot. Unlike how Recall is a separate feature in Windows 11 25H2 where we can enable/disable it. This is what stopped me over the past week on buying a Copilot+ PC/laptop with Snapdragon X (X Elite actually). I haven't had time to research this part, but those of you that have Snapdragon laptops will probably know for sure. This information came from retail stores on when I asked about Snapdragon laptops.

Mark K · May 3, 2026

I had to find this link, otherwise it would have been in my previous post.

I have not ran this one yet, but I have before, this seems to be the best method on disabling AI in Windows 11. Not sure if this runs on ARM64:

GitHub: RemoveWindowsAI

FrancoDT · May 3, 2026

Mark K said:
What I heard, and not sure if this is true or correct, is that the Windows 11 26H1 for ARM64/Snapdragon processors you cannot disable or turn off Recall because it is integrated within Copilot. Unlike how Recall is a separate feature in Windows 11 25H2 where we can enable/disable it. This is what stopped me over the past week on buying a Copilot+ PC/laptop with Snapdragon X (X Elite actually). I haven't had time to research this part, but those of you that have Snapdragon laptops will probably know for sure. This information came from retail stores on when I asked about Snapdragon laptops.

WorkloadsSessionHost.exe is the main culprit for memory use so I focused on that one and it no longer respawns now on my ARM machine. The two intel machines show WSAIFabricSvc in services but don't show WorkloadsSessionHost.exe or any memory usage from it in Task Manager so those will stay enabled. So far no adverse effects seen and more overall memory available for other task. I only have 16GB on that machine so it's a noticeable amount.

Mark K · May 3, 2026

FrancoDT said:
WorkloadsSessionHost.exe is the main culprit for memory use so I focused on that one and it no longer respawns now on my ARM machine. The two intel machines show WSAIFabricSvc in services but don't show WorkloadsSessionHost.exe or any memory usage from it in Task Manager so those will stay enabled. So far no adverse effects seen and more overall memory available for other task. I only have 16GB on that machine so it's a noticeable amount.

Is the WSAIFabricSvc disabled in Services (services.msc)? If not, the next update will re-enable it all. That is what happened to my systems.

As I found out from focusing on WorkloadSessionHost and WorkloadSessionManager, these also connect to AIXhost and AImgr services. Not all AI services and packages are removable:

Code:

PS C:\> Get-AppxPackage -AllUsers |
>> Where-Object {
>>     ($_.Name -match "AI|Recall|Copilot|AIX") -and
>>     ($_.NonRemovable -eq $false)
>> } |
>> Select Name, PackageFullName, NonRemovable

Name                                          PackageFullName
----                                          ---------------
MicrosoftCorporationII.WinAppRuntime.Main.1.8 MicrosoftCorporationII.WinAppRuntime.Main.1.8_8000.836.2153.0_x64__8we...
Microsoft.Ink.Handwriting.Main.en-US.1.0.1    Microsoft.Ink.Handwriting.Main.en-US.1.0.1_0.1121.1848.0_x64__8wekyb3d...
Microsoft.Paint                               Microsoft.Paint_11.2601.441.0_x64__8wekyb3d8bbwe
Microsoft.MicrosoftSolitaireCollection        Microsoft.MicrosoftSolitaireCollection_4.25.4290.0_x64__8wekyb3d8bbwe
WindowsWorkload.EP.AMD.VitisAI.1.8            WindowsWorkload.EP.AMD.VitisAI.1.8_1.8.58.0_x64__8wekyb3d8bbwe
aimgr                                         aimgr_0.20.47.0_x64__8wekyb3d8bbwe

Here are the NonRemovable packages linked to AI services:

Code:

PS C:\> Get-AppxPackage -AllUsers |
>> Where-Object {
>>     ($_.Name -match "AI|Recall|Copilot|AIX") -and
>>     ($_.NonRemovable -eq $true)
>> } |
>> Select Name, PackageFullName, NonRemovable

Name                           PackageFullName                                                     NonRemovable
----                           ---------------                                                     ------------
Microsoft.AIFabric.CBS.1.6     Microsoft.AIFabric.CBS.1.6_1.6.935.100_x64__8wekyb3d8bbwe                   True
MicrosoftWindows.Client.CoreAI MicrosoftWindows.Client.CoreAI_1000.26100.8328.0_x64__cw5n1h2txyewy         True
MicrosoftWindows.Client.AIX    MicrosoftWindows.Client.AIX_1000.26100.8328.0_x64__cw5n1h2txyewy            True

Note: the removable aimgr package will get reprovisioned (aka re-installed) when needed and linked to the AI services again.

Mark K · May 3, 2026

I forgot one detail to this AI re-triggering the AI garbage load.

If you are using a Microsoft account in Windows 11 sign-in or local account with singing in to Microsoft Edge with a Microsoft account (two conditions that I know about), the Microsoft Accoung Sign-in Assistant services will re-enable AI services as well.

Code:

PS C:\> Get-Service | Select-Object Name, Status, StartType, DisplayName | Where-Object { $_.Name -in @("SysMain","WSAIFabricSvc","wlidsvc") }

Name           Status StartType DisplayName
----           ------ --------- -----------
SysMain       Running Automatic SysMain
wlidsvc       Stopped    Manual Microsoft Account Sign-in Assistant
WSAIFabricSvc Running Automatic WSAIFabricSvc

Setting the StartType to Disable for the Microsoft Account Sign-in Assistant service will work, however, that itself causes an entire set of other problems.

FrancoDT · May 3, 2026

Mark K said:
Is the WSAIFabricSvc disabled in Services (services.msc)? If not, the next update will re-enable it all. That is what happened to my systems.

Yes, disabled in Services. I guess I'm more concerned about MS reenabling the feature package in a future build and somehow forcing me to keep the WorkloadsSessionHost.exe enabled and it being an even worse memory hog.

FrancoDT · May 3, 2026

Mark K said:
I forgot one detail to this AI re-triggering the AI garbage load.

If you are using a Microsoft account in Windows 11 sign-in or local account with singing in to Microsoft Edge with a Microsoft account (two conditions that I know about), the Microsoft Accoung Sign-in Assistant services will re-enable AI services as well.

Code:

PS C:\> Get-Service | Select-Object Name, Status, StartType, DisplayName | Where-Object { $_.Name -in @("SysMain","WSAIFabricSvc","wlidsvc") } Name Status StartType DisplayName ---- ------ --------- ----------- SysMain Running Automatic SysMain wlidsvc Stopped Manual Microsoft Account Sign-in Assistant WSAIFabricSvc Running Automatic WSAIFabricSvc

Setting the StartType to Disable for the Microsoft Account Sign-in Assistant service will work, however, that itself causes an entire set of other problems.

I'm ok with the basic AI, i.e. I use Co-Pilot. I want nothing to do with Recall however and I don't like services eating up resources for a feature (Recall) I don't want or ever intend to use.

Mark K · May 3, 2026

FrancoDT said:
I only have 16GB on that machine so it's a noticeable amount.

This is why I recommend Windows users to buy any Windows computer with 32GB memory on them. Windows 11 25H2 with Microsoft's default configuration consumes around 14GB memory with nothing else installed.

This story outlines it with gaming, but it applies to anything consuming more than 16GB of memory in Windows 11.

You are not alone that the Copilot+ computers consume much more memory with AI running in it.

I have a non-AI Windows 11 Pro 25H2 computer using a 10th gen Intel i5 2.4GHz with 16GB memory (boots up using only 6.5GB memory) and it seems to run faster than the newer Copilot+ computers. There are no AI apps installed, no AI services running. This is why I now want a non-AI processor computer.

TraderGary · May 3, 2026

I've not noticed any memory problems or anything unusual on either System One or System Two.

System Two is an ARM, Microsoft Surface Laptop 7 Snapdragon X Elite.

FrancoDT · May 3, 2026

Mark K said:
This is why I recommend Windows users to buy any Windows computer with 32GB memory on them. Windows 11 25H2 with Microsoft's default configuration consumes around 14GB memory with nothing else installed.

This story outlines it with gaming, but it applies to anything consuming more than 16GB of memory in Windows 11.

You are not alone that the Copilot+ computers consume much more memory with AI running in it.

I have a non-AI Windows 11 Pro 25H2 computer using a 10th gen Intel i5 2.4GHz with 16GB memory (boots up using only 6.5GB memory) and it seems to run faster than the newer Copilot+ computers. There are no AI apps installed, no AI services running. This is why I now want a non-AI processor computer.

Yeah ,I should have known better then to cheap out on the memory. My other machines have 32GB and 64GB of memory. To it's credit that little Surface Laptop is a really snappy machine even with just 16 GB, I just worry about the long term with AI and Recall becoming more invasive as that seems to be the trend now.

Mark K · May 3, 2026

TraderGary said:
I've not noticed any memory problems or anything unusual on either System One or System Two.

System Two is an ARM, Microsoft Surface Laptop 7 Snapdragon X Elite.

You have two good systems there. What does Task Manager - Performance - Memory shows in use after a restart before you run any programs?

I only have Microsoft Edge open with 4 tabs open, and memory shows 14.4GB in use out of 32GB. In a 16GB system, this provides very little memory to do much:

TraderGary · May 3, 2026

FrancoDT said:
Yeah ,I should have known better then to cheap out on the memory. My other machines have 32GB and 64GB of memory. To it's credit that little Surface Laptop is a really snappy machine even with just 16 GB, I just worry about the long term with AI and Recall becoming more invasive as that seems to be the trend now.

I have Recall turned OFF on both computers so I'm not concerned.

I do use Copilot on both machines with no problems.

gunrunnerjohn · May 3, 2026

FrancoDT said:
Yeah ,I should have known better then to cheap out on the memory. My other machines have 32GB and 64GB of memory. To it's credit that little Surface Laptop is a really snappy machine even with just 16 GB, I just worry about the long term with AI and Recall becoming more invasive as that seems to be the trend now.

It's impossible nowadays to "cheap out" on memory. You can buy less than you need, but cheap doesn't enter the picture! :lmao:

FrancoDT · May 3, 2026

TraderGary said:
I've not noticed any memory problems or anything unusual on either System One or System Two.

System Two is an ARM, Microsoft Surface Laptop 7 Snapdragon X Elite.

Just a tip, open your Task Manager to the Details page on the ARM machine and select it's order by memory and see what your top process is and if it's WorkloadsSessionHost.exe. Course you may use Recall but I don't even have it installed let alone enabled and that was my biggest memory user by far.

gunrunnerjohn · May 3, 2026

I have done nothing to reduce the memory footprint of Windows, and currently I'm using right around 16GB of my 64GB of memory.

Mark K · May 3, 2026

Memory consumption in Windows 11 Pro 25H2 26200.8328 on a non-AI system is far less than what an AI consumes:

Mark K · May 3, 2026

FrancoDT said:
Yes, disabled in Services. I guess I'm more concerned about MS reenabling the feature package in a future build and somehow forcing me to keep the WorkloadsSessionHost.exe enabled and it being an even worse memory hog.

I think I remember seeing Microsoft patched a memory leak in WorkloadsSessionHost about two months ago, but it got quickly corrected. Hopefully Microsoft reduces the memory usage on AI running in Windows 11.

AI Component	Version
Image Search	1.2604.515.0
Content Extraction	1.2604.515.0
Semantic Analysis	1.2604.515.0
Settings Model	1.2604.515.0

Available	Next Step
	Open Start > Settings > Windows Update. > Advanced options > Optional updates. In the Optional updates available area, you will find the link to download and install available updates. Check for optional updates
	To install this release from the Microsoft Update Catalog, select the option that matches your device architecture (arm64 or x64), and then follow the instructions.

Win Update KB5083631 Windows 11 Cumulative Update Preview build 26100.8328 (24H2) and 26200.8328 (25H2) - April 30

April 30, 2026 - KB5083631 (OS Builds 26200.8328 and 26100.8328) Preview​

Announcements and messages​

Windows Secure Boot certificate expiration​

Highlights​

Windows 11 PC experiences​

AI Components​

Windows 11 servicing stack update (KB5088467)- 26100.8247​

Known issues in this update​

How to get this update​

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

Well-known member

My Computers My Computers

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

Well-known member

My Computers My Computers

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

Stock Market Wizard

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

Stock Market Wizard

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

Well-known member

My Computers My Computers

April 30, 2026 - KB5083631 (OS Builds 26200.8328 and 26100.8328) Preview

Announcements and messages

Windows Secure Boot certificate expiration

Highlights

Windows 11 PC experiences

AI Components

Windows 11 servicing stack update (KB5088467)- 26100.8247

Known issues in this update

How to get this update

My Computers

My Computer

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers