lucasg/Dependencies · warning

{0:s} file could not be found !

Error message

{0:s} file could not be found !

What it means

Shown by ModuleTreeViewItem.OpenPeviewer (DependenciesGui/DependencyWindow.xaml.cs:458) when File.Exists(programPath) is false, where programPath = Dependencies.Properties.Settings.Default.PeViewerPath. The external peview.exe (bundled from ProcessHacker) is required to open a module in the PE viewer, so if that configured path is missing the action is aborted with a MessageBox and OpenPeviewer returns false.

Source

Thrown at DependenciesGui/DependencyWindow.xaml.cs:458

                }

                return _OpenPeviewerCommand;
            }
        }

        public bool OpenPeviewer(object Context)
        {
            string programPath = Dependencies.Properties.Settings.Default.PeViewerPath;
            Process PeviewerProcess = new Process();

            if (Context == null)
            {
                return false;
            }

            if (!File.Exists(programPath))
            {
                System.Windows.MessageBox.Show(String.Format("{0:s} file could not be found !", programPath));
                return false;
            }

            string Filepath = ModuleFilePath;
            if (Filepath == null)
            {
                return false;
            }

            PeviewerProcess.StartInfo.FileName = String.Format("\"{0:s}\"", programPath);
            PeviewerProcess.StartInfo.Arguments = String.Format("\"{0:s}\"", Filepath); 
            return PeviewerProcess.Start();
        }

        public RelayCommand OpenNewAppCommand
        {
            get
            {

View on GitHub (pinned to 1997a40000)

Solutions

1. In Options->Properties set PeViewerPath to a valid peview.exe (or install the full release bundle that includes it).
2. Restore peview.exe from quarantine if your AV removed it, or add an exclusion.
3. If you intentionally use the peview-less build, disable/hide the 'open in peview' command.

string programPath = Dependencies.Properties.Settings.Default.PeViewerPath;
if (!File.Exists(programPath))
{
    System.Windows.MessageBox.Show($"{programPath} file could not be found !");
    return false;
}
// safe to launch peview

When it happens

Trigger: User clicks the 'open in peview' command on a tree node but PeViewerPath points at a file that does not exist (default install moved, peview deleted, or the AV-safe build without peview.exe is in use).

Common situations: Running the `Dependencies_x64_Release_.without.peview.exe` package; PeViewerPath reset to empty after a portable-app relocation; antivirus quarantining peview.exe (the README notes peview can trigger AV).

Related errors

• peview.exe file could not be found !
• Loading PE file "{0:s}" failed : file not present on disk.
• {0:s} is not present on the disk
• We could not find {0:s} file on the disk anymore, please fix
• [x] Could not find file {0:s} on disk

AI-assisted analysis of lucasg/Dependencies@1997a40000 (2026-08-13). Data as JSON: /api/errors/184e5b0f6939af36. Report an issue: GitHub.