Because AutoSettingsPS runs low-level system commands, it must be executed with elevated administrative permissions. Step 1: Adjust Execution Policies
The you are targeting (e.g., Windows 10 LTSC, Windows 11 Pro).
@ # AutoSettingsPS v0.5.9 Configuration Manifest OptimizationSettings = @ DisableTelemetry = $true RemoveUWPBloat = $true EnableHighPerformance = $true DisableCortana = $true SecurityHardening = @ SetStrictUAC = $true BlockRemoteRegistry = $true ConfigureDefender = $true UserInterface = @ ShowFileExtensions = $true HideTaskbarSearch = $true ApplyDarkTheme = $false Use code with caution. AutoSettingsPS by westlife v0.5.9
To use AutoSettingsPS, you typically need to run it through an elevated PowerShell terminal. Since it modifies deep system settings and registry keys, it is highly recommended to: before running any scripts.
A newer version, , also exists (often found in a folder named “windows10 1809+” inside some distributions), but 0.5.9 remains widely used due to its stability and the specific fixes it introduced. To use AutoSettingsPS, you typically need to run
The goal is to “disable all possible data collection and modern functions, leaving standard Windows functionality for games or work”.
Key features typically included in this version: The goal is to “disable all possible data
Have you used AutoSettingsPS v0.5.9? Share your experience in the technical forums. And as always, back up your data before running any system-altering scripts.
: Always create a fresh system checkpoint right before running the utility ( Checkpoint-Computer -Description "BeforeAutoSettings" -RestorePointType MODIFY_SETTINGS ).