Troubleshooting Reset

Recover from bad settings, profile problems, or stale local data.

Use this page when the app has a mysterious startup problem, crash, or strange behavior that reinstalling did not fix.

Assume the problem may happen very early while the app is loading app settings, the selected profile, or image cache state. In that situation, the app may close before you can open Settings, Cache, Profiles, Log, or Help inside the app.

Reinstalling replaces the app files. It does not necessarily remove user data stored under your Windows AppData folders. A bad app setting, profile file, or stale image cache can therefore survive a reinstall and affect the next run.

Try these steps in order. Stop when the app starts and behaves normally again.

Before you reset anything

  1. Close the app.
  2. Keep captured images and staged originals. The steps below should not require deleting image files.
  3. Keep log files unless support asks you to remove them. Logs may explain what happened before the reset.
  4. Do not rely on in-app pages being available. Use the Windows paths below when the app crashes during startup.
  5. If you can still open the app later, use the Log page to copy recent error entries for support.

You can open the main user-data folders even when the app cannot start:

  1. Press Windows+R.
  2. Enter %APPDATA%\[app name].
  3. Open the folder for the app version you are troubleshooting. If you are not sure, open the newest version folder.

The version folder contains app-wide settings and profiles. For example, a version folder may look like %APPDATA%\[app name]\6.0.8.0.

The default unpackaged image cache is under %LOCALAPPDATA%\[app name]\[version]\T. If you moved the cache to a custom location, use that custom folder instead.

Step 1: Reset app settings

Use this first when the app does not start normally or the window, layout, navigation, licensing, logging, or recent-setting state seems broken.

The startup keyboard reset is the fastest settings reset:

  1. Close the app.
  2. Start the app again while holding Left Ctrl and Left Shift.
  3. Keep both keys held during startup.

The app deletes this version's Settings.json file and rebuilds app-wide settings from defaults.

This reset does not delete saved profile files, image cache files, captured images, staged originals, installation files, or log files.

Because license keys may be stored with app settings, you may need to register the app again after this reset.

If the app still crashes during startup, or if you are not sure the keyboard reset was detected, remove the settings file manually:

  1. Close the app.
  2. Press Windows+R.
  3. Enter %APPDATA%\[app name].
  4. Open the current version folder.
  5. Open the Settings folder.
  6. Move Settings.json to a temporary backup folder, or rename it to Settings-disabled.json.
  7. Start the app again.

Step 2: Move profile files out of the way

Use this after resetting settings when the app still crashes during startup, crashes while applying profile-backed settings, or support suspects a profile problem.

Only move, rename, or delete profile files while the app is not running. Profile files are app state, and changing them while the app is open can lose changes or leave the running app with stale profile data.

The direct profile path is %APPDATA%\[app name]\[version]\Profiles.

Use the direct path first when the app cannot open:

  1. Close the app.
  2. Press Windows+R.
  3. Enter %APPDATA%\[app name].
  4. Open the current version folder.
  5. Move the Profiles folder to a temporary backup folder, or rename it to Profiles-disabled.
  6. Start the app again.

If the app opens later, you can also use the built-in folder button to find the folder:

  1. Go to Settings > System.
  2. In Settings and Profiles, press Explore.
  3. Close the app before changing any profile files.
  4. Open the Profiles folder.
  5. Move the .prf files to a temporary backup folder, or rename the Profiles folder to Profiles-disabled.
  6. Start the app again.

Moving or renaming profile files is safer than deleting them. Support may ask to inspect a profile file later.

When no profile files are available, the app creates a new Default profile.

Step 3: Reset the image cache

Use this after settings and profiles have been ruled out, especially if the app crashes while initializing the Image Browser or if thumbnails, previews, metadata, or image-browser behavior look wrong.

The default unpackaged cache path is %LOCALAPPDATA%\[app name]\[version]\T.

Use the direct path first when the app cannot open:

  1. Close the app.
  2. Press Windows+R.
  3. Enter %LOCALAPPDATA%\[app name].
  4. Open the current version folder.
  5. Move the T folder to a temporary backup folder, or rename it to T-disabled.
  6. Start the app again.

If you previously moved the cache to a custom location, remove or rename that custom cache folder instead. If you do not remember the custom cache location, reset Settings.json first so the app returns to the default cache path.

If the app opens later, you can also use the built-in cache reset:

  1. Go to Settings > Cache.
  2. Press Reset.
  3. Let the app rebuild cache files the next time folders are opened in the Image Browser.

The image cache contains generated thumbnails, previews, metadata, and histogram data. It does not contain your source images.

Step 4: Reinstall only after local data is checked

Reinstalling can help when installation files are missing or damaged.

If reinstalling did not help, focus on app settings, profiles, cache data, and logs. Those are the files most likely to survive a normal reinstall and continue affecting the next run.

What not to delete

Do not delete captured images, staged originals, log files, or installation folders unless support specifically asks for that.

If you are unsure which folder is which, rename the folder instead of deleting it. Renaming keeps a backup while letting the app create fresh data.