How to Copy and Deploy Snipping Tool Between Devices Using PowerShell

Overview

The Snipping Tool in Windows 11 (Microsoft.ScreenSketch) is an MSIX-packaged application — it cannot be copied between devices the same way a traditional .exe can. Attempting a simple file copy will not produce a working installation on the target device.

This article covers four PowerShell-based methods for deploying the Snipping Tool from one device to another, ranging from a single-command re-registration to a full MSIX export-and-import workflow for air-gapped environments, with an Intune option for enterprise fleet management.

Prerequisites

• Windows 11 on both source and target devices
• Administrator rights on both devices
• PowerShell 5.1 or later (built into Windows 11)
• For Method 2: a shared network folder or removable drive accessible from both devices
• For Method 3: internet access and winget installed (built into Windows 11)
• For Method 4: Microsoft Intune license and enrolled devices

Method 1 — Re-Register from the Windows Image

This is the fastest approach and works in most scenarios. When the Snipping Tool is provisioned in Windows but not installed for the current user — or after an accidental removal — you can re-register it directly from the existing package files on disk without copying anything from another device.

Run the following script as Administrator on the target device:

# Run as Administrator on the target device

$pkg = Get-AppxPackage -AllUsers -Name "Microsoft.ScreenSketch" | Select-Object -First 1

if ($pkg) {
    Write-Host "Re-registering Snipping Tool from:" -ForegroundColor Cyan
    Write-Host $pkg.InstallLocation -ForegroundColor White
    Add-AppxPackage -DisableDevelopmentMode -Register "$($pkg.InstallLocation)\AppxManifest.xml"
    Write-Host "Snipping Tool registered successfully." -ForegroundColor Green
} else {
    Write-Host "Package not found in provisioned store." -ForegroundColor Yellow
    Write-Host "Use Method 2 (export/import) or Method 3 (winget)." -ForegroundColor Yellow
}

Method 2 — Export from Source and Install on Target via Network Share

Use this method when the target device is offline or air-gapped, or when you need to deploy to a device with an identical Windows build without internet access. This involves two scripts: one to export from the source device and one to install on the target.

Script A — Run on the source device

# Run as Administrator on the SOURCE device
# Update $DestinationShare to your UNC path or local folder

$DestinationShare = "\\SERVER\Share\SnippingTool"
$AppName          = "Microsoft.ScreenSketch"

# Locate the installed package
$pkg = Get-AppxPackage -AllUsers -Name $AppName
if (-not $pkg) {
    Write-Error "Snipping Tool not found on this device. Exiting."
    exit 1
}

Write-Host "Package found: $($pkg.PackageFullName)" -ForegroundColor Cyan
Write-Host "Source location: $($pkg.InstallLocation)" -ForegroundColor Cyan

# Create the destination folder
if (-not (Test-Path $DestinationShare)) {
    New-Item -ItemType Directory -Path $DestinationShare -Force | Out-Null
    Write-Host "Created destination folder: $DestinationShare" -ForegroundColor Gray
}

# Grant read access to the protected WindowsApps folder
$source = $pkg.InstallLocation
takeown /f $source /r /d y 2>&1 | Out-Null
icacls $source /grant "Administrators:F" /t 2>&1 | Out-Null

# Copy package files to the share
Copy-Item -Path $source -Destination "$DestinationShare\AppFiles" -Recurse -Force
Write-Host "Package files copied." -ForegroundColor Cyan

# Save package metadata for reference
$pkg | Select-Object Name, Version, PackageFullName, InstallLocation |
    Export-Csv "$DestinationShare\PackageInfo.csv" -NoTypeInformation

Write-Host "Export complete. Share path: $DestinationShare" -ForegroundColor Green

Script B — Run on the target device

# Run as Administrator on the TARGET device
# Update $SourceShare to match the path used in Script A

$SourceShare = "\\SERVER\Share\SnippingTool"
$Manifest    = "$SourceShare\AppFiles\AppxManifest.xml"

# Verify the manifest exists before attempting installation
if (-not (Test-Path $Manifest)) {
    Write-Error "AppxManifest.xml not found at: $Manifest"
    Write-Error "Verify the share path and that Script A completed successfully."
    exit 1
}

Write-Host "Installing Snipping Tool from: $SourceShare" -ForegroundColor Cyan

try {
    Add-AppxPackage -DisableDevelopmentMode -Register $Manifest
    Write-Host "Snipping Tool installed successfully." -ForegroundColor Green
}
catch {
    Write-Error "Installation failed: $_"
}

Method 3 — Install via Winget

For internet-connected devices, winget provides the simplest deployment path. It downloads and installs the latest Snipping Tool directly from the Microsoft Store.

Run the following as Administrator on the target device:

# Install by Microsoft Store App ID (most reliable)
winget install --id "9MZ95KL8MR0X" --source msstore `
    --accept-package-agreements --accept-source-agreements

# Alternative: install by name
winget install --name "Snipping Tool" --source msstore `
    --accept-package-agreements --accept-source-agreements

Method 4 — Deploy via Microsoft Intune (Enterprise)

For managed device fleets, deploying the Snipping Tool through Microsoft Intune as a Microsoft Store app is the recommended approach. It scales to any number of devices, enforces the deployment silently, and keeps the app updated automatically.

Step 1 — Add the app in the Intune admin center

1. Sign in to the Microsoft Intune admin center.
2. Navigate to Apps → All apps → + Add.
3. Under App type, select Microsoft Store app (new) and click Select.
4. Search for Snipping Tool, select it, and click Select.
5. Configure the app name, description, and publisher details, then click Next.
6. On the Assignments tab, assign the app to the required device or user group as Required (auto-install) or Available (user-initiated from Company Portal).
7. Click Review + create → Create.

Step 2 — Verify deployment with a PowerShell detection script

Use the following as an Intune detection rule or remediation script to confirm the app is present on target devices:

# Intune detection script — exits 0 if Snipping Tool is installed, 1 if not

$pkg = Get-AppxPackage -Name "Microsoft.ScreenSketch" -ErrorAction SilentlyContinue

if ($pkg) {
    Write-Output "Snipping Tool detected: $($pkg.PackageFullName)"
    exit 0
} else {
    Write-Output "Snipping Tool not found."
    exit 1
}

Method Comparison

Troubleshooting

Error: Add-AppxPackage deployment failed with HRESULT 0x80073CF6

This error indicates a dependency conflict. Run the following to reset and retry:

Get-AppxPackage -AllUsers *ScreenSketch* | Remove-AppxPackage -AllUsers
# Then re-run Method 1 or Method 2 Script B

Error: Package could not be registered — files in use

Close any open Snipping Tool windows or processes, then retry the registration command.

winget returns “No package found”

Ensure the App Installer package is up to date. Open the Microsoft Store, search for App Installer, and update it. Then retry the winget command.

Summary

Deploying the Snipping Tool between Windows 11 devices requires working with its MSIX package structure rather than copying files directly. For most day-to-day scenarios, Method 1 (re-register) resolves the issue in seconds. Method 2 handles offline environments. Method 3 via winget is the quickest fix for internet-connected devices. For organizations managing endpoints at scale, Method 4 via Intune is the right long-term solution — it deploys automatically, keeps the app current, and provides full deployment visibility from the admin center.

Related Articles

• PowerShell MSIX cmdlets – Microsoft Learn
• Use the winget tool to install and manage applications – Microsoft Learn
• Add Microsoft Store apps to Microsoft Intune – Microsoft Learn
• Install Windows apps with App Installer – Microsoft Learn