Following intense cybersecurity backlash and regulatory inquiries across Europe and North America, Microsoft completely redesigned its controversial AI activity recording feature for late 2026, releasing Windows Recall 2.0. The overhauled version introduces opt-in enrollment, mandatory Windows Hello biometric authentication, an AppContainer isolated Virtual Hard Disk (VHDX), and encrypted local SQLite vector indexes.
Despite these improvements, privacy-conscious prosumers, software engineers, and enterprise IT administrators frequently require Recall to be completely decoupled and eradicated from the OS image. The background capture daemon continues to consume background disk I/O, write cycles on SSDs, and up to 25GB of reserved storage. Here is our tested, permanent guide to removing Recall 2.0 cleanly via PowerShell and DISM without damaging native Windows Search or File Explorer indexing.
1. The Architecture of Recall 2.0: Where Your Data Lives
To safely eliminate Recall, you must understand its four system touchpoints:
- Capture Daemon:
C:WindowsSystemAppsMicrosoftWindows.Client.AIExperience_cw5n1h2txyewyexecutes periodic screen grabs using DirectX surface capture every 5 seconds. - Semantic Vector Store: An encrypted SQLite database (
ukg.db) located inside%LOCALAPPDATA%CoreAIPlatform.00UKP{GUID}. This file stores optical character recognition (OCR) text embeddings and vector similarities. - Biometric VHDX Container: An encrypted virtual disk mounted exclusively when Windows Hello biometric facial recognition or fingerprint authentication succeeds.
- DISM Optional Feature: The foundational system package registered under the identifier
Recall.
2. Step 1: Auditing Your Current Recall 2.0 Status
Open an elevated PowerShell console (Right-click Start β Terminal (Admin)) and execute the following query to inspect whether Recall is active and determine its disk footprint:
# Query current DISM package status
dism /online /get-featureinfo /featurename:Recall
# Check if the AI experience daemon is currently registered in memory
Get-Process -Name "*AIExperience*" -ErrorAction SilentlyContinue | Select-Object ProcessName, Id, WS
If the state returns Enabled, proceeding with the removal steps below will permanently deactivate the capture pipeline.
Join NextByte Tech Community on Telegram
Get immediate notifications for new verified Windows fixes, open-source utilities, and tech tutorials.
2026 Windows 11 Optimization Cheat Sheet
Download our complete verified cheat sheet with 25+ PowerShell commands, debloating scripts, and service tweaks to get sub-10 second boot times.
3. Step 2: Disabling Recall via Group Policy & Registry
Before purging system files, lock the policy flags to ensure Windows Update does not silently re-enable the feature during monthly cumulative patches:
For Windows 11 Pro / Enterprise / Education:
- Press Win + R, type
gpedit.msc, and hit Enter. - Navigate to:
Computer Configuration β Administrative Templates β Windows Components β Windows AI β Recall. - Double-click "Turn off Recall", select Enabled, and click Apply.
For Windows 11 Home (PowerShell Registry Commands):
# Force Recall policy disabled in Local Machine Hive
New-Item -Path "HKLM:SOFTWAREPoliciesMicrosoftWindowsWindowsAI" -Force | Out-Null
Set-ItemProperty -Path "HKLM:SOFTWAREPoliciesMicrosoftWindowsWindowsAI" -Name "DisableAIDataAnalysis" -Value 1 -Type DWord
Set-ItemProperty -Path "HKLM:SOFTWAREPoliciesMicrosoftWindowsWindowsAI" -Name "RecallPolicyEnabled" -Value 0 -Type DWord
# Disable user-level snapshot triggers
New-Item -Path "HKCU:SoftwarePoliciesMicrosoftWindowsWindowsAI" -Force | Out-Null
Set-ItemProperty -Path "HKCU:SoftwarePoliciesMicrosoftWindowsWindowsAI" -Name "RecallPolicyEnabled" -Value 0 -Type DWord
4. Step 3: Complete DISM Package Deprovisioning
Now execute the core package removal command using DISM. This strips the binary hooks and de-registers the AI background listener from the Windows Component Store:
# Deprovision the Recall OS package
dism /online /disable-feature /featurename:Recall /norestart
# Confirm removal
dism /online /get-featureinfo /featurename:Recall
The console will output: The operation completed successfully. State : Disabled.
5. Step 4: Purging the Hidden SQLite Vector Cache & VHDX
Disabling the feature stops future recordings, but existing snapshots and SQLite vector embeddings may remain cached on disk. Run the following cleanup routine to reclaim storage space:
# Stop any hanging background handlers
Stop-Process -Name "*AIExperience*" -Force -ErrorAction SilentlyContinue
# Target and delete existing CoreAIPlatform data stores
$RecallPath = "$env:LOCALAPPDATACoreAIPlatform.00"
if (Test-Path $RecallPath) {
Remove-Item -Path "$RecallPath*" -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "Successfully purged Recall semantic cache." -ForegroundColor Green
} else {
Write-Host "No cached Recall data detected." -ForegroundColor Cyan
}
6. Verifying That Windows Search & Indexing Remain 100% Intact
A common misconception is that removing Recall impairs Windows Search. Recall operates on independent semantic vector embeddings; standard Windows search relies on the classic Windows Search Service (WSearch) using traditional inverted index files (Windows.edb).
Verify that your standard search service is running unaffected:
Get-Service -Name "WSearch" | Select-Object Name, Status, StartType
The output must confirm Status: Running and StartType: Automatic. Press Win + S and search for any local application or fileβresults will appear instantaneously with zero background snapshot overhead.