[Resolved] Access violation in module FileVoyager.exe

Home Forums Issues and bugs reports [Resolved] Access violation in module FileVoyager.exe

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
  • #4783

    I installed the latest update today and when I restarted FileVoyager, I got this:

    EAccessViolation in module FileVoyager.exe at 974C


    Hi alexpc,

    Could you uninstall FileVoyager and reinstall it clean ?

    Also, can you tell me what Windows version you’re using ?

    Thank youin advance


    I have uninstalled and reinstalled it. I am running Windows Version 10.0.19045 Build 19045


    So your Windows version is very decent 👍
    And do you still experience the Access Violation?

    if yes

    • close FileVoyager if it’s running
    • in File Explorer, type %LOCALAPPDATA% in the path bar (keep the percent characters)
    • you should land in the AppData\Local folder
    • spot the FileVoyager folder and rename it to, let’s say, FileVoyager.bak
    • restart FileVoyager and see if the Access Violation occurs again

    if not, it means that something in FV’s app data is corrupted

    let me know what is the result


    Note that, by doing the above, you’ll restart FV without you personalisation.
    wéll see together how to recover most of your settings.


    Interesting. I followed your instructions, but there was no entry in AppData\Local folder, so I couldn’t rename it. I started FileVoyager and this time there was no access violation. (I guess this may not be good news, because the problem is not repeatable. I’ll let you know if the problem re-occurs and follow those steps if it does.)


    And I suppose you have recovered all your settings, because I gave you the wrong environement variable.
    FV settings are actually stored in %APPDATA%, not %LOCALAPPDATA%.

    Fortunately, this error worked in your favor: your settings were preserved, and the Access Violation issue has been resolved. 😉

    I will mark this topic as [RESOLVED]. However, please don’t hesitate to create a new topic or post here again if the issue reoccurs.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.

Comments are closed.