Access Violation message

/Access Violation message

Access Violation message

After launch an “Access Violation” message with a fearful warning appears. Can be ignored without any visible effect.

Windows 7 x64 administrative user.

By |2017-12-19T12:08:25+00:00December 1st, 2017|3 Comments

About the Author:


  1. Homer Slated 24/01/2019 at 18:52 - Reply

    Same here.

    Steps to reproduce:
    Download Quick Hash from
    Extract using 7zip
    Navigate to Quickhash-Windows-Notsigned-v3.0.4\64-Bit
    Double click on QuickHash-Windows-v3.0.4-x64.exe


    System: Win10 Pro 64-bit, Version 1809 OS Build 17763.253

    The 32-bit version exhibits the same behaviour.

    Version 3.0.2 exhibits the same behaviour (64 and 32 bit).

    Version 2.8.4 does not exhibit this behaviour.

    I don’t have Windows debugging tools to provide further information.


    • Ted 24/01/2019 at 19:26 - Reply

      do you have the SQLite DLL files in the same location as the executable? The message is most likely due to the inability of Quickhash to either use the SQLite files (as they were added with v3.0.0) or it cannot write some temporary files to your systems default temp directory. Either it does not know your system default directory for temp data or it cannot write to them. So it can’t generate the files, so it can’t access them, thus the violation error. I suspect anyway.

  2. Ted 01/12/2017 at 18:06 - Reply

    When you say “after launch” do you mean before QuickHash has appeared or has it appeared and then the message is displayed? What button triggers the message and can you provide a screenshot?

    Also, what operating system are you using? Windows, Linux or OSX? QH creates a small XML file in the home profile of the user and the way it does this differs per operating system, so this may be the issue.

    I need more specifics, and ideally a screenshot to help debug the problem.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.