ShareX Settings Not Saving: How to Fix Lost Preferences

When ShareX settings are not saving, the clearest symptom is persistence failure: you change a hotkey, destination, workflow, or application preference, but the change disappears after ShareX restarts. This is different from a setting that remains selected but does not produce the expected result because another option overrides it. Lost preferences usually point to a configuration folder that cannot be written, a portable installation in a protected location, two ShareX copies using different configurations, security software blocking writes, or a sync or backup tool restoring older files.

The steps below begin with a small reproduction test, then move through configuration storage, Windows permissions, duplicate processes, portable installations, security controls, and clean testing. After each fix, restart ShareX and check the same test preference. Once the change survives a restart, stop changing unrelated options. You have confirmed that configuration persistence works, and any remaining problem can be investigated separately.

1. Confirm the Symptom With a Simple Test

Before editing permissions or deleting files, verify that the problem truly involves settings persistence. Choose a harmless, visible preference that you can easily reverse. Avoid testing with an upload destination or a complex workflow because credentials, task settings, and destination rules can introduce separate variables.

1.1 Run a save-and-restart test

1. Open ShareX from the system tray.
2. Choose a simple application preference or create a temporary, unused hotkey.
3. Close the relevant settings window normally.
4. Exit ShareX completely from its tray menu rather than ending it in Task Manager.
5. Wait several seconds, then confirm that no ShareX process remains in Task Manager.
6. Start ShareX from the same shortcut you used previously.
7. Return to the tested preference and check whether it remains changed.

Success means the preference is still present after a complete exit and restart. If it survives, ShareX can probably write its configuration, and the original issue may involve an overridden task setting, destination-specific option, or workflow rule instead of lost settings. If the preference resets, continue with the persistence checks below.

1.2 Test a clean exit separately

ShareX needs an opportunity to finish writing configuration changes. A forced shutdown, crash, Task Manager termination, or immediate Windows sign-out can interrupt that process. Make one change, leave ShareX open briefly, and then use its Exit command. Restart it manually instead of rebooting Windows for this test.

If preferences survive a normal exit but disappear after a shutdown or forced termination, the storage location is probably usable. Focus on why ShareX is not exiting cleanly, whether Windows is closing it abruptly, or whether another process is replacing its files during startup or shutdown.

2. Check the ShareX Configuration Location

ShareX stores user data in its personal folder. For a standard installation, this is commonly a ShareX folder under the current Windows user's Documents folder. Portable operation can instead keep data beside the executable or in another selected personal folder. The location matters more than memorizing a path because it can change with portable use, folder redirection, OneDrive, or customized settings.

2.1 Find the folder ShareX is actually using

Open ShareX and look in its application settings for the personal folder path or an option that opens that folder. Use the folder shown by the running application rather than assuming that every ShareX shortcut points to the same location. The folder may contain JSON configuration files and subfolders for history, screenshots, or other data.

Make a note of the complete path. Then change a harmless preference and watch the configuration folder in File Explorer. A relevant configuration file should normally receive an updated modified timestamp when ShareX saves the change or exits cleanly. The exact files present can vary, so do not rename or edit a file merely because its name appears unfamiliar.

Success means you have identified the active personal folder and can see its configuration files updating. If one folder changes while you were inspecting another, the apparent reset was probably caused by using the wrong installation or configuration location.

2.2 Verify folder write permission

Test whether your Windows account can write to the active ShareX personal folder. In File Explorer, create a temporary text file in that folder, rename it, and delete it. This simple test checks create, modify, and delete access without altering ShareX configuration.

If Windows refuses any part of the test, inspect the folder's Properties and Security tab. Confirm that your current account has permission to modify the folder. Also check whether the folder is marked read-only because it was copied from another computer, restored from an archive, or inherited restrictive permissions from its parent folder.

Do not grant broad permissions to an entire protected system directory just to make ShareX work. A safer solution is to place ShareX data in a normal user-writable folder. Success means your account can create, edit, and delete the test file, and a ShareX preference then survives a normal restart.

2.3 Check portable folder write access

A portable ShareX copy may try to store preferences near its executable. That fails when the portable folder is inside Program Files, a read-only network share, a locked archive, removable media with write protection, or a directory controlled by another administrator account.

Move or extract the complete portable folder to a user-owned location, such as a dedicated folder inside your user profile. Do not run the executable directly from a ZIP archive. Start it from the new location, change one preference, exit normally, and reopen that exact executable.

If the preference now persists, the original portable path was not reliably writable. Keep the portable installation in the working location rather than compensating by always running ShareX as administrator. Mixing elevated and non-elevated launches can create more confusion about file ownership and hotkey behavior.

3. Eliminate Duplicate Copies and Configuration Overwrites

ShareX settings may appear to reset when two installations, shortcuts, or running processes use different personal folders. A synchronization service can produce a similar symptom by replacing a newly saved configuration with an older copy.

3.1 Check for multiple ShareX processes

Exit ShareX from the tray, then open Task Manager and search for remaining ShareX processes. End a leftover process only after giving the application time to exit normally. Next, start ShareX once from a known shortcut.

Multiple instances can compete over configuration files. One copy may save new preferences, while an older copy later exits and writes its in-memory settings over them. Duplicate startup entries can also launch separate installed and portable copies.

Review the Startup apps page in Windows Settings or Task Manager. Keep one intended ShareX startup entry. Remove obsolete shortcuts from the Startup folder, taskbar, desktop, and Start menu when they point to a different executable.

Success means only one ShareX process and one intended executable are involved, and the test preference survives closing and reopening that copy.

3.2 Identify duplicate installations

Right-click the shortcut you normally use and inspect its target or open the executable's file location. Compare that path with any pinned taskbar icon, desktop shortcut, startup entry, and portable folder. A taskbar icon can continue pointing to an old executable after a new copy is installed elsewhere.

Unpin obsolete icons and create a fresh shortcut from the executable you intend to keep. If you use both installed and portable editions deliberately, label their folders and shortcuts clearly and expect them to have separate configurations unless you have intentionally configured otherwise.

3.3 Pause sync and backup restoration

If the personal folder is under OneDrive, Dropbox, another synchronization service, roaming profile software, or an automated backup tool, temporarily pause that software. Change a test preference, exit ShareX cleanly, and reopen it.

Look for conflict copies, restoration notifications, or configuration files whose modified timestamps move backward. Sync tools can restore an older version after detecting a conflict, especially when ShareX is active on more than one computer. Backup software should not continuously restore configuration files while ShareX is using them.

If pausing synchronization fixes the problem, exclude the active configuration files from live restoration, resolve the conflict, or move the ShareX personal folder to a local user-writable location. Success means the newest configuration remains in place after ShareX and the sync service restart.

4. Check Windows Security and Storage Controls

Windows security features and third-party endpoint protection can block an application from changing files without making ShareX itself appear broken. This is particularly relevant when the personal folder is in Documents, which may be protected by Controlled Folder Access.

4.1 Review Controlled Folder Access

Open Windows Security and review ransomware protection settings and protection history. If Controlled Folder Access is enabled, look for a recent event showing that ShareX was blocked from writing to a protected folder.

If a block is confirmed, allow the trusted ShareX executable through Controlled Folder Access or move its personal folder to an appropriate writable location. Select the executable you actually run, especially if multiple ShareX copies exist. Do not disable ransomware protection permanently merely to test one application.

Success means no new block event appears when you save a preference, the configuration file's timestamp updates, and the preference remains after restart.

4.2 Inspect antivirus and enterprise restrictions

Third-party security software may include application control, protected folders, rollback, sandboxing, or file virtualization. Review its event history for ShareX or the configuration path. On a managed work computer, policy may prevent users from modifying particular folders even when File Explorer initially appears to allow access.

If the device belongs to an employer or school, ask the administrator to review the event and approve the official ShareX executable or a suitable data location. Avoid bypassing organizational controls. Success is a confirmed policy exception or approved folder where ShareX can update its files normally.

4.3 Check drive and folder availability

A custom personal folder on a disconnected network drive, unavailable removable disk, or offline redirected Documents folder cannot reliably preserve preferences. Confirm that the drive is connected before ShareX starts and that the folder is available without an authentication prompt.

Also verify that the drive is not full. Low storage can prevent configuration writes even though the application continues running. Once the path is available and writable, repeat the simple save-and-restart test.

5. Run a Clean Temporary Test

If permissions and duplicate copies look correct, use a clean temporary configuration to determine whether the existing configuration is damaged. Preserve the original data first. This test should not begin by deleting anything.

5.1 Back up the active personal folder

1. Exit ShareX normally.
2. Confirm in Task Manager that no ShareX process remains.
3. Copy the entire active ShareX personal folder to a clearly labeled backup location.
4. Verify that the copied folder contains files and has a plausible size.
5. Do not store the only backup inside the folder you plan to rename or reset.

This backup may contain hotkeys, upload destinations, custom workflows, history, and other user data. Some destination settings can include sensitive credentials or tokens, so protect the backup and do not upload it publicly.

5.2 Create a fresh configuration safely

With ShareX closed, rename the active personal folder rather than deleting it. For example, add a suffix that identifies it as the old configuration. Start ShareX and allow it to create a new folder with default settings. Make one harmless preference change, exit normally, and reopen the same executable.

If the preference survives, the application and Windows folder access are working with a clean configuration. The old configuration may be malformed, locked, or carrying a path that no longer exists. Recreate important settings gradually instead of copying every old configuration file back at once. Copying everything immediately can restore the original fault.

If the clean preference also disappears, stop rebuilding settings. The cause is more likely the executable location, folder permissions, security controls, duplicate process, or external file replacement.

5.3 Restore data carefully

If you need the old setup, close ShareX before restoring anything. Bring back only the data you understand and test persistence after each small group of changes. Keep the full backup until hotkeys, destinations, workflows, and recent tasks have been checked.

Do not manually merge JSON files unless you are comfortable validating structured data. For most users, recreating a limited number of settings through the interface is safer than editing configuration syntax.

6. Check Logs, History, and Recent Output

Task history is most useful when a preference remains saved but a capture, upload, recording, OCR action, or workflow does not behave as expected. It is less likely to explain a basic preference that vanishes from the interface, but it can reveal that the original symptom was misclassified.

6.1 Separate persistence from workflow failure

After restarting ShareX, first check whether the selected option is still displayed. If it is, configuration persistence succeeded. Then run the affected task and inspect task history, recent output, destination response, and any visible error message.

• If a hotkey remains listed but does not trigger, check for a Windows or application hotkey conflict.
• If a destination remains selected but uploads elsewhere, inspect task-specific destination overrides.
• If recording settings remain selected but audio is missing, inspect the selected audio source and Windows privacy access.
• If a workflow remains present but performs different actions, inspect its after-capture and after-upload task assignments.
• If an upload fails, check network access, authentication, destination status, and the task error rather than resetting all preferences.

This distinction prevents unnecessary configuration deletion. Once a setting survives restart, stop treating it as a ShareX settings not saving problem and troubleshoot the specific task instead.

6.2 Preserve useful evidence

Record the exact time of a failed save test, the executable path, the personal folder path, and whether the configuration file timestamp changed. Capture the full text of any error rather than paraphrasing it. These details make community or administrator support much more effective.

7. Quick Fix Checklist

• Change one harmless preference, exit ShareX normally, and reopen the same executable.
• Confirm the active ShareX personal folder instead of assuming its location.
• Test create, rename, and delete access in that folder.
• Move portable ShareX out of Program Files, archives, and read-only locations.
• Confirm that only one ShareX copy is running.
• Remove duplicate startup entries and obsolete shortcuts.
• Check Controlled Folder Access and antivirus protection history for blocked writes.
• Pause sync or backup tools that may restore older configuration files.
• Confirm custom, network, and removable storage paths are online and writable.
• Back up the entire personal folder before renaming or resetting it.
• Test a fresh configuration before rebuilding destinations and workflows.
• Stop changing settings as soon as the test preference survives a restart.

8. Frequently Asked Questions

8.1 Where are ShareX configuration files stored?

A standard setup commonly uses a ShareX personal folder under the current user's Documents folder. Portable or customized setups may store data beside the executable or in another selected location. The reliable method is to check the personal folder shown by the running ShareX copy. Folder redirection and synchronization can make the apparent Documents path differ from its physical location.

8.2 Why do ShareX settings reset after every restart?

The most common categories are blocked folder writes, an unwritable portable location, multiple ShareX copies overwriting one another, a forced or incomplete exit, security software blocking configuration changes, or synchronization software restoring an older file. A simple preference test and configuration timestamp check can narrow the cause quickly.

8.3 Should I run ShareX as administrator?

Not as a permanent ShareX settings not saving fix. Elevation may temporarily bypass a permission problem, but it can create different file ownership, startup, drag-and-drop, and hotkey behavior. It is better to place ShareX and its personal data in appropriate user-writable locations and correct the specific permission or security block.

8.4 Can I delete the ShareX configuration folder?

You can reset the configuration, but first exit ShareX and copy the entire active personal folder to a safe backup location. Renaming the original folder is safer than deleting it because it preserves hotkeys, destinations, workflows, and history for recovery. Remember that configuration backups may contain sensitive upload credentials.

8.5 Why does one setting fail even though other settings save?

If the setting remains selected after restart, persistence is working. The behavior may be controlled by a task-specific override, custom workflow, destination selection, hotkey conflict, recording device, privacy permission, or network condition. Inspect the affected task and recent output instead of resetting the complete configuration.

8.6 When should I reinstall ShareX?

Reinstallation is not the first step because an installer may leave the same personal folder and external permission problem in place. First test folder access, duplicate copies, security controls, and a clean temporary configuration. Consider reinstalling from the official source if the executable itself is damaged or if a clean configuration fails despite confirmed write access and no external blocks. Preserve your personal folder backup before uninstalling or changing installations.