ShareX Region Capture Freezes or Will Not Select: How to Fix It

When ShareX region capture freezes, the screen may dim normally but then stop responding. You might be unable to draw a selection, move the selection handles, confirm the region, or return to the desktop. This usually points to a problem with the region-selection overlay rather than the screenshot file itself. Common causes include another overlay intercepting input, a permission mismatch, unusual multi-monitor or HDR behavior, graphics driver problems, or a damaged capture-related setting.

The steps below isolate those causes without requiring developer tools. Begin with the simple desktop test, make one change at a time, and stop as soon as region selection works normally. That approach prevents unrelated ShareX settings, upload destinations, and automation workflows from being changed unnecessarily.

1. Confirm the Symptom and Reproduce It With a Simple Test

Before changing settings, determine whether ShareX is freezing during region selection or completing the capture and failing afterward. These are different problems and require different troubleshooting paths.

1.1 Identify an overlay problem

You are probably dealing with a region-selection overlay problem if one or more of these symptoms occur immediately after starting region capture:

• The desktop dims, but dragging the mouse does not create a selection box.
• A selection box appears, but its handles or borders do not respond.
• The cursor moves while clicks and keyboard commands appear to do nothing.
• The overlay remains visible after you release the mouse button.
• ShareX never reaches its after-capture tasks.
• No new item appears in ShareX history after you escape from the overlay.

By contrast, if you can draw and confirm a region, the overlay closes, and the problem occurs while saving, uploading, copying, annotating, or opening the image, region selection itself is working. In that case, investigate the destination folder, upload service, after-capture tasks, file permissions, or image editor instead.

1.2 Recover from a stuck overlay

Press Esc once and wait a few seconds. Esc normally cancels region selection without closing ShareX. If that does not restore the desktop, press Esc again, then use Alt+Tab to move away from the overlay. You can also press Ctrl+Shift+Esc to open Task Manager if Windows remains responsive.

After the overlay closes, find the ShareX icon in the notification area. Right-click it and exit ShareX normally, then start it again. If the tray icon is hidden, select the notification-area arrow. If ShareX does not respond, end its process through Task Manager and reopen it. This clears a temporary overlay process state without changing any configuration.

Success means the desktop returns to normal and ShareX can be opened from the tray or Start menu. Once it recovers, do not immediately repeat the capture over the same application. First test against the plain Windows desktop.

1.3 Run the desktop test

Minimize all applications, pause any full-screen game or video, and display a normal section of the Windows desktop. Start region capture from the ShareX tray menu instead of using your usual hotkey. Try to select a small area containing only the wallpaper and one desktop icon.

If this works, ShareX can create a basic region capture. The failure is likely tied to the original application, its permissions, an overlay, the hotkey workflow, or a particular monitor. If it freezes even on the desktop, focus on ShareX capture settings, display configuration, graphics drivers, and competing capture software.

2. Check the ShareX Settings Directly Related to This Problem

ShareX has many features, but upload accounts, OCR services, image effects, and file-naming options do not normally control whether the region-selection box accepts mouse input. Limit initial changes to settings associated with capture, hotkeys, and the region overlay.

2.1 Start region capture without the hotkey

Open ShareX and start a standard region capture from its Capture menu or tray menu. This bypasses possible hotkey collisions. Windows, graphics utilities, gaming software, and other screenshot tools can register the same key combination or respond before ShareX does.

If menu-based capture works but the hotkey freezes, does nothing, or opens a different overlay, assign a temporary unused shortcut in ShareX hotkey settings. Test a combination that is not registered by Windows or another capture utility. Success means the new shortcut opens an interactive overlay and completes a desktop capture. At that point, keep the working shortcut and stop changing capture options.

2.2 Test a basic region-capture workflow

A custom hotkey can be attached to a specialized workflow with additional tasks. Create or use a plain region-capture task that does not immediately invoke screen recording, scrolling capture, OCR, annotation, upload, or external commands. The purpose is to determine whether the selector itself works before extra steps run.

If the basic task succeeds, re-enable workflow steps individually. The first restored step that causes the problem identifies the area to investigate. If the overlay freezes before a region is confirmed, however, after-capture upload and save settings are unlikely to be the cause.

2.3 Review region and capture options

Open ShareX task settings and inspect the capture-related options available in your installation. Temporarily disable optional behavior that changes how the selector identifies windows, controls, or screen content. Setting names and locations can change, so record the original values before editing them.

Do not reset all application settings at this stage. ShareX may contain upload credentials, custom destinations, hotkeys, naming patterns, image effects, and automation tasks that have no connection to the frozen overlay. A targeted test is safer and easier to reverse.

3. Check Windows, Display, Permission, and Workflow Factors

The ShareX overlay must cover the relevant desktop area, receive mouse and keyboard input, and read the displayed content. Software that inserts its own overlay or runs at a different permission level can interrupt that process.

3.1 Close competing overlays and capture tools

Temporarily exit programs that draw over other windows or capture the screen. Do not merely minimize them, because many continue running in the notification area or as background services. Likely conflicts include:

• Game launchers and in-game overlays
• GPU recording, performance, or frame-rate overlays
• Other screenshot and screen-recording programs
• Streaming and broadcasting tools with preview or overlay features
• Windows screen-dimming, color-temperature, or eye-comfort utilities
• Remote desktop, virtual display, or screen-sharing tools
• Mouse enhancement and window-management utilities

Exit one category at a time and repeat the desktop test. If region selection starts working, reopen the programs individually until the conflict returns. Success is not merely seeing the dimmed screen. You should be able to draw a region, confirm it, and see the completed task in ShareX.

3.2 Correct administrator permission mismatches

If the target application is running as administrator while ShareX is running normally, ShareX may be unable to interact with that elevated window as expected. This is especially relevant for administrative utilities, setup programs, system-management tools, and some games.

First, test the normal desktop and a non-elevated application. If those work but the elevated application does not, close and restart ShareX with matching privileges for that test. Right-click ShareX and choose Run as administrator, then retry the capture. Alternatively, run the target application without elevation if it does not require administrator access.

If matching permissions fixes the issue, use elevated ShareX only when necessary. Running automation or upload tools with administrator rights increases their access to the system. There is no reason to change permission settings if capture already works in both elevated and normal windows.

3.3 Isolate multi-monitor problems

Mixed monitor layouts can expose coordinate, scaling, color, or graphics-driver problems. This is more likely when displays use different scaling percentages, resolutions, orientations, refresh rates, or HDR modes.

Move ShareX and the target application to the primary monitor, then capture a region entirely within that screen. Avoid drawing across monitor boundaries. If that works, test each monitor separately. Next, temporarily align display scaling or disconnect the secondary display through Windows display settings and repeat the test.

Success on one display but not another narrows the issue to display configuration or the graphics driver rather than ShareX uploads or file saving. Keep the working layout while you update the driver or adjust the affected display. You do not need to reset ShareX if a single-monitor test consistently succeeds.

3.4 Test HDR and screen-enhancement features

HDR changes the display pipeline and can interact differently with overlays, graphics drivers, and capture applications. If the problem began after enabling HDR, changing monitors, docking a laptop, or installing a display utility, temporarily turn HDR off for the affected display and test again.

Also pause third-party dimmers, night-mode applications, color calibration overlays, and monitor-control software. Windows Night light is less likely to block input than a third-party overlay, but it can still be disabled briefly as part of a controlled display test.

If capture works with HDR or an enhancement tool disabled, confirm the result with a second attempt before treating it as the cause. Re-enable unrelated features and stop changing settings once the responsible condition is identified.

3.5 Refresh the graphics path

A graphics driver fault can leave a transparent or dimmed overlay visible while input or drawing fails. Restart Windows first, particularly if the issue appeared after waking from sleep, connecting a dock, changing displays, or closing a full-screen game.

If the problem returns, install a stable graphics driver supplied by the GPU or computer manufacturer. If it began immediately after a driver update, use Windows driver rollback only when the previous driver was known to work. Avoid installing unofficial driver packages.

Where ShareX exposes a relevant hardware acceleration option, test the opposite setting and restart ShareX. Change only that option, because the test is intended to determine whether GPU-assisted rendering is involved. Success means repeated region captures draw smoothly and close normally after confirmation.

4. Run a Clean Temporary Test With Minimal ShareX Settings

If ShareX region capture freezes even on the desktop after overlays and display factors have been checked, use a minimal temporary configuration. The objective is diagnosis, not immediately replacing your working setup.

4.1 Protect the current configuration

Before resetting anything, use ShareX's available settings export or backup feature, or close ShareX and make a safe copy of its configuration data. Do not delete configuration files while ShareX is running. Record important hotkeys, destinations, and workflow options that may be difficult to reconstruct.

4.2 Reset only capture-related behavior

Return modified region-capture options to their defaults or create a new basic hotkey task for region capture. Disable optional capture actions and test without automatic upload, image effects, annotation, OCR, or external commands. Leave account and destination settings untouched unless testing proves the overlay finishes and a later task fails.

If a minimal capture works, restore options in small groups and test after each group. Stop when you identify the setting or task that reproduces the freeze. If the minimal test still freezes, restore your original configuration and continue with Windows display, driver, or software-conflict investigation. A full settings reset is unlikely to help when the same symptom survives a genuinely clean capture test.

5. Check Task History, Logs, and Recent Workflow Output

History and logs are most useful for deciding whether ShareX reached the end of region selection. Open ShareX after recovering from the frozen overlay and look for a new history item, thumbnail, file path, upload result, or error corresponding to the test.

5.1 Interpret what you find

• No new task or history item: The overlay probably failed or was canceled before capture completion.
• A new image exists: Region capture completed, so investigate what happened after capture.
• An image was saved but not uploaded: Check the destination, credentials, network, and upload response.
• An error names a folder or executable: Check that specific save path, permission, or external action.
• The image is black, blank, or incorrectly colored: Focus on protected content, HDR, the graphics path, or the target application's rendering method.

A blank or corrupted saved image is not the same symptom as an unresponsive selector. Likewise, an upload failure cannot normally explain why selection handles refuse to move before the screenshot is created.

If ShareX provides an error log or debug output in your installation, preserve the relevant message before restarting or clearing anything. When requesting support, include the exact action used, whether desktop capture works, the monitor arrangement, HDR status, permission levels, and the point at which the workflow stops.

6. Quick Fix Checklist

1. Press Esc to cancel the stuck selector, then restart ShareX from the tray.
2. Start region capture from the ShareX menu instead of your usual hotkey.
3. Test a small region on the plain Windows desktop.
4. Exit game, GPU, recording, streaming, dimming, and screenshot overlays.
5. Match ShareX and the target application's administrator level for one test.
6. Capture entirely on the primary monitor without crossing display boundaries.
7. Temporarily disable HDR and third-party color or dimming tools.
8. Restart Windows and install a stable graphics driver if the problem persists.
9. Test a plain capture task without OCR, upload, editing, or external actions.
10. Reset only capture-related settings after backing up the configuration.
11. Check history or logs to distinguish overlay failure from post-capture failure.

After every step, repeat the same desktop-region test. Stop troubleshooting when you can draw, adjust, and confirm a region several times and ShareX records the completed captures. Additional changes after success can hide the real cause or create new problems.

7. Frequently Asked Questions

7.1 Why does the screen dim and get stuck when I start ShareX region capture?

The dimming indicates that the selection overlay opened. If it does not accept input, another overlay may be intercepting clicks, ShareX may have a permission mismatch with the target application, or the graphics and display path may not be drawing the selector correctly. Press Esc, recover ShareX through the tray, and test on the desktop with competing overlays closed.

7.2 Why does ShareX work on the desktop but not over one program?

The target program may be elevated, use exclusive full-screen rendering, display protected content, or run its own overlay. Match permission levels, switch the target to windowed or borderless mode where appropriate, and disable its overlay. If ShareX works everywhere else, avoid resetting the entire application.

7.3 Can multiple monitors make ShareX region selection freeze?

They can contribute, especially with mixed scaling, HDR, orientation, refresh rates, or GPU connections. Test entirely on the primary monitor. If that works, check each display separately and avoid selecting across monitor boundaries until the display or driver issue is resolved.

7.4 Should I reinstall ShareX?

Reinstallation is not the best first step because configuration and Windows-level conflicts may remain. First test the desktop, close overlays, verify permissions, isolate monitors, and try a minimal capture configuration. Reinstall only after preserving your settings and confirming that the installed application files may be damaged.

7.5 What if ShareX creates an image but does not save or upload it?

That is a post-capture problem, not a frozen region selector. Check ShareX history, the destination folder, available storage, folder permissions, network access, upload credentials, and after-capture tasks. Do not troubleshoot selection handles if the overlay already closed and an image was created.

7.6 When should I report the issue?

Report it when the freeze remains reproducible in a plain desktop capture with competing overlays closed, a single primary display, matching permission levels, and minimal capture settings. Include exact reproduction steps, Windows and display details, graphics hardware and driver information, relevant ShareX logs, and whether Esc can close the overlay. These details are more useful than stating only that ShareX is not working.