lucasg/Dependencies · warning

{0:s} is not present on the disk

Error message

{0:s} is not present on the disk

What it means

Shown by DependencyWindow.InitializeView (DependenciesGui/DependencyWindow.xaml.cs:552) when NativeFile.Exists(this.Filename) is false for the PE passed to the window constructor. A modal MessageBox ('Invalid PE') is shown and InitializeView returns before any analysis runs.

Source

Thrown at DependenciesGui/DependencyWindow.xaml.cs:552

			if (CustomSearchFolders != null)
			{
				this.CustomSearchFolders = CustomSearchFolders;
			}
			else
			{
				this.CustomSearchFolders = new List<string>();
			}
			
			this.Filename = Filename;
			this.WorkingDirectory = Path.GetDirectoryName(this.Filename);
			InitializeView();
        }

        public void InitializeView()
        {
            if (!NativeFile.Exists(this.Filename))
            {
                MessageBox.Show(
                    String.Format("{0:s} is not present on the disk", this.Filename),
                    "Invalid PE",
                    MessageBoxButton.OK
                );

                return;
            }

            this.Pe = (Application.Current as App).LoadBinary(this.Filename);
			if (this.Pe == null || !this.Pe.LoadSuccessful)
			{
                MessageBox.Show(
                    String.Format("{0:s} is not a valid PE-COFF file", this.Filename),
                    "Invalid PE",
                    MessageBoxButton.OK
                );

                return;

View on GitHub (pinned to 1997a40000)

Solutions

1. Confirm the file still exists at the given path before opening.
2. Remove the stale recent-files entry that produced the bad path.
3. Re-drop or re-open the file from its current location.

// Validate before constructing/opening the DependencyWindow.
if (!NativeFile.Exists(filename))
{
    MessageBox.Show($"{filename} is not present on the disk", "Invalid PE", MessageBoxButton.OK);
    return;
}

When it happens

Trigger: Constructing a DependencyWindow with a path that does not exist or is a directory (NativeFile.Exists rejects directories too); drag-drop of a moved file; command-line arg pointing at a gone path.

Common situations: File deleted between selection and window creation; recent-files entry pointing at a removed path; relative path resolved against an unexpected working directory.

Related errors

• Loading PE file "{0:s}" failed : file not present on disk.
• {0:s} file could not be found !
• {0:s} is not a valid PE-COFF file
• We could not find {0:s} file on the disk anymore, please fix
• peview.exe file could not be found !

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