Interactive Troubleshooter

Published: Oct 28, 2026

Windows 11 Snipping Tool Not Working: App Permission Diagnostic

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Exhaustive diagnostic guide for Windows 11 Snipping Tool failures. Pinpoints UWP background permissions, expired digital certificates, app package corruptions, and graphics driver hook conflicts.

Full Diagnostic Tree & Step-by-Step Overview

What specific symptom or error behavior is occurring when using Snipping Tool on Windows 11?

Snipping Tool fails to open when pressing Win + Shift + S or Print Screen, but opens manually from Start.
Snipping Tool fails to open completely, crashes immediately on launch, or gives a 'This app can't open' error.
Snipping Tool opens and captures screen, but fails to save screenshots, clipboard fails, or gives 'Access Denied'.
Snipping Tool opens, but screen darkens and freezes, rendering overlay unresponsive during screen capture.

Which condition best describes the hotkey non-responsiveness?

Print Screen key or Win+Shift+S does nothing; background permissions or hotkey mapping are disabled.
A third-party application (e.g., OneDrive, Dropbox, Lightshot, ShareX) hijacked the Print Screen key.
Windows Snipping Tool Notification toggles are disabled under System Notifications.
Group Policy or MDM policy has blocked screen clipping and hotkey triggers across the system.

UWP Background App Permission & Hotkey Re-Binding Fix

Solution:

Root Cause: Disabled UWP Background Permissions and Global Hotkey Re-Binding Failure

In Windows 11, Snipping Tool (Microsoft.ScreenSketch) relies on background task execution managed by the Universal Windows Platform (UWP) application lifecycle service (TimeBrokerServer). When 'Background apps permissions' are set to 'Never' or Windows Shell hotkey bindings become unhooked in explorer.exe, pressing Win + Shift + S fails to spawn the background process SnippingTool.exe without raising a user-visible error.

Diagnostic Verification:

Open PowerShell as Administrator and execute:

Get-AppxPackage -Name *ScreenSketch* | Select-Object Name, InstallLocation, Status

Check Windows Event Viewer: Windows Logs -> Application -> Look for Event ID 1000 or 1002 under Application Error referencing SnippingTool.exe or ShellExperienceHost.exe.

Step-by-Step Fix:

1Enable Background App Permission for Snipping Tool:

Open Settings (Win + I) and navigate to Apps > Installed apps.

Search for Snipping Tool, click the three-dots menu icon, and select Advanced options.

Under Background apps permissions, set Let this app run in the background to Always (or Power optimized).

2Enable Print Screen Key Shortcut Binding:

Navigate to Settings > Accessibility > Keyboard.

Toggle ON Use the Print screen button to open screen snipping.

3Restart Windows Explorer Shell:

Open Task Manager (Ctrl + Shift + Esc), locate Windows Explorer in the Processes tab.

Right-click Windows Explorer and select Restart to re-hook system keyboard events.

4Reset Hotkey State via PowerShell (if problem persists):

Run PowerShell as Administrator and re-register the app package:

Get-AppxPackage -AllUsers *ScreenSketch* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Prevention & Long-Term Monitoring:

Ensure group policies do not override background app lifecycle settings. Periodically audit app settings after major Windows 11 feature updates.

Third-Party Hotkey Interception & Key Hook Conflict Fix

Solution:

Root Cause: Windows Low-Level Keyboard Hook (WH_KEYBOARD_LL) Interception

When utility software such as Microsoft OneDrive, Dropbox, Snagit, Lightshot, or gaming overlays (NVIDIA ShadowPlay/GeForce Experience, Discord) register a low-level global keyboard hook (SetWindowsHookExW) on VK_SNAPSHOT (Print Screen) or Win+Shift+S, Windows passes the keyboard interrupt exclusively to the registered process. If that application consumes the input without executing a snip, the native Windows Snipping Tool receives no notification.

Diagnostic Verification:

Perform a clean boot to verify if a startup application is conflicting.

Check running hook listeners using PowerShell:

Get-Process | Where-Object {$_.MainWindowTitle -ne ''} | Select-Object ProcessName, Id, Path

Step-by-Step Fix:

1Disable Screenshot Interception in Common Cloud Storage Apps:

OneDrive: Right-click OneDrive cloud icon in tray > Settings (Gear icon) > Sync and backup > Toggle OFF Save screenshots I capture to OneDrive.

Dropbox: Open Preferences > Import > Uncheck Share screenshots using Dropbox.

2Rebind Hotkeys in Screen Capture Utilities:

If running ShareX, Lightshot, or Snagit, open their respective settings menu and remove PrtScn or Win+Shift+S from their global hotkey list.

3Verify Keyboard Driver & Windows System Binding:

Open Settings > Accessibility > Keyboard.

Toggle Use the Print screen button to open screen snipping to Off, wait 5 seconds, and toggle it back On.

4Restart system or restart Windows Explorer process via Task Manager.

Prevention & Long-Term Monitoring:

Review third-party application shortcut settings before installing desktop productivity suites or screen recording software.

Windows Shell Notification Service & Focus Assist Fix

Solution:

Root Cause: Action Center / Notification State Suppression

Snipping Tool stores captured snippets in the system clipboard and relies on the Windows Notification Service (wpnUserService) to present the interactive popup editor. If notifications for Snipping Tool are turned off, or if Do Not Disturb / Focus Assist suppression rules drop notification toasts, Snipping Tool appears non-functional despite capturing the region successfully in RAM.

Diagnostic Verification:

Capture a snippet using Win + Shift + S, then open Notepad and press Ctrl + V. If the image or clipping text pastes, Snipping Tool captured successfully, but the UI notification toast failed to trigger.

Step-by-Step Fix:

1Enable Snipping Tool System Notifications:

Open Settings > System > Notifications.

Ensure global Notifications are turned On.

Scroll down to Notifications from apps and other senders, locate Snipping Tool, and ensure the toggle is On.

Click Snipping Tool and check both Show notification banners and Show notifications in notification center.

2Configure Do Not Disturb / Focus Settings:

Go to Settings > System > Focus or Do not disturb.

Ensure Snipping Tool is added to Priority notifications list or disable automatic Focus sessions during normal operation.

3Restart Windows Push Notifications User Service (wpnUserService):

Open PowerShell as Administrator and run:

Get-Service wpnuserService* | Restart-Service -Force

Prevention & Long-Term Monitoring:

Ensure Windows Focus Mode rules do not permanently suppress high-priority app banners from system applications.

Group Policy / Registry Hotkey Restriction Fix

Solution:

Root Cause: Policy Restrictions on Windows Hotkeys & Screen Capture

In managed enterprise environments or tweaked Windows installations, administrative policies enforced via Group Policy (GPO) or Local Registry keys disable screen clipping APIs (DisableScreenSketchHotkey) or general Windows hotkey combinations (NoWinKeys).

Diagnostic Verification:

Open Command Prompt and check registry policy values:

reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\AppPrivacy" /v LetAppsRunInBackground
reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" /v NoWinKeys

Step-by-Step Fix:

1Re-enable Windows Hotkeys via Registry Editor:

Press Win + R, type regedit, and press Enter.

Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer

If DWORD value NoWinKeys exists, set its value to 0 or delete the entry.

2Verify Screen Sketch Group Policy:

Press Win + R, type gpedit.msc, and press Enter (Windows Pro/Enterprise).

Navigate to: User Configuration > Administrative Templates > Windows Components > Tablet PC > Accessories.

Ensure Do not allow Snipping Tool to run is set to Not Configured or Disabled.

3Force Policy Update:

Open Command Prompt as Administrator and run:

gpupdate /force

4Sign out of Windows and sign back in.

Prevention & Long-Term Monitoring:

Coordinate system images with domain administrators to ensure developer or end-user endpoints allow native OS screenshot utility policies.

What error message or behavior occurs when attempting to launch Snipping Tool?

Error message: 'This app can't open. A problem with Windows is preventing Snipping Tool from opening.'
Snipping Tool window opens briefly, flashes white/black, and crashes immediately without an explicit dialog.
Error: 'File System Error (-2147219196)' or general MSIX / AppX package deployment failure.
App is completely missing from system, greyed out, or displays deployment error 0x80073CF6.

Expired Windows Digital Certificate Repair Protocol

Solution:

Root Cause: Expired AppX/MSIX Package Digital Signature Certificate

A critical issue on Windows 11 builds (specifically originating from expired Microsoft digital certificates for UWP applications) causes Snipping Tool, along with the Touch Keyboard and Emoji Panel, to crash upon initialization due to validation failure in AppxAppExecutionAlias.dll.

Diagnostic Verification:

Open Event Viewer > Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server > Operational.

Search for Event ID 404 or 855 containing certificate validation errors (0x800B0101 - CERT_E_EXPIRED).

Reference the Microsoft Official Support Guide on Windows App Certificate Validation for additional details on AppX signature enforcement.

Step-by-Step Fix:

1Apply Official KB / Cumulative System Update:

Open Settings > Windows Update.

Click Check for updates and install all pending cumulative updates (ensure KB5008295 or later is applied).

2Date Rollback Workaround (If offline or unable to update immediately):

Open Settings > Time & language > Date & time.

Toggle OFF Set time automatically.

Change date manually to October 31, 2021.

Launch Snipping Tool to confirm functionality.

Change date back to Set time automatically (Snipping Tool will remain functional until package re-validation).

3Re-register App Package via PowerShell:

Run PowerShell as Administrator:

Get-AppxPackage -AllUsers *ScreenSketch* | Reset-AppxPackage

Prevention & Long-Term Monitoring:

Keep Windows 11 serviced with mandatory security update quality rollups to prevent cryptographic certificate expiration on UWP app signatures.

Corrupted App State Reset & OpenCL/OpenGL Compatibility Fix

Solution:

Root Cause: Hardware Acceleration / Graphics Hook Crash or App Cache Corruption

Snipping Tool utilizes DirectComposition and OpenCL/OpenGL DirectX Interop for rendering the capture overlay canvas. Corrupted user app data in %LocalAppData%\Packages\Microsoft.ScreenSketch_8wekyb3d8bbwe or conflicting OpenCL/OpenGL compatibility packs cause immediate native crash (0xc0000005 Access Violation) in dxgi.dll or SnippingTool.exe.

Diagnostic Verification:

Open Event Viewer > Windows Logs > Application.

Look for Event ID 1000 (Faulting application name: SnippingTool.exe, Faulting module name: dxgi.dll or OpenCL.dll).

Step-by-Step Fix:

1Repair and Reset Snipping Tool App Data:

Open Settings > Apps > Installed apps.

Locate Snipping Tool, click the three dots, and select Advanced options.

Click Repair. If the issue persists, click Reset (Note: clears app preferences).

2Remove Conflicting OpenCL/OpenGL Compatibility Pack:

In Installed apps, search for OpenCL and OpenGL Compatibility Pack.

Click the three dots and select Uninstall.

3Clear AppData Local Cache:

Press Win + R, paste the following path, and press Enter:

%LocalAppData%\Packages\Microsoft.ScreenSketch_8wekyb3d8bbwe\LocalState

Delete all contents within the LocalState directory.

4Restart system and re-test Snipping Tool.

Prevention & Long-Term Monitoring:

Avoid installing untested compatibility packs unless required for legacy CAD/3D rendering application pipelines.

File System Error (-2147219196) & License Service Repair

Solution:

Root Cause: Windows Store License Manager Service (ClipSVC) Inconsistency

File System Error -2147219196 (0x80040154 or 0x80073CF6) occurs when the Windows AppX License Manager service (ClipSVC) fails to validate the user license for the UWP package, or when bad disk sectors corrupt the underlying Windows Store package repository file StateRepository-Machine.sdb.

Diagnostic Verification:

Open PowerShell as Administrator and execute:

Get-Service ClipSVC | Select-Object Status, StartType

Verify that ClipSVC is not disabled.

Step-by-Step Fix:

1Reset and Restart ClipSVC (Client License Service):

Open PowerShell as Administrator and execute:

net stop ClipSVC
net start ClipSVC

2Re-register Microsoft Store Licensing Services:

In administrative PowerShell, run:

Get-AppXPackage -AllUsers -Name Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

3Run System File Checker (SFC) and DISM Image Repair:

Run the following commands sequentially in Command Prompt (Admin):

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

4Re-install Snipping Tool via winget:

Execute command: winget install --id 9MZ95KL8MR0L --source msstore (installs native Microsoft Snipping Tool package).

Prevention & Long-Term Monitoring:

Ensure the Windows License Manager Service (ClipSVC) startup type is configured to Manual or Automatic.

Complete Package Provisioning & AppX Re-installation Protocol

Solution:

Root Cause: AppX Package Registry De-provisioning or Corrupted MSIX Store Database

When Snipping Tool is missing or reports installation failure 0x80073CF6, the system-wide manifest registration in C:\Program Files\WindowsApps\Microsoft.ScreenSketch_... has broken links in the AppXDeploymentServer database.

Diagnostic Verification:

Run PowerShell as Administrator:

Get-AppxProvisionedPackage -Online | Where-Object DisplayName -like "*ScreenSketch*"

If output is blank, the app is fully de-provisioned from the OS image.

Step-by-Step Fix:

1Completely Remove Existing Residual Package Instances:

Run administrative PowerShell:

Get-AppxPackage -AllUsers *ScreenSketch* | Remove-AppxPackage -AllUsers

2Re-provision Snipping Tool for All Users:

Execute command:

Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -like "*ScreenSketch*"} | Remove-AppxProvisionedPackage -Online

3Reinstall Fresh Store Package:

Open Microsoft Store, search for Snipping Tool, and click Get / Install.

Alternatively, install via PowerShell using winget:

winget install --id "Microsoft.SnippingTool" --accept-source-agreements --accept-package-agreements

4Perform Full System Reboot.

Prevention & Long-Term Monitoring:

Avoid using aggressive third-party Windows debloating scripts that prematurely remove system AppX packages without verifying dependencies.

Where is the failure occurring during the capture or save operation?

Snipping Tool takes screenshot, but auto-save or manual save fails with 'Access Denied' or write errors.
Snipping Tool captures image, but fails to copy to Clipboard ('Clipboard image copy failed').
Screen recording mode fails to initialize or yields corrupt video files (MP4 encoding error).
Snipping Tool works in administrator account, but fails under standard user domain accounts.

Pictures Directory ACL Permission & Controlled Folder Access Fix

Solution:

Root Cause: NTFS Access Control List (ACL) Misconfiguration or Defender Controlled Folder Access

Snipping Tool automatically writes screenshot captures to %USERPROFILE%\Pictures\Screenshots. If the User Account Control (UAC) token lacks write permissions to the Pictures library, or if Controlled Folder Access in Windows Defender prevents SnippingTool.exe from modifying files in personal folders, file save operations fail silently or return Access Denied.

Diagnostic Verification:

Attempt to create a manual text file inside %USERPROFILE%\Pictures\Screenshots.

Check Windows Defender Event Log: Event Viewer > Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational > Look for Event ID 1123 (Controlled Folder Access block).

Step-by-Step Fix:

1Configure Windows Defender Controlled Folder Access:

Open Windows Security > Virus & threat protection.

Click Manage ransomware protection under *Ransomware protection*.

Click Allow an app through Controlled folder access.

Click Add an allowed app > Recently blocked apps and select SnippingTool.exe (or browse to C:\Program Files\WindowsApps\Microsoft.ScreenSketch_...\SnippingTool.exe).

2Restore Default Security Permissions on Screenshots Folder:

Open File Explorer and navigate to %USERPROFILE%\Pictures.

Right-click Screenshots folder and select Properties > Security tab.

Click Advanced > Click Enable inheritance > Click Apply.

Ensure your current user account has Full control.

3Relocate Screenshots Special Folder Registry Key (If standard path is broken):

Press Win + R, type regedit, press Enter.

Navigate to: HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

Verify string {B7BED03A-4E5D-4588-9577-C8455E4C084E} is set to %USERPROFILE%\Pictures\Screenshots.

Prevention & Long-Term Monitoring:

When deploying ransomware policies, exclude standard native OS productivity tools like ScreenSketch from execution blocklists.

Windows Clipboard Service & History Buffer Reset

Solution:

Root Cause: Windows Clipboard Service (`cbdhsvc`) Lock or Data Payload Corruption

When Snipping Tool completes a region select, it passes bitmap raw data to the Windows Clipboard Service (cbdhsvc). If the system clipboard buffer is locked by an unresponsive process, or if Clipboard History syncing is jammed, the bitmap transfer fails silently.

Diagnostic Verification:

Press Win + V to bring up Clipboard History. If a spinner displays indefinitely or an error appears, the Clipboard Service payload queue is locked.

Step-by-Step Fix:

1Restart Windows Clipboard User Service:

Open PowerShell as Administrator and run:

Get-Service cbdhsvc* | Restart-Service -Force

2Clear System Clipboard Buffer:

Open Settings > System > Clipboard.

Click Clear next to Clear clipboard data.

Toggle Clipboard history OFF, wait 5 seconds, and toggle back ON.

3Re-enable Auto-Copy in Snipping Tool Options:

Open Snipping Tool manually from Start.

Click the three dots menu (...) in top-right corner > Select Settings.

Ensure Automatically copy changes to clipboard is toggled ON.

Prevention & Long-Term Monitoring:

Clear clipboard history periodically when handling large high-resolution dual-monitor framebuffer grabs.

Graphics Encoder & Video Capture Permission Fix

Solution:

Root Cause: Missing Hardware Video Codec (HEVC/AVC) or Privacy Camera/Screen Capture Policy

Snipping Tool's screen recording functionality relies on Windows Media Foundation AAC/H.264 video hardware encoding pipelines and Windows App Graphics Capture APIs. If hardware video encoding driver features fail or screen recording permissions are restricted under App Privacy settings, video captures fail immediately upon clicking 'Start'.

Diagnostic Verification:

Open PowerShell and verify Media Foundation encoder registration:

Get-WmiObject Win32_VideoController | Select-Object Name, DriverVersion

Step-by-Step Fix:

1Enable App Screen Capture Privacy Settings:

Open Settings > Privacy & security > App permissions.

Ensure Graphics capture and display border and Microphone (if audio recording is enabled) are turned ON for Snipping Tool.

2Update GPU Drivers:

Update display adapters via Device Manager or direct from vendor (NVIDIA, Intel, AMD) to ensure active Media Foundation H.264/NVENC/AMF encoders.

3Reset Snipping Tool App Package via PowerShell:

Run administrative PowerShell:

Get-AppxPackage *ScreenSketch* | Reset-AppxPackage

Prevention & Long-Term Monitoring:

Keep graphics hardware drivers up to date to preserve video hardware capture acceleration capabilities.

Domain Account SID & UWP App Execution Alias Permission Fix

Solution:

Root Cause: User Profile SID ACL Misconfiguration on AppX Execution Aliases

In domain-joined environments or systems created via disk cloning (sysprep), standard user Security Identifiers (SIDs) may lack read and execute permissions on the execution alias directory %LocalAppData%\Microsoft\WindowsApps\SnippingTool.exe.

Diagnostic Verification:

Log into affected standard user account, open Command Prompt, and run:

%LocalAppData%\Microsoft\WindowsApps\Microsoft.ScreenSketch_8wekyb3d8bbwe\SnippingTool.exe

Check for 'Access is denied' command output.

Step-by-Step Fix:

1Repair Execution Alias Permissions via icacls:

Open Command Prompt as Administrator and execute:

icacls "%LocalAppData%\Microsoft\WindowsApps" /reset /T /C

2Re-register UWP App Packages for Active User Profile:

Open PowerShell (non-elevated, under affected user account) and execute:

Add-AppxPackage -Register "C:\Program Files\WindowsApps\Microsoft.ScreenSketch_8wekyb3d8bbwe\AppXManifest.xml" -DisableDevelopmentMode

3Verify Group Policy AppLocker / Software Restriction Policies:

Ensure AppLocker rules under Computer Configuration > Windows Settings > Security Settings > Application Control Policies do not block packaged UWP apps (Publisher: CN=Microsoft Corporation).

Prevention & Long-Term Monitoring:

Ensure domain provisioning scripts include UWP package registration steps during new user profile creation.

What display or visual rendering issue occurs during screen overlay capture?

Screen freezes entirely, darkens, and requires pressing Esc multiple times or force-closing explorer.
Snipping Tool overlay appears black, blank, or fails to capture protected application windows.
Multi-monitor scaling is distorted; snippet selector cuts off on high-DPI external displays.
HDR monitors show severe color washing, overexposure, or distorted colors in captured snips.

Graphics Driver Thread Lock & DirectComposition Reset

Solution:

Root Cause: GPU Driver Thread Deadlock in DirectComposition Overlay

When Win + Shift + S triggers, Snipping Tool requests a full-screen frame buffer capture from the Desktop Window Manager (dwm.exe) and creates a transparent DirectComposition layer. Hardware acceleration bugs or outdated display drivers can cause a deadlock between dwm.exe and dxgi.dll, freezing visual frame updates while trapping input focus.

Diagnostic Verification:

Open Event Viewer > Windows Logs > System > Look for Display warnings: 'Display driver dwm stopped responding and has successfully recovered.'

Step-by-Step Fix:

1Restart Graphics Driver Stack in Real-Time:

Press Win + Ctrl + Shift + B. The screen will flicker black and beep, resetting the display driver stack immediately without restarting Windows.

2Turn Off Hardware-Accelerated GPU Scheduling (HAGS) (If crash persists):

Open Settings > System > Display > Graphics.

Click Change default graphics settings.

Toggle Hardware-accelerated GPU scheduling to Off.

Restart PC.

3Clean Install Graphics Drivers:

Download latest drivers directly from GPU vendor (NVIDIA/AMD/Intel).

Execute perform clean installation to purge corrupted DirectX cache files.

Prevention & Long-Term Monitoring:

Maintain current display drivers and monitor DWM stability during heavy 3D rendering workloads.

Hardware Overlay Protection & DRM Window Exclude Protocol

Solution:

Root Cause: Hardware Overlay Protection (HDCP / DRM / SetWindowDisplayAffinity)

Applications such as streaming video clients (Netflix, Hulu, Apple TV), banking software, or enterprise security agents invoke the Win32 API function SetWindowDisplayAffinity(hWnd, WDA_EXCLUDEFROMCAPTURE). When active, Desktop Window Manager (dwm.exe) renders those application surfaces as solid black/blank regions during any screen capture request to enforce copy protection.

Diagnostic Verification:

Close protected browser tabs or streaming desktop apps and re-test Snipping Tool.

Check if Hardware Acceleration is enabled in browser applications (Chrome/Edge/Firefox).

Step-by-Step Fix:

1Disable Web Browser Hardware Acceleration (For web capture testing):

Open Microsoft Edge or Google Chrome settings.

Search for Use graphics acceleration when available (or *Hardware Acceleration*) and toggle OFF.

Relaunch browser.

2Identify and Close DRM-Protected Applications:

Close active desktop applications running protected content streams or remote desktop management sessions enforcement.

3Force Snipping Tool to Use Software Rendering (Fallback):

Open Settings > System > Display > Graphics.

Scroll down to Snipping Tool, click Options, and select Power saving (forces integrated GPU usage rather than discrete graphics hardware overlay hooks).

Prevention & Long-Term Monitoring:

Recognize that DRM-protected media streams enforce native hardware blocks at kernel graphic pipeline layers that bypass standard screenshot utilities.

Multi-Monitor High-DPI Scaling & Per-Monitor DPI Fix

Solution:

Root Cause: Per-Monitor DPI Awareness Multi-Monitor Framebuffer Mismatch

When mixing displays with different scaling percentages (e.g., 4K primary monitor at 150% scaling and 1080p secondary monitor at 100% scaling), SnippingTool.exe may miscalculate virtual desktop coordinate bounds if Per-Monitor DPI Awareness v2 context fails to negotiate with explorer.exe.

Diagnostic Verification:

Connect single monitor and verify snip coordinates. If single display works normally, multi-monitor DPI coordinate mismatch is confirmed.

Step-by-Step Fix:

1Override High DPI Scaling Settings for Snipping Tool:

Open File Explorer and navigate to:

C:\Program Files\WindowsApps\Microsoft.ScreenSketch_8wekyb3d8bbwe\ (Note: Requires owner access permission) or locate executable shortcut.

Right-click SnippingTool.exe > Properties > Compatibility tab.

Click Change high DPI settings.

Check Override high DPI scaling behavior and set Scaling performed by: to Application or System (Enhanced).

2Align Display Scaling Settings Across Monitors:

Open Settings > System > Display.

Select each display and verify scaling percentages are matched or set to recommended native values.

3Restart Desktop Window Manager:

Open Command Prompt as Admin and run:

taskkill /f /im dwm.exe (DWM will automatically restart).

Prevention & Long-Term Monitoring:

Set primary and secondary monitor scaling ratios to integer multipliers where possible to prevent virtual screen coordinate clipping.

HDR Tone Mapping & Auto HDR Color Calibration Fix

Solution:

Root Cause: High Dynamic Range (HDR) Dynamic Range / SDR Color Mapping Clipping

When High Dynamic Range (HDR) is enabled in Windows 11, the display pipeline renders in scRGB / HDR10 color space (10-bit/12-bit wide color gamut). Snipping Tool captures screen frames in SDR (8-bit color space). Without appropriate ICC profile color mapping or Windows Auto HDR conversion, captured images appear blown-out, overexposed, or severely washed out.

Diagnostic Verification:

Press Win + Alt + B to toggle Windows HDR on/off. Take a test snip with HDR disabled to confirm color fidelity returns.

Step-by-Step Fix:

1Enable HDR Screenshot Color Correction in Windows 11:

Ensure Windows 11 is updated to Build 22621 or higher.

Open Snipping Tool > Click three dots (...) > Settings.

Toggle ON HDR Screen Capture Color Corrector (if available in current build).

2Run Windows HDR Calibration Tool:

Download and run Windows HDR Calibration app from Microsoft Store.

Complete the calibration steps to generate a valid ICC color profile for your monitor.

3Quick Toggle HDR via Keyboard Shortcut Before Snip:

Press Win + Alt + B to temporarily disable HDR.

Execute screen capture (Win + Shift + S).

Press Win + Alt + B to re-enable HDR mode.

Prevention & Long-Term Monitoring:

Ensure accurate color management ICC profiles are attached to active monitors in Windows Display Management when working in HDR color spaces.

Related Diagnostic Guides

Windows Update Error 0x80070002 Missing Files Diagnostic Guide

System Restore Failed 0x80070005 Antivirus Conflict Tree

Windows Photo Viewer Not Showing Thumbnails: Codec Diagnostic

Safe Mode Password Not Working With Microsoft Account Fix

Clipboard History Not Working Windows 11: Sync Service Tree

Subscribe to StepDiag

Embed Guide on Your Website