FileNotFoundException Java Origin: Application & API Last updated 13 Oct 2026

java.io.FileNotFoundException: config.properties (No such file or directory)

Java couldn’t open the file — wrong path relative to the working directory, missing file, or a classpath resource read as a file.

Exact message you may see (No such file or directory)(The system cannot find the file specified)
Seen on: Java

Meaning

Relative paths resolve from the JVM working directory. Files inside a JAR aren’t files at all; read them with getResourceAsStream.

Common causes

  • Relative path + different working directory
  • Resource inside a JAR opened with new File()
  • Missing file in deployment
  • Permission denied (message says so)

⚡ Quick fix

  1. Load classpath resources with getClass().getResourceAsStream("/config.properties")
  2. Use absolute or configurable paths
  3. Check System.getProperty("user.dir")

Detailed fix by platform

Java

  1. try (InputStream in = App.class.getResourceAsStream("/config.properties")) { props.load(in); }

How to diagnose

  1. Path — Exact path
  2. CWD — user.dir
  3. Packaging — Inside a JAR?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Application & API. Errors that are often confused with or caused by this one (click to open):

0x80070020 — 0x80070020: The process cannot access the file because it is being used by another process (Windows)0x800700200x80070570 — Error 0x80070570: The file or directory is corrupted and unreadable (Windows)0x80070570Access to the path is denied — System.UnauthorizedAccessException: Access to the path 'x' is denied (.NET)Access to the path is…AccessDeniedException — java.nio.file.AccessDeniedException: /path (Java)AccessDeniedExceptionArgument list too long — bash: /bin/rm: Argument list too long (Linux)Argument list too longEEXIST — Error: EEXIST: file already exists, mkdir (Node.js)EEXISTEISDIR — Error: EISDIR: illegal operation on a directory, read (Node.js)EISDIRENOENT — Error: ENOENT: no such file or directory (Node.js)ENOENTFileNotFo…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.