Path assumptions to test
- Relative paths resolved against an unexpected working directory.
- Hard-coded drive letters or user-profile folders.
- Mapped drives absent for services, elevated users or new sessions.
- UNC shares unavailable because of name resolution, credentials or network state.
- Installer-created directories not reproduced on the new PC.
- Permissions presenting as an unavailable path in the application.
Resolve without hiding the dependency
Trace the full requested path, test access in the same user/elevation context and identify where the assumption originates. Prefer configurable stable paths or UNC names over undocumented mappings; create required local directories through deployment.
If the directory exists but a specific file does not, use error 53 diagnosis. For initialization failures that later surface as an object error see error 91. Modern deployment context is covered by VB6 on Windows 11 and the pillar.
Provide the full path, user context, launch method, mapping/share details and working-machine configuration.