Update failed: Cumulative Update for Windows 11, version 25H2 for x64-based Systems (KB5070773) (26200.6901)

1. Click Start, type Create a restore point and press Enter.
   • (Or press Win+R, type sysdm.cpl and press Enter → Advanced tab → System Protection.)
2. In the System Properties window that opens, click the System Protection tab.
3. Select the drive you want protection for (usually C and click Configure.
4. Choose Turn on system protection, set Max Usage (5–10% is common), then click Apply → OK.
5. Back in the System Protection tab click Create.
6. Give the restore point a meaningful name (for example: "Before Oct 25 cleanup" or "After removing Windows.old") and click Create.
7. Wait — Windows will report when the restore point is created successfully.

• Open PowerShell as Administrator (right‑click Start → Windows Terminal (Admin) or search PowerShell → Run as administrator).
• Run:
  Checkpoint-Computer -Description "Before cleanup - Oct 25, 2025" -RestorePointType "MODIFY_SETTINGS"
  Notes:
  • Run as admin and System Protection must be enabled for the drive.
  • If Checkpoint-Computer returns an error, read the Troubleshooting section below.

• List existing restore points:
  Get-ComputerRestorePoint
  That will show the description, timestamp, and sequence number for each restore point.

• Open Create a restore point as above → System Protection tab → click System Restore… → Next → choose the restore point → Next → Finish.
• The system will restart and apply the restore point. Your installed programs and system settings will return to the snapshot’s state, but your personal files are not touched.

• Boot into Windows Recovery Environment (hold Shift while selecting Restart, or boot from recovery media).
• Troubleshoot → Advanced options → System Restore → pick a restore point and apply.

• If System Protection is grayed-out or you can’t create a restore point:
  • Ensure the drive has System Protection turned on (System Properties → System Protection tab → Configure).
  • Ensure the Volume Shadow Copy and Microsoft Software Shadow Copy Provider services are running:
  • Start them from Services (services.msc) or run as admin:
    
    Code:

    sc start vss
    sc start swprv

  • Check disk space used by restore points:
    vssadmin list shadowstorage
  • If Checkpoint-Computer fails, the common causes are: System Protection disabled, insufficient disk quota for restore points, or Group Policy blocking restore points.
• Reminder: System Restore does not back up user documents — it restores system files, the registry and program files. For full safety, consider creating a system image or a File History/backup of your personal data.

• Create a restore point just before major changes (driver updates, large Windows updates, major app installs).
• Give descriptive names and include the date/time.
• Keep a regular backup (File History, third-party imaging, or full system image) alongside restore points.

• Walk you through the GUI steps with screenshots,
• Run the PowerShell commands for you (tell me if you want the exact command text copied),
• Or check whether System Protection is currently enabled on your C: drive (I can give the exact commands to run and how to paste the results here).

• Turn off Search history and Search highlights (Settings). This removes recent searches and the web/content “highlights.”
• Turn off app‑tracking and “most used”/recent items in Start (Settings) — this removes the Top Apps and Recent items Windows learns from your launches.
• If you still want no Search flyout content at all, hide the search box/icon on the taskbar (Taskbar settings) and use Win+S / Start typing when you need search.

• Open Settings → Privacy & security → Search permissions.
• Under History: turn off “Search history on this device” and click “Clear device search history.”
  This prevents Windows saving new searches and clears what’s stored.

• In the same Search permissions page, under More settings, turn off “Show search highlights.”
  This removes the web/content highlights from the search pane. Note: after turning it off you may still see Quick searches and Top apps.

• Settings → Privacy & security → General → turn off “Let Windows improve Start and search results by tracking app launches.”
• Settings → Personalization → Start → turn off “Show most used apps” and “Show recently opened items in Start, Jump Lists, and File Explorer.”
  Turning off the app‑launch tracking plus those Start settings prevents Windows from populating the Top Apps / recent list.

• Easiest non‑destructive option: hide the Search box (right‑click taskbar → Taskbar settings → Taskbar items → Search → set to Hide). You can still search with Win+S or Start then type. This removes the flyout UI from the taskbar.

• Clearing the Search cache (temporary) — Windows stores a DeviceSearchCache that repopulates. Deleting it clears Top Apps temporarily; it will be recreated. Some users create a junction to block it permanently, but that’s a hack and can break search behaviour for some apps. If you want the path and safe removal steps, I can paste the exact commands — note the Package folder name can vary by build. (discussion / workaround example on Microsoft Q&A).

• There’s no single “remove Top apps / quick searches” master switch in current Windows 11 — the supported approach is the Settings toggles above. Some heavy manual hacks exist (DeviceSearchCache deletion/junction or disabling Windows Search) but they have side effects (search breaks, apps not found, or things repopulate).
• After changing these settings, sign out / restart or open and close Search a couple of times to force the UI to refresh on some builds.

• Give the exact PowerShell/RegEdit commands to turn off the app‑tracking setting (Start_TrackProgs) and clear DeviceSearchCache?
• Or walk you through the GUI clicks with screenshots for your exact build?

• Run the PowerShell blocks as Administrator (right‑click Start → Windows Terminal (Admin) or PowerShell (Admin)) except where I call out HKCU edits (those don’t need elevation).
• I recommend you sign out/sign in or restart Explorer after the registry change so Start updates immediately. You’ll see the cache repopulate later if app tracking is still enabled in other places — these commands address the specific registry + cache you asked about.

stop search service​

find Search package folder (user profile)​

restart search service​

• Stopping WSearch (the Windows Search service) is the safe way to make sure files are not locked when deleting the cache. If Stop-Service fails (permission / service state), you can reboot and run the Remove-Item part early in the session.
• Deleting DeviceSearchCache clears the flyout’s cached Top Apps / Quick searches temporarily; Windows will repopulate it as you use apps unless tracking is fully disabled (we set Start_TrackProgs = 0 above and you already turned off the Settings toggles).

• After clearing cache and changing the reg value, sign out/in or restart Explorer (see Restart Explorer above). Also open the search flyout a few times to let Windows rebuild any cached lists. A reboot will certainly apply everything.

• Confirm Start_TrackProgs is 0:
  reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" /v Start_TrackProgs
• List remaining DeviceSearchCache (if any):
  Get-ChildItem "$env:LOCALAPPDATA\Packages\Microsoft.Windows.Search*" -Recurse -Directory | Where-Object Name -eq "DeviceSearchCache"

• Even after the above, Windows can repopulate suggestions from other signals (cloud / web suggestions or other telemetry settings). You already turned off the Settings toggles, which is the main supported method — clearing DeviceSearchCache just removes the local cache immediately. See earlier notes about Settings toggles + cache behavior.

• Paste the exact commands into a single runnable PowerShell script for you to run as Admin, or
• Walk you through running these one step at a time in your session and confirm the results.

• disables Start_TrackProgs (turns off app‑launch tracking),
• stops Windows Search, finds and moves (backs up) any DeviceSearchCache for your user,
• restarts Windows Search and Explorer so the UI refreshes,
• logs actions and records the previous Start_TrackProgs value so you can undo.

<#
.SYNOPSIS
  Disable Start_TrackProgs and clear (move backup) DeviceSearchCache for the current user, then restart search/explorer.

.NOTES
  Save as Clear-SearchCacheAndDisableTracking.ps1
  Run from an elevated PowerShell (Run as Administrator).
  Example:
    Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -Force
    .\Clear-SearchCacheAndDisableTracking.ps1

  The script moves the cache to a timestamped backup folder under $env:LOCALAPPDATA\DeviceSearchCacheBackup_<timestamp>.
  A log is written to $env:LOCALAPPDATA\DeviceSearchCacheCleanup.log
#>

function Assert-Elevated {
    $isAdmin = ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)
    if (-not $isAdmin) {
        Write-Error "This script must be run as Administrator. Right-click PowerShell and choose 'Run as administrator'. Exiting."
        exit 1
    }
}

# Ensure script is elevated (we need to stop/start services and restart explorer)
Assert-Elevated

$logFile = Join-Path $env:LOCALAPPDATA "DeviceSearchCacheCleanup.log"
Add-Content -Path $logFile -Value "==== Starting run: $(Get-Date -Format u) ===="

# 1) Read current Start_TrackProgs (store old value)
$regPath = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced"
try {
    $oldVal = Get-ItemProperty -Path $regPath -Name "Start_TrackProgs" -ErrorAction SilentlyContinue | Select-Object -ExpandProperty Start_TrackProgs -ErrorAction SilentlyContinue
} catch {
    $oldVal = $null
}
Add-Content -Path $logFile -Value "Previous Start_TrackProgs value: $($oldVal -ne $null ? $oldVal.ToString() : '<not present>')"

# 2) Set Start_TrackProgs = 0 (disable app tracking for Start/search)
try {
    New-ItemProperty -Path $regPath -Name "Start_TrackProgs" -PropertyType DWord -Value 0 -Force | Out-Null
    Add-Content -Path $logFile -Value "Set Start_TrackProgs = 0"
    Write-Output "Set Start_TrackProgs to 0 (disabled)."
} catch {
    Write-Warning "Failed to set Start_TrackProgs: $_"
    Add-Content -Path $logFile -Value "Failed to set Start_TrackProgs: $_"
}

# 3) Stop Windows Search service (WSearch) to safely remove cache
$svcName = "WSearch"
try {
    if (Get-Service -Name $svcName -ErrorAction SilentlyContinue) {
        Write-Output "Stopping service $svcName..."
        Stop-Service -Name $svcName -Force -ErrorAction SilentlyContinue
        Start-Sleep -Seconds 2
        Add-Content -Path $logFile -Value "Stopped $svcName"
    } else {
        Add-Content -Path $logFile -Value "$svcName not found"
    }
} catch {
    Write-Warning "Could not stop $svcName: $_"
    Add-Content -Path $logFile -Value "Could not stop $svcName: $_"
}

# 4) Find Microsoft.Windows.Search package folder(s) and move DeviceSearchCache to a backup folder
$packagesPath = Join-Path $env:LOCALAPPDATA "Packages"
$searchPkgs = Get-ChildItem -Path $packagesPath -Directory -ErrorAction SilentlyContinue | Where-Object { $_.Name -like "Microsoft.Windows.Search*" }

$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$backupRoot = Join-Path $env:LOCALAPPDATA "DeviceSearchCacheBackup_$timestamp"
New-Item -Path $backupRoot -ItemType Directory -Force | Out-Null
$foundAny = $false

foreach ($pkg in $searchPkgs) {
    $cachePath = Join-Path $pkg.FullName "LocalState\DeviceSearchCache"
    if (Test-Path $cachePath) {
        $foundAny = $true
        $dest = Join-Path $backupRoot ($pkg.Name + "_DeviceSearchCache")
        try {
            # Move the folder (preserves data); if Move fails, fall back to Remove-Item
            Move-Item -Path $cachePath -Destination $dest -Force -ErrorAction Stop
            Write-Output "Moved DeviceSearchCache from '$cachePath' to backup '$dest'"
            Add-Content -Path $logFile -Value "Moved '$cachePath' -> '$dest'"
        } catch {
            Write-Warning "Could not move '$cachePath' (will attempt remove): $_"
            Add-Content -Path $logFile -Value "Move failed for '$cachePath': $_"
            try {
                Remove-Item -Path $cachePath -Recurse -Force -ErrorAction Stop
                Write-Output "Removed DeviceSearchCache at '$cachePath'"
                Add-Content -Path $logFile -Value "Removed '$cachePath'"
            } catch {
                Write-Warning "Failed to remove '$cachePath': $_"
                Add-Content -Path $logFile -Value "Failed to remove '$cachePath': $_"
            }
        }
    } else {
        Add-Content -Path $logFile -Value "No DeviceSearchCache at expected path: $cachePath"
    }
}

if (-not $foundAny) {
    Write-Output "No Microsoft.Windows.Search package folder with DeviceSearchCache was found under $packagesPath"
    Add-Content -Path $logFile -Value "No DeviceSearchCache found in any Microsoft.Windows.Search package"
}

# 5) Restart Windows Search service
try {
    Start-Service -Name $svcName -ErrorAction SilentlyContinue
    Start-Sleep -Seconds 2
    Add-Content -Path $logFile -Value "Started $svcName"
    Write-Output "Restarted Windows Search service ($svcName)."
} catch {
    Write-Warning "Could not start $svcName: $_"
    Add-Content -Path $logFile -Value "Could not start $svcName: $_"
}

# 6) Restart Explorer to refresh Start/Search UI (optionally you may prefer to sign out or reboot)
try {
    Write-Output "Restarting Explorer to refresh Start/search UI..."
    Add-Content -Path $logFile -Value "Restarting Explorer..."
    Stop-Process -Name explorer -Force -ErrorAction SilentlyContinue
    Start-Sleep -Seconds 2
    Start-Process explorer.exe
    Add-Content -Path $logFile -Value "Explorer restarted."
} catch {
    Write-Warning "Failed to restart Explorer: $_"
    Add-Content -Path $logFile -Value "Failed to restart Explorer: $_"
}

# 7) Final messages and undo help
Add-Content -Path $logFile -Value "==== Completed run: $(Get-Date -Format u) ===="

Write-Output ""
Write-Output "Done. Log written to: $logFile"
if ($foundAny) {
    Write-Output "DeviceSearchCache was backed up to: $backupRoot"
} else {
    Write-Output "No DeviceSearchCache folders were found to back up."
}
Write-Output ""
Write-Output "Note: Windows may re-populate Top Apps / Quick searches over time if other tracking settings are enabled. You already changed Start_TrackProgs; if you want to restore the previous value run the undo command shown below."
Write-Output ""
Write-Output "Undo / restore Start_TrackProgs to previous value (run in an elevated PowerShell or a normal shell if you prefer):"
Write-Output "  # To restore tracking on (set to 1):"
Write-Output "  Set-ItemProperty -Path 'HKCU:\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Advanced' -Name 'Start_TrackProgs' -Type DWord -Value 1"
Write-Output ""
Write-Output "If you want to restore the backed-up cache (not usually needed) you can move it back from the $backupRoot folder into the original LocalState path for the relevant package and then restart WSearch and Explorer."

1. Save the script file to your downloads or Documents folder as Clear-SearchCacheAndDisableTracking.ps1.
2. Open Start → Windows Terminal (Admin) or PowerShell (Admin).
3. Navigate to the script folder, then run:
   Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -Force
   .\Clear-SearchCacheAndDisableTracking.ps1
4. After the script finishes, sign out/sign in or reboot if anything still appears.

• produce a single one-line command to paste into an already-elevated shell instead of saving a file; or
• modify the script to permanently delete (no backup) the cache instead of moving it; or
• add an -Undo parameter that restores Start_TrackProgs and (optionally) moves backup cache back.

• PowerShell complains because the string contained $svcName: $_ — the colon after the variable name makes the parser try to treat "$svcName:" as a variable/drive token. PowerShell wants the variable name delimited when followed by punctuation. Use $() (or $() around each variable) or string formatting so the parser knows where the variable name ends. (This is why the error message suggested using ${} to delimit the name.)

• Replace every instance of "… $svcName: $" (and "… $svcName: $" in Add-Content lines) with either:
  • "$($svcName): $($_)" (easy, readable)
  • or use the formatting operator: "Could not stop {0}: {1}" -f $svcName, $_

# (Same header/notes as before)
function Assert-Elevated {
    $isAdmin = ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)
    if (-not $isAdmin) {
        Write-Error "This script must be run as Administrator. Right-click PowerShell and choose 'Run as administrator'. Exiting."
        exit 1
    }
}

Assert-Elevated

$logFile = Join-Path $env:LOCALAPPDATA "DeviceSearchCacheCleanup.log"
Add-Content -Path $logFile -Value "==== Starting run: $(Get-Date -Format u) ===="

$regPath = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced"
try {
    $oldVal = Get-ItemProperty -Path $regPath -Name "Start_TrackProgs" -ErrorAction SilentlyContinue | Select-Object -ExpandProperty Start_TrackProgs -ErrorAction SilentlyContinue
} catch {
    $oldVal = $null
}
Add-Content -Path $logFile -Value "Previous Start_TrackProgs value: $($oldVal -ne $null ? $oldVal.ToString() : '<not present>')"

try {
    New-ItemProperty -Path $regPath -Name "Start_TrackProgs" -PropertyType DWord -Value 0 -Force | Out-Null
    Add-Content -Path $logFile -Value "Set Start_TrackProgs = 0"
    Write-Output "Set Start_TrackProgs to 0 (disabled)."
} catch {
    Write-Warning "Failed to set Start_TrackProgs: $_"
    Add-Content -Path $logFile -Value "Failed to set Start_TrackProgs: $($_)"
}

$svcName = "WSearch"
try {
    if (Get-Service -Name $svcName -ErrorAction SilentlyContinue) {
        Write-Output "Stopping service $svcName..."
        Stop-Service -Name $svcName -Force -ErrorAction SilentlyContinue
        Start-Sleep -Seconds 2
        Add-Content -Path $logFile -Value "Stopped $svcName"
    } else {
        Add-Content -Path $logFile -Value "$svcName not found"
    }
} catch {
    Write-Warning "Could not stop $($svcName): $($_)"
    Add-Content -Path $logFile -Value "Could not stop $($svcName): $($_)"
}

$packagesPath = Join-Path $env:LOCALAPPDATA "Packages"
$searchPkgs = Get-ChildItem -Path $packagesPath -Directory -ErrorAction SilentlyContinue | Where-Object { $_.Name -like "Microsoft.Windows.Search*" }

$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$backupRoot = Join-Path $env:LOCALAPPDATA "DeviceSearchCacheBackup_$timestamp"
New-Item -Path $backupRoot -ItemType Directory -Force | Out-Null
$foundAny = $false

foreach ($pkg in $searchPkgs) {
    $cachePath = Join-Path $pkg.FullName "LocalState\DeviceSearchCache"
    if (Test-Path $cachePath) {
        $foundAny = $true
        $dest = Join-Path $backupRoot ($pkg.Name + "_DeviceSearchCache")
        try {
            Move-Item -Path $cachePath -Destination $dest -Force -ErrorAction Stop
            Write-Output "Moved DeviceSearchCache from '$cachePath' to backup '$dest'"
            Add-Content -Path $logFile -Value "Moved '$cachePath' -> '$dest'"
        } catch {
            Write-Warning "Could not move '$cachePath' (will attempt remove): $($_)"
            Add-Content -Path $logFile -Value "Move failed for '$cachePath': $($_)"
            try {
                Remove-Item -Path $cachePath -Recurse -Force -ErrorAction Stop
                Write-Output "Removed DeviceSearchCache at '$cachePath'"
                Add-Content -Path $logFile -Value "Removed '$cachePath'"
            } catch {
                Write-Warning "Failed to remove '$cachePath': $($_)"
                Add-Content -Path $logFile -Value "Failed to remove '$cachePath': $($_)"
            }
        }
    } else {
        Add-Content -Path $logFile -Value "No DeviceSearchCache at expected path: $cachePath"
    }
}

if (-not $foundAny) {
    Write-Output "No Microsoft.Windows.Search package folder with DeviceSearchCache was found under $packagesPath"
    Add-Content -Path $logFile -Value "No DeviceSearchCache found in any Microsoft.Windows.Search package"
}

try {
    Start-Service -Name $svcName -ErrorAction SilentlyContinue
    Start-Sleep -Seconds 2
    Add-Content -Path $logFile -Value "Started $svcName"
    Write-Output "Restarted Windows Search service ($svcName)."
} catch {
    Write-Warning "Could not start $($svcName): $($_)"
    Add-Content -Path $logFile -Value "Could not start $($svcName): $($_)"
}

try {
    Write-Output "Restarting Explorer to refresh Start/search UI..."
    Add-Content -Path $logFile -Value "Restarting Explorer..."
    Stop-Process -Name explorer -Force -ErrorAction SilentlyContinue
    Start-Sleep -Seconds 2
    Start-Process explorer.exe
    Add-Content -Path $logFile -Value "Explorer restarted."
} catch {
    Write-Warning "Failed to restart Explorer: $($_)"
    Add-Content -Path $logFile -Value "Failed to restart Explorer: $($_)"
}

Add-Content -Path $logFile -Value "==== Completed run: $(Get-Date -Format u) ===="
Write-Output "Done. Log written to: $logFile"
if ($foundAny) { Write-Output "DeviceSearchCache was backed up to: $backupRoot" } else { Write-Output "No DeviceSearchCache folders were found to back up." }
Write-Output "To undo Start_TrackProgs run: Set-ItemProperty -Path 'HKCU:\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Advanced' -Name 'Start_TrackProgs' -Type DWord -Value 1"

1. Save the corrected file.
2. Open Windows Terminal (Admin) or PowerShell (Admin).
3. cd to the folder and run:
   Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -Force
   .\Clear-SearchCacheAndDisableTracking.ps1

• upload the corrected script text as a file for you to download, or
• paste a single one-line command to patch the current script file in-place.

• Your PowerShell session is the built‑in Windows PowerShell (5.1). My script used a C‑style ternary expression ( ? : ) inside a string to produce a short value — that syntax is only supported in PowerShell 7+. PowerShell 5.1 throws "Unexpected token '?'" when it sees that.

1. Open the script in Notepad (from an elevated PowerShell / terminal you were already using):
   notepad .\Clear-SearchCacheAndDisableTracking.ps1
2. Find this line (the one that caused the error):
   Add-Content -Path $logFile -Value "Previous Start_TrackProgs value: $($oldVal -ne $null ? $oldVal.ToString() : '<not present>')"
3. Replace it with these two lines:
   $oldValString = if ($null -ne $oldVal) { $oldVal.ToString() } else { '<not present>' }
   Add-Content -Path $logFile -Value "Previous Start_TrackProgs value: $oldValString"
4. Save the file and rerun the script (still in an elevated shell):
   Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -Force
   .\Clear-SearchCacheAndDisableTracking.ps1

• The replacement uses PowerShell 5.1 compatible if/else to build a safe string, then writes that string to the log. No ternary operator needed.

• paste the entire corrected script here for you to overwrite your file, or
• patch the script for you with a single command (I can give the one‑liner to run in elevated PowerShell that makes the exact replacement), or
• skip the script and run the three commands manually now to disable Start_TrackProgs and remove the cache — tell me which.

• New language features (ternary operator, pipeline chaining, null coalescing, etc.) so scripts written for PS7 won’t error in 5.1.
• Actively maintained on modern .NET (better performance and security updates).
• Can be set as your interactive default (Windows Terminal, VS Code) while keeping system PowerShell for OS tasks.

• PowerShell 7 (pwsh.exe) is side‑by‑side — it does not replace Windows PowerShell (powershell.exe). Some Windows modules that depend on the full .NET Framework may not work in PS7. If a module fails, run it in Windows PowerShell 5.1 or use compatibility tools.
• If you have scripts that rely on 5.1 behavior, test them before switching defaults.
• Installing from Microsoft Store auto‑updates; MSI / winget give you manual control.

1. Open Microsoft Store.
2. Search for “PowerShell” (publisher: Microsoft Corporation).
3. Install the app. It will add pwsh to your Start menu and auto‑update via Store.

1. Open the official PowerShell releases page (PowerShell/PowerShell on GitHub) and download the latest stable Windows MSI for your architecture (x64 or x86).
2. Run the MSI as Administrator and follow the installer. By default it adds pwsh.exe to your PATH.
3. After installation you can launch PowerShell 7 as “PowerShell” or “pwsh” from Start/Terminal.

1. In an elevated or normal command prompt, run:
   • winget search PowerShell
   • note the package Id shown (it will be something like a PowerShell package by Microsoft)
   • then run: winget install <PackageId> --exact
     If you want, I can look up the exact current winget Id for you and paste the single command to run.

• Open PowerShell 7 from Start (or run pwsh from terminal) and run:
  pwsh -NoProfile -ExecutionPolicy Bypass -File .\Clear-SearchCacheAndDisableTracking.ps1
  This runs the script using PowerShell 7 and will avoid the 5.1 parsing errors you saw.

• Open Windows Terminal → Settings → Default profile → choose the PowerShell 7 profile (usually named “PowerShell” or “pwsh”). This only affects interactive sessions launched from Terminal.

• If a module isn’t working in PS7, you can:
  • Run it in Windows PowerShell (powershell.exe) for that task, or
  • Use the WindowsCompatibility/WindowsCompatibilityHelper approach (there’s a community/official compatibility helper to auto‑import modules into PS7 via implicit remoting) — I can provide commands if you hit a broken module.

• Uninstall via Settings → Apps → Installed apps (find “PowerShell” and uninstall) or use Programs & Features if installed via MSI. Microsoft Store apps can be removed from the Store UI.

• Yes — install PowerShell 7 (Microsoft Store or MSI). Then run the corrected script in pwsh (just use the pwsh command above). That will let you use the ternary/other new operators without changing the script for PS5.1.

• Open an elevated Command Prompt / PowerShell (recommended for installs) and run:
  winget search --source winget PowerShell

• Run as Administrator:
  winget install --id Microsoft.PowerShell --exact
  (short form: winget install --id Microsoft.PowerShell -e)

• After installation, confirm version:
  pwsh --version

• From the same elevated prompt (or a new pwsh session):
  pwsh -NoProfile -ExecutionPolicy Bypass -File "C:\path\Clear-SearchCacheAndDisableTracking.ps1"
  (use the actual path where you saved the script)

• Run: winget show --id Microsoft.PowerShell
  That will show if the package exists in your winget source. If the Id differs on your machine, use the Id shown by winget show or winget search.

• Microsoft Store: install “PowerShell” (store entry) — convenient because the Store auto‑updates.
• MSI from GitHub releases: download and run the official MSI if you prefer manual control.

• paste a single copy/paste command to install PowerShell 7 for you now, or
• walk you through the install interactively and then run the script under pwsh and show the log output?

• Clearing UserAssist removes your recorded “most used” counts (Top Apps). It’s reversible only by restoring the backup export file I show.
• Rebuilding the search index can take some time and will temporarily make Windows Search slower until the index is rebuilt.
• I’ll include undo steps for everything.

• Control Panel → Indexing Options → Advanced → Rebuild (this is simple and recommended).

rename the index folder (keeps a copy)​

restart explorer (will close/start shell)​

• Some entries (Quick searches / Recent) can be repopulated from cloud/online signals or from the rebuilt index as apps are used. The combination above removes the local signals (UserAssist counts, index, device search history) and disables web suggestions so new entries should be minimal going forward.

• turn off Search history on this device (and click Clear device search history)
• turn off Show search highlights
• turn off “Search online and include web results” (if present)

• Control Panel → Indexing Options → Advanced → Rebuild

• GUI rebuild is easiest and less invasive. The PowerShell rename keeps a backup of the old index if you want to revert.
• Rebuilding the index can take some minutes and may temporarily make search slower.

• After clearing UserAssist and rebuilding the index, Top Apps / Most used should be cleared. Quick Searches and Recent should also be reduced once the index is rebuilt and device search history is cleared. If you still see items after reboot, they’re likely coming from cloud/web suggestions or repopulation from app usage — the registry flags above should have stopped cloud suggestions; app usage will repopulate as you launch apps.

• package Steps A–E into a single test-and-execute PowerShell script (with prompts and a dry‑run mode), or
• walk you through the GUI Indexing Options rebuild and then run just the UserAssist clear for you.