Windows - Software - Uninstall Print3D

What the Print3D Uninstaller does

This Automox Worklet™ detects the Print3D application on Windows endpoints and flags them for automatic remediation. The Worklet uses PowerShell to scan for the Microsoft.Print3D AppX package, which contains a security vulnerability tracked as CVE-2023-23378.

During remediation, the Worklet removes all instances of the Print3D AppX package from the endpoint, including both user-installed and provisioned packages. This maintains complete removal of the vulnerable software across all user profiles.

Why remove Print3D from your endpoints

CVE-2023-23378 is a security vulnerability in Print3D that could allow attackers to execute code remotely. Removing this application eliminates the attack surface and reduces the risk of exploitation on your Windows endpoints. Unless your organization actively uses Print3D for 3D printing operations, keeping it installed introduces unnecessary security risk.

Automating the removal through this Worklet maintains consistent compliance across your entire fleet. Instead of manually uninstalling Print3D from each endpoint, you deploy the Worklet once and Automox handles the remediation automatically.

How Print3D removal works

1. Evaluation phase: Scans the endpoint using Get-AppxPackage to check if Microsoft.Print3D is installed for any user profile. If Print3D is found, the evaluation exits with a non-compliant status to trigger remediation.

2. Remediation phase: Uses Remove-AppxPackage to uninstall the Print3D package for all users, then removes the AppX provisioned package using Remove-AppxProvisionedPackage to prevent it from being automatically reinstalled on new user accounts.

Print3D removal requirements

• Windows 8 or later (Windows 10, Windows 11, Windows Server 2016 and later)

• PowerShell 5.0 or later

• Local administrator privileges to remove AppX packages and provisioned packages

• Network connectivity to the Automox agent for deployment and reporting

Expected state after Print3D removal

After the Worklet completes successfully, the Print3D application is completely removed from the endpoint. The Microsoft.Print3D AppX package is uninstalled for all user profiles, and the provisioned package is removed to prevent automatic installation on new user accounts. Users no longer have access to Print3D through the Windows Start menu or Applications list.

Subsequent evaluation scans will show the endpoint as compliant because Print3D is no longer installed. The Worklet remains in the remediation queue, but no further action is taken until Print3D is reinstalled (which would indicate a non-compliant state that triggers remediation again).

How to validate uninstall print3d changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for uninstall print3d.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Get-AppxPackage, Where-Object, Write-Output.

4. Validate remediation effects from script operations such as Get-AppxPackage, Where-Object, Write-Verbose, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for uninstall print3d. This supports repeatable software lifecycle workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as Get-AppxPackage, Where-Object, Write-Output and remediation operations such as Get-AppxPackage, Where-Object, Write-Verbose. Use these indicators to verify that endpoint changes match intended policy outcomes.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for uninstall print3d. This supports repeatable software lifecycle workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as Get-AppxPackage, Where-Object, Write-Output and remediation operations such as Get-AppxPackage, Where-Object, Write-Verbose. Use these indicators to verify that endpoint changes match intended policy outcomes.