lucasg/Dependencies · warning
Loading PE file "{0:s}" failed : file not present on disk.
Error message
Loading PE file "{0:s}" failed : file not present on disk. What it means
Status message set by App.LoadBinary (DependenciesGui/App.xaml.cs:55) when NativeFile.Exists(path) is false. LoadBinary sets StatusBarMessage (which propagates to the status bar via App_PropertyChanged) and returns null. This is the GUI analogue of error 8 and is non-modal: no dialog, just the status bar.
Source
Thrown at DependenciesGui/App.xaml.cs:55
{
PropertyChanged?.Invoke(this, new PropertyChangedEventArgs(propertyName));
}
private void App_PropertyChanged(object sender, PropertyChangedEventArgs e)
{
if (e.PropertyName == "StatusBarMessage")
{
mainWindow.AppStatusBarMessage.Content = (object)StatusBarMessage;
}
}
public PE LoadBinary(string path)
{
StatusBarMessage = String.Format("Loading module {0:s} ...", path);
if (!NativeFile.Exists(path))
{
StatusBarMessage = String.Format("Loading PE file \"{0:s}\" failed : file not present on disk.", path);
return null;
}
PE pe = BinaryCache.LoadPe(path);
if (pe == null || !pe.LoadSuccessful)
{
StatusBarMessage = String.Format("Loading module {0:s} failed.", path);
}
else
{
StatusBarMessage = String.Format("Loading PE file \"{0:s}\" successful.", pe.Filepath);
}
return pe;
}
void App_Startup(object sender, StartupEventArgs e)
{View on GitHub (pinned to 1997a40000)
Solutions
- Check the status bar message and confirm the path still exists on disk.
- Re-add the file via File->Open after restoring/moving it back.
- Clear stale entries from the recent-files list if the path is permanently gone.
Defensive patterns
Strategy: validation
Validate before calling
// Pre-check existence before calling App.LoadBinary to control the failure mode.
public PE SafeLoadBinary(string path)
{
if (!NativeFile.Exists(path))
{
StatusBarMessage = $"Loading PE file \"{path}\" failed : file not present on disk.";
return null;
}
return (Application.Current as App).LoadBinary(path);
} Prevention
- NativeFile.Exists is preferable to File.Exists here because it disables WOW64 FS redirection and rejects directories.
- Null-check the return of LoadBinary at every call site (it returns null on missing files).
When it happens
Trigger: Opening a PE in DependenciesGui whose path does not exist or is a directory, via drag-drop, command-line arg, or recent-files list.
Common situations: A file was moved/deleted since it was added to recents; drag-dropping a shortcut whose target is gone; UNC path not reachable; typo in a typed path.
Related errors
- Loading module {0:s} failed.
- {0:s} file could not be found !
- {0:s} is not present on the disk
- 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/4eee3f1035667fa3.
Report an issue: GitHub.