fs.existsSync returns wrong value on windows if there are no permissions on the given file #17921

Activity

1. vsemozhetbyt

   added

   fsIssues and PRs related to file-system APIs and the fs module.Issues and PRs related to file-system APIs and the fs module.

   windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.

   on Dec 30, 2017
2. jaulz commented on Jan 17, 2018

   

   jaulz

   on Jan 17, 2018

   Last edited by jaulz

   More actions

   I have a similar issue where existsSync returns true though the file does not exist. Happens on Windows 10 with NodeJS v8.9.1.

   👍React with 👍11Reacted by Galaktikos, Gábor Kriskó, A, 1vomarek1, Michael Sorensen, Mark Hansen, jorugit, Taehyun Hwang, claudiogg88, IonDev and 1 more

   👎React with 👎1Reacted by John Savadkuhi
3. Johnsavadkuhi commented on Jan 17, 2018

   

   Johnsavadkuhi

   on Jan 17, 2018

   Contributor

   More actions

   let me to see your code

   👎React with 👎3Reacted by Galaktikos, Amine Abdelli and Michal Jarnot
4. bnoordhuis

   added

   docIssues and PRs related to Node.js documentation.Issues and PRs related to Node.js documentation.

   on Jan 17, 2018
5. bnoordhuis commented on Jan 17, 2018

   

   bnoordhuis

   on Jan 17, 2018

   Member

   More actions

   Perhaps the documentation could be improved (I'll add the label) but fs.exists() works the same way as fs.stat() in this regard: it queries the operating system for file metadata for the specified path and passes on the error that the operating system returns.

   The difference is that fs.stat() would have returned an error whereas fs.exists() returns false because true or false is the only thing it's allowed to return.

   You might get better results with fs.access(), depending on the situation.
6. jaulz commented on Jan 17, 2018

   

   jaulz

   on Jan 17, 2018

   More actions

   Following the code I use:

   console.log('bin')
   console.log(bin)
   console.log('fs.existsSync(bin)')
   console.log(fs.existsSync(bin))
   try {
     console.log('fs.accessSync(bin)')
     console.log(fs.accessSync(bin))
   } catch (error) {
     console.log('-')
   }
   while (true) { }

   This is the output:

   bin
   C:\Users\XXX\.appcelerator\install\7.0.1\package\bin\appc
   fs.existsSync(bin)
   true
   fs.accessSync(bin)
   undefined
   

   I put a while(true) {} to stop at that very stage but if I run >cd C:\Users\XXX\.appcelerator in parallel the output is: The system cannot find the path specified.

   Any idea?

   👍React with 👍1Reacted by Marat Ahmetzyanov
7. bnoordhuis commented on Jan 17, 2018

   

   bnoordhuis

   on Jan 17, 2018

   Member

   More actions

   @jaulz That's probably some ACL or permissions issue. The directory is there, it's just inaccessible.
8. jaulz commented on Jan 18, 2018

   

   jaulz

   on Jan 18, 2018

   More actions

   @bnoordhuis not sure... I cannot even find that folder via command nor via explorer.
9. 6-8-axnw1bom81v5xa3nh48c commented on Jan 20, 2018

   

   6-8-axnw1bom81v5xa3nh48c

   on Jan 20, 2018

   Last edited by 6-8-axnw1bom81v5xa3nh48c

   More actions

   I am the reporter of this issue, but I accidentally deleted my account.

   @bnoordhuis So, this actually works as intended? Ok, then it would be a good idea to mention it somewhere in the doc. Or, even better, change the behavior of fs.existsSync to try to read parent dir in case of error and if the file is located in the parent dir, then return true, no matter if the actual file is accessible or not.

   @Johnsavadkuhi What does your thumbs down mean: you cannot reproduce the issue, or you disagree that this issue should be considered as a bug? "Let me to see your code" - my code or @jaulz's code?
10. bzoz commented on Feb 1, 2018

    

    bzoz

    on Feb 1, 2018

    Contributor

    More actions

    In this case existsSync call to stat fails with EPERM, maybe we could make existsSync return false when the error is ENOENT? Or, is there a reason why existsSync does not use accessSync?
11. bnoordhuis commented on Feb 1, 2018

    

    bnoordhuis

    on Feb 1, 2018

    Member

    More actions

    In this case existsSync call to stat fails with EPERM, maybe we could make existsSync return false when the error is ENOENT?

    fs.existsSync() always returns false when the stat fails.

    Or, is there a reason why existsSync does not use accessSync?

    Yes, see #4679 - Windows CI issue.
12. bzoz

    closed this as completedin d3955d1on Feb 22, 2018
13. bzoz

    added a commit that references this issue on Mar 28, 2018

    fs: use fs.access in fs.exists

    ...

    2a0b198
14. targos

    added 2 commits that reference this issue on Apr 4, 2018

    fs: use fs.access in fs.exists

    ...

    92fb0e4

    fs: use fs.access in fs.exists

    ...

    5e90fc6
15. MayaLekova

    added a commit that references this issue on May 8, 2018

    fs: use fs.access in fs.exists

    ...

    89dc53d
16. cawoodm commented on Mar 27, 2019

    

    cawoodm

    on Mar 27, 2019

    More actions

    I'm using NodeJS v11.10.0 on Windows 10 and having the same issue: existsSync says a file does not exist but it does and I do have permissions on it. What to do?

    👍React with 👍2Reacted by Glen Thomas and Surya
17. BridgeAR commented on Mar 27, 2019

    

    BridgeAR

    on Mar 27, 2019

    Member

    More actions

    @cawoodm you probably want to either use fs.accessSync or you directly want to call fs.open as recommended in the documentation.

    There is no guarantee that the file does not exist if fs.existsSync returns false. It only let's you know if the file is there and is accessible for you. There could be multiple reasons for the cause in case it returns false.
18. cawoodm commented on Mar 30, 2019

    

    cawoodm

    on Mar 30, 2019

    More actions

    Oops, I think my problem was with backslashes in the path C:\temp being interpreted as tabs. Sorry for jostling!
19. ohuu commented on May 4, 2020

    

    ohuu

    on May 4, 2020

    Last edited by ohuu

    More actions

    Sorry to comment on a closed issue but I'm seeing the same thing.

    OS: Windows 10
    Node version: 13.12.0

    The file in question is java installed via scoop C:\Users\Oliver\scoop\apps\openjdk11\current\bin\java. It has permissions and definitely exists but existsSync returns false!

    Calling accessSync returns this error:

    Error: ENOENT: no such file or directory, access 'C:/Users/Oliver/scoop/apps/openjdk11/current/bin/java'
        at Object.accessSync (fs.js:208:3) {
      errno: -4058,
      syscall: 'access',
      code: 'ENOENT',
      path: 'C:/Users/Oliver/scoop/apps/openjdk11/current/bin/java'
    }
    

    calling open returns undefined.
20. ohuu commented on May 7, 2020

    

    ohuu

    on May 7, 2020

    Last edited by ohuu

    More actions

    Finally got to the bottom of this. Windows has to have the extension of the file in order to check that it exists so fs.existsSync('C:/Users/Oliver/scoop/apps/openjdk11/current/bin/java.exe') works but fs.existsSync('C:/Users/Oliver/scoop/apps/openjdk11/current/bin/java') doesn't

    👍React with 👍1Reacted by Justin M. Keyes

    👎React with 👎5Reacted by solartes, Guillermo Cortés, SuppliedOrange, IonDev and Ricardo Romero

    🎉React with 🎉1Reacted by Andrew
21. badrelmers commented on Mar 23, 2022

    

    badrelmers

    on Mar 23, 2022

    More actions

    this is really a stupid language

    🚀React with 🚀10Reacted by Colin Ihrig, wishty, selene466, Jens A. Koch, Axel H., Matthieu VANCAYZEELE, black-ray, lechuhuuha, Ricardo Romero and Bohdan
22. sjarmak

    added a commit that references this issue on Jul 27, 2026

    fs: use fs.access in fs.exists

    ...

    d3955d1