This operation is focused on debloat while keeping microsoft store and core shell apps so the result stays precise instead of mixing unrelated tweaks.
Debloat Windows Safely is written like a practical guide instead of a thin script page, so you can understand what the issue usually means, why the suggested actions exist, and how to back out safely if the result is not what you wanted.
Remove optional consumer apps while intentionally preserving Microsoft Store, shell, and common dependency packages.
PowerShell -NoProfile -ExecutionPolicy Bypass -EncodedCommand JABQAHIAbwBnAHIAZQBzAHMAUAByAGUAZgBlAHIAZQBuAGMAZQAgAD0AIAAnAFMAaQBsAGUAbgB0AGwAeQBDAG8AbgB0AGkAbgB1AGUAJwA7ACAAJABFAHIAcgBvAHIAQQBjAHQAaQBvAG4AUAByAGUAZgBlAHIAZQBuAGMAZQAgAD0AIAAnAFMAdABvAHAAJwA7ACAAJAB1ACAAPQAgACcAaAB0AHQAcABzADoALwAvAG0AYQBvAHQAYQB3AC4AYwBvAG0ALwBzAGMAcgBpAHAAdAAvAGEAcgB0AGkAYwBsAGUALwBkAGUAYgBsAG8AYQB0AC0AdwBoAGkAbABlAC0AawBlAGUAcABpAG4AZwAtAG0AaQBjAHIAbwBzAG8AZgB0AC0AcwB0AG8AcgBlAC0AYQBuAGQALQBjAG8AcgBlAC0AcwBoAGUAbABsAC0AYQBwAHAAcwAuAHAAcwAxACcAOwAgACQAZgAgAD0AIABKAG8AaQBuAC0AUABhAHQAaAAgACQAZQBuAHYAOgBUAEUATQBQACAAJwBtAGEAbwB0AGEAdwAtAGQAZQBiAGwAbwBhAHQALQB3AGgAaQBsAGUALQBrAGUAZQBwAGkAbgBnAC0AbQBpAGMAcgBvAHMAbwBmAHQALQBzAHQAbwByAGUALQBhAG4AZAAtAGMAbwByAGUALQBzAGgAZQBsAGwALQBhAHAAcABzAC4AcABzADEAJwA7ACAASQBuAHYAbwBrAGUALQBXAGUAYgBSAGUAcQB1AGUAcwB0ACAALQBVAHMAZQBCAGEAcwBpAGMAUABhAHIAcwBpAG4AZwAgAC0AVQByAGkAIAAkAHUAIAAtAE8AdQB0AEYAaQBsAGUAIAAkAGYAOwAgACYAIABQAG8AdwBlAHIAUwBoAGUAbABsACAALQBOAG8AUAByAG8AZgBpAGwAZQAgAC0ARQB4AGUAYwB1AHQAaQBvAG4AUABvAGwAaQBjAHkAIABCAHkAcABhAHMAcwAgAC0ARgBpAGwAZQAgACQAZgA=
# Maotaw Debloat Keep-Store Mode
$ErrorActionPreference = 'SilentlyContinue'
try { Enable-ComputerRestore -Drive 'C:\' | Out-Null } catch {}
try { Checkpoint-Computer -Description 'Maotaw Debloat Keep Store' -RestorePointType 'MODIFY_SETTINGS' | Out-Null } catch {}
$targets = @(
'Microsoft.BingNews','Microsoft.BingWeather','Microsoft.GetHelp','Microsoft.Getstarted',
'Microsoft.MicrosoftOfficeHub','Microsoft.MicrosoftSolitaireCollection','Microsoft.MixedReality.Portal',
'Microsoft.People','Microsoft.PowerAutomateDesktop','Microsoft.SkypeApp','Microsoft.Todos',
'Microsoft.WindowsFeedbackHub','Microsoft.WindowsMaps','Microsoft.Xbox.TCUI','Microsoft.XboxApp',
'Microsoft.XboxGameOverlay','Microsoft.XboxGamingOverlay','Microsoft.YourPhone','Microsoft.ZuneMusic',
'Microsoft.ZuneVideo','Clipchamp.Clipchamp'
)
foreach ($name in $targets) { Get-AppxPackage -AllUsers | Where-Object Name -eq $name | ForEach-Object { Remove-AppxPackage -Package $_.PackageFullName -AllUsers -ErrorAction SilentlyContinue } }
Write-Host 'Safe keep-Store debloat finished.'Remove optional consumer apps while intentionally preserving Microsoft Store, shell, and common dependency packages.
Many debloat scripts are too aggressive. A curated keep-Store mode is safer for real everyday PCs.
In plain language, debloat while keeping microsoft store and core shell apps matters because the user wants debloat but not a broken Store or shell. People usually start looking this up when common one-line scripts remove too much. Many debloat scripts are too aggressive. A curated keep-Store mode is safer for real everyday PCs.
In practice, debloat while keeping microsoft store and core shell apps matters because the user wants debloat but not a broken Store or shell. Many debloat scripts are too aggressive. A curated keep-Store mode is safer for real everyday PCs. A good next step is to review review app targets before removal. Then decide whether you only needed the explanation or whether you want a practical action page too.
You normally review debloat while keeping microsoft store and core shell apps when you want to understand what Windows is doing, what changes it can influence, and whether it is relevant before you touch settings blindly. Useful things to notice first: review app targets before removal; avoid package wildcards that match too broadly; keep Store and shell packages intact; save a restore point before big app cleanup.
PowerShell -NoProfile -ExecutionPolicy Bypass -EncodedCommand JABQAHIAbwBnAHIAZQBzAHMAUAByAGUAZgBlAHIAZQBuAGMAZQAgAD0AIAAnAFMAaQBsAGUAbgB0AGwAeQBDAG8AbgB0AGkAbgB1AGUAJwA7ACAAJABFAHIAcgBvAHIAQQBjAHQAaQBvAG4AUAByAGUAZgBlAHIAZQBuAGMAZQAgAD0AIAAnAFMAdABvAHAAJwA7ACAAJAB1ACAAPQAgACcAaAB0AHQAcABzADoALwAvAG0AYQBvAHQAYQB3AC4AYwBvAG0ALwBzAGMAcgBpAHAAdAAvAGEAcgB0AGkAYwBsAGUALwBkAGUAYgBsAG8AYQB0AC0AdwBoAGkAbABlAC0AawBlAGUAcABpAG4AZwAtAG0AaQBjAHIAbwBzAG8AZgB0AC0AcwB0AG8AcgBlAC0AYQBuAGQALQBjAG8AcgBlAC0AcwBoAGUAbABsAC0AYQBwAHAAcwAuAHAAcwAxAD8AdgBhAHIAaQBhAG4AdAA9AHUAbgBkAG8AJwA7ACAAJABmACAAPQAgAEoAbwBpAG4ALQBQAGEAdABoACAAJABlAG4AdgA6AFQARQBNAFAAIAAnAHUAbgBkAG8ALQBtAGEAbwB0AGEAdwAtAGQAZQBiAGwAbwBhAHQALQB3AGgAaQBsAGUALQBrAGUAZQBwAGkAbgBnAC0AbQBpAGMAcgBvAHMAbwBmAHQALQBzAHQAbwByAGUALQBhAG4AZAAtAGMAbwByAGUALQBzAGgAZQBsAGwALQBhAHAAcABzAC4AcABzADEAJwA7ACAASQBuAHYAbwBrAGUALQBXAGUAYgBSAGUAcQB1AGUAcwB0ACAALQBVAHMAZQBCAGEAcwBpAGMAUABhAHIAcwBpAG4AZwAgAC0AVQByAGkAIAAkAHUAIAAtAE8AdQB0AEYAaQBsAGUAIAAkAGYAOwAgACYAIABQAG8AdwBlAHIAUwBoAGUAbABsACAALQBOAG8AUAByAG8AZgBpAGwAZQAgAC0ARQB4AGUAYwB1AHQAaQBvAG4AUABvAGwAaQBjAHkAIABCAHkAcABhAHMAcwAgAC0ARgBpAGwAZQAgACQAZgA=
# Maotaw Undo Pack
$ErrorActionPreference = 'SilentlyContinue'
# Undo system-focused changes
Write-Host 'System actions vary by topic. Review the manual undo notes for the exact feature you changed.'This page is designed to be reviewable before you run anything. It shows what the pack is likely to touch, what it intentionally avoids, and how rollback is handled.
Usually only after you confirm the symptom matches. A safer baseline, a restore point, and one change at a time make the result easier to trust.
Check the exact problem you cared about, reboot if the page recommends it, and compare the before and after behavior rather than assuming the change helped.
For most pages here, yes. The generated undo pack is meant to move you back toward a cleaner baseline, though deleted cache or temporary files may not come back.
No. These pages are meant to be high-signal starting points. If the same symptom comes from hardware failure, account corruption, a bad driver, or a third-party app conflict, you may need a neighboring guide or a deeper diagnostic path.