ShareX Portable Settings Not Loading: How to Fix It

When ShareX portable settings are not loading after you move the program to another folder, drive, USB device, or computer, the problem is usually not that every preference has been erased. More often, ShareX has started with a different data location, cannot read or update the portable configuration files, or is loading a second ShareX instance that uses another profile. Broken absolute paths, incomplete cloud synchronization, blocked downloads, and drive-letter changes can also make hotkeys, destinations, history, or automated workflows appear missing. The steps below focus specifically on portable configuration behavior and help you identify the cause without repeatedly changing unrelated screenshot or recording options.

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

Start by determining exactly what failed to load. This prevents a destination-path problem from being mistaken for a complete configuration failure.

Open the portable copy you intend to use and inspect several recognizable items:

• A custom hotkey that you created
• A destination or uploader configuration
• Your preferred screenshot folder
• A workflow or after-capture task
• Recent task history
• A visible application preference, such as a notification or editor choice

If all custom items are missing and ShareX looks newly configured, it is probably reading a different or empty settings location. If preferences load but captures fail, the configuration may be present while a saved path, destination, credential, or permission is no longer valid. If only history is absent, the history data may not have been copied or synchronized with the other portable files.

1.1 Perform a marker-setting test

Choose one harmless, easy-to-recognize preference and change it in the portable copy. Close ShareX completely, including its notification-area process, and then inspect the portable folder for files whose modified timestamps just changed. Reopen the same executable and check whether the marker preference remains.

This test answers two important questions: whether ShareX can write its configuration and whether the executable you reopened is using the same data location. If the preference survives a full exit and restart, basic portable configuration loading is working. Stop changing general settings at that point and investigate only the missing path, destination, hotkey, or history item.

1.2 Make sure you launched the intended executable

Windows shortcuts, pinned taskbar icons, Start menu entries, and file associations may still point to an installed ShareX copy. Instead of using a shortcut, browse directly to the portable folder and launch ShareX.exe from there. You can use Task Manager to locate the running process and open its file location if you are unsure which copy is active.

Success means the running executable is located inside the portable folder you are testing and your marker setting survives a restart. If Task Manager reveals another location, close every ShareX process before continuing.

2. Check the ShareX Settings Directly Related to This Problem

2.1 Verify where the portable settings live

A portable ShareX setup is intended to keep its user data with the portable application rather than relying on the normal profile used by an installed copy. The exact files present can vary with configuration and the features you have used, but the portable directory may contain configuration, uploader, hotkey, history, workflow, log, and related data files or subfolders.

Do not migrate only ShareX.exe. Copy the complete extracted portable folder, preserving its subfolders and data files. If you still have the original working folder, compare it with the new folder by file count, names, sizes, and modification dates. A comparison tool can help, but File Explorer is sufficient for a small directory.

If the new location contains only program files, or its configuration files are newly created and much smaller than those in the source folder, the migration was incomplete. Copy the missing data while ShareX is closed. Success means the destination folder has the same relevant data as the source and ShareX shows your previous preferences after launch.

2.2 Confirm that the copy remains in portable mode

Use the official portable package rather than constructing a portable copy by copying files from an installed application directory. Installed and portable packages may start with different assumptions about where personal data belongs. Keep all marker files, folders, and supporting files supplied with the portable archive.

If you extracted a fresh official portable package, compare its structure with the folder that is failing. Do not delete unfamiliar portable-mode files simply because they do not contain obvious settings. A missing marker or altered folder layout can cause the program to behave differently from the original portable package.

2.3 Correct absolute paths after a move

Portable application files can move successfully while saved workflows still point to fixed Windows locations. An absolute path includes a specific drive and directory, such as E:\Captures or C:\Users\Name\Pictures\ShareX. If the new computer does not have that drive or user folder, ShareX may load the setting correctly but fail when it tries to use it.

Review settings that reference:

• Screenshot and screen-recording output folders
• Custom file-name or subfolder workflows
• External image editors and command-line tools
• Watch folders
• Custom upload scripts or executables
• Temporary, OCR, or automation output locations
• Destination files, keys, or locally stored resources

Relative paths are more portable because they are interpreted from an application-related working location, but not every field or external tool handles relative paths in the same way. Use a relative path only where ShareX or the connected tool supports it. Otherwise, update the absolute path to a valid location on the new computer.

Success means a new capture is saved or processed in the intended folder without a path-not-found error. Once that happens, stop editing path settings.

2.4 Account for changing drive letters

USB drives and removable disks do not always receive the same drive letter on every computer. A workflow saved as F:\Screenshots will not find that folder when Windows mounts the device as G:.

You can either update the paths in ShareX after the move or assign the removable drive a stable letter through Windows Disk Management when your permissions and environment allow it. Choose a letter that is unlikely to conflict with mapped or local drives. Be cautious on managed business computers, where drive assignments may be controlled by administrators.

Success means the configured folder and any external tools exist at the path shown in ShareX, and a test capture completes normally.

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

3.1 Test write permissions on USB and network drives

ShareX must be able to update portable configuration and history data. A USB device with a read-only switch, a restricted file system, a network share with read-only access, or a folder inherited from another user can let ShareX launch while preventing it from saving changes.

In the portable folder, create a small text file, edit it, save it, rename it, and delete it. This simple test is more relevant than checking whether you can merely open the folder. Then make a marker-setting change in ShareX, exit fully, and reopen it.

If the text-file test fails, move the entire portable folder temporarily to a user-writable local folder, such as a folder under Documents, and test again. Avoid placing the test copy under protected locations such as Program Files. Running as administrator may hide the permission problem, so it is better to repair the folder permissions or choose a writable location for normal use.

Success means both the ordinary file test and the ShareX marker-setting test persist without elevation.

3.2 Let cloud synchronization finish before launching

OneDrive, Dropbox, Google Drive, and similar services can create a partial portable folder before every file has downloaded. Files may also be represented by online-only placeholders. Launching ShareX during synchronization can cause it to encounter missing, stale, or conflicting configuration data.

Pause ShareX, wait for the folder to report that synchronization is complete, and make the entire portable folder available offline. Check for conflict copies or duplicate configuration files created by the sync service. Do not run the same synchronized portable folder on two computers simultaneously because both instances may write competing changes.

For diagnosis, copy the synchronized folder to a normal local folder and launch it there. If settings load locally, the application data is probably intact and synchronization timing or file locking is the issue. Stop changing ShareX preferences and fix the sync arrangement instead.

3.3 Avoid running installed and portable ShareX together

An installed ShareX copy may start automatically with Windows while you manually open the portable copy. Because both applications look similar and use the same notification-area icon, it is easy to edit one profile and later conclude that the other failed to save it. Global hotkeys can also conflict because only one running application can register a particular hotkey combination.

Exit ShareX from the notification area, open Task Manager, and confirm that no ShareX process remains. Temporarily disable automatic startup for the installed copy, then launch ShareX.exe directly from the portable folder. Do not test both editions at the same time.

Success means only one ShareX process is running from the expected portable path, the correct settings appear, and hotkeys register without conflicts.

3.4 Check blocked downloads and security software

Windows can mark files downloaded from the internet, and security software may quarantine, restrict, or remove executable components. If you still have the downloaded ZIP file, open its Properties dialog and use the Unblock option if Windows displays one. Then extract the complete archive again into a new folder. Unblocking the archive before extraction is generally more reliable than checking many extracted files individually.

Also review Windows Security protection history or your organization’s security console for actions involving ShareX or files in the portable directory. Do not disable antivirus protection broadly. Restore or allow a file only after confirming that the package came from ShareX’s official website or official GitHub release page.

Success means the official portable package extracts completely, launches normally, and can read and update its local data without repeated security alerts.

3.5 Separate configuration loading from destination failures

If your hotkeys and preferences appear but uploading no longer works, the portable profile probably loaded. Focus on the configured destination instead. A new computer or network may have different firewall, proxy, DNS, certificate, or authentication conditions. Credentials may also depend on files or environment variables that were not migrated.

Run a local screenshot test with uploading disabled. If local capture and saving work, re-enable the destination and inspect its error. Success at the local stage means you should stop modifying the portable configuration location and troubleshoot the upload destination or network separately.

4. Run a Clean Temporary Test With Minimal ShareX Settings

A clean test distinguishes damaged or incomplete portable data from a Windows-wide problem. Download a fresh portable package from an official ShareX source and extract it to a new, short, writable local path. Do not place it inside the old folder, a cloud-synced folder, a USB drive, a network share, or Program Files.

1. Exit every installed and portable ShareX process.
2. Extract the fresh portable archive into its own folder.
3. Launch the executable directly from that folder.
4. Change one harmless marker preference.
5. Create a local screenshot using a simple built-in workflow.
6. Exit ShareX fully and reopen it.
7. Confirm that the preference and new task information remain.

If the clean copy works, Windows can run ShareX and the failure is likely limited to the old folder, its configuration, its paths, or its permissions. Do not immediately copy every old file over the clean test because that can reproduce the problem without revealing its source.

Instead, make a backup and migrate the old portable data in controlled groups while ShareX is closed. Test after each group. Prioritize the configuration needed for hotkeys and workflows, then destinations, history, and optional supporting files. If one group causes the problem to return, restore the last working test folder and narrow the comparison further.

If the clean local copy also fails to retain a marker setting, inspect security controls, folder permissions, and logs before modifying the old portable data.

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

Task history is useful evidence, but missing history does not automatically mean that all settings failed to load. History may be stored separately from application preferences and can be omitted during a partial copy. It can also remain on the old drive while the main configuration is present in the new folder.

Compare the source and destination portable folders for history and log files or related data directories. Use modification times to identify which location the active copy is updating. Never edit configuration or history files while ShareX is running because the application may overwrite your changes when it exits.

When an operation fails, record the exact error text and the workflow stage that produced it. Useful distinctions include:

• The hotkey does nothing, which may indicate a hotkey conflict or inactive instance
• The capture opens but cannot save, which suggests an output-path or permission problem
• The file saves but cannot upload, which points toward destination, credentials, or networking
• The setting works until restart, which indicates a write or profile-location problem
• Everything appears new, which suggests the wrong executable or data location

Logs may reveal inaccessible paths, missing files, rejected uploads, or other concrete failures. Use them to choose the next test rather than changing several unrelated options at once. Success means you can repeat the original action without a new error and see the expected output in history or the target folder.

6. Back Up Before Repairing or Migrating

Before replacing, resetting, or selectively copying portable data, close ShareX and make a complete backup of the original portable folder. A full folder copy is safer than guessing which files contain important preferences.

Your backup should preserve:

• Application preferences and hotkey configuration
• Uploader and destination settings
• Custom workflows and task settings
• Task history and logs you want to retain
• Custom scripts, templates, tools, and supporting files
• Any portable-mode marker and original directory structure

Treat destination files as sensitive because they may contain authentication details or references to private services. Store the backup securely and do not upload it to a public troubleshooting forum.

After copying, keep the original backup unchanged until the new portable installation has survived several restarts and completed representative capture, recording, editing, upload, and automation tasks. That stable backup gives you a safe stopping point if later changes cause regressions.

7. Quick Fix Checklist

• Exit all ShareX processes before copying or editing portable data.
• Launch ShareX.exe directly from the portable folder, not a pinned shortcut.
• Confirm the complete portable folder was copied, not only the executable.
• Use a marker-setting test to verify that changes survive a restart.
• Compare source and destination files by name, size, date, and folder structure.
• Update absolute paths that still reference an old drive letter or user folder.
• Confirm the USB, network, or local folder allows creating and modifying files.
• Wait for cloud synchronization and make all portable files available offline.
• Run only the portable copy while testing to avoid profile and hotkey confusion.
• Unblock the official downloaded archive before extracting a fresh test copy.
• Test a clean portable package in a writable, nonsynchronized local folder.
• Back up the entire working or original portable folder before migration.

Stop changing settings as soon as the marker preference survives a restart and the original workflow succeeds. Additional changes after that point make it harder to identify which fix worked and can introduce new problems.

8. Frequently Asked Questions

8.1 Where do ShareX portable settings live?

In a genuine portable setup, ShareX keeps its user data with the portable application rather than depending on the normal installed profile location. The folder can include multiple configuration and data files, so migrate the complete portable directory. If you are uncertain which files are active, change one marker preference, exit ShareX, and inspect modified timestamps.

8.2 Why do my settings load but screenshots no longer save?

This usually means the configuration loaded but contains an absolute path that does not exist or cannot be written on the new computer. Check the screenshot folder, drive letter, user-folder name, network path, and permissions. A successful local save confirms that general settings loading is not the problem.

8.3 Can I run installed and portable ShareX at the same time?

It is not a useful troubleshooting setup. The copies can be confused visually, and they may compete for global hotkeys. Close every ShareX process and test only the portable executable. Once repaired, keep startup behavior clear so you know which copy handles shortcuts and workflows.

8.4 Is a cloud-synced folder safe for portable ShareX?

It can work, but live configuration files are vulnerable to incomplete downloads, file locks, sync conflicts, and simultaneous edits from multiple computers. Keep files available offline, allow synchronization to finish, and avoid running the same synchronized portable folder on two systems at once. A local unsynchronized copy is the best diagnostic test.

8.5 Will assigning the USB drive the old letter fix everything?

It can repair workflows that use absolute paths tied to that letter, but it will not fix missing files, read-only storage, wrong shortcuts, blocked downloads, or an incomplete portable copy. Confirm both the drive letter and the folder’s write access.

8.6 What should I back up before moving ShareX portable?

Back up the entire portable folder while ShareX is closed. This preserves preferences, hotkeys, destinations, history, logs, scripts, tools, and the directory structure that supports portable operation. Protect the backup because uploader configurations may contain sensitive information.