Remove All Windows 10 Apps Except Store And Calculator

Estimate reclaimed storage and cleanup time when removing all Windows 10 apps except Store and Calculator.

Why remove all Windows 10 apps except Store and Calculator?

Many Windows 10 deployments arrive with a generous suite of preinstalled applications that cover everything from games to consumer media, yet business environments frequently need only a minimal baseline. When the goal is to “remove all Windows 10 apps except Store and Calculator,” it is typically driven by a desire to streamline the user experience, reduce unnecessary background activity, and reclaim storage space on devices with tight capacity. The Microsoft Store remains essential for controlled app distribution, while Calculator is a core productivity tool that nearly every user expects. This specific approach provides a balanced minimum footprint: it reduces clutter without compromising enterprise app delivery or everyday utility.

Beyond aesthetics, removing bundled apps can reduce attack surface by limiting executables and services that run in the background. While these apps are not inherently unsafe, every installed component is a potential vector, especially if it remains unpatched. Minimal baselines align with many security frameworks and configuration standards. If you are maintaining a fleet of Windows 10 devices, consistent baseline management is often recommended by federal and educational security guidelines such as those available from CISA and NIST. By removing nonessential apps, you can align a deployment with least-privilege design and establish a predictable operating environment.

Preparation: inventory, policy alignment, and communication

Before you remove Windows 10 apps, it is critical to inventory what is currently installed, determine which apps are provisioned for new users, and confirm policy requirements. A single Windows 10 machine can contain two layers of app installation: user-specific apps and system-provisioned apps that will install for every new user profile. Removing only the user layer can lead to the app reappearing for a new login; removing the provisioned layer ensures the app is not reinstalled for new users.

It is also vital to communicate with stakeholders. Users may rely on certain apps, even if they appear nonessential. For example, a group might depend on the Photos app for quick viewing or the Mail app for secondary accounts. Your strategy should state that the goal is to keep Store and Calculator while removing everything else, but you can maintain a list of approved re-additions if needed.

• Confirm you are not violating software license requirements or organizational policy.
• Export an inventory of installed packages and provisioned packages.
• Plan a rollback or reinstallation strategy for any removed app.
• Notify users about expected changes and provide alternatives.

Understanding the app types you will remove

Windows 10 uses a combination of traditional Win32 applications and modern UWP (Universal Windows Platform) apps. The removal process typically targets UWP packages installed per-user and provisioned packages that are part of the OS image. Most of the “built-in” apps such as 3D Viewer, Xbox components, and consumer media are UWP packages. You will also see dependencies and framework packages that should remain intact to prevent disruptions. Removing everything except Store and Calculator must be done with precision to avoid breaking the Store’s dependencies.

Primary categories of Windows 10 apps

• Consumer apps: games, streaming, social, and promotional apps.
• System utilities: Photos, Groove Music, and 3D apps.
• Enterprise tools: Your Phone, mixed reality, or other optional system components.
• Core services: Store, Calculator, and frameworks.

Method overview: PowerShell and provisioning removal

PowerShell is the preferred management tool to remove all Windows 10 apps except Store and Calculator. It offers precise filtering so that you can target app packages by name. A typical process includes listing installed packages, removing user-specific packages, and removing provisioned packages from the base image. Some administrators also use DISM on offline images or Group Policy to restrict consumer experiences. For most scenarios, PowerShell provides the balance of control and transparency.

Recommended workflow

First, list all packages and identify Store and Calculator. The modern Calculator is usually named Microsoft.WindowsCalculator, while the Store package is typically Microsoft.WindowsStore. Your script should explicitly exclude these package names while removing everything else. Next, remove provisioned packages with the same exclusions. This ensures that future users do not receive the removed apps again. Always test on a single machine before using automation at scale.

Key PowerShell concepts for safe removal

When working in PowerShell, you will encounter two common commands: Get-AppxPackage and Remove-AppxPackage. The first enumerates installed packages per user. For provisioned packages, use Get-AppxProvisionedPackage -Online and remove with Remove-AppxProvisionedPackage -Online. The phrase “remove all Windows 10 apps except Store and Calculator” indicates a filtered removal, which can be accomplished using Where-Object filters.

Be mindful of frameworks such as Microsoft.VCLibs or Microsoft.NET.Native. These are dependencies for Store or other system components. While the requirement is to remove everything except Store and Calculator, you should avoid touching frameworks unless you have validated the impact. A safe approach is to remove consumer apps while leaving framework packages and the Store itself intact.

Data table: common apps and removal priority

App Package Name	Category	Typical Priority	Notes
Microsoft.WindowsStore	Core	Keep	Store required for managed app distribution.
Microsoft.WindowsCalculator	Core	Keep	Essential utility for users.
Microsoft.XboxGamingOverlay	Consumer	Remove	Gaming overlay not needed in most business environments.
Microsoft.3DBuilder	Consumer	Remove	Typically unnecessary for enterprise deployment.

Data table: estimated storage savings

Device Type	Average App Count	Estimated Savings	Time to Remove (minutes)
Standard Office Laptop	28	2.5 GB	4 – 6
Education Chromebook Replacement	35	3.2 GB	6 – 10
High-End Workstation	25	2.0 GB	4 – 5

Building a repeatable removal script

When you scale up to dozens or hundreds of endpoints, manual removal is inefficient. Use a PowerShell script that loops through the package list, excludes Store and Calculator, and logs every removal. Logging is vital for audit and troubleshooting. You can redirect output to a CSV or central log file for later review. In enterprise environments, test scripts against your standard image, then deploy via management platforms like Microsoft Endpoint Configuration Manager or Intune.

An example pattern is: collect all Appx packages, filter out Microsoft.WindowsStore and Microsoft.WindowsCalculator, then remove the remaining packages. Follow by removing provisioned packages with the same exclusions. This ensures that new user profiles do not regain the removed apps, keeping the deployment clean over time.

Handling critical dependencies and user experience

The command to remove all Windows 10 apps except Store and Calculator may sound straightforward, but Windows has hidden dependencies. The Store relies on certain frameworks, and Calculator in some builds uses components from the Windows app framework. If you remove these dependencies, you risk disabling the Store or causing Calculator to fail to launch. That is why a careful filter that targets consumer apps while preserving frameworks is best practice. You might also exclude Microsoft.WindowsAppRuntime and other modern dependencies depending on build version. Always confirm whether these components are system-critical by referencing Microsoft documentation or the security baselines from government and educational sources like NIST Cybersecurity Framework.

In a user-facing sense, removing apps can reduce distractions and improve focus, but it can also cause confusion if users see pinned icons or tile placeholders. It is wise to reset the Start menu layout after removal. Also consider replacing removed apps with enterprise-approved alternatives. For example, if you remove Photos, ensure a lightweight viewer is available. If you remove Mail, provide instructions for Outlook or webmail access.

Monitoring, compliance, and update considerations

Windows updates can reintroduce certain apps or change package names. Because of this, a one-time cleanup may not be sufficient. Build an ongoing compliance task that periodically verifies the presence of unwanted apps and removes them again if they return. Group Policy and provisioning control can reduce the frequency of reappearance, but large feature updates may still add new packages. Keep a watch list of app IDs and track release notes from Microsoft to stay ahead of changes.

From a compliance perspective, you should align your app reduction strategy with internal policies and external guidelines. Security recommendations from CISA secure configuration resources often emphasize minimal software baselines. Additionally, educational institutions can consult guidance at university security pages to align with academic requirements. Document your approach to demonstrate that removal was systematic, tested, and backed by documented business need.

Common mistakes to avoid

Removing the Store unintentionally

Store is often removed by broad scripts that remove all Appx packages. When you remove Store, you lose a primary distribution channel and updates for apps. Recovering it can be complex, sometimes requiring reinstallation or a repair install. Always explicitly exclude Store in your script. If you plan to use offline provisioning, ensure the Store package remains in your image.

Ignoring provisioned packages

Removing only per-user apps leaves the provisioned packages intact, which means new users will still get the unwanted apps. Make sure your script removes provisioned packages with proper exclusions. If you are creating a custom image, remove these packages in the offline image before deployment.

Skipping pilot testing

Every environment is unique. Users may rely on tools you did not anticipate. Pilot testing on a representative group allows you to discover dependency issues, missing apps, or compatibility problems. Document findings and adjust the exclusion list accordingly.

Optimizing the removal process for performance

In large deployments, performance matters. Removing apps in a single pass can be faster than multiple loops. Use PowerShell pipeline operations to reduce overhead and consider running the script during maintenance windows. If using enterprise management tools, schedule removal tasks when devices are idle or during off-hours. Logging should include timestamps and machine IDs to measure progress and identify any failures.

Reinstallation strategy and reversibility

Even with a clear policy, someone may require a removed app. The simplest method to restore a removed UWP app is through Microsoft Store or by using Add-AppxPackage with the app’s source. If the app was removed from provisioning, you may need to add it back for new users. Maintain a catalog of app packages, version numbers, and sources. For secure environments, keep a central repository of approved app packages.

Checklist for removing all Windows 10 apps except Store and Calculator

• Inventory installed and provisioned packages on a test machine.
• Identify Store and Calculator package names and ensure they are excluded.
• Create a PowerShell script with logging and error handling.
• Run a pilot deployment and collect user feedback.
• Roll out at scale via management tools with staged deployment.
• Set a compliance task to remove reintroduced apps after updates.
• Maintain a reinstallation plan for exceptions.

Final thoughts

Removing all Windows 10 apps except Store and Calculator is an efficient way to refine the operating system, improve focus, and reduce the footprint of nonessential software. It requires a methodical approach that respects dependencies and the user experience. A well-structured removal plan includes an inventory step, PowerShell-based filtering, provisioned package cleanup, and ongoing monitoring. By aligning this process with security frameworks and maintaining a clear rollback strategy, you can deliver a clean, manageable Windows 10 baseline that serves both users and administrators.

When executed carefully, this approach simplifies support, accelerates performance on storage-constrained devices, and aligns with modern security expectations. It turns Windows 10 into a lean, purpose-built platform where the Store remains the gateway for approved software and Calculator remains a universally trusted utility. That balance makes it a popular and practical standard for modern IT teams.