I am experimenting with the Registry: HKEY_CLASSES_ROOT.cc\PersistentHandler
by changing the Data to (value not set)
Why is there a debug file on my computer and how to I fix it
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
90 answers
Sort by: Most helpful
-
Anonymous
2020-10-23T14:05:50+00:00 -
Anonymous
2020-10-22T13:06:22+00:00 We saw the creation of this debug file when making a copy of an Excel file within a folder. The new file was created successfully.
Seems like there is no obvious pattern here related to user apps - Chrome, Edge, Chromium, programming tools all mentioned as potential sources. The only constant for all users may be Windows Explorer.
-
Anonymous
2020-10-20T08:07:03+00:00 Trois mois pour un bug ! ! Pour une fois que Microsoft fait appel à Google pour développer un navigateur super-efficace, nous pouvons dire que le succès est là! Lamentable ...
-
Anonymous
2020-10-20T07:47:26+00:00 Update: the Chromium bug tracker issue I filed earlier has been merged into another one, where this has actually been tracked since July. (I'm not clear on why it's just showing up for all of us in the latest build from 2 weeks ago.) They have a fix that they're testing now, so if that works I'd expect to see this fix itself as it rolls out to the browsers, but that could take a month or three (or even longer, for some). In the meantime, no one has suggested any other workarounds -- you're probably just going to keep getting the extra file.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 79%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGN%3C/text%3E%3C/svg%3E)
Günter Born 49,461 Reputation points2020-10-18T22:38:36+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)
The debug file is created for Chromium 68x based browsers randomly. There is now an issue entry in Google's bug tracker for Chromium. And maybe it helps to delete the content of the folder Crashpad.
Chromium 68 browsers (Chrome, Edge etc.) create debug.log files