How to Remove Pre-Installed Apps Using PowerShell Commands

The Hidden Impact of Factory Software on Computer Performance

When buying a new computer, it is common to find dozens of programs we never asked for. These software items, known in the market as bloatware, take up storage space, consume RAM, and frequently run background processes without our consent. In practice, this means part of the money invested in high-end hardware is wasted running third-party utilities that only serve the commercial interests of manufacturers. The Windows operating system has historically come bundled with dozens of native tools and commercial suggestions that make manual cleanup difficult through the traditional graphical interface.

Cleaning these elements not only speeds up machine startup but also restores full user control over owned hardware. While the settings panel helps remove common programs, it often fails when trying to eliminate packaged applications in the modern Windows format, known as AppX packages. These packages are installed per user and are embedded in the operating system image, making deletion challenging for those relying solely on mice and visual windows. This exact scenario is where PowerShell, Microsoft's automation tool, comes into play.

Understanding the Power and Safety of PowerShell

PowerShell is an automation and configuration management framework created by Microsoft, consisting of an object-based command line and a robust scripting language. For those accustomed only to clicks, thinking about using text commands can seem intimidating, but in practice it acts as a direct assistant that executes exact orders without intermediaries. Unlike the old Command Prompt, PowerShell understands complex data structures, allowing you to filter, select, and manipulate operating system information surgically.

Despite its immense flexibility, tinkering with system internals requires caution. The popular saying that with great power comes great responsibility applies perfectly here. Some pre-installed packages seem useless at first glance yet support crucial subsystems like the taskbar, default calculator, or store integration. Therefore, before executing any destructive command, the ideal approach is to understand exactly which package is targeted, ensuring the system remains stable and functional after digital cleanup.

Mapping and Listing Installed Applications

The first step in any safe cleaning routine is investigation. Before erasing anything, we need to see what is installed in the current user profile. For this, we use a cmdlet, which is the technical term for an individual PowerShell command, called Get-AppxPackage. When we type this command without filters, PowerShell returns a massive list with hundreds of items, making manual reading practically impossible for any human.

To make this list useful, we combine the listing command with filtering tools. For instance, we can request only packages containing certain commercial names or focus on those non-essential to the system core. The following command lists installed packages in a simplified way within the terminal:

Get-AppxPackage | Select-Object Name, PackageFullName

This command gathers all packages and selects only the friendly name and full technical name of each. In practice, this filtering gives us the overview needed to identify culprits consuming unnecessary resources before moving to definitive removal.

Filtering Specific Software and Avoiding Critical Risks

After understanding the universe of programs present on the machine, the next challenge is separating wheat from chaff. Manufacturers usually mix games, streaming apps, and productivity utilities into a single homogeneous list. To avoid accidents that break the system, it is crucial to restrict searches to keywords that clearly identify unwanted software, such as the name of a specific social network or promotional game bundled from the factory.

PowerShell allows refining this search using conditional filters directly in the command line. Below is a practical example of how to search for packages containing specific terms:

Get-AppxPackage -Name *Xbox*

This command restricts the scope only to packages related to the Xbox platform. If the user does not play games on the computer and wants to reclaim space and memory consumed by these background services, this is the most direct way to find them. The asterisk (*) acts as a wildcard character, meaning any text can precede or follow the searched word, facilitating exact target location.

Executing Removal Safely at the User Level

With the target properly identified and isolated, we reach the actual removal moment. The command responsible for this task is Remove-AppxPackage. However, there is an important caveat: by default, Windows installs many of these apps so they remain available to any new user logging into the machine. If you remove the app only for your current user, it might reappear during the next major system update.

To perform deep cleaning affecting both the current user and the base system image, we combine commands using a logical pipeline (|), represented by the vertical bar character. Here is how to structure the command to remove an unwanted app from the current profile:

Get-AppxPackage *ZuneMusic* | Remove-AppxPackage

In practice, this command locates the old music package and sends it directly to the uninstallation function. If you wish to remove the app globally, preventing it from returning for new users, the -AllUsers parameter must be added to the main command, though this requires running PowerShell with Administrator privileges.

If you have an extensive list of unwanted programs and want to automate the process all at once, creating a small script is the best alternative. Instead of running command by command manually, we can group multiple targets into an array and iterate over them using a loop. Below is a functional batch cleanup script example:

$bloatware = @(
    '*XboxApp*',
    '*ZuneMusic*',
    '*YourPhone*',
    '*GetHelp*'
)
foreach ($app in $bloatware) {
    Get-AppxPackage -AllUsers -Name $app | Remove-AppxPackage -ErrorAction SilentlyContinue
}
This script iterates through each item in the list and executes global removal. The -ErrorAction SilentlyContinue parameter ensures that if any of the apps are no longer installed on the machine, the script keeps running without interrupting the flow with red error messages on screen.
Validating Results and Maintaining System Stability
After executing cleanup commands or scripts, it is vital to verify if the system continues operating seamlessly. Restarting the computer is the first step to ensure no orphan services remain hanging in RAM. Should any unexpected behavior occur, most packages removed via AppX can be easily reinstalled through the official Windows app store by searching for the original software name.
Maintaining an automation routine for cleaning new installations saves dozens of minutes of manual work, especially for IT professionals preparing multiple corporate computers. By mastering these basic PowerShell commands, users stop being hostages to manufacturer-imposed settings and gain total autonomy over their digital workspace, ensuring a faster, cleaner, and leaner operating system.