Why is there a debug file on my computer and how to I fix it

Anonymous
2020-10-10T06:50:09+00:00

In the debug file it says [1010/132558.157:ERROR:directory_reader_win.cc(43)] FindFirstFile: The system cannot find the path specified. (0x3)

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

90 answers

Sort by: Newest
  1. Anonymous
    2020-10-15T13:01:51+00:00

    I also noticed the same file "notepad"  ya'll talking about  with the same name "debug" and the same thing written inside "FindFirstFile: The system cannot find the path specified. (0x3)"

    appearing on my desktop several times now .. I use opera gx as my main browser not chrome so I don't think it has something to do with the type of browser you use

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-10-15T12:46:14+00:00

    디버그 파일에서 [1010/132558.157:error:directory_reader_win.cc(43)] FindFirstFile: 시스템이 지정된 경로를 찾을 수 없습니다. (0x3)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-10-15T11:58:10+00:00

    j'ai le même problème avec chrome vscode , npm, node et browsersyncro .

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-10-15T11:20:49+00:00

    I recently started running Karma unit tests, from VSCode, which drive a Chrome browser.  As far as I'm aware, I never had this problem before I started doing these tests.  It could be related to the arguments used by Karma's Chrome driver?  The debug.log file appears in the root of the project workspace where I'm running my tests.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Sumit 44,316 Reputation points Volunteer Moderator
    2020-10-15T09:19:46+00:00

    I actually saw a case where OP said the issue started appearing after installing VS Code, hence was asking. Thank you - let me see we can find what is generating the same.

    Was this answer helpful?

    0 comments No comments