Windows - Software - Uninstall Print3D

What the Print 3D Uninstaller does

This Automox Worklet™ uninstalls the Microsoft Print 3D AppX package from Windows endpoints across your fleet. The Worklet detects the Microsoft.Print3D package in any user profile, removes the per-user installation, and unregisters the provisioned package so new user profiles do not receive a fresh copy at first sign-in.

Microsoft deprecated Print 3D and removed it from the Microsoft Store in 2023. The app no longer receives feature work or security servicing from Microsoft, yet the AppX package still ships preinstalled on most Windows 10 and earlier Windows 11 images. The Worklet treats Print 3D as orphaned bloatware: code present on the endpoint with no patching pipeline behind it.

The script uses native PowerShell AppX cmdlets – Get-AppxPackage, Remove-AppxPackage, and Remove-AppxProvisionedPackage – so it does not depend on the Microsoft Store, the App Installer service, or any third-party tooling. The remediation is idempotent: re-running the Worklet on a clean endpoint succeeds without taking action.

Why remove Microsoft Print 3D from your fleet

Print 3D is a Universal Windows Platform app Microsoft retired in November 2023. The store listing is gone, the app has no future security updates, and CVE-2023-23378 – a 3MF parser remote code execution flaw rated CVSS 7.8 – was the last public vulnerability disclosed before deprecation. Any endpoint that still has the AppX package installed is running unsupported Microsoft code with a known CVE and no vendor path forward. For organizations that never used 3D printing, the app has been pure attack surface since first boot.

Deprecated UWP apps are a recurring last-mile problem: they ship in the image, sit dormant for years, and become a finding on the next CVE-2023-23378 scanner pass. This Worklet runs Remove-AppxPackage against every installed copy on the endpoint and Remove-AppxProvisionedPackage against the provisioned image so the package does not reinstall when a new user account first signs in. Scheduling the policy on a recurring cadence catches Windows 10 and Windows 11 image refreshes that ship the provisioned copy back to the endpoint, so the next vulnerability scan returns a clean Print 3D finding.

How Print 3D removal works

1. Evaluation phase: Runs Get-AppxPackage -AllUsers -Name Microsoft.Print3D and Get-AppxProvisionedPackage -Online filtered on the same publisher name. If either command returns a package object, the endpoint is flagged non-compliant and remediation is scheduled. If both return empty, the endpoint is compliant and no action is taken.

2. Remediation phase: Pipes the Get-AppxPackage result to Remove-AppxPackage to uninstall Print 3D from every user profile on the endpoint, then runs Remove-AppxProvisionedPackage -Online -PackageName <name> against the provisioned entry so new user profiles do not receive a copy at first sign-in. The script exits 0 when both removals succeed, or non-zero with a message in stderr when an AppX cmdlet returns an error.

Microsoft Print 3D removal requirements

• Windows 10, Windows 11, or Windows Server 2016 and later (the AppX servicing stack)

• PowerShell 5.1 or later, available by default on every supported Windows build

• Local administrator privileges (the Automox agent already runs in SYSTEM context, which satisfies this)

• Network connectivity to the Automox agent endpoint for evaluation reporting and policy delivery

• No prerequisite tooling on the endpoint – the Worklet uses only native PowerShell AppX cmdlets

Expected endpoint state after Print 3D removal

After a successful remediation run, Microsoft.Print3D is gone from the endpoint. Get-AppxPackage -AllUsers -Name Microsoft.Print3D returns nothing, the app no longer appears under Settings, Apps, Installed apps, and the Print 3D tile is removed from the Start menu for every user profile. Files saved by the application (.3mf files in the user's Documents folder, for example) are preserved; only the application package is removed. The Worklet also leaves no orphan registry keys behind, because AppX uninstallation is handled by the Windows AppX servicing stack rather than a legacy MSI installer.

Subsequent evaluation runs continue to report the endpoint as compliant because the package is no longer present. If a sysprep image refresh or an out-of-band Microsoft update reintroduces the AppX package, the next scheduled evaluation flags the endpoint and remediation removes Print 3D again. For audit evidence, capture the Automox activity log entry showing the remediation exit code 0 alongside the Get-AppxPackage -AllUsers output confirming the empty result; together they document the before-and-after state for the policy run.