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

90 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-10-16T01:56:07+00:00

    debug.log popped again.  I tried using rm .\debug.log in pwsh but it was being used by another process.  When I closed Google Chrome I was able to run rm .\debug.log and it removed the file.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-10-16T02:13:30+00:00

    Dave,

    I am having the same problem.  It started after the latest Windows update.  Along with the debug file, my command prompt window opens occasionally without me prompting it.

    Please escalate up the food chain and provide a patch or uninstall until the error is fixed.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-16T08:03:32+00:00

    Following as have had the same issue for the last couple of days.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-16T08:11:37+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)

    same happened to me, the issue is with the Microsoft edge browser.   this is usually happen when you open pdf using edge browser.   use another application to open pdf files.

    google chrome doesn't need to uninstalled.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-10-16T10:08:46+00:00

    Everybody prodding Microsoft about this, please read the last couple pages.  This is almost certainly an issue with **Chromium**, the open source engine that powers Chrome (and the new Edge, and Opera, and Brave, and...) and therefore not something that Microsoft can fix themselves.

    I filed this bug on the Chromium tracker. If you want to get this fixed, go star it, which should help it get more attention from the Chromium team.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments