Autopsy User Documentation  4.18.0
Graphical digital forensics platform for The Sleuth Kit and other tools.

Table of Contents

If you are experiencing an error, we encourage you to post on the forum (, including as much information as possible:

Specific Issues

Font Size Too Small in Windows

Make the following changes if the application is hard to navigate in High DPI systems:

  1. Right-click on the application icon on your Desktop, Start Menu, etc.
  2. Choose Properties.
  3. Go to Compatibility tab.
  4. Click "Change high DPI settings" button.
  5. Select "Override high DPI scaling behavior".
  6. Change the "Scaling performed by:" drop down box to "System".
  7. Restart Autopsy.

General Troubleshooting

Deleting the Autopsy User Folder

If Autopsy starts behaving strangely, stops loading entirely, or menu items go missing, you probably need to delete your user folder. Doing so essenitally gives you a fresh installation. On Windows the user folder is located in "C:\Users\(user name)\AppData\Roaming\autopsy".

Note that if you delete this folder you will lose all your Autopsy settings including keyword lists, interesting file sets, and general configuration. If you have settings you want to keep you can try the following:

Alternately, you could copy the fresh user folder somewhere, move your old version back, and replace folders until it works again.

Viewing the Logs

The logs are generally the most helpful in figuring out why an error is occurring. There are two sets of logs - the system logs and the case logs. There is an option in the UI to open the log folder:


If you have a case open, clicking this will open the folder containing the case logs. If not, it will open the system log folder. You can also browse to these folders normally:

In either case, the log of interest is most likely "autopsy.log.0", although it could be one of the older versions if you've closed and reopened Autopsy since the error occurred. You're looking for entries starting with "SEVERE" and possibly "WARNING" if there are no severe errors. Note that it's not unusual to have many warnings in the log. This is an example of a severe error with a stack trace:

Sep 23, 2020 9:48:24 AM saveToCase
SEVERE: Error saving tag name definition
org.sleuthkit.datamodel.TskCoreException: Error adding row for Follow Up tag name to tag_names table
        at org.sleuthkit.datamodel.SleuthkitCase.addOrUpdateTagName(
        at org.sleuthkit.autopsy.casemodule.Case.openCaseLevelServices(
        at org.sleuthkit.autopsy.casemodule.Case.lambda$doOpenCaseAction$6(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$
Caused by: java.sql.SQLException: ResultSet closed
        at org.sqlite.core.CoreResultSet.checkOpen(
        at org.sqlite.jdbc3.JDBC3ResultSet.findColumn(
        at org.sqlite.jdbc3.JDBC3ResultSet.getLong(
        at com.mchange.v2.c3p0.impl.NewProxyResultSet.getLong(
        at org.sleuthkit.datamodel.SleuthkitCase.addOrUpdateTagName(
        ... 10 more

If the error message doesn't help you solve the problem yourself, please post to the forum including the full stack trace (if available).

Creating a Thread Dump

You can also generate a thread dump of the current state. This is useful if an ingest module or other process seems to be stuck. To generate a thread dump, go to "Help" then "Thread Dump" in the UI.


You'll then see a file similar to this in a text viewer:

"Module-Actions" Id=222 RUNNABLE
        at Method)
        at org.sleuthkit.autopsy.actions.ThreadDumpAction$ThreadDumper.createThreadDump(
        at org.sleuthkit.autopsy.actions.ThreadDumpAction$ThreadDumper.doInBackground(
        at org.sleuthkit.autopsy.actions.ThreadDumpAction$ThreadDumper.doInBackground(
        at javax.swing.SwingWorker$

"IM-start-ingest-jobs-0" Id=218 WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7ceb341e
        at sun.misc.Unsafe.park(Native Method)
        -  waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@7ceb341e
        at java.util.concurrent.locks.LockSupport.park(
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(
        at java.util.concurrent.LinkedBlockingQueue.take(
        at java.util.concurrent.ThreadPoolExecutor.getTask(
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

If the thread dump says anything about a deadlock then that's the problem. Please make sure to post any deadlocks to the forum. Even if not the thread dump could help diagnose your problem so consider including in your post.

Copyright © 2012-2021 Basis Technology. Generated on Sat Feb 27 2021
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License.