- Many users noticed recently a debug.log file on their desktops containing error keywords.
- This type of file is generated every once in a while and is a bug that can be removed.
- Whenever you're in doubt about certain software errors, you'll surely find the right answers in our Troubleshooting Hub.
- Visit our large collection of articles on Browsers, to find everything there's to know on this topic.
With certain updates, Chromium-based browsers such as Chrome, Edge, Opera, Vivaldi randomly generate a debug.log file that lands on the users’ desktops, generating confusion.
The same happened last week, with the latest Google Chrome update. Shortly afterward, questions started to pop up on forums asking for clarifications regarding a debug Notepad file containing some errors codes and the following text:
FindFirstFile: The system cannot find the path specified. (0x3)
As noticed by many, they could delete the file, but it would reappear on their desktop each time their device connected to the Internet or each time they opened certain files or apps in their browsers.
What is the debug.log file and is it harmful?
The file is generated by Chromium 68x based browsers (as mentioned above) and it doesn’t point out toward a system issue.
Initially, it was advised on Microsoft’s forums to delete the file, as it didn’t pose any security threat.
Actually, upon a system scan with a third-party antivirus, no malware can be found (at least not one related to the file in question).
However, the file would be re-generated on the desktop, only containing another error code.
How do I get rid of the debug file?
It seems there is only one fix for these situations, as suggested by a moderator of the Microsoft community.
Namely, users noticing the file have to delete a Crashpad folder contained in their browser folder.
- Open File Explorer.
- In the search bar, paste the following: %LocalAppData%\Google\Chrome\User Data
- Note: Replace Chrome with the browser generating the debug.log file.
- You should see a Crashpad folder that you have to delete.
Many users mentioned that this solution helped them.
On the other hand, the developers team at Chromium has taken notice of the issue and opened a bug tracker and they are likely to release a fix soon..
We hope that the trick mentioned above helped to get rid of the debug.log file. Your feedback is welcome – use the comments sections below.